Bzr plugins *must* die!
John Arbash Meinel
john at arbash-meinel.com
Thu Sep 25 14:57:03 BST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Martin Pool wrote:
> On Thu, Sep 25, 2008 at 5:27 AM, John Arbash Meinel
> <john at arbash-meinel.com> wrote:
>> Just to mention...
>> I just uploaded packages for bzrtools 1.6 and 1.7 to the ppa, for dapper,
>> gutsy, hardy and intrepid.
>> Unfortunately, I uploaded both the 1.6 and 1.7 for dapper at the same time,
>> and the ppa noticed 1.7 first, so it refused the 1.6 version... :(
> Well, unless <https://bugs.launchpad.net/soyuz/+bug/209515> has been
> silently fixed, it would have made no difference - the 1.6 version
> would be discarded when you made the 1.7 upload.
I'm pretty sure it has been. I seem to remember a post on another list
about it. And if you look here:
You can see the meta-info is still around. Though looking closer I see a:
Removed from disk on 2008-08-27.
On the entries, so they may not be there at all.
>> It seems reasonable enough to package bzrtools when we release bzr, since
>> there *is* a tight coupling (probably tighter than strictly necessary.)
> I believe the bzrtools code (separate from the packaging) insists on a
> perfect match. Unless/until that's relaxed, its good to represent it
> in the packaging level too. As long as we package them at the same
> time, and as long as there are not substantial periods where there's
> no bzrtools release that works with the current bzr release, we should
> be good.
I believe if it sees "dev" it gives a 1 version slack (so you can use
bzrtools 1.7 with bzr.dev 1.8-dev). But otherwise, yes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar