FS#10860 - CVS/SVN access is broken

Attached to Project: Arch Linux
Opened by Andreas Hauser (buggs) - Tuesday, 08 July 2008, 12:53 GMT
Last edited by Dale Blount (dale) - Friday, 23 January 2009, 01:01 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dale Blount (dale)
Architecture All
Severity Low
Priority High
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
CVS access lags behind SVN. Today CVS is also broken:
cvs [update aborted]: connect to cvs.archlinux.org(66.211.213.17):2401 failed: Connection timed out

Please enable anonymous svn access instead.
This task depends upon

Closed by  Dale Blount (dale)
Friday, 23 January 2009, 01:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  CVS is dead, use SVN which is working now.
Comment by Andrea Scarpino (BaSh) - Friday, 11 July 2008, 11:13 GMT
moved to ArchLinux project
Comment by Andreas Hauser (buggs) - Friday, 11 July 2008, 11:56 GMT
Today I get:
$ cvs up
cvs update: failed to create lock directory for `/home/cvs-extra/extra/modules' (/home/cvs-extra/extra/modules/#cvs.lock): Permission denied
cvs update: failed to obtain dir lock in repository `/home/cvs-extra/extra/modules'
cvs [update aborted]: read lock failed - giving up

Comment by Xavier (shining) - Saturday, 12 July 2008, 09:20 GMT
Why do you need a svn access and why isn't the rsync access enough?
Maybe you need the history or checking out specific packages instead of whole repo?
If only the latter, this is also possible with rsync :
http://www.archlinux.org/pipermail/pacman-dev/2008-July/012329.html
Comment by Andreas Hauser (buggs) - Saturday, 12 July 2008, 18:33 GMT
I need the access to maintani my own set of patches.
I often change the PKGBUILDs etc. With svn/cvs i can update and merge and thus keep my changes.
And when my changes conflict the SCM will tell me and I can easily merge them.
Updating is more intelligent resources wise too, since the SCM knows much better what changed
than a general sync tool like rsync.

I've never understood why any one would use ABS, which offers less and is a new tool to learn,
while I can have also the comfort of a common Source Code Managementsystem.

If this great feature, that I am used from BSDs too, does not come back, that would really give
me a hard time staying with Arch :(

If any resources, be it hardware, hosting or admin time, are the problem, please let me know,
I could provide any of it.

Thanks
Comment by Andreas Hauser (buggs) - Monday, 14 July 2008, 13:45 GMT Comment by Aaron Griffin (phrakture) - Friday, 25 July 2008, 19:26 GMT
Can someone verify this is acceptable?
svn co -N svn://archlinux.org/home/svn-packages

Please, for the love of freaking god, check this out non-recursive and do NOT abuse this privilege. Do a non-recursive checkout and use "svn up" to checkout individual packages, as described here:
http://wiki.archlinux.org/index.php/DeveloperWiki:HOWTO_Be_A_Packager
Comment by Aaron Griffin (phrakture) - Friday, 25 July 2008, 21:17 GMT Comment by Andreas Hauser (buggs) - Saturday, 26 July 2008, 14:24 GMT
Thanks Aaron this works great!

Of course being able to checkout recursivley would still be nice and make things work more easily.
How about making available a tar of a complete checkout once a month/week. People could start
from that and it would sure leverage the load on your servers.
I would also be willing to commit time and resources to improve this situation further.
E.g. i could clone the whole svn to a server and make it available to the rest of the world.
I'd commit to admin that server be it an offical archlinux server or my own hardware,
which i'd also commit.

You can reach me in IRC (buggs) or email.

Thanks a lot.
Comment by Andreas Hauser (buggs) - Friday, 05 December 2008, 20:23 GMT
Broken again since the planned downtime of 2008-11-19 :(

svn: No repository found in 'svn://archlinux.org/home/svn-packages'
Comment by Aaron Griffin (phrakture) - Friday, 05 December 2008, 20:37 GMT
That's because the location changed. Docs above were updated. Please update your path.

If you already have a checkout, you probably want to use "svn switch --relocate OLDPATH NEWPATH"

Loading...