1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #5041 resolved

Can't visit my repository page alfredchen/linux-gc (BB-6329)

Alfred Chen
created an issue

It seems like 500 error with the following tips said

This might be useful in debugging the problem:

ff42c331d0844ae298cdb1b55d6bb07b$3115d3c3064c6769c8e8f7b96f0ee46f

when visit my repository @

https://bitbucket.org/alfredchen/linux-gc

Comments (9)

  1. Erik van Zijst staff

    Ok, I had a look at the issue it seems that Bitbucket is unable to read your tag refs/tags/v2.6.16.31-rc1.

    This ref is an annotated tag and looks like:

    $ git cat-file tag 20c93a0fba73095196eeaa1e57a1f774518b55ff
    object afaa018cefb6af63befef1df7d8febaae904434f
    type commit
    tag v2.6.16.31-rc1
    tagger Adrian Bunk <bunk@stusta.de> 1162716505 +0100
    

    This causing our git library to fail, claiming that this is a malformed tag object, because it doesn't contain the message section.

    It's worth noting that Git itself seems to have no trouble reading the tag:

    $ git show --oneline 20c93a0fba73095196eeaa1e57a1f774518b55ff
    tag v2.6.16.31-rc1
    afaa018 Linux 2.6.16.31-rc1
    diff --git a/Makefile b/Makefile
    index 6957e4c..2b983d5 100644
    --- a/Makefile
    +++ b/Makefile
    @@ -1,7 +1,7 @@
     VERSION = 2
     PATCHLEVEL = 6
     SUBLEVEL = 16
    -EXTRAVERSION = .30
    +EXTRAVERSION = .31-rc1
     NAME=Stable Penguin
    
     # *DOCUMENTATION*
    

    According to the git-mktag man page, the description section is indeed optional and so it seems that you have uncovered a bug in our Git library!

  2. Erik van Zijst staff

    While we work to get this fixed, you should be able to simply just delete that tag from your Bitbucket repo (you can keep it locally so that you can push it back up once we get this fixed).

    Also not that this bug should only affect the website and so I expect you to still be able to push and pull.

  3. Alfred Chen reporter

    Thanks for the quick reply.

    Yes, it seems like that it only affect the website, my local copy seems ok with push and pull. I mainly just the git itself for the work, so I am fine with it. I think I will wait for the next sync with upstream (next week) to test the push/pull again.

    Hoping that this issue can be fixed then the website can be shown off.

  4. Log in to comment