kernel.bkbits.net off the air
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Davide Libenzi
Quoted 1 line · Nick Piggin
What happens if the the tree is updated while the client is fetching >> it [using a single LOCKfile method]?
Surprise, it breaks :-) Yes, the double file approach is needed (excluding changes to rsync).
Sorry to be so dumb, but it seems to me that the two methods are exactly equivalent in every way:
A test for file1 != file2 is exactly eqivalent to testing LOCK != NULL. It's a simple binary TRUE/FALSE test.
What am I missing? (BTW I'm not arguing against the two-file method. I just don't understand why it's different.)
Now, if multiple people are updating the tree at the same time then a simple TRUE/FALSE test provides insufficient information: you would then need enough 'bits' of information to count the number of people updating at the same time.
But this problem is certainly not unique to this group. Anyone using a source repository has the same problem to deal with. Or am I not with the program here at all?
Quoted 9 lines · walt
Sorry to be so dumb, but it seems to me that the two methods are exactly equivalent in every way:
A test for file1 != file2 is exactly eqivalent to testing LOCK != NULL. It's a simple binary TRUE/FALSE test.
What am I missing? (BTW I'm not arguing against the two-file method. I just don't understand why it's different.)
So you check the lock, do rsync, and check the lock again. But the lock could have flipped several times during the rsync and you wouldn't know about it.
My preferred solution is a single sequence file as described by Adreas:
Assuming sequence starts at 0,
To modify the repository, +1 to sequence file contents, modify repo, +1 to sequence
To get a coherent copy,
do
seq1 = read(sequence file)
rsync repo
seq2 = read(sequence file)
until seq1==seq2 and !(seq1&1)
Quoted 10 lines · Andrew Walrond
So you check the lock, do rsync, and check the lock again. But the lock could have flipped several times during the rsync and you wouldn't know about it.
My preferred solution is a single sequence file as described by Adreas:
Assuming sequence starts at 0,
To modify the repository, +1 to sequence file contents, modify repo, +1 to sequence
Quoted 6 lines
To get a coherent copy,
do
seq1 = read(sequence file)
rsync repo
seq2 = read(sequence file)
until seq1==seq2 and !(seq1&1)
yep.
Followup to: <[email protected]> By author: Andrew Walrond <[email protected]> In newsgroup: linux.dev.kernel
Quoted 8 lines
My preferred solution is a single sequence file as described by Adreas:
Assuming sequence starts at 0,
To modify the repository, +1 to sequence file contents, modify repo, +1 to sequence
Quoted 7 lines
To get a coherent copy,
do
seq1 = read(sequence file)
rsync repo
seq2 = read(sequence file)
until seq1==seq2 and !(seq1&1)
OK... this still doesn't deal with how to get mirrors to pick stuff up with a minimum of fuss. The "minimum of fuss" bit is *extremely* important... I still haven't managed to get all mirrors to use rsync.
-hpa
Signature · 4 lines
<[email protected]> at work, <[email protected]> in private! If you send me mail in HTML format I will assume it's spam. "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
Quoted 5 lines · H. Peter Anvin
OK... this still doesn't deal with how to get mirrors to pick stuff up with a minimum of fuss. The "minimum of fuss" bit is *extremely* important... I still haven't managed to get all mirrors to use rsync.
1. Don't bother with cvs.Just host a clone of the main bk repository
2. Persuade Larry to release a 'clone/pull-only' version of bk which *anyone* can use to access open source software
3. Having lit the blue touch paper, run...
Seriously though; There isn't another way that I can see for mirroring cvs repos coherently, unless cvsup does something clever? Anyone know?
Andrew Walrond
Quoted 2 lines · Andrew Walrond
2. Persuade Larry to release a 'clone/pull-only' version of bk which *anyone* can use to access open source software
I tried to ask this to Larry but no one else seemed interested at the time. Personally I would be happy even with only the removal of "you cannot work/dev on any other SCM" kinda clause.
- Davide
Quoted 7 lines · Andrew Walrond
Quoted 4 lines · H. Peter Anvin
OK... this still doesn't deal with how to get mirrors to pick stuff up with a minimum of fuss. The "minimum of fuss" bit is *extremely* important... I still haven't managed to get all mirrors to use rsync.
1. Don't bother with cvs.Just host a clone of the main bk repository
There's a good idea :)
Quoted 2 lines
2. Persuade Larry to release a 'clone/pull-only' version of bk which *anyone* can use to access open source software
As I've explained in the past, this doesn't make sense. I'd be far more likely to build a sort of CVS like client that could do checkouts and updates of read only files. That's a pretty straightforward thing to do, in fact, nobody needs BK source to do that, it could all be done as wrappers pretty trivially. If someone wanted to code that up and make the code available under a BSD license we'd take a good look at adding that into the BK server side. It doesn't need to be bundled in BK however. Anyone could write a daemon that locally called BK to get the data and a client that talked to the daemon.
The hard part is renames but even that can be handled reasonably easily.
Quoted 2 lines
Seriously though; There isn't another way that I can see for mirroring cvs repos coherently, unless cvsup does something clever? Anyone know?
I could make some comment about this being a good example of one of the zillion little problems we've had to solve but if I go there it's going to start a flame war. So I won't. I will note that none of the solutions proposed come close to being acceptable, they all fail on NFS and on SMB shares. And they don't cascade properly as HPA has noted.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 3 lines · Larry McVoy
going to start a flame war. So I won't. I will note that none of the solutions proposed come close to being acceptable, they all fail on NFS and on SMB shares. And they don't cascade properly as HPA has noted.
FWIW arch would solve this completely too, but we need to checkout a coherent cvs to import the data into arch.
Quoted 7 lines
Quoted 2 lines
2. Persuade Larry to release a 'clone/pull-only' version of bk which *anyone* can use to access open source software
As I've explained in the past, this doesn't make sense. I'd be far more likely to build a sort of CVS like client that could do checkouts and updates of read only files. That's a pretty straightforward thing to do, in fact, nobody needs BK source to do that, it could all be done as
I'm a bit confused (not unusual). I think what I'm suggesting is exactly what you've just described and doesn't involve releasing any bk source; Release a binary only tool which will clone and pull only, (Ie can be used to access open source software but not develop it) which is free of the license restrictions of the full bk (ie can be used to access open source software by anybody, regardless of what they might be working on)
Or am I missing something? How does this hurt the bk business model?
Quoted 5 lines
I could make some comment about this being a good example of one of the zillion little problems we've had to solve but if I go there it's going to start a flame war. So I won't. I will note that none of the solutions proposed come close to being acceptable, they all fail on NFS and on SMB shares. And they don't cascade properly as HPA has noted.
Absolutely. Bk is, undeniably, brilliant, and would solve all these problems at a stroke, except that the open source community cannot with good conscience exclude *anyone* from being able to access the sources.
Quoted 8 lines · Andrew Walrond
Quoted 7 lines
Quoted 2 lines
2. Persuade Larry to release a 'clone/pull-only' version of bk which *anyone* can use to access open source software
As I've explained in the past, this doesn't make sense. I'd be far more likely to build a sort of CVS like client that could do checkouts and updates of read only files. That's a pretty straightforward thing to do, in fact, nobody needs BK source to do that, it could all be done as
Quoted 5 lines
I'm a bit confused (not unusual). I think what I'm suggesting is exactly what you've just described and doesn't involve releasing any bk source; Release a binary only tool which will clone and pull only,
Or am I missing something? How does this hurt the bk business model?
It doesn't hurt the BK business model. It also doesn't require any access to BK source to do it. Anyone could wrap a network daemon around BK and serve up repositories. So that means you could do it if it is important to you. So could anyone else.
Quoted 9 lines
Quoted 5 lines
I could make some comment about this being a good example of one of the zillion little problems we've had to solve but if I go there it's going to start a flame war. So I won't. I will note that none of the solutions proposed come close to being acceptable, they all fail on NFS and on SMB shares. And they don't cascade properly as HPA has noted.
Absolutely. Bk is, undeniably, brilliant, and would solve all these problems at a stroke, except that the open source community cannot with good conscience exclude *anyone* from being able to access the sources.
But noone is excluded from having access to the sources.
I suppose it sounds like we don't want to give out more free engineering but let's put things into perspective. The CVS server has about 6 users. It's cost us a pile of money to build and support that technology. For 6 users. On the other hand, there are thousands if not tens of thousands of BK users for the kernel alone. About a year ago we added unique ID's to the repositories themselves (the clones) and a few months later I counted over 10,000 clones having connected to to openlogging.org for the kernel tree (people do use BK for other things).
So what do you want? Do you want us to spend what little resources we have to give you on something that is used by less than 1/100th of one percent of the people? Are you sure? What about us spending some time and making performance and functionality of BK itself better? Wouldn't that be a better use of our time and help dramatically more people? Remember, there is a limited amount that we can do. Ask for the work that helps the most people.
I'm starting to (finally) learn that there are a small number of people who complain loudly (not you Andrew, I just happened to hit reply to your mail) but they in no way represent the majority of the people doing work. As far as I can tell, most people are using BK and if there wasn't any whining they'd be content with that and what they'd really like is for BK itself to improve (*). Linus doesn't get any benefit from one more enhancement to the CVS gateway, he doesn't use it. Neither do thousands of other people. All those people would be one heck of a lot happier if the BK integrity checks were faster, if the GUI tools were faster, if we added digital signatures to changesets, the list goes on and on.
As much as I'd love to have zero complaining about BK, I don't see that ever happening. And it is a mistake for me to listen to that complaining and help people who dislike BK, our license, and who knows what else. There are a lot of silent people who are going about getting their job done using BK and they deserve our help one heck of a lot more than a bunch of whiners.
--lm
(*) Insert obligatory statement about everyone also wanting BK GPLed, a chicken in every pot, a porsche in every garage, and a supermodel with a PhD opening up your door to greet you with a smile at the end of your hard day.
Quoted 7 lines · Larry McVoy
I'm starting to (finally) learn that there are a small number of people who complain loudly (not you Andrew, I just happened to hit reply to your mail) but they in no way represent the majority of the people doing work. As far as I can tell, most people are using BK and if there wasn't any whining they'd be content with that and what they'd really like is for BK itself to improve (*). Linus doesn't get any benefit from one more
...
Larry: You tried to get it working, and keep it working. To me, this is more than enough effort. The whiners (yes, whiners - every participant has the opportunity of *doing* something - choosing to complain and demand that others *do* something is whining in my books) are an unfortunate fact of life.
mark
Signature · 9 lines
[email protected]/[email protected]/[email protected] __________________________ . . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder |\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ | | | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada One ring to rule them all, one ring to find them, one ring to bring them all and in the darkness bind them... http://mark.mielke.cc/
Quoted 4 lines · Larry McVoy
I suppose it sounds like we don't want to give out more free engineering but let's put things into perspective. The CVS server has about 6 users. It's cost us a pile of money to build and support that technology. For 6 users. On the other hand, there are thousands if not tens of
Larry, if there are really six users (i'm one of them, rsync) among pserver and rsync access, I am the first to tell you shut it down. It is not worth. On the other hand IIRC it was you that, when Pavel showed up with the bitbucket hack to extract metadata from BK, volunteered to do it internally inside BM. Do I remember correctly?
- Davide
Quoted 7 lines · Davide Libenzi
Quoted 4 lines · Larry McVoy
I suppose it sounds like we don't want to give out more free engineering but let's put things into perspective. The CVS server has about 6 users. It's cost us a pile of money to build and support that technology. For 6 users. On the other hand, there are thousands if not tens of
Quoted 5 lines
Larry, if there are really six users (i'm one of them, rsync) among pserver and rsync access, I am the first to tell you shut it down. It is not worth. On the other hand IIRC it was you that, when Pavel showed up with the bitbucket hack to extract metadata from BK, volunteered to do it internally inside BM. Do I remember correctly?
Not really, the revision history of the CVS gateway predates Pavel's so-called hacks.
I don't mind us supporting this gateway for the small number of users, if it makes them happy, that's fine. What I mind is people coming back and asking for more stuff for a tiny number of people. That doesn't make sense. We should put our efforts into helping the people using BK, not the people using CVS. If you want to help yourselves, that's a fine idea, go for it.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 8 lines · Larry McVoy
Quoted 7 lines · Davide Libenzi
Quoted 4 lines · Larry McVoy
I suppose it sounds like we don't want to give out more free engineering but let's put things into perspective. The CVS server has about 6 users. It's cost us a pile of money to build and support that technology. For 6 users. On the other hand, there are thousands if not tens of
Quoted 8 lines
Quoted 5 lines
Larry, if there are really six users (i'm one of them, rsync) among pserver and rsync access, I am the first to tell you shut it down. It is not worth. On the other hand IIRC it was you that, when Pavel showed up with the bitbucket hack to extract metadata from BK, volunteered to do it internally inside BM. Do I remember correctly?
Not really, the revision history of the CVS gateway predates Pavel's so-called hacks.
Looking here:
http://lkml.org/lkml/2003/2/15/96
it didn't seem so, but it's not that makes a huge difference.
Quoted 5 lines
I don't mind us supporting this gateway for the small number of users, if it makes them happy, that's fine. What I mind is people coming back and asking for more stuff for a tiny number of people. That doesn't make sense. We should put our efforts into helping the people using BK, not the people using CVS. If you want to help yourselves, that's a fine idea, go for it.
I really would like to know from Peter/DaveM how many hits the rsync of the CVS repo at kernel.org has. If really a few cats are looking at it and if for BM is an hassle to support it, we have to ask ourselves if it is worth. Both for kernel.org maintainers and for BM.
(rsync on CVS repo on kernel.org does not give me any new data by days)
- Davide
Quoted 7 lines · Davide Libenzi
Larry, if there are really six users (i'm one of them, rsync) among pserver and rsync access, I am the first to tell you shut it down. It is not worth. On the other hand IIRC it was you that, when Pavel showed up with the bitbucket hack to extract metadata from BK, volunteered to do it internally inside BM. Do I remember correctly?
- Davide
As one of the six, I would happily 2nd the shutting down of the pserver...rsync is fine with me. I would actually prefer no CVS archive at all as long as the raw changesets were rsyncable...then the community would be responsible for doing something useful with them instead of BM.
-Tupshin
On Thu, 2003-11-13 10:21:10 -0800, Tupshin Harper <[email protected]> wrote in message <[email protected]>:
Quoted 10 lines
Quoted 5 lines · Davide Libenzi
Larry, if there are really six users (i'm one of them, rsync) among pserver and rsync access, I am the first to tell you shut it down. It is not worth. On the other hand IIRC it was you that, when Pavel showed up with the bitbucket hack to extract metadata from BK, volunteered to do it internally inside BM. Do I remember correctly?
As one of the six, I would happily 2nd the shutting down of the pserver...rsync is fine with me. I would actually prefer no CVS archive at all as long as the raw changesets were rsyncable...then the community would be responsible for doing something useful with them instead of BM.
That would be fine with me, too, but there's one little drawback: The changeset format. You can't simply use a patch(1) file because there is a (really little) number of non-text files in the kernel source tree that won't diff...
MfG, JBG
Signature · 4 lines
Jan-Benedict Glaw [email protected] . +49-172-7608481 "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
Quoted 14 lines · Jan-Benedict Glaw
On Thu, 2003-11-13 10:21:10 -0800, Tupshin Harper <[email protected]> wrote in message <[email protected]>:
Quoted 9 lines
Quoted 3 lines · Davide Libenzi
Larry, if there are really six users (i'm one of them, rsync) among pserver and rsync access, I am the first to tell you shut it down. It is not worth. On the other hand IIRC it was you that, when Pavel showed up with the bitbucket hack to extract metadata from BK, volunteered to do it internally inside BM. Do I remember correctly?
As one of the six, I would happily 2nd the shutting down of the pserver...rsync is fine with me. I would actually prefer no CVS archive at all as long as the raw changesets were rsyncable...then the community would be responsible for doing something useful with them instead of BM.
Quoted 9 lines
That would be fine with me, too, but there's one little drawback: The changeset format. You can't simply use a patch(1) file because there is a (really little) number of non-text files in the kernel source tree that won't diff...
MfG, JBG
An acceptable hurdle to overcome.
-Tupshin
Quoted 11 lines · Tupshin Harper
Quoted 6 lines · Davide Libenzi
Larry, if there are really six users (i'm one of them, rsync) among pserver and rsync access, I am the first to tell you shut it down. It is not worth. On the other hand IIRC it was you that, when Pavel showed up with the bitbucket hack to extract metadata from BK, volunteered to do it internally inside BM. Do I remember correctly?
As one of the six, I would happily 2nd the shutting down of the pserver...rsync is fine with me. I would actually prefer no CVS archive at all as long as the raw changesets were rsyncable...then the community would be responsible for doing something useful with them instead of BM.
Just wondering: the emails sent to the bk-commits mailing lists are just all changesets in a `neutral' format that contains all meta information, right?
So if all individual mails were archived somewhere with correct sequence numbers, they could be used to recreate the whole repository in whatever format you want. I guess it's just a matter of importing them like patches into arch.
Gr{oetje,eeting}s,
Geert
P.S. I did use the CVS gateway before to have a base tree to verify that the
patches I send to Linus and Marcelo still apply cleanly. But these days full releases are so frequent that I can use these as base trees. And I monitor the bk-commits lists so I know what's happening in between.
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
On Fri, 2003-11-14 10:56:56 +0100, Geert Uytterhoeven <[email protected]> wrote in message <[email protected]>:
Quoted 9 lines · Tupshin Harper
Quoted 5 lines
Davide Libenzi wrote:
As one of the six, I would happily 2nd the shutting down of the pserver...rsync is fine with me. I would actually prefer no CVS archive at all as long as the raw changesets were rsyncable...then the community would be responsible for doing something useful with them instead of BM.Just wondering: the emails sent to the bk-commits mailing lists are just all changesets in a `neutral' format that contains all meta information, right?
These changesets represent what someone "submitted". You can't expect these to apply cleanly. I've tried once, it will not work.
Quoted 3 lines
So if all individual mails were archived somewhere with correct sequence numbers, they could be used to recreate the whole repository in whatever format you want. I guess it's just a matter of importing them like patches into arch.
Nope. You'll have to heal with conflicts first.
MfG, JBG
Signature · 4 lines
Jan-Benedict Glaw [email protected] . +49-172-7608481 "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
Hi,
Quoted 3 lines · Geert Uytterhoeven
So if all individual mails were archived somewhere with correct sequence numbers, they could be used to recreate the whole repository in whatever format you want. I guess it's just a matter of importing them like patches into arch.
The problematic part are "correct sequence numbers" here. These numbers in the commit list mails are pretty much useless. At least the numbers in this line:
# ChangeSet 1.1437+1.1350.5.10 -> 1.1438
have to be replaced with a unique identifier. This identifier does exist, e.g. it's visible in the exclude mails.
As soon as someone finds out how to export changesets in this format and stores them somewhere, other people can make use of this data. Unfortunately it's rather unlikely that anyone who can do the first, knows also how to do the latter (but maybe Larry can tell us the trick). Anyway, if someone has this data I'd be interested in a copy.
bye, Roman
This is degenerating, but I don't want anyone mistaking my position, so...
For the record and so nobody gets the the wrong end of the stick; I am a bk advocate. I use it for my open source activities, and urge others to do so as well.
But... There are tiny minority of people (who work on other SCM projects) who cannot access my sources because they can't use BK.
I don't particularly care, and I'm still using bk, but that particular clause of the bk license has caused Larry ridiculous amounts of grief for no discernable return.
And I still maintain that a stripped out, redistributable, clone/pull only binary tool without the restrictive license would be a real smart business move.
But it ain't my business, so I'll leave it there :)
Andrew Walrond
Quoted 3 lines · Andrew Walrond
And I still maintain that a stripped out, redistributable, clone/pull only binary tool without the restrictive license would be a real smart business move.
I'm trying to see why.
Our commercial customers don't care about this so there isn't any business incentive there.
The actual BK users don't care about this, they use BK.
The BK detractors aren't going to touch anything that we produce, they are convinced we're out to do them harm somehow.
So who's left?
And a better question is why doesn't some open source person do this? All you need to do is create a network daemon which responds to clone requests and pull requests. The clone request sends across a tarball and the client side untars it. The pull request sends a changeset key (which was sent in the last clone/pull) and gets a tarball of new/changed files, the new top of trunk changeset key, and a list of renames. Actually the easier way is to do it more like diff does, for each file that has been changed, send across a "delete this file and any directories the deletion leaves empty" list, and then you unpack the tarball on top of the tree.
This would be easy to build but I don't see it solving anything. All it does is act as a replacement for rsync. It doesn't have revision history, you can't do diffs, etc. As soon as this exists, people will ask you for all the other features. Which is why I don't want to build it, I don't want to get sucked into the "please rebuild BK as a GPLed product" business.
What am I missing?
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
On Thursday 13 Nov 2003 7:28 pm, Larry McVoy wrote:
You're getting to be a cynical old git ;)
Quoted 1 line
What am I missing?
The point. You got one major o/s project hosted on bk when you ought to have them all. Loads more developers using bk at home means loads more demanding it at work.
And all it would take is a lobotomised, redistributable, license free client so anyone can pull o/s software from bk repos.
And, for the record, you'd be a hungry fool if you GPLed bk.
Quoted 3 lines · Andrew Walrond
And all it would take is a lobotomised, redistributable, license free client so anyone can pull o/s software from bk repos.
Larry, ain't that what you plan to do with bkbits? To be able to pull regular patches.
No binaries, just a simple URL.
Sam
Quoted 6 lines · Sam Ravnborg
Quoted 3 lines · Andrew Walrond
And all it would take is a lobotomised, redistributable, license free client so anyone can pull o/s software from bk repos.
Larry, ain't that what you plan to do with bkbits? To be able to pull regular patches.
Yes.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 6 lines · Andrew Walrond
The point. You got one major o/s project hosted on bk when you ought to have them all. Loads more developers using bk at home means loads more demanding it at work.
And all it would take is a lobotomised, redistributable, license free client so anyone can pull o/s software from bk repos.
One of us is not getting it, maybe it's me. To build something like you describe is pretty easy IF AND ONLY IF all you are asking for is an update mechanism. As soon as you want revision history, diffs, rollbacks, modifiable files, etc., you have to go to real BK. Is that OK? All you want is a "keep me up to date" mechanism? No diffs, no history, it's a replacement for tarballs and patches?
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 8 lines · Larry McVoy
Quoted 6 lines · Andrew Walrond
The point. You got one major o/s project hosted on bk when you ought to have them all. Loads more developers using bk at home means loads more demanding it at work.
And all it would take is a lobotomised, redistributable, license free client so anyone can pull o/s software from bk repos.
Quoted 6 lines
One of us is not getting it, maybe it's me. To build something like you describe is pretty easy IF AND ONLY IF all you are asking for is an update mechanism. As soon as you want revision history, diffs, rollbacks, modifiable files, etc., you have to go to real BK. Is that OK? All you want is a "keep me up to date" mechanism? No diffs, no history, it's a replacement for tarballs and patches?
Yes exactly. Fundamentally I want *anybody*, without restriction, to ge able to pull and update sources from any open-source project hosted with bk.
The requirements are the equivalent functionality to:
lobobk clone ...
lobobk -r co
lobobk pull
lobobk export -r tag dest
Ie, Get a local clone of the repo, Be able to keep it updated, checkout the head version and export any particular tagged version.
and absolutely nothing else.
Not necessary, but if the cloned repo was complete enough to be recloned, It would also make the perfect tool for anyone wanting to host a coherent mirror of the repo. Which takes us full circle I believe :)
Andrew Walrond
Quoted 16 lines · Andrew Walrond
Quoted 8 lines · Larry McVoy
Quoted 6 lines · Andrew Walrond
The point. You got one major o/s project hosted on bk when you ought to have them all. Loads more developers using bk at home means loads more demanding it at work.
And all it would take is a lobotomised, redistributable, license free client so anyone can pull o/s software from bk repos.
Quoted 6 lines
One of us is not getting it, maybe it's me. To build something like you describe is pretty easy IF AND ONLY IF all you are asking for is an update mechanism. As soon as you want revision history, diffs, rollbacks, modifiable files, etc., you have to go to real BK. Is that OK? All you want is a "keep me up to date" mechanism? No diffs, no history, it's a replacement for tarballs and patches?
Quoted 6 lines
Yes exactly. Fundamentally I want *anybody*, without restriction, to ge able to pull and update sources from any open-source project hosted with bk.
The requirements are the equivalent functionality to:
lobobk clone ...
Sure.
Quoted 1 line
lobobk -r co
There are no local revision history files in lobobk, it's just a file transport.
Quoted 1 line
lobobk pull
Sure.
Quoted 1 line
lobobk export -r tag dest
That's
lobobk clone -r tag FROM DEST
And you of course realize that you as a BK user could code up this system with zero changes needed from us, right?
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 2 lines · Larry McVoy
And you of course realize that you as a BK user could code up this system with zero changes needed from us, right?
A client only solution that would talk to bkd? In a flash mate. But I don't think you'd like that ;)
You I'm sure mean a server side wrapper which calls on bk to extract sources and diffs and handles transport to the client. Not exactly hastle free and encouraging people to host their o/s projects with bk, is it? Probably of dubious legality as well (for scm developers).
Andrew Walrond
Quoted 7 lines · Andrew Walrond
Quoted 2 lines · Larry McVoy
And you of course realize that you as a BK user could code up this system with zero changes needed from us, right?
A client only solution that would talk to bkd? In a flash mate. But I don't think you'd like that ;)
I think that might be harder than you think but you're right, we wouldn't be too thrilled with that. If for no other reason than the amount of cursing you'd do as you figured out that our protocol is pretty ad-hoc and should be rewritten.
Quoted 4 lines
You I'm sure mean a server side wrapper which calls on bk to extract sources and diffs and handles transport to the client. Not exactly hastle free and encouraging people to host their o/s projects with bk, is it? Probably of dubious legality as well (for scm developers).
You're already a BK user and I'd happily make it clear that it is OK for you to do this work, we can have that discussion offline. As for hassle free, I don't get that comment at all. What you describe is exactly what we would do anyway. The only difference is that we could extend the bkd itself to answer these requests and you couldn't without a lot of headaches. But if you built this and wanted us to included it in the bkd, we'd look at doing that.
The points are
a) I'm not at all convinced this is going to make anyone other than you happy. They all want a BK replacement, not a tarball+patch replacement.
b) If I'm wrong, there isn't anything preventing you from building this.
Convince me that (a) is all wrong and I'll see about building it. So far, all the other people have made it clear they want all the functionality of BK, the transport, the diffs, the history, etc. Giving them a tarball/patch transport isn't like to make them happy and I'll be in another one of these conversations after having wasted a pile of engineering (which is not free, nor cheap).
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 4 lines
The points are
a) I'm not at all convinced this is going to make anyone other than you happy. They all want a BK replacement, not a tarball+patch
replacement
No. The fundamental point is:
There are a small group of people who cannot legally extract sources from o/s
projects hosted with bk. However small the group, this is unacceptible for an o/s project.
So Bk is unsuitable for general hosting of o/s, 'free and available to all' projects. They will use cvs or arch.
Thats why you should provide this facility. Not because I want it, but because you should want as many o/s projects as possible to use bk, for sound business reasons.
I think I can see granny looking hungrily at a basket of eggs, so I'm finished.
Andrew Walrond
Quoted 3 lines · Larry McVoy
The points are
a) I'm not at all convinced this is going to make anyone other than you happy. They all want a BK replacement, not a tarball+patch replacement.
As a quite irrelevant (from a kernel development point - as i don't do anything other than test / use and bug report) data point, this is somehting I would like to see, and preferably with a license that would make it possible to incluse in the mainline debian distribution. that way it would be possible for more people to test bk repository versions of software (not jsut the kernel) without having to install the full version of BK.
so all I'd like is to be able to do a get/update to the head revision of the repository, and if possible get/convert to a tagged version.
having the second would have made chasing down what version of the kernel broke my pcmcia support easier :)
cheers
Sven
Quoted 12 lines · Sven Dowideit
Quoted 3 lines · Larry McVoy
The points are
a) I'm not at all convinced this is going to make anyone other than you happy. They all want a BK replacement, not a tarball+patch replacement.As a quite irrelevant (from a kernel development point - as i don't do anything other than test / use and bug report) data point, this is somehting I would like to see, and preferably with a license that would make it possible to incluse in the mainline debian distribution. that way it would be possible for more people to test bk repository versions of software (not jsut the kernel) without having to install the full version of BK.
Quoted 5 lines
so all I'd like is to be able to do a get/update to the head revision of the repository, and if possible get/convert to a tagged version.
having the second would have made chasing down what version of the kernel broke my pcmcia support easier :)
We'd be happy to build this if there was some indication that it would actually make a lot more people happy. Examples of that would be agreement from the debian crowd to include it, find some BK flamers who say this would resolve their issues, etc.
We've been burned once by doing a bunch of work and getting beat up for it, i.e., doing the BK2CVS converter and people still aren't happy. We spend a lot of unseen time maintaining bkbits.net and the hosting machines. I'd *love* to have a better relationship with the open source world but if this is a solution for a handful of people but it does nothing for the other people then we aren't moving forward.
Just to be clear, what we are talking about is a free client which talks to a modified BK server. The client has the ability to
- get a workspace (bk clone equiv)
- get a version of the workspace as of any tag (bk clone -r equiv)
- update a workspace (bk pull equiv)
Anything more than that could be done but would be left to you to extend the client (you'd get source to the client).
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 2 lines
Just to be clear, what we are talking about is a free client which talks to a modified BK server. The client has the ability to
I just wanted to be clear on what you meant by "free". Is that free as in binary with less restrictive license than the current bk client, or "free" as in includes the source under the GPL? If the latter, you can bet your ass I'd use it. If the former, it would allow me to use it, but I can't guarantee I would.
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/
Quoted 8 lines · Ben Collins
Quoted 2 lines
Just to be clear, what we are talking about is a free client which talks to a modified BK server. The client has the ability to
I just wanted to be clear on what you meant by "free". Is that free as in binary with less restrictive license than the current bk client, or "free" as in includes the source under the GPL? If the latter, you can bet your ass I'd use it. If the former, it would allow me to use it, but I can't guarantee I would.
It would be free as in w/ source, probably BSD rather than GPL but some license you'd like. About the only thing we'd need to worry about is our commercial customers taking this and using it as a way to not pay for some seats so there is some chance that we'd want to put in some hook there, I'd have to think about that before promising anything.
I'm curious as to why you would think this is better than the CVS gateway. The CVS gateway is actually a really nice thing. The whiners think we have somehow hamstrung the data in the gateway but that's only because they haven't looked at the data, if they had done a careful comparison then they'd know it's all in there.
So what's the attraction? Having a client that will work with any BK server? Do you realize that the client is just a way to get at the head? And tagged releases? It doesn't have 1/10th the functionality of BK itself.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Larry,
Quoted 5 lines · Larry McVoy
It would be free as in w/ source, probably BSD rather than GPL but some license you'd like. About the only thing we'd need to worry about is our commercial customers taking this and using it as a way to not pay for some seats so there is some chance that we'd want to put in some hook there, I'd have to think about that before promising anything.
to my mind this would be brilliant, but i don't remember every whinging about bk ;).
The only requirements that would need to be fulfilled for it to go into debian, would be source, a licence that does not restrict the usage of the code/ package, and a distinct lack of invariant sections in the license. (a real debian developer can probably elaborate better than i)
Quoted 6 lines
I'm curious as to why you would think this is better than the CVS gateway. The CVS gateway is actually a really nice thing. The whiners think we have somehow hamstrung the data in the gateway but that's only because they haven't looked at the data, if they had done a careful comparison then they'd know it's all in there.
last time i tried the cvs gateway, i think i had trouble getting a full shadow.. I should try again really, but i would hope that the openBKClient could be faster, better and more modern (oh, and sexy too)
(and would mean that you don't need the cvs gateway anymore!)
Quoted 4 lines
So what's the attraction? Having a client that will work with any BK server? Do you realize that the client is just a way to get at the head? And tagged releases? It doesn't have 1/10th the functionality of BK itself.
yep. and for me, until i do some actual kernel development (unlikely as i just can't find the time), this is all i think i want - i should be able to do a bit more testing this way.
cheers
Sven
I'm likely to get a slap for this one, but....
Quoted 6 lines · Larry McVoy
I'm curious as to why you would think this is better than the CVS gateway. The CVS gateway is actually a really nice thing. The whiners think we have somehow hamstrung the data in the gateway but that's only because they haven't looked at the data, if they had done a careful comparison then they'd know it's all in there.
Since you've already done all the work for bk2cvs, why not add the functionality to bkd which would allow a simple client to do
lobobk cvsclone
and
lobobk cvspull
Ie be able to clone and update a local cvs repo from bkd? This would have the added advantage that users (kernel testers) could get any tagged versions from their local repo using cvs, rather than requiring diff trasmission from bkd to convert to another version. The client would be very simple too.
Obviously the local cvs repo would be read-only, and only useful for people to fetch sources. Bitkeeper would be required for development work. It would make the perfect mirroring tool aswell.
And when you've finished that, I'd like a moon rocket please. GPL, of course ;)
Andrew Walrond
Quoted 13 lines · Andrew Walrond
I'm likely to get a slap for this one, but....
Quoted 6 lines · Larry McVoy
I'm curious as to why you would think this is better than the CVS gateway. The CVS gateway is actually a really nice thing. The whiners think we have somehow hamstrung the data in the gateway but that's only because they haven't looked at the data, if they had done a careful comparison then they'd know it's all in there.
Since you've already done all the work for bk2cvs, why not add the functionality to bkd which would allow a simple client to do
Quoted 8 lines
lobobk cvsclone
and
lobobk cvspullIe be able to clone and update a local cvs repo from bkd? This would have the added advantage that users (kernel testers) could get any tagged versions from their local repo using cvs, rather than requiring diff trasmission from bkd to convert to another version. The client would be very simple too.
Presumably because he's said several times that the bk2cvs gateway software is based on (and requires) the commercial version of bk. Not to mention that the way it generates repositories isn't really compatible with this model.
Signature · 2 lines
Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
Quoted 5 lines · Daniel Jacobowitz
Presumably because he's said several times that the bk2cvs gateway software is based on (and requires) the commercial version of bk. Not to mention that the way it generates repositories isn't really compatible with this model.
I was (obviously?) assuming that the bk(d) was the commercial version, but I don't see how that would affect the client from being o/s?
And why is this different from bk2cvs? Because then I have to rsync the cvs repo with all the problems (discussed at length in this thread) of getting a coherent local copy of the repo.
I guess it all comes back to my wanting to host my (commercial and open- source) public code repositories with bk, but have to guarantee 100% access to my 'users'. 99% Isn't good enough.
I'm not, Daniel, a FSF/GPL whiner, and do not appreciate being labelled as such.
Andrew Walrond
Quoted 7 lines · Andrew Walrond
Quoted 5 lines · Larry McVoy
I'm curious as to why you would think this is better than the CVS gateway. The CVS gateway is actually a really nice thing. The whiners think we have somehow hamstrung the data in the gateway but that's only because they haven't looked at the data, if they had done a careful comparison then they'd know it's all in there.
Quoted 6 lines
Since you've already done all the work for bk2cvs, why not add the functionality to bkd which would allow a simple client to do
lobobk cvsclone
and
lobobk cvspull
Because the translation process is hugely CPU intensive. It takes something like 6 hours to do the 2.5 tree on 2.2Ghz Athlon with a gig of ram. And it uses every bit of that ram, that's my desktop machine and _everything_ is paged out when I come in in the morning.
I agreed to the BK2CVS stuff as a way of ensuring that people had the data in a format that they could use without BK and was useful. I'm willing to do that for each main tree of each major project (i.e., if XFree86 or something like that moved to BK we'd agree to do the CVS conversion so that there was no lockin).
But doing it for every branch of every tree is nuts unless you are donating a 16 way with a zillion gigs of ram. And a zillion disk arms, this thrashes the heck out of the disk.
Quoted 2 lines
And when you've finished that, I'd like a moon rocket please. GPL, of course ;)
Yeah, and I'd like all the open source developers of the world to acknowledge that I'm a good guy and I'm trying to help. In writing, of course ;)
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Hi Larry
Quoted 5 lines · Larry McVoy
Because the translation process is hugely CPU intensive. It takes something like 6 hours to do the 2.5 tree on 2.2Ghz Athlon with a gig of ram. And it uses every bit of that ram, that's my desktop machine and _everything_ is paged out when I come in in the morning.
But once you've done it, incoming changesets are then added incrementally, right? You don't just convert the tree once a day?
So you'd just need to maintain two copies of the cvs tree, one which currently available for coherent transmission to lobobk clients, and the other which can be updated, with a means of swapping them
Quoted 5 lines
I agreed to the BK2CVS stuff as a way of ensuring that people had the data in a format that they could use without BK and was useful. I'm willing to do that for each main tree of each major project (i.e., if XFree86 or something like that moved to BK we'd agree to do the CVS conversion so that there was no lockin).
But, as I described in my previous post, it also has at least one useful commercial application.
Quoted 3 lines
But doing it for every branch of every tree is nuts unless you are donating a 16 way with a zillion gigs of ram. And a zillion disk arms, this thrashes the heck out of the disk.
The 2.5 tree is <300Mb, so just stick 4Gb in your machine, the bk and cvs tree in tmpfs and, well, throw the HD away ;)
Quoted 2 lines
Quoted 2 lines
And when you've finished that, I'd like a moon rocket please. GPL, of course ;)
This was in anticipation of somebody calling me a whinging pom. And sure enough... (And yes, my antipodean mates, we are going to _stuff_ you on saturday!)
Quoted 3 lines
Yeah, and I'd like all the open source developers of the world to acknowledge that I'm a good guy and I'm trying to help. In writing, of course ;)
I think everyone who works for a living knows that already :)
Quoted 10 lines · Ben Collins
Quoted 2 lines
Just to be clear, what we are talking about is a free client which talks to a modified BK server. The client has the ability to
I just wanted to be clear on what you meant by "free". Is that free as in binary with less restrictive license than the current bk client, or "free" as in includes the source under the GPL? If the latter, you can bet your ass I'd use it. If the former, it would allow me to use it, but I can't guarantee I would.
I think he said something about providing source code. GPL would be wise to use because, for instance, BSD license would give away too much to his competitors.
Maybe this will tone down some of the whining.
Quoted 4 lines · Larry McVoy
One of us is not getting it, maybe it's me. To build something like you describe is pretty easy IF AND ONLY IF all you are asking for is an update mechanism. As soon as you want revision history, diffs, rollbacks, modifiable files, etc., you have to go to real BK. Is that OK? All you
Spec for bk-lite:
1) Binary with "no worky on other SCM" kinda license
2) update+history+diff (no rollbacks, no modifiable files, no etc...)
In that way all current users of bk2cvs, bk2svn, bk2xxx can simply do a pull from a bk repo and have they own scripts on their local machine to do their bk2xxx. It will be a lower headache for you and for kernel.org maintainers. Is it feasible ?
- Davide
Quoted 9 lines · Davide Libenzi
Quoted 4 lines · Larry McVoy
One of us is not getting it, maybe it's me. To build something like you describe is pretty easy IF AND ONLY IF all you are asking for is an update mechanism. As soon as you want revision history, diffs, rollbacks, modifiable files, etc., you have to go to real BK. Is that OK? All you
Spec for bk-lite:
Quoted 7 lines
1) Binary with "no worky on other SCM" kinda license
2) update+history+diff (no rollbacks, no modifiable files, no etc...)In that way all current users of bk2cvs, bk2svn, bk2xxx can simply do a pull from a bk repo and have they own scripts on their local machine to do their bk2xxx. It will be a lower headache for you and for kernel.org maintainers. Is it feasible ?
update, yes. history, no, use bk/web. diffs, no, use bk/web or bk. building it is certainly possible and you could do it yourself. We already built the cvs exporter which is a lot nicer than what you are asking for and building another thing for another 6 users seems pointless. If you want to pay for the engineering then contact me offline.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 5 lines · Larry McVoy
update, yes. history, no, use bk/web. diffs, no, use bk/web or bk. building it is certainly possible and you could do it yourself. We already built the cvs exporter which is a lot nicer than what you are asking for and building another thing for another 6 users seems pointless. If you want to pay for the engineering then contact me offline.
I want nothing new. A BK with only the CVS exporter that you already have will work plain fine. We do not need even 25 exports formats. Once we have your existing binary that does:
bk2cvs remote-bkrepo local-cvs-repo
would be great. All other export can be based from that with local scripts. With a little bit less restrictive license, Is it something painful for BM to do?
- Davide
Quoted 12 lines · Davide Libenzi
Quoted 5 lines · Larry McVoy
update, yes. history, no, use bk/web. diffs, no, use bk/web or bk. building it is certainly possible and you could do it yourself. We already built the cvs exporter which is a lot nicer than what you are asking for and building another thing for another 6 users seems pointless. If you want to pay for the engineering then contact me offline.
I want nothing new. A BK with only the CVS exporter that you already have will work plain fine. We do not need even 25 exports formats. Once we have your existing binary that does:
Quoted 5 lines
bk2cvs remote-bkrepo local-cvs-repo
would be great. All other export can be based from that with local scripts. With a little bit less restrictive license, Is it something painful for BM to do?
Yes. bk2cvs is not a supported product, and it is based on the commercial only version of BK. We're not giving that out for free.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 2 lines · Larry McVoy
Yes. bk2cvs is not a supported product, and it is based on the commercial only version of BK. We're not giving that out for free.
Fine then. I guess we will live with the existing CVS repo rsync from kernel.org, that is plain good for me. I was trying to find a solution to reduce headaches for BM and kernel.org maintainers ...
- Davide
Quoted 8 lines · Davide Libenzi
Quoted 2 lines · Larry McVoy
Yes. bk2cvs is not a supported product, and it is based on the commercial only version of BK. We're not giving that out for free.
Fine then. I guess we will live with the existing CVS repo rsync from kernel.org, that is plain good for me. I was trying to find a solution to reduce headaches for BM and kernel.org maintainers ...
It's not a headache for us to do the conversion, that's fine. I'd like to get rid of the pserver on kernel.bkbits.net because it and the SVN server beat up the machine quite a bit. So an rsync based solution sounds good to me if HPA can handle it.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Followup to: <[email protected]> By author: Larry McVoy <[email protected]> In newsgroup: linux.dev.kernel
Quoted 6 lines
It's not a headache for us to do the conversion, that's fine. I'd like to get rid of the pserver on kernel.bkbits.net because it and the SVN server beat up the machine quite a bit. So an rsync based solution sounds good to me if HPA can handle it.
Machine-resource-wise or bandwidth-wise it's not a problem. The coherency mechanism -- in particular, deploying it -- is the only issue.
-hpa
Signature · 4 lines
<[email protected]> at work, <[email protected]> in private! If you send me mail in HTML format I will assume it's spam. "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
Quoted 7 lines · Larry McVoy
Quoted 1 line · Andrew Walrond
And I still maintain that a stripped out, redistributable, clone/pull only binary tool without the restrictive license would be a real smart business move.
I'm trying to see why.
Quoted 8 lines
Our commercial customers don't care about this so there isn't any business incentive there.
The actual BK users don't care about this, they use BK.
The BK detractors aren't going to touch anything that we produce, they are convinced we're out to do them harm somehow.
So who's left?
Well, me for one. (I don't use BK, but I also don't complain about it. ;) ) The reason I don't use it, is I've been playing around in the SCM space as an interesting diversion/exploration/mental-exercise, and I don't want to violate your license. (Letter or spirit.)
But I've been happy using the offical release tarballs and -rmk patches, so I don't count from a business view. :)
Quoted 8 lines
And a better question is why doesn't some open source person do this? All you need to do is create a network daemon which responds to clone requests and pull requests. The clone request sends across a tarball and the client
side untars it. The pull request sends a changeset key (which was sent in
the last clone/pull) and gets a tarball of new/changed files, the new top of trunk changeset key, and a list of renames. Actually the easier way is to do it more like diff does, for each file that has been changed, send
across a "delete this file and any directories the deletion leaves empty"
list, and then you unpack the tarball on top of the tree.
Quoted 8 lines
This would be easy to build but I don't see it solving anything. All it does is act as a replacement for rsync. It doesn't have revision history, you can't do diffs, etc. As soon as this exists, people will ask you for all the other features. Which is why I don't want to build it, I don't want to get sucked into the "please rebuild BK as a GPLed product" business.
What am I missing?
If (as I understand the above to imply[1]) the daemon responding to requests runs BK locally, then those who can't run BK can't run the daemon, and so the above doesn't actually solve their problem. (They would have to find someone willing to accept the license to run the daemon and test it during development, and there are no guarrantees there.)
Anyway, I'm just adding noise... I'm happy using the tarballs, etc., and I'm glad you've improved Linus's development life.
C-ya,
Eli
[1] If you are saying that daemon talks the BK protocol, then my point no longer stands. --------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
Am Don, den 13.11.2003 schrieb Larry McVoy um 17:27:
Quoted 2 lines
I suppose it sounds like we don't want to give out more free engineering but let's put things into perspective. The CVS server has about 6 users.
I really do believe you about the amount of users. That's probably because CVS sucks rocks and everyone complaining about it doesn't make it better. Shut it down and we'll all have a merrier live.
What really makes me mad though is that there's no permanent way to retrieve and update current kernels at the moment for those who don't want or cannot use BK. I'm waiting for quite some period to get SVN back online so I can continue the merging work I've been trying to do. And yes, I'm one of those fools who are stuck behind a huge 64k pay-big-bucks-for-the-minute and really have troubles changing back and forth between several mechanisms to get current versions (ftp/rsync/CVS/SVN), especially since Linus obviously doesn't release patches as frequently anymore since he uses BK. :(
Signature · 2 lines
Servus,
DanielQuoted 7 lines · Daniel Egger
Am Don, den 13.11.2003 schrieb Larry McVoy um 17:27:
Quoted 3 lines
I suppose it sounds like we don't want to give out more free engineering but let's put things into perspective. The CVS server has about 6 users.
Quoted 8 lines
I really do believe you about the amount of users. That's probably because CVS sucks rocks and everyone complaining about it doesn't make it better. Shut it down and we'll all have a merrier live.
What really makes me mad though is that there's no permanent way to retrieve and update current kernels at the moment for those who don't want or cannot use BK.
Actually, at http://www.kernel.org/ there is a link to daily snapshots. There are also changesets generated every couple of hours at the "C" link at the right of the page.
Even if Linus doesn't release as often (doesn't he? I don't know), this is surely much better than pre BK. Maybe I didn't understand you right?
Best regards,
Nick
Am Fre, den 14.11.2003 schrieb Nick Piggin um 10:56:
Quoted 6 lines
Actually, at http://www.kernel.org/ there is a link to daily snapshots. There are also changesets generated every couple of hours at the "C" link at the right of the page.
Even if Linus doesn't release as often (doesn't he? I don't know), this is surely much better than pre BK. Maybe I didn't understand you right?
Seems so. I assume you missed the "bandwidth constraint" part. Fetching a whole snapshot every day is not even close to workable. The snapshots in patch form are nice however patching forth and back is not really an option. If svn doesn't get back up I'd be tempted to use rsync and use vendor branches in my own SVN repository but this also seems far from optimal to me. rsync alone doesn't cut it because there's no version management and I've lost quite a few patches due to an not thoroughly considered rsync use.
Signature · 2 lines
Servus,
DanielQuoted 12 lines · Daniel Egger
Am Fre, den 14.11.2003 schrieb Nick Piggin um 10:56:
Quoted 8 lines
Actually, at http://www.kernel.org/ there is a link to daily snapshots. There are also changesets generated every couple of hours at the "C" link at the right of the page.
Even if Linus doesn't release as often (doesn't he? I don't know), this is surely much better than pre BK. Maybe I didn't understand you right?
Quoted 9 lines
Seems so. I assume you missed the "bandwidth constraint" part. Fetching a whole snapshot every day is not even close to workable. The snapshots in patch form are nice however patching forth and back is not really an option. If svn doesn't get back up I'd be tempted to use rsync and use vendor branches in my own SVN repository but this also seems far from optimal to me. rsync alone doesn't cut it because there's no version management and I've lost quite a few patches due to an not thoroughly considered rsync use.
There are compressed incremental patches of the snapshots available:
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/incr/
They average maybe 150KB per day.
Nick
Quoted 4 lines · Nick Piggin
There are compressed incremental patches of the snapshots available:
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/incr/
They average maybe 150KB per day.
I'd hope they average a _lot_ less lately. I've been trying to be an absolute _bastard_ when it comes to patches.
Yeah, I just looked. Lately they've been averaging about 3-4kB per day.
And the sick thing is, I'm still not satisfied. I want it to become an absolute _trickle_ of one-liners that fix real bugs.
So if you want incrementals and have a 1200 baud modem - be happy. The last week or so has been a pretty good week.
Linus
Quoted 2 lines · Linus Torvalds
I'd hope they average a _lot_ less lately. I've been trying to be an absolute _bastard_ when it comes to patches.
So it didn't change much. You've *always* been a bastard when it comes to patches :-)
- Davide
Quoted 3 lines · Davide Libenzi
So it didn't change much. You've *always* been a bastard when it comes to patches :-)
*Snif*. I don't know what to say. Thank you. Your kind words make it all worth it.
Linus "kernel bastard, and proud of it" Torvalds
Quoted 4 lines · Linus Torvalds
*Snif*. I don't know what to say. Thank you. Your kind words make it all worth it.
Linus "kernel bastard, and proud of it" Torvalds
Your welcome ;)
Davide "gotta wait big time before next patch will be merged" Libenzi
Am Sam, den 15.11.2003 schrieb Nick Piggin um 04:02:
Quoted 3 lines
There are compressed incremental patches of the snapshots available:
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/incr/
They average maybe 150KB per day.
Me likee. Thanks a lot, this is a missing piece in the puzzle. With this I can easily build my own repository.
Signature · 2 lines
Servus,
DanielHi!
Quoted 10 lines
Quoted 9 lines
Quoted 5 lines
I could make some comment about this being a good example of one of the zillion little problems we've had to solve but if I go there it's going to start a flame war. So I won't. I will note that none of the solutions proposed come close to being acceptable, they all fail on NFS and on SMB shares. And they don't cascade properly as HPA has noted.
Absolutely. Bk is, undeniably, brilliant, and would solve all these problems at a stroke, except that the open source community cannot with good conscience exclude *anyone* from being able to access the sources.
Quoted 5 lines
But noone is excluded from having access to the sources.
I suppose it sounds like we don't want to give out more free engineering but let's put things into perspective. The CVS server has about 6 users.
I do not know where you got that number, but its wrong. You cited 6 unique IP addresses... I certainly did updates from more than _that_. But I use time rsync -zav --delete rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.5 ., so I'm probably not counted in your statistics.
Pavel
Signature · 2 lines
When do you have a heart between your knees? [Johanka's followup: and *two* hearts?]
Quoted 9 lines · Pavel Machek
Quoted 3 lines
I suppose it sounds like we don't want to give out more free engineering but let's put things into perspective. The CVS server has about 6 users.
I do not know where you got that number, but its wrong. You cited 6 unique IP addresses... I certainly did updates from more than _that_. But I use time rsync -zav --delete rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.5 ., so I'm probably not counted in your statistics.
"CVS server", Pavel. That means people talking to the pserver process, not rsync.
Signature · 2 lines
--- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
Quoted 2 lines · Andrew Walrond
Seriously though; There isn't another way that I can see for mirroring cvs repos coherently, unless cvsup does something clever? Anyone know?
cvsup does something clever.
For non-CVS repositories, it uses the "rsync" algorithm.
For CVS repositories, it will do per-change updates.
I'm not sure what it does if a change disappears from the source (haven't tried that yet), but I do know that if you are careful enough to avoid creating conflicting revision numbers in the mirror, you can *commit* to it as well.
I'm using cvsup for mirroring a CVS repository at work, and it's worked very well (and is remarkably low load).
I believe the "mirror consistency" problem isn't solved by this unfortunately, but considering that there are mirrors not using rsync, I have a feeling that it's not truly solvable, entirely.
I think I can provide an example set of configuration files for cvsup now that I've configured it 3 times, if anyone is interested.
Signature · 2 lines
Ryan Anderson sometimes Pug Majere