Justin C. Sherrill wrote:
> How about now? I think it was missing the language packs that it looks
> for when encountering a browser that's using a language different than
> the default. (This is not documented in the somewhat unfocused
> install/upgrade docs, so I'm taking a wild stab.)
Nope. I
On Tue, January 29, 2008 2:14 am, Hasso Tepper wrote:
> Doesn't work for me with any internationalised browser (tested Konqueror
> and Firefox):
>
> AttributeError
> 'NoneType' object has no attribute 'startswith'
>
> /usr/pkg/lib/python2.4/posixpath.py:60
>
>
> Switching to en_US fixes the problem
On Wed, January 30, 2008 5:35 am, Sdävtaker wrote:
> When i do a full text search, i got this:
> --> -->
Fixed - moinmoin was trying to access a file as a directory, and blew up
when it couldn't open it as it expected.
Garance A Drosihn wrote:
Just use rsync, and shut up about it already.
What are you people blabering about? cvsup SUCKS. not the idea, but the
language it is implemented in. and cvsup inherits the suckage. as simple
as that. if it was written in a portable language, nobody would bother
At 4:38 PM -0600 1/30/08, Vincent Stemen wrote:
That's a good point. It is possible that cvsup would fair better with
a matching sup directory. I actually forgot about cvsup keeping that
separate state directory when I ran the benchmarks. However, from my
viewpoint that does not invalidate th
On Wed, Jan 30, 2008 at 09:54:29AM +, Rahul Siddharthan wrote:
> As I understand, cvsup maintains state between updates using checkout
> files in a separate "sup" directory. If you are missing that
> directory, or it does not correspond to your "aged" tree, cvsup won't
> do very well. You sho
At 6:38 AM + 1/30/08, Vincent Stemen wrote:
My conclusions:
===
The results are dramatic, with rsync performing hundreds of percent faster on
average while only loading the processor on the client side a little over
a third as much as cvsup. Either the performance claims about
Guys, I just don't care about minor differences in client or server
cpu use, or bandwidth.
I think the only real issue here is the one Rahul brought up which is,
in fact, the original reason why cvsup was written in the first place,
so cvs tagging wouldn't require a complete re
Simon 'corecode' Schubert wrote:
*snip*
Simon,
Your command of the *language* is superb.
But it isn't about debating skills.
Test 100 simultaneous connections.
Or Not.
IDGASEW
Bill
"Simon 'corecode' Schubert" <[EMAIL PROTECTED]> wrote:
>Thank you for these thorough tests! We finally have some hard numbers to
>work with. I think it is obvious that rsync should be the preferred
>update mechanism if you want to download the cvs repository.
To download, yes, to update, that'
Bill Hacker wrote:
To state it clearly for everybody:
=
Use rsync to sync your repos! It is faster and can even be compiled!
To state it even MORE clearly...
" ...so long as you do not give a damn about the extra load
Simon 'corecode' Schubert wrote:
Hello Vincent,
Vincent Stemen wrote:
The results are dramatic, with rsync performing hundreds of percent
faster on
average while only loading the processor on the client side a little over
a third as much as cvsup. Either the performance claims about cvsup
be
Justin C. Sherrill wrote:
The only minor thing I'd bring up is that I recall one reason for cvsup is
that rsync placed a relatively higher load per client on the server.
That needs to be established. We already heard that cvsup - contrary to
claims - is not competitive with rsync, on the clie
On Wed, January 30, 2008 1:38 am, Vincent Stemen wrote:
>
> I have some benchmark test results comparing rsync to cvsup. I did 12
> client side tests over the last week. 5 against TheShell.com, 3 against
> AllBSD.org, and 4 against chlamydia.fs.ei.tum.de. All tests were
> mirroring the DragonFly
On Wed, January 30, 2008 5:35 am, Sdävtaker wrote:
> When i do a full text search, i got this:
> --> -->
>
> Traceback (most recent call last):
> File
I'll work on this, along with the language issues Hasso reported - I
didn't get a chance last night.
Hello Vincent,
Vincent Stemen wrote:
The results are dramatic, with rsync performing hundreds of percent faster on
average while only loading the processor on the client side a little over
a third as much as cvsup. Either the performance claims about cvsup being
faster than rsync are based on t
When i do a full text search, i got this:
--> -->
Traceback (most recent call last):
File
"/usr/local/www/wiki/lib/python2.4/site-packages/MoinMoin/request/__init__.py",
line 1283, in run
handler(self.page.page_name, self)
File
"/usr/local/www/wiki/lib/python2.4/site-packages/MoinMoin/a
Vincent Stemen <[EMAIL PROTECTED]> wrote:
>I have some benchmark test results comparing rsync to cvsup. I did 12 client
>side tests over the last week. 5 against TheShell.com, 3 against AllBSD.org,
>and 4 against chlamydia.fs.ei.tum.de. All tests were mirroring the DragonFly
>BSD source reposito
18 matches
Mail list logo