Someone asked...
> Has anyone had any success with going to libpq5_8.3.0-1 from unstable?
Tried it. Still does not work.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: exim4
Version: 4.68-2
Followup-For: Bug #463929
Due to other packages on my machine (apache etc) I can't easily do the
libpq5 downgrade. Has anyone had any success with going to
libpq5_8.3.0-1 from unstable?
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
On 2008-02-06 "Marc F. Clemente" <[EMAIL PROTECTED]> wrote:
> On 2008-02-04 Ralph Rößner <[EMAIL PROTECTED]> wrote:
> > Just a quick confirm: Same problem for us, downgrading libpq5 to
> > version 8.2.6-1 makes the problem go away.
> On Mon, Feb 04, 2008 at 08:22:22PM +0100, Andreas Metzler wrot
On 2008-02-04 Ralph Rößner <[EMAIL PROTECTED]> wrote:
> Just a quick confirm: Same problem for us, downgrading libpq5 to
> version 8.2.6-1 makes the problem go away.
On Mon, Feb 04, 2008 at 08:22:22PM +0100, Andreas Metzler wrote:
> Is yours also amd64? I do not see this on i386.
I have two (alm
On Mon, Feb 04, 2008 at 08:22:22PM +0100, Andreas Metzler wrote:
[...]
>
> The major difference between the two pq5 versions is that the
> newer one is linked against libldap-2.4-2 itself.
Hmm, that might be a reason why something is deinitialized twice at
program exit time. Even so, there should
On 2008-02-04 Ralph Rößner <[EMAIL PROTECTED]> wrote:
> Just a quick confirm: Same problem for us, downgrading libpq5 to version
> 8.2.6-1 makes the problem go away.
> Since the segfault occurs in free(), the real cause could be anywhere,
> and libldap just happens to trip over it.
The major diff
Just a quick confirm: Same problem for us, downgrading libpq5 to version
8.2.6-1 makes the problem go away.
Since the segfault occurs in free(), the real cause could be anywhere,
and libldap just happens to trip over it.
Sincerely,
Ralph Rößner
--
Ralph Rößner
CAPCom AG < http://www.capcom.d
On Mon, Feb 04, 2008 at 02:55:38PM +0100, Marc Haber wrote:
> On Mon, Feb 04, 2008 at 01:24:35PM +, Jonathan McDowell wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0x2ba2de5c6cc0 (LWP 2944)]
> > 0x2ba2dc19eb6b in free () from /lib/libc.so.6
> > (gd
On Mon, Feb 04, 2008 at 01:24:35PM +, Jonathan McDowell wrote:
> There's a limit to what I can do as it involves breaking mail for
> people. Also it appears installing exim4-dbg forces eximon4 to be
> installed, which then drags in X11 libraries. Meh.
Agreed. I have relaxed exim4-dbg's depende
On Mon, Feb 04, 2008 at 01:42:20PM +0100, Marc Haber wrote:
> On Mon, Feb 04, 2008 at 09:33:28AM +, Jonathan McDowell wrote:
> > After upgrading libpq5 from 8.2.6-1 to 8.3~rc2-1+b1 last night I
> > started to experience exim4 segfaults; log entries like:
> >
> > 2008-02-03 23:51:21 1JLocK-
On Mon, Feb 04, 2008 at 09:33:28AM +, Jonathan McDowell wrote:
> After upgrading libpq5 from 8.2.6-1 to 8.3~rc2-1+b1 last night I started
> to experience exim4 segfaults; log entries like:
>
> 2008-02-03 23:51:21 1JLocK-PR-OM appendfile transport process returned
> non-zero status 0x000b:
Package: exim4
Version: 4.68-2
Severity: important
After upgrading libpq5 from 8.2.6-1 to 8.3~rc2-1+b1 last night I started
to experience exim4 segfaults; log entries like:
2008-02-03 23:51:21 1JLocK-PR-OM appendfile transport process returned
non-zero status 0x000b: terminated by signal 11
12 matches
Mail list logo
