asterisk 1.2.0-0beta1

[Mark Purcell]

On Sunday 09 October 2005 02:06, Tzafrir Cohen wrote:
> > > >   Which means that when we want to upload released 1.2.0, we will
> > > > have to use another trick or mak epoch 2: For example, something as
> > > > easy as 1:1.2.0.beta1.dfsg-1 will work (as final will be
> > > > 1:1.2.0.dfsg-1 and d > b) Anyway, dpkg --compare-versions is your
> > > > friend in this situations.

Correct. Lets not use epoch's as they are a nasty hack ;(

Versioning for asterisk should go as follows:

1:1.2.0.beta1.dfsg-1	-> experimental
1:1.2.0.beta1.dfsg-2	-> experimental (if debian makes changes)
1:1.2.0.beta2.dfsg-1	-> experimental (if upstream makes another beta release)
1:1.2.0.rc1.dfsg-1		-> experimental (if upstream makes a RC release)
1:1.2.0.rc2.dfsg-1		-> experimental
[...]
1:1.2.0.dfsg-1			-> unstable (when upstream makes final release)
1:1.2.0.dfsg-2			-> unstable (when debian makes another release)

> > > This works for Asterisk. What about libpri and zaptel? create a .dfsg
> > > tarball for them as well? Without the .dfsg this fails:

But we don't want to use .dfsg unles we change the upstream tarballs.

Unfortunatly I made a mistake uploading libpri & zapel (1.2.0-0beta1-1) to 
experimental and since it is already uploaded we have to live with it until 
we can release an unstable version to fixup numbering.

> OK, so I'll give it a shot. libpri seems the simpler of the packages, so
> I'll start with it. I eventually used 1.1.9.0beta1-1 , which seems
> simpler.

But since zaptel  & libpri (1.2.0-0beta1-1) are already uploaded we are stuck 
with that, and anything else we upload to experimental must be greater 
than ;-(

What I propose for zaptel & libpri numbering is as follows:

1.2.0-0beta1-1		-> already uploaded to expiermenal
1.2.0-0beta1-2		-> experimental (next debian release)
1.2.0-0beta2-1		-> experimental (upstream next beta release)
1.2.0-0rc1-1		-> experimental (upstream RC release)
[...]
1.2.0-1			-> unstable (when upstream makes final release)

However as everyone has noted that :
	New version specified (1.2.0-1) is less than
	the current version number (1.2.0-0beta1-2)!  Use -b to force.

We can force this version using -b and we can upload to unstable, even though 
the unstable version is less than the experimental version. At this point 
zaptel, libpri and asterisk are back in sync version numbering wise :-)

Then to cleanup the versioning I would suggest that we upload:
1.2.0-cvs2005xxxx-1	-> experimental (to cover the post 1.2.0 release version)

Mark