-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Nov 30, 2008 at 09:31:53PM +0100, Adeodato Simó wrote: >So, because of this, library uploads to unstable during freezes should >be done with a lot of care, and nothing which is not targetted to >$next_stable should be uploaded. A SONAME bump is simply not >acceptable.
Thanks for enlightening me. I do understand now. Unfortunately too late. :-( >So, as for what to do, please do stop for squeeze bumping the SONAME Agreed, that is (and was) my plan to implement post-lenny. >As for Lenny, the SONAME bump has to be somehow reverted, because we're >not doing a transition at this stage. Since there are no versioned >dependencies on libc-client2007b, it is possible to make >libc-client2007d Provide: libc-client2007b. As posted by Faidon, asterisk has a versioned build-dependency. I believe that this single complexity is most simple solved by a new release of the asterisk package with bumped build-dependency. >This is the easiest way forward, though it requires that we migrate the >package to testing. >But we want that anyway, since we want the security fixes in lenny. The security fixes is already contained in uw-imap 7:2007b~dfsg-3+lenny1 released through testing-security. >Can you prepare an upload doing that (add the Provides field)? >Hopefully I got all things right, and it will work. If you still - with the new(?) info on asterisk - believe this to be the proper approach, I am more than willing to release an uw-imap 7:2007d~dfsg-2 with the following change (plus changelog, off course): diff --git a/debian/control b/debian/control index 39f81ec..88763f9 100644 - --- a/debian/control +++ b/debian/control @@ -54,7 +54,7 @@ Architecture: any Depends: libc-client2007d (= ${binary:Version}), ${devlibs:Depends} Conflicts: libc-client-dev Replaces: libc-client-dev - -Provides: libc-client-dev +Provides: libc-client-dev, libc-client2007b Description: c-client library for mail protocols - development files IMAP (Internet Message Access Protocol) is a method of accessing electronic messages kept on a (possibly shared) mail server. If you need me to do more work than that, I am also willing to do so - thanks to your patient educating me, I now realize what big fuckup I've made here :-/ >Finally, regarding alpine, is there any mail record of your discussion >with the maintainer. Both the release team and the security team are >very unhappy about code duplication, so unless there's an excellent >reason to do it, we'll chip in and put on some weight on the request. See bug#460695. Rereading it, I realize that I never emphasized the security issue of code duplication, and until Marc Glisse in message#35 explicitly mentioned it I took it for granted that Asheesh already was well aware that the very cause of bug#460695 was identical code. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkzDG0ACgkQn7DbMsAkQLijSgCgnz+eKU1X/rrGQqdCO15gquM/ 9pIAn38ME3gICoJL0z1bZym2yhU8WxhI =atCa -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]