[Pkg-bazaar-maint] location for new uploads

Reinhard Tartler siretart at tauware.de
Fri May 4 11:02:16 UTC 2007


James Westby <jw+debian at jameswestby.net> writes:

> On (30/04/07 22:49), Wouter van Heyst wrote:
>> There is something to be said for releasing a 0.16 for easier matching
>> of bzr and it's plugins, but lets test first and then decide if it turns
>> out it's compatible.
>
> It wasn't compatible, even with 0.15 (#421900). I have fixed this, and
> also included the start of a testsuite that I have been working on. It
> tests the mechanics quite well, but doesn't test any of the logic yet, I
> need some more refactoring to do that. It should help by exercising all
> of the builders though.
>
> I have released version 0.16 to
>
>   http://bazaar.launchpad.net/~bzr-builddeb-hackers/bzr-builddeb/builddeb.0.16
>
> If I make anymore changes it will be a 0.16.1.
>
> I set the maintainer to pkg-bazaar.

I have a question regarding the version numbering. I'd like to upload
this package to ubuntu, since we already have 0.16 there
(hrmpf). However, it shouldn't be numbered as 0.16, since we need to
indicate that this is not the one intended for debian. In order to be
able to sync from debian in ubuntu, we need to choose a version number
which is lower than 0.16.

If bzr was a non-native package, we could use 0.16-1 for debian, and
0.16-0ubuntu1 for the first ubuntu upload. There are AFAIK no real
guidelines how to handle it with native package.

Before I go ahead and upload something to ubuntu with a version number
of 0.16~ubuntu1 (which I don't think is particulary pretty), I'd like to
ask the pkg-bazaar team for input on this.  Is there any particular
reason why bzr-builddeb doesn't release an 'upstream' tarball, so that
we can use non-native version numbering?

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4



More information about the Pkg-bazaar-maint mailing list