official janus_patch4 ready

Jose Carlos Garcia Sogo jsogo@debian.org
Mon, 9 Aug 2004 14:02:21 +0200


--XMCwj5IQnwKtuyBG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 09, 2004 at 09:24:23PM +1000, Mark Purcell wrote:
> On Mon, Aug 09, 2004 at 10:40:01AM +0200, Kilian Krause wrote:
> > Hi,
> >=20
> > the new and shiny packs are ready to be rolled out onto the mirrors.=20
> > http://www.akademy.org/~kk/deb/sid/i386/
> >=20
> > I hope that pwlib has now a fix that's making it compile on alpha (make
> > optshared worked already).. we'll see..
> >=20
> > Again: whoever reads this first, uploading would be nice.=20
>=20
>=20
> Killian,
>=20
> Just spent all morning downloading the -3 debs for signing and was about
> to upload when I saw this message. They were dated 8 Aug.
>=20
> After your message here it appears that the -3 debs are now dated 9 Aug.
>=20
> I take it they are not the same as yesterday's -3 debs :-(
>=20
> Could I ask that you bump the debian version number when making changes.
>=20
> Or have I got this completly wrong.

 Well, the problem here is that while he was preparing packages for
 janus_patch3 (-3) janus_patch4 appeared and he just packaged them. As
 we have such a strange numbering and versioning method (and problems),
 janus_patch3 and janus_patch4 have the same upstream version number,
 which shouldn't. I mean, if we had a "sane" upstream, patch3 should
 have been 1.6.6.3 and patch4 1.6.6.4 or so. Of curse we should have had
 also a sane soname versioning scheme, because our main problem is going
 from 1.6.6 to 1.6.7, as we're using version as soname, because of all
 those ABI/API breakages among versions which shouldn't break that
 stuff.

 So basically Kilian has made the packages well by not changing the
 version (as they weren't uploaded yet to Sid), but as the same time,
 that's not really optimal.

 Anyway, don't worry about the packages. I'm going to upload them right
 now.

 Cheers,

BTW, I have not yet any idea on your problem in trunk/ for asterisk.
BTW2, I'd like you too take a look at tags/2.0.8-2.1/ which is our gnugk NMU
(as you haven't yet changed maintainer for that package)

--=20
Jose Carlos Garcia Sogo
   jsogo@debian.org

--XMCwj5IQnwKtuyBG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBF2fNS+BYJZB4jhERAvt2AKCTaFD1C136pJjmuN3nwTsJusga6wCgn1QW
kdJUvRzotDElEYGlVfmpS/Y=
=7xE2
-----END PGP SIGNATURE-----

--XMCwj5IQnwKtuyBG--