#104181 anoncvs (only!): can't co netbsd-soc's pkg_install module

closed
David Burley
5
2006-06-06
2006-06-01
Hubert Feyrer
No

The netbsd-soc project is hosting a number of modules
for NetBSD and the Google Summer-of-Code. I have
trouble checking out one of the modules, 'pkg_install'
_via anoncvs_. It can be checked out fine with a 'real'
account, and I can check out other modules both via
anoncvs and a 'real' account, only that one makes problems:

Here's what happens when using a 'real' account,
checking out the 'jffs' module (for testing) and the
'pkg_install' module:

miyu% cd /tmp
miyu% mkdir anon hf
miyu% cd /tmp/hf/
miyu% cvs -d
:ext:hubertf@netbsd-soc.cvs.sourceforge.net:/cvsroot/netbsd-soc
co jffs
U jffs/index.html
miyu% cvs -d
:ext:hubertf@netbsd-soc.cvs.sourceforge.net:/cvsroot/netbsd-soc
co pkg_install
U pkg_install/index.html
U pkg_install/doc/Makefile
U pkg_install/doc/pkg_install.docbook
U pkg_install/doc/pkg_install.html

This works fine. Now trying the same thing via anoncvs:

miyu% cd /tmp/anon
miyu% cvs -d
:pserver:anonymous@netbsd-soc.cvs.sourceforge.net:/cvsroot/netbsd-soc
co jffs
U jffs/index.html
miyu% cvs -d
:pserver:anonymous@netbsd-soc.cvs.sourceforge.net:/cvsroot/netbsd-soc
co pkg_install
U pkg_install/index.html
cvs checkout: failed to create lock directory for
`/cvsroot/netbsd-soc/pkg_install/doc'
(/cvsroot/netbsd-soc/pkg_install/doc/#cvs.lock):
Permission denied
cvs checkout: failed to obtain dir lock in repository
`/cvsroot/netbsd-soc/pkg_install/doc'
cvs [checkout aborted]: read lock failed - giving up
miyu%

Is it possible that anoncvs is somehow not in sync with
the 'real' repository? (which seems strange as they
have an identical path /cvsroot/netbsd-soc, but what do
I know).

Please direct your answers to hubertf@NetBSD.org.

Thanks!

- Hubert

Discussion

  • Logged In: YES
    user_id=126005

    The problem is specific to the netbsd-soc repository, in
    message id
    20060602072145.98738.qmail@web25502.mail.ukl.yahoo.com the
    same problem was reported with the pkgsrc-wip repository.

    In both cases the culprit seems to be a newly added directory.

     
  • David Burley
    David Burley
    2006-06-06

    Logged In: YES
    user_id=597273

    Greetings,

    To the best of my knowledge, this matter has now been resolved.
    Should you require further assistance from the SourceForge.net
    team, please add a comment to this Support Request and we'll
    reopen it for you.

    SourceForge.net Support

     
  • David Burley
    David Burley
    2006-06-06

    • status: open --> closed
     
  • David Burley
    David Burley
    2006-06-06

    • assigned_to: nobody --> burley