Re: May one use ~rc1 within versions although older lintians are complaining?
Am Mittwoch, 21. März 2007 schrieb Manoj Srivastava:
> On Tue, 13 Mar 2007 15:56:44 -0300, Margarita Manterola
> > On 3/13/07, Roman Müllenschläder <email@example.com> wrote:
> >> I'm packaging for debian right now and wanted to now if I may use a
> >> version number like: 1.0.8~rc1-1 ?
> > If you use that number, the upstream version should be 1.0.8~rc1.
> > Is that the upstream number? If you want to have release candidates
> > of your _own_ package, you should do: 1.0.8-1~rc1
> Hmm? Suppose upstream version is currently 1.07 released, and
> they are planning on releasing 1.08 in the future. Now they are
> running through 1.08 release candidates, and so we have 1.08 rc1,
> soon to be followed by 1.08 rc2. The upstream version variables,
> used by them, are all at 1.08 (not 1.08 '~'.
> How do you propose the debian releases of the release
> candidates be numbered? When upstream releases, upstream releases
> shall have 1.08, 1.08.1 or 1.08-1, and so on.
The upstream currently released is 18.104.22.168. Coming is 22.214.171.124 followed by
1.0.9, if there isn't a 126.96.36.199 ;) The devel-branch therefore is 1.0.9.
So I'm only doing packages of _released_ upstreams, not of a devel-branch. As
long as the upstream is not fullfilling the needs to be sponsored and
uploaded, I do test-debs and provide them on my own repository, to let users
use them for testing purposes.
Therefore the upstream stays the same (188.8.131.52 - as long as 184.108.40.206 is not
released) but the debs change to get them "perfect". Thus having
220.127.116.11-1~rcX as versions for my 'unofficial' packages.
Debian release will be not until 18.104.22.168 and therefore with version 22.214.171.124-1.
Until that I maybe do unofficial 126.96.36.199-1~rcX again for testing and to let
debian release be 188.8.131.52-1.
So ~rcX only counts for the debian package state, not upstream.
Was that your question?
With doing these unofficial-own-repository-releases, I hope to get the
packages be tested more than I am able to do alone. Cause of 184.108.40.206-1~rcX <
220.127.116.11-1, once officially uploaded to debian, the packages get updated and
debian-release version is correct ... only thing that has to be done is
shrinking the changelog ;)