Re: Recent DJB package GLibC problems
On Mon, Dec 23, 2002 at 03:32:07PM -0600, Jon Marler wrote: To all users of the official QMail and Ucspi-tcp Debian source packages: I am aware of the recent libc6 problems, and appreciate your bug reports and input. I am currently analyzing what the best course of action to take is. I am worried that if I make a quick patch to the DJB packages, that libc6 may be changed again, breaking the DJB packages again, which would require the change to be backed out. I will most likely be using the patch provided by: Jurriaan [EMAIL PROTECTED] to fix both packages, once I have confirmed that the libc6 change is permanent. Is anyone able to confirm if this recent libc6 change will be permanent? If so, as of which Debian package release was this change made permanent? (So I can correctly change the Depends: entry for the DJB source packages.) Eh? You don't understand the issue correctly. If you use errno.h (which is hopefully the fix you're talking about) then it will behave correctly; old glibc, new glibc, whatever. The change may be backed down for compatibility reasons, if we can get it to work (dubious) but that's no excuse for not doing it the right way. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Recent DJB package GLibC problems
Quoting Daniel Jacobowitz [EMAIL PROTECTED]: Eh? You don't understand the issue correctly. If you use errno.h (which is hopefully the fix you're talking about) then it will behave correctly; old glibc, new glibc, whatever. The change may be backed down for compatibility reasons, if we can get it to work (dubious) but that's no excuse for not doing it the right way. I agree that it should be fixed the right way. Once I can confirm that changing the QMail source will fix the problem, and not introduce any other bugs, I'll make the change and upload. I just didn't want to jump in too soon and make the wrong fix. If this was affecting stable, I would be more inclined to make a quicker change. Cheers! Jon - This mail sent through Click2E-Mail http://www.click2e-mail.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Recent DJB package GLibC problems
To all users of the official QMail and Ucspi-tcp Debian source packages: I am aware of the recent libc6 problems, and appreciate your bug reports and input. I am currently analyzing what the best course of action to take is. I am worried that if I make a quick patch to the DJB packages, that libc6 may be changed again, breaking the DJB packages again, which would require the change to be backed out. I will most likely be using the patch provided by: Jurriaan [EMAIL PROTECTED] to fix both packages, once I have confirmed that the libc6 change is permanent. Is anyone able to confirm if this recent libc6 change will be permanent? If so, as of which Debian package release was this change made permanent? (So I can correctly change the Depends: entry for the DJB source packages.) I have asked Garrit Pape, the maintainer of the un-official packages, what his thoughts are as well. Bugs in reference: 174005 - Ucspi-tcp-src 174045 - Qmail-src If anyone has any questions, please let me know. Cheers! Jon [EMAIL PROTECTED] - This mail sent through Click2E-Mail http://www.click2e-mail.com
Re: Recent DJB package GLibC problems
On Mon, Dec 23, 2002 at 03:32:07PM -0600, Jon Marler wrote: To all users of the official QMail and Ucspi-tcp Debian source packages: I am aware of the recent libc6 problems, and appreciate your bug reports and input. I am currently analyzing what the best course of action to take is. I am worried that if I make a quick patch to the DJB packages, that libc6 may be changed again, breaking the DJB packages again, which would require the change to be backed out. I will most likely be using the patch provided by: Jurriaan [EMAIL PROTECTED] to fix both packages, once I have confirmed that the libc6 change is permanent. Is anyone able to confirm if this recent libc6 change will be permanent? If so, as of which Debian package release was this change made permanent? (So I can correctly change the Depends: entry for the DJB source packages.) Eh? You don't understand the issue correctly. If you use errno.h (which is hopefully the fix you're talking about) then it will behave correctly; old glibc, new glibc, whatever. The change may be backed down for compatibility reasons, if we can get it to work (dubious) but that's no excuse for not doing it the right way. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
Re: Recent DJB package GLibC problems
Quoting Daniel Jacobowitz [EMAIL PROTECTED]: Eh? You don't understand the issue correctly. If you use errno.h (which is hopefully the fix you're talking about) then it will behave correctly; old glibc, new glibc, whatever. The change may be backed down for compatibility reasons, if we can get it to work (dubious) but that's no excuse for not doing it the right way. I agree that it should be fixed the right way. Once I can confirm that changing the QMail source will fix the problem, and not introduce any other bugs, I'll make the change and upload. I just didn't want to jump in too soon and make the wrong fix. If this was affecting stable, I would be more inclined to make a quicker change. Cheers! Jon - This mail sent through Click2E-Mail http://www.click2e-mail.com
Re: Recent DJB package GLibC problems
Dne po 23. of December 2002 22:32 Jon Marler napsal(a): To all users of the official QMail and Ucspi-tcp Debian source packages: I am aware of the recent libc6 problems, and appreciate your bug reports and input. I am currently analyzing what the best course of action to take is. I am worried that if I make a quick patch to the DJB packages, that libc6 may be changed again, breaking the DJB packages again, which would require the change to be backed out. I will most likely be using the patch provided by: Jurriaan [EMAIL PROTECTED] to fix both packages, once I have confirmed that the libc6 change is permanent. Is anyone able to confirm if this recent libc6 change will be permanent? If so, as of which Debian package release was this change made permanent? (So I can correctly change the Depends: entry for the DJB source packages.) Please add conflict with old qmail to libc6 package too. Think about this: On update you get new libc6 and qmail-src. libc6 is updated, qmail-src is updated but old qmail package is in the system. You can build and install new qmail deb from qmail-src (by build-qmail) but you probably can't be forced to do it right now. This can lead to big problem. -- Petr Balas (petr at balas dot cz)
