#5577 adminrepo cvs broken

fixed
Chris Tsai
pkgsrc-wip
2013-10-21
2013-10-11
Thomas Klausner
No

When logged in as thomasklausner,pkgsrc-wip:

-bash-3.2$ adminrepo --checkout cvs
Lock and checkout the cvs repository for pkgsrc-wip? [ny] y
-bash-3.2$ ls /cvsroot
pkgsrc-wip
-bash-3.2$ cd /cvsroot
-bash-3.2$ ls
pkgsrc-wip
-bash-3.2$ cd pkgsrc-wip/
-bash-3.2$ ls
-bash-3.2$ ls -al
total 8
drwxr-xr-x 2 root root 4096 Oct 11 20:26 .
drwxr-xr-x 3 root root 4096 Oct 11 20:26 ..

Even worse because of
bug 2363 rsync backup of CVS repositories stoppped working

So I don't know how to backup the repository any longer.

Related

Site Support: #2363

Discussion

  • Chris Tsai
    Chris Tsai
    2013-10-15

    • labels: --> siteops, p3, so-54466
    • status: unread --> assigned
    • assigned_to: Chris Tsai
     
  • Chris Tsai
    Chris Tsai
    2013-10-15

    Greetings,

    I added myself to you project to test, and I didn't see the exact same issues, but it wasn't as smooth as it should have been. I neded to try twice to get a good checkout, and when I try to discard the repo checkout, I get the following:

    [ctsai@shell-23003 pkgsrc-wip]$ adminrepo --discard cvs
    Discard and unlock the cvs repository for pkgsrc-wip? [ny] y
    The /cvsroot/pkgsrc-wip copy has been unmounted and will be discarded.
    
    Unable to discard the repo copy for pkgsrc-wip.
    [ctsai@shell-23003 pkgsrc-wip]$ adminrepo --discard cvs
    The /cvsroot/pkgsrc-wip does not exist.
    Show status from 0 minutes ago? [yn] y
    The /cvsroot/pkgsrc-wip copy has been unmounted and will be discarded.
    
    Unable to discard the repo copy for pkgsrc-wip.
    [ctsai@shell-23003 pkgsrc-wip]$
    

    As such, I'm escalating this to our operations team to investigate further.

    I'm also re-raising the rsync issue while I'm at it.

    On the plus side though, since I was able to get an adminrepo checkout, I took a backup of that to the following location: /home/project-web/pkgsrc-wip/CVS-Backup-2013-10-15

    Regards,
    Chris Tsai, SourceForge.net Support

     
  • Chris Tsai
    Chris Tsai
    2013-10-18

    • status: assigned --> pending
     
  • Chris Tsai
    Chris Tsai
    2013-10-18

    Greetings,

    The staff member who investigated this notes the following:

    The history file was 2.2G, which is insanely huge. The rest of the project's cvs files are just in the few hundred MB range.

    I moved the history file to history-old and bzip2-ed it (it's now around 130 MB). They have a new, empty history file that will get their newest history data. This should make the copying operations less likely to time-out and cause problems.

    I tested an adminrepo checkout and it worked fine for me. rsync should work now as well. It worked fine for me using version 3.1.0 (the 2.6.9 version I had on my system previously would still fail though).

    Please give this a shot yourself and let me know.

    Regards,
    Chris Tsai, SourceForge.net Support

     
  • Chris and nameless staff member: Thanks a lot for your help!
    I've tried both rsync and adminrepo, and both succeeded.
    I especially appreciated the CVS backup at the time when it wasn't clear yet how quickly you would be able to solve the problem.
    Thank you.

     
  • Chris Tsai
    Chris Tsai
    2013-10-21

    • status: pending --> fixed
     
  • Chris Tsai
    Chris Tsai
    2013-10-21

    Excellent, thanks for the update.

    Regards,
    Chris Tsai, SourceForge.net Support