Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-28 Thread Raphael Hertzog
On Mon, 28 Aug 2006, Adeodato Simó wrote: * Brian May [Mon, 28 Aug 2006 13:22:55 +1000]: Adeodate Also, do you remember having root Adeodato bzr as root? Huh? Sorry, that should have read: do you remember having *run* bzr as root. It's the most likely cause for those .pyc

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-28 Thread Josselin Mouette
Le dimanche 27 août 2006 à 19:12 +0200, Adeodato Simó a écrit : bzrtools 0.9 does not put files under /usr/lib/python2.4, since it uses python-support; and its maintainer scripts for 0.9 did not bytecompile the modules, so the most plausible explanation for .pyc files in /usr/lib/python2.4

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-27 Thread Brian May
Adeodato == Adeodato =?utf-8?B?U2ltw7M=?= [EMAIL PROTECTED] writes: Robert Could you please run 'bzr upgrade' while using bzr Robert 0.9rc1. If my guess at your situation is right this will Robert take a while to run, but correct your performance issues. Did I do something

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-27 Thread Adeodato Simó
Version: 0.9-1 * Brian May [Sun, 27 Aug 2006 17:43:24 +1000]: Robert Could you please run 'bzr upgrade' while using bzr Robert 0.9rc1. If my guess at your situation is right this will Robert take a while to run, but correct your performance issues. Did I do something wrong?

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-27 Thread Brian May
Adeodato == Adeodato =?utf-8?B?U2ltw7M=?= [EMAIL PROTECTED] writes: Adeodato Hm. I'd say that you have .pyc files left in: Adeodato Adeodato /usr/lib/python2.4/site-packages/bzrlib/plugins/bzrtools Adeodato Can you check, please? Yes, see below. Adeodate Also, do you

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-27 Thread Adeodato Simó
* Brian May [Mon, 28 Aug 2006 13:22:55 +1000]: Adeodate Also, do you remember having root Adeodato bzr as root? Huh? Sorry, that should have read: do you remember having *run* bzr as root. It's the most likely cause for those .pyc files to be there, since bzrtools did not. Thanks,

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-27 Thread Brian May
Adeodato == Adeodato =?utf-8?B?U2ltw7M=?= [EMAIL PROTECTED] writes: Adeodato Sorry, that should have read: do you remember having Adeodato *run* bzr as root. It's the most likely cause for Adeodato those .pyc files to be there, since bzrtools did not. No - I don't recall running

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-26 Thread Brian May
Robert == Robert Collins [EMAIL PROTECTED] writes: Robert On Sun, 2006-08-06 at 12:01 +1000, Brian May wrote: Curiously though, the problems continue even after the archive appears to be converted successfully - if I do a diff operation, it reports all files as deleted, but if

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-26 Thread Adeodato Simó
* Brian May [Sun, 27 Aug 2006 13:53:01 +1000]: Robert == Robert Collins [EMAIL PROTECTED] writes: Robert On Sun, 2006-08-06 at 12:01 +1000, Brian May wrote: Curiously though, the problems continue even after the archive appears to be converted successfully - if I do a diff

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-12 Thread Brian May
Robert == Robert Collins [EMAIL PROTECTED] writes: Robert On Sun, 2006-08-06 at 12:01 +1000, Brian May wrote: Curiously though, the problems continue even after the archive appears to be converted successfully - if I do a diff operation, it reports all files as deleted, but

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-12 Thread Lars Wirzenius
la, 2006-08-12 kello 15:59 +1000, Brian May kirjoitti: Are there any Debian packages of 0.9rc1 available? http://packages.debian.org/unstable/devel/bzr says 0.9~rc1-1. (Lookup time: about ten seconds. :) -- On a clear disk, you seek forever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED]

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-12 Thread Robert Collins
On Sat, 2006-08-12 at 15:59 +1000, Brian May wrote: Robert == Robert Collins [EMAIL PROTECTED] writes: Robert On Sun, 2006-08-06 at 12:01 +1000, Brian May wrote: Curiously though, the problems continue even after the archive appears to be converted successfully - if I do a

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-06 Thread Robert Collins
On Sun, 2006-08-06 at 12:01 +1000, Brian May wrote: Curiously though, the problems continue even after the archive appears to be converted successfully - if I do a diff operation, it reports all files as deleted, but if I try to revert it, it slows to a grinding halt. Could you please run

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-05 Thread Robert Collins
On Sat, 2006-08-05 at 10:58 +1000, Brian May wrote: Robert == Robert Collins [EMAIL PROTECTED] writes: Robert Are you doing conversions from SVN? Current bzr uses 20MB Robert of ram to do a native branch operation in similar Robert circumstances. (bug report gets fixed, new at

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-05 Thread Brian May
Robert == Robert Collins [EMAIL PROTECTED] writes: Robert Its likely to be a different bug - the conversion approach Robert used for svn/baz is very different. That said, conversion Robert from $any system is going to use more memory than native Robert bzr operations, simply

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-04 Thread Brian May
Robert == Robert Collins [EMAIL PROTECTED] writes: Robert Are you doing conversions from SVN? Current bzr uses 20MB Robert of ram to do a native branch operation in similar Robert circumstances. (bug report gets fixed, new at 11 :)). No, this was a conversion from baz. Might be the

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-03 Thread Otavio Salvador
Robert Collins [EMAIL PROTECTED] writes: bzr is also working on a high performance server at the moment, which will operate over either a socketpair - i.e. tunnelling via ssh (which can still be done without granting shell access), or over plain http via an apache rewrite rule. Is it already

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-03 Thread Robert Collins
On Thu, 2006-08-03 at 08:27 -0300, Otavio Salvador wrote: Robert Collins [EMAIL PROTECTED] writes: bzr is also working on a high performance server at the moment, which will operate over either a socketpair - i.e. tunnelling via ssh (which can still be done without granting shell access),

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-03 Thread Otavio Salvador
Robert Collins [EMAIL PROTECTED] writes: On Thu, 2006-08-03 at 08:27 -0300, Otavio Salvador wrote: Robert Collins [EMAIL PROTECTED] writes: bzr is also working on a high performance server at the moment, which will operate over either a socketpair - i.e. tunnelling via ssh (which can

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-03 Thread Brian May
Adeodato == Adeodato =?utf-8?B?U2ltw7M=?= [EMAIL PROTECTED] writes: Adeodato But if you have a set of equal developers, bzr can be Adeodato also used in a very similar way to Subversion, where all Adeodato commits go to a central repository, and nobody has to Adeodato collect

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-03 Thread Robert Collins
On Fri, 2006-08-04 at 09:56 +1000, Brian May wrote: For documentation on checkouts and bound branches, see http://bazaar-vcs.org/CheckoutTutorial http://bazaar-vcs.org/BzrUsingBoundBranches However, I am not convinced the following paragraph in the first page is correct: Getting a

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-02 Thread Adeodato Simó
* Otavio Salvador [Tue, 01 Aug 2006 15:43:56 -0300]: Adeodato Simó [EMAIL PROTECTED] writes: Then each developer can prepare a set of changes offline, do all the branching, merging, commiting and uncommiting (gotta love that) that they want, and when they're done, do e.g.: % bzr push

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-02 Thread Otavio Salvador
Adeodato Simó [EMAIL PROTECTED] writes: * Otavio Salvador [Tue, 01 Aug 2006 15:43:56 -0300]: Adeodato Simó [EMAIL PROTECTED] writes: Then each developer can prepare a set of changes offline, do all the branching, merging, commiting and uncommiting (gotta love that) that they want, and

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-02 Thread Christoph Haas
On Wednesday 02 August 2006 21:44, Otavio Salvador wrote: Adeodato Simó [EMAIL PROTECTED] writes: * Otavio Salvador [Tue, 01 Aug 2006 15:43:56 -0300]: Adeodato Simó [EMAIL PROTECTED] writes: Then each developer can prepare a set of changes offline, do all the branching, merging,

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-02 Thread Roland Mas
Adeodato Simó, 2006-08-02 21:20:09 +0200 : % bzr push sftp://costa.debian.org/bzr/pkg-xiph/vorbis-tools [...] Ask in #alioth. Note, however, that TTBOMK still does not offer HTTP access, so if you want that, better stick to htdocs for a while. I hope to be able to bribe buxy to provide

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-02 Thread Robert Collins
On Wed, 2006-08-02 at 22:29 +0200, Christoph Haas wrote: That's in fact an issue that made me feel sceptical about bzr, darcs and mercury. All of them require a shell account or some scripting through a special mail address to commit changes. And it's not only the recent kernel

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-01 Thread Adeodato Simó
* Adeodato Simó [Tue, 01 Aug 2006 20:31:37 +0200]: they want, and when they're done, do e.g.: % bzr push sftp://costa.debian.org/bzr/pkg-xiph/vorbis-tools Forgot to add that it can be even _identical_ to subversion, in the sense that you don't have to commit locally, and then push. Just

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-01 Thread martin f krafft
also sprach Adeodato Simó [EMAIL PROTECTED] [2006.08.01.1936 +0100]: Forgot to add that it can be even _identical_ to subversion, in the sense that you don't have to commit locally, and then push. Just make a checkout (refer to the bzr docs), and every commit you make will go to the main repo

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-01 Thread Otavio Salvador
Adeodato Simó [EMAIL PROTECTED] writes: Then each developer can prepare a set of changes offline, do all the branching, merging, commiting and uncommiting (gotta love that) that they want, and when they're done, do e.g.: % bzr push sftp://costa.debian.org/bzr/pkg-xiph/vorbis-tools We're

Re: centralized bzr (Re: Successful and unsuccessful Debian development tools)

2006-08-01 Thread Robert Collins
On Tue, 2006-08-01 at 19:44 +0100, martin f krafft wrote: also sprach Adeodato Simó [EMAIL PROTECTED] [2006.08.01.1936 +0100]: Forgot to add that it can be even _identical_ to subversion, in the sense that you don't have to commit locally, and then push. Just make a checkout (refer to the