Josh: why did you do this change:
Changed in cyrus-sasl2 (Ubuntu):
status:Fix Released → Fix Committed
Are you sure you know about the bug statuses:
https://wiki.ubuntu.com/Bugs/Status ?
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Fix Committed => Fix Released
--
sasl2-bin bro
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Fix Released => Fix Committed
--
sasl2-bin broken, segfaulting during install
https://bugs.launchpad.net/bugs/323409
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in ubuntu.
(You forgot to subscribe ubuntu-main-sponsors, else it would have been a
bit quicker :-/)
--
sasl2-bin broken, segfaulting during install
https://bugs.launchpad.net/bugs/323409
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in
This bug was fixed in the package cyrus-sasl2 - 2.1.22.dfsg1-23ubuntu3
---
cyrus-sasl2 (2.1.22.dfsg1-23ubuntu3) jaunty; urgency=low
* Revert libdb-dev build dependency change introduced in the
last version, it makes everyhing crash when libdb-dev is
4.7.*. See LP: #323409
Good work, Fabien - this bug bit me too when I upgraded my server to
Jaunty.
--
sasl2-bin broken, segfaulting during install
https://bugs.launchpad.net/bugs/323409
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in ubuntu.
--
** Changed in: cyrus-sasl2 (Ubuntu)
Importance: Undecided => High
** Changed in: cyrus-sasl2 (Ubuntu)
Status: Confirmed => Triaged
--
sasl2-bin broken, segfaulting during install
https://bugs.launchpad.net/bugs/323409
You received this bug notification because you are a member of Ubunt
The problem disappears when I revert the libdb-dev build dependency to
libdb4.6-dev.
(debs are in my PPA if you want to test).
This is just a work-around, but I least, my SMTP AUTH is back.
A proper fix would be to sort this db 4.6/4.7 mess.
** Attachment added:
"cyrus-sasl2_2.1.22.dfsg1-23ubun
Thank you.
I had a closer look and all binaries are crashing almost in the same place.
I initially thought it was caused by some changes in db4.6 but strangely
enough, it works fine in Intrepid, with almost the same db4.6 (just
unrelated packaging changes).
The changes for cyrus-sasl2 between int
Same here... Jaunty 32bit
--
sasl2-bin broken, segfaulting during install
https://bugs.launchpad.net/bugs/323409
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs
I can confirm these errors, using jaunty 64bit.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New => Confirmed
--
sasl2-bin broken, segfaulting during install
https://bugs.launchpad.net/bugs/323409
You received this bug notification because you are a member of Ubuntu
Server Team, which is s
a better stack trace:
#0 0xb7a1f393 in strchrnul () from /lib/tls/i686/cmov/libc.so.6
#1 0xb79e287b in vfprintf () from /lib/tls/i686/cmov/libc.so.6
#2 0xb79e75f0 in buffered_vfprintf () from /lib/tls/i686/cmov/libc.so.6
#3 0xb79e2aae in vfprintf () from /lib/tls/i686/cmov/libc.so.6
#4 0
SourcePackage: cyrus-sasl2
Stacktrace:
#0 0xb7b2c393 in strchrnul () from /lib/tls/i686/cmov/libc.so.6
#1 0xb7aef87b in vfprintf () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7af45f0 in buffered_vfprintf () from /lib/tls/i686/cmov/libc.so.6
#3 0xb7aefaae in vfprintf () from /lib/tls/i686/cmov/
12 matches
Mail list logo
