#2850 Repo browser incorrectly displays repo as empty, mount point criteria should be relaxed, git configs should be migrated

fixed
https://sourceforge.net/p/evilnet/wiki/Home/
evilnet
2013-07-18
2013-02-20
No

I clicked through the wizard to upgrade the evilnet project to the new forge. It appears to have trashed most of my repositories and mis-named some others.

I had a git repository called x3 (/home/scm_git/evilnet/x3) which seems to have been renamed to 'git' which makes no sense obviously. (Do not confuse this with the old hg repository called x3-donotuse.. we recently converted this project to git)

All of the hg repositories except the one called 'Nefarious2' seem to be empty.

What is going on? I also notice that the /home/scm_* paths dont seem to be used for the new system. Where do I go to set up hooks? /home/git/p/evilnet has the backend files but they are owned by apache.

Also, I tried to re-create the x3 repository, but the UI tells me the mount point "x3" is not valid. Creating one called "test" worked though. What are the requirements?

This process does not appear to be ready for users. Please help!

Discussion

  • Alex Schumann

    Alex Schumann - 2013-02-20

    Correction: the hg repositories are not really empty, just claimed to be empty by the sourceforge hg browser. They are fine when checked out (and in fact you can browse them by clicking on the branch on the left)

    And, apparently you have some magic (posix acl?) allowing me to edit the files in /home/git even though i don't appear have traditional access, so never mind that part. I can add hooks OK.

    What I need is for the "git" git repo to be renamed to "x3", and the browser to work on all the hg repositories where it claims they are empty (all but Nefarious2)

    I also second #2854 that my config settings got wiped out which broke the mail hook without warning.

    Thanks,

     
    Last edit: Alex Schumann 2013-02-20
  • Anonymous - 2013-02-20
    • labels: --> engr, nf-5501, nf-5103, nf-5459
    • status: unread --> assigned
    • assigned_to: Chris Tsai
     
  • Anonymous - 2013-02-20

    Current mountpoint criteria are the same as projects, 3-15 char, start with a letter, lowercase only. We have a ticket to relax these requirements here: [allura:tickets:#5501]

    For the "empty" code browsers, the issue appears to be poor handling of repositories that don't have the standard "default" branch. We have a ticket for better handling of those here: [allura:tickets:#5103]

    The issue with the configs not being migrated is being worked on in this ticket (and is currently in code-review): [allura:tickets:#5459]

    I'll let you know as these issues are addressed. That said though, for the git config item, that's really just informational, as that would only affect new upgrades, not ones that have been already run.

    Regards,
    Chris Tsai, SourceForge.net Support

     

    Related

    Apache Allura: Tickets: #5459

  • Anonymous - 2013-02-20
    • summary: Conversion to new forge trashed all my repositories --> Repo browser incorrectly displays repo as empty, mount point criteria should be relaxed, git configs should be migrated
     
  • Alex Schumann

    Alex Schumann - 2013-02-21

    Thanks Chris. I have re-created the git repo by hand called x3serv and copied the config elements I needed. You can close this and I will keep an eye on #5103 for when the browser gets fixed.

     
    Last edit: Alex Schumann 2013-02-21
  • Anonymous - 2013-02-26
    • labels: engr, nf-5501, nf-5103, nf-5459 --> engr, nf-5501, nf-5103
     
  • Anonymous - 2013-02-26

    Git configs are now maintained for new upgrades.

     
  • Anonymous - 2013-04-30
    • labels: engr, nf-5501, nf-5103 --> engr, nf-5103
     
  • Anonymous - 2013-04-30

    The restrictions for mount points is now as follows:

    • The mount point is the name of the tool as it will appear in a URL. A valid mount point for this tool must begin with a letter or number, contain only letters, numbers, dashes, underscores, periods, and plus signs, and be from 1-63 characters in length.
     
  • Anonymous - 2013-07-18
    • status: assigned --> fixed
     
  • Anonymous - 2013-07-18

    You may now define a default branch via Admin -> Tools.

    Regards,
    Chris Tsai, SourceForge.net Support

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks