exim 3.16-3.1 and 3.16-4 (and libc6 2.1.3-13)
Robert Ramiega
Just a quick note:
Yestradys night i've upgraded my system. I saw that there is exim-3.16_3.1
(and thou i knew it was there to fix incompatibilites with libc 2.1.94 i
didn't expect it to break). This was a BIG mistake. I ended up without MTA
for more that 15 hours (exim seg faulted when trying to enter daemon mode). I
recompiled both 3.1 and 4 package fro sources to no avail. After some
twidling i got my ystem to accept messages (exim was running from inetd) but
couldn't sent messages out (exim -q crashed with signal 11).
Thankfully i found some lagged debian mirror that stil had exim-3.16_3.deb
I just wonder how did exim-3.16_3.1.deb slip out? Was it compiled against
libc6 2.1.94? Or libc6 2.1.3? (to say it loud and clear: i don;t blame anyone
for my problems! I should hold exim since i knew it was meant for libc6
package that is not available for ppc at that moment; i'm just curious =o))
(is the build daemon running again?)
--
Robert Ramiega | rob...@plukwa.net IRC: _Jedi_ | Don't underestimate
UIN: 13201047 | http://www.plukwa.net/ | the power of Source
--
To UNSUBSCRIBE, email to debian-powe...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sergio Brandano
Hi Robert,
I am using libc6 2.1.3-10, that also seems the only one available
for woody, together with exim 3.16-3.1 and I am reporting no
problems so far. Where did you get libc6 2.1.94 from? The c libs
are the most delicate thing to compile by yourself, and I would
recommend to stick with 2.1.3-10.
Cheers,
Sergio
Robert Ramiega wrote:
> Just a quick note:
> Yestradys night i've upgraded my system. I saw that there is exim-3.16_3.1
>(and thou i knew it was there to fix incompatibilites with libc 2.1.94 i
>didn't expect it to break). This was a BIG mistake. I ended up without MTA
>for more that 15 hours (exim seg faulted when trying to enter daemon mode). I
>recompiled both 3.1 and 4 package fro sources to no avail. After some
>twidling i got my ystem to accept messages (exim was running from inetd) but
>couldn't sent messages out (exim -q crashed with signal 11).
>
> Thankfully i found some lagged debian mirror that stil had exim-3.16_3.deb
>
> I just wonder how did exim-3.16_3.1.deb slip out? Was it compiled against
>libc6 2.1.94? Or libc6 2.1.3? (to say it loud and clear: i don;t blame anyone
>for my problems! I should hold exim since i knew it was meant for libc6
>package that is not available for ppc at that moment; i'm just curious =o))
>
>(is the build daemon running again?)
--
Robert Ramiega
On Tue, Oct 03, 2000 at 03:54:33PM +0100, Sergio Brandano wrote:
> I am using libc6 2.1.3-10, that also seems the only one available
> for woody, together with exim 3.16-3.1 and I am reporting no
> problems so far. Where did you get libc6 2.1.94 from? The c libs
I guess my wording is not to good (sorry English is not my native language).
Anyway i *don't* have libc6 2.1.94 installed (two days ago it was not
available) all i did was upgraded exim to 3.16-3.1 (there were some other
packages upgraded; unfortunately i don't recall which ones). I saw thread on
debian-devel on libc6 upgrades and on Intel box i simply put those packages
on hold. On my powerpc box i let dselect upgrade exim as i didn't suspect any
problems.
When i tried to run exim in daemon mode it simply segfaulted. When i put it
in inetd it started to receive messages but was crashing while processing the
queue.
All this was gone when i switched to exim 3.16-3.
> are the most delicate thing to compile by yourself, and I would
> recommend to stick with 2.1.3-10.
2.1.3-13 is in security.d.o and generally You are correct (this time i'll
wait till some of You install latest glibc and what came out of it =o))))))
--
Robert Ramiega | rob...@plukwa.net IRC: _Jedi_ | Don't underestimate
UIN: 13201047 | http://www.plukwa.net/ | the power of Source