Hi,
Jiri B wrote on Thu, Feb 09, 2012 at 07:52:44AM -0500:
Somebody suggested:
find . -path '*CVS/Root' | xargs rm
Never ever!
Well, certainly not when you are working in a mixed tree intentionally
using different servers for different subdirectories.
However, on a laptop i'm carrying
Stuart Henderson wrote [2012-02-10 01:01+0100]:
On 2012-02-09, Steffen Daode Nurpmeso sdao...@googlemail.com wrote:
On the long run cvs(1) will die, and be replaced by Schily SCCS
oh please don't, even as a joke.
It's not that bad!
It's from 1972, and only good things can come from 1972.
Otto Moerbeek wrote [2012-02-03 12:47+0100]:
I like to say that long delays I have seen when using cvs had to do
with multiple different values of CVS/Root files in my local tree.
Otto, could you please elaborate?
How does this slow down a cvs update?
Is it really due to the fact that there
On Thu, Feb 09, 2012 at 01:16:10PM +0100, Jan Stary wrote:
+it maybe wise to issue a command sequence like the following:
+pre
+ # strongcd /usr/src/strong
+ # strongfind . -path '*CVS/Root' | xargs rm/strong
+ # strongcvs -d anon...@anoncvs.ca.openbsd.org:/cvs -q up -Pd/strong
On Thu, Feb 09, 2012 at 01:16:10PM +0100, Jan Stary wrote:
Otto Moerbeek wrote [2012-02-03 12:47+0100]:
I like to say that long delays I have seen when using cvs had to do
with multiple different values of CVS/Root files in my local tree.
Otto, could you please elaborate?
How does
On Thu, Feb 09, 2012 at 07:52:44AM -0500, Jiri B wrote:
On Thu, Feb 09, 2012 at 01:16:10PM +0100, Jan Stary wrote:
+it maybe wise to issue a command sequence like the following:
+pre
+ # strongcd /usr/src/strong
+ # strongfind . -path '*CVS/Root' | xargs rm/strong
+ # strongcvs -d
1.
On the long run cvs(1) will die, and be replaced by Schily SCCS
(oh god, why does v6 not have any branch name info, too??), which
will rule the world.
Without having the need to use GNU autoconf at all, so that
software will compile with make(1) not gmake(1).
Make bootstrapping easy.
Freedom!
there aren't all that many repositories the size of ours out
there.
My upload-traffic problem never occurred with binutils, which is
also an *incredible* large repository, especially if you up -d.
10% there and my monthly traffic would exhaust, and no begging
would help.
I have no idea, I
Replying to myself,
On Feb 09 13:16:10, Jan Stary wrote:
Also, specifying 'cvs -d mirror' explicitly should get rid of this
problem then (right?), and speed things up, which it doesn't.
it does; see below.
Or is the slowdown possibly due to the sheer *number* of CVS/Root
files that are
On Thu, Feb 09, 2012 at 06:15:50PM +0100, Jan Stary wrote:
Replying to myself,
[snip]
Things might change if (1) the cvsroot is remote (2) it is not
the same for all files. I will try that next.
Jan
That last case (remote repo's and different Roots) is the actual case I
have
On Feb 09 18:54:45, Otto Moerbeek wrote:
BTW, AFAIK, cvs -d up does not write Root files.
It does:
cd /usr/src
ftp -o - ftp://MIRROR/pub/OpenBSD/5.0/sys.tar.gz | tar xzpf
cd sys
find . -name Root
cvs -q -d MIRROR up
find . -name Root
Jan
On Feb 09 20:10:11, Jan Stary wrote:
On Feb 09 18:54:45, Otto Moerbeek wrote:
BTW, AFAIK, cvs -d up does not write Root files.
It does:
cd /usr/src
ftp -o - ftp://MIRROR/pub/OpenBSD/5.0/sys.tar.gz | tar xzpf
cd sys
find . -name Root
cvs -q -d MIRROR up
find . -name Root
Ah, you mean
On Thu, Feb 09, 2012 at 08:16:25PM +0100, Jan Stary wrote:
On Feb 09 20:10:11, Jan Stary wrote:
On Feb 09 18:54:45, Otto Moerbeek wrote:
BTW, AFAIK, cvs -d up does not write Root files.
It does:
cd /usr/src
ftp -o - ftp://MIRROR/pub/OpenBSD/5.0/sys.tar.gz | tar xzpf
cd sys
On 2012-02-09, Steffen Daode Nurpmeso sdao...@googlemail.com wrote:
On the long run cvs(1) will die, and be replaced by Schily SCCS
oh please don't, even as a joke.
anyway they are still releasing new versions of CVS.
(they have to, they add new features with security holes...)
I like my
On 02/09/12 12:54, Otto Moerbeek wrote:
On Thu, Feb 09, 2012 at 06:15:50PM +0100, Jan Stary wrote:
Replying to myself,
[snip]
Things might change if (1) the cvsroot is remote (2) it is not
the same for all files. I will try that next.
Jan
That last case (remote repo's and
On Fri, Feb 03, 2012 at 12:47:02PM +0100, Otto Moerbeek wrote:
On Thu, Feb 02, 2012 at 03:15:29PM +0100, Steffen Daode Nurpmeso wrote:
Henning Brauer wrote:
there aren't all that many repositories the size of ours out there.
That's true.
But no Henning, i don't believe it's that;
On Thu, Feb 02, 2012 at 03:15:29PM +0100, Steffen Daode Nurpmeso wrote:
Henning Brauer wrote:
there aren't all that many repositories the size of ours out there.
That's true.
But no Henning, i don't believe it's that;
you know, it's just that i don't have anything to say, because
i have
Otto Moerbeek wrote [2012-02-03 12:47+0100]:
I like to say that long delays I have seen when using cvs had to do
with multiple different values of CVS/Root files in my local tree.
Those different entries can be created when doing a cvs up -d that
creates a new dir. If a cvs -d option is used
On Fri, 3 Feb 2012, Otto Moerbeek wrote:
On Thu, Feb 02, 2012 at 03:15:29PM +0100, Steffen Daode Nurpmeso wrote:
Henning Brauer wrote:
there aren't all that many repositories the size of ours out there.
That's true.
But no Henning, i don't believe it's that;
you know, it's just that i
On 2012-02-02, Brett brett.ma...@gmx.com wrote:
Yes, I also finally got around to trying cvsync because of this thread and
its a lot quicker.
And even more speedy when I added a scanfile /root/cvsync-scanfile line in
the collection part of the config file.
You're running it as root?
It
On Thu, 2 Feb 2012 11:40:22 + (UTC)
Stuart Henderson s...@spacehopper.org wrote:
On 2012-02-02, Brett brett.ma...@gmx.com wrote:
Yes, I also finally got around to trying cvsync because of this thread and
its a lot quicker.
And even more speedy when I added a scanfile
On 2012/02/02 23:00, Brett wrote:
On Thu, 2 Feb 2012 11:40:22 + (UTC)
Stuart Henderson s...@spacehopper.org wrote:
On 2012-02-02, Brett brett.ma...@gmx.com wrote:
Yes, I also finally got around to trying cvsync because of this thread
and its a lot quicker.
And even more
And even more speedy when I added a scanfile /root/cvsync-scanfile
line in the collection part of the config file.
You're running it as root?
It makes a lot more sense to use a separate user.
I have been updating as root (the few times I have used it so far) but
Henning Brauer wrote:
there aren't all that many repositories the size of ours out there.
That's true.
But no Henning, i don't believe it's that;
you know, it's just that i don't have anything to say, because
i have no knowledge about the internals of cvs(1).
I always thought of this as some
Hi Amit,
Amit Kulkarni wrote [2012-02-01 00:57+0100]:
this motivated me to use cvsync from anoncvs and use a
CVSROOT=/home/amit/MYLOCALREPO to update from cvs. Much much faster
and while initial checkout from cvsync takes 5-10 hrs
Yes, that's a real pity.
I think it would be great if tarballs
Dave Anderson wrote [2012-01-28 15:13+0100]:
[.]
I haven't yet had a chance to look into how cvs works beyond
reading the man page, faq, etc.
If you're doing your updates in such a regular manner, i think
your best bet is cvsync(1), even if that means additional local
storage -
2012/1/31 Dave Anderson d...@daveanderson.com:
I do have a slowish ADSL link (384Kbps/1536Kbps) which would limit me to
very roughly 1MB/min outbound, so I took advice to use '-z 9' to
compress data and that reduced the total time for a xenocara source tree
update from about 11 hours to about
On Sat, Jan 28, 2012 at 8:43 AM, Steffen Daode Nurpmeso
sdao...@googlemail.com wrote:
Hey,
Dave Anderson wrote [2012-01-28 15:13+0100]:
[.]
I haven't yet had a chance to look into how cvs works beyond
reading the man page, faq, etc.
Also true for me.
I've run into this problem perhaps a
On Sat, 28 Jan 2012, Nick Holland wrote:
On 01/28/12 09:12, Dave Anderson wrote:
Thanks for the info. I've been using -Pd because
http://www.openbsd.org/anoncvs.html says to use them; I haven't yet
had a chance to look into how cvs works beyond reading the man page,
faq, etc.
and please
* Steffen Daode Nurpmeso sdao...@googlemail.com [2012-01-28 15:44]:
I've noted a lot of upload network traffic when doing 'cvs up'
on OpenBSD repos; i.e., before anything else happened about
~70 MB (www) and ~150 MB (src) *upstream* traffic were produced,
and it took more than an hour before
On Fri, 27 Jan 2012, Philip Guenther wrote:
On Fri, Jan 27, 2012 at 12:10 PM, Dave Anderson d...@daveanderson.com
wrote:
I've run into this problem perhaps a dozen times over the past several
months while running amd64-current, most recently at 15:53 2012/1/26 EST
while running a system built
Hey,
Dave Anderson wrote [2012-01-28 15:13+0100]:
[.]
I haven't yet had a chance to look into how cvs works beyond
reading the man page, faq, etc.
Also true for me.
I've run into this problem perhaps a dozen times over the past several
months
[.]
I've noted a lot of upload network
On 2012-01-28, Philip Guenther guent...@gmail.com wrote:
I've run into this problem perhaps a dozen times over the past several
months while running amd64-current, most recently at 15:53 2012/1/26 EST
while running a system built from source updated at about 14:30
2012/1/21 EST: when trying to
On 01/28/12 09:12, Dave Anderson wrote:
Thanks for the info. I've been using -Pd because
http://www.openbsd.org/anoncvs.html says to use them; I haven't yet
had a chance to look into how cvs works beyond reading the man page,
faq, etc.
and please continue to use them.
-Pd is the RIGHT way.
I've run into this problem perhaps a dozen times over the past several
months while running amd64-current, most recently at 15:53 2012/1/26 EST
while running a system built from source updated at about 14:30
2012/1/21 EST: when trying to update the xenocara source tree there is a
very long
On Fri, Jan 27, 2012 at 9:10 PM, Dave Anderson d...@daveanderson.com wrote:
I've run into this problem perhaps a dozen times over the past several
months while running amd64-current, most recently at 15:53 2012/1/26 EST
while running a system built from source updated at about 14:30
2012/1/21
On Fri, Jan 27, 2012 at 12:10 PM, Dave Anderson d...@daveanderson.com
wrote:
I've run into this problem perhaps a dozen times over the past several
months while running amd64-current, most recently at 15:53 2012/1/26 EST
while running a system built from source updated at about 14:30
2012/1/21
37 matches
Mail list logo