Bug#403750: jabberd2: New upstream release
tag 403750 patch tag 402498 patch tag 406459 patch tag 324829 patch tag 386900 patch thanks Hi, I made very experimental packages of jabberd 2.1.1. They are available here: http://mentors.debian.net/debian/pool/main/j/jabberd2 Please note that they have a few warts that need to be fixed: *SASL is not tested. *stat overrides should be removed on upgrade. However I have tested basic functionality with Kopete and it seems to work. I have a few other ideas about this package. First, I think we should build one binary package with support for all database and authentication options. This would simplify packaging a lot, for the price of a few additional library dependencies, which is not so bad. (And if you want to avoid it, then the proper solution is to put the db code in loadable modules à la freeradius.) What do you think, should I give it a try? Also the packages require some cleanup to get rid of the dozens of lintian errors and warnings. Regards, Marcus jabberd2 (2.1-1~unreleased.1) experimental; urgency=low * New upstream version. (Closes: #403750) - SASL support included. (Closes: #402498) * Don't install irrelevant README and outdated NEWS files. (Closes: #406459) * Don't depend on jabber-common. (Closes: #324829) * debian/control: - Bump standards-version and compat level. - Add dependencies on libexpat1-dev and libsasl2-dev. - Improved and updated package descriptions. * debian/*.postinst: Remove the stat overrides, install directories with correct permissions instead. (Closes: #386900) -- Marcus Better [EMAIL PROTECTED] Sun, 14 Jan 2007 13:58:10 +0100 pgpY1kVkLkYto.pgp Description: PGP signature
Bug#403750: jabberd2: New upstream release
Marcus Better wrote: I have a few other ideas about this package. First, I think we should build one binary package with support for all database and authentication options. This would simplify packaging a lot, for the price of a few additional library dependencies, which is not so bad. (And if you want to avoid it, then the proper solution is to put the db code in loadable modules à la freeradius.) What do you think, should I give it a try? I wouldn't like to install a package requiring me to install the libmysql* mess. I'm using PostgreSQL, so I don't need, and would like to avoid, any other DB client libs. pgphB21pTlcio.pgp Description: PGP signature
Bug#403750: jabberd2: New upstream release
I wouldn't like to install a package requiring me to install the libmysql* mess. I'm using PostgreSQL, so I don't need, and would like to avoid, any other DB client libs. Actually jabberd2 only supports PostgreSQL nowadays (since 2.1), so you are lucky... :) pgpYedMDsnWXn.pgp Description: PGP signature
Bug#403750: jabberd2: New upstream release
Julian Mehnle wrote: Marcus Better wrote: I have a few other ideas about this package. First, I think we should build one binary package with support for all database and authentication options. This would simplify packaging a lot, for the price of a few additional library dependencies, which is not so bad. (And if you want to avoid it, then the proper solution is to put the db code in loadable modules à la freeradius.) What do you think, should I give it a try? I wouldn't like to install a package requiring me to install the libmysql* mess. I'm using PostgreSQL, so I don't need, and would like to avoid, any other DB client libs. This is precisely why I originally split the packaging the way I did. Unfortunately, I no longer have the time to maintain Jabberd2 as it should be. I will be putting the package up for adoption within the next few days as time allows. -- Jamin W. Collins -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
