On Mon, 2009-05-11 at 00:12 +0200, Andreas Henriksson wrote:
> No segfault (only occured on the very first configure attempt, not
> reproducible) but the problem to configure persisted even with the new
> version.
>
> Manually running the scripts somehow magically fixed the problem:
I think debco
On sön, 2009-05-10 at 22:13 +0300, Fabian Fagerholm wrote:
> 2.1.22.dfsg1-24 does indeed have a build error which causes segfaults.
> Please try 2.1.22.dfsg1-25 instead. If the segfault persists, you can
> reopen this bug.
No segfault (only occured on the very first configure attempt, not
reproduc
reassign 528040 cyrus-sasl2
fixed 528040 2.1.22.dfsg1-25
forcemerge 523007 528040
thanks
Hi Andreas,
Thanks for the report!
On Sun, 2009-05-10 at 15:48 +0200, Andreas Henriksson wrote:
> When upgrading sasl2-bin a segfault occured:
[...]
2.1.22.dfsg1-24 does indeed have a build error which caus
Processing commands for cont...@bugs.debian.org:
> reassign 528040 cyrus-sasl2
Bug#528040: sasl2-bin: segfault on upgrade -> fails to configure.
Bug reassigned from package `sasl2-bin' to `cyrus-sasl2'.
> fixed 528040 2.1.22.dfsg1-25
Bug#528040: sasl2-bin: segfault on
Package: sasl2-bin
Version: 2.1.22.dfsg1-24
Severity: serious
Justification: breaks upgrade
When upgrading sasl2-bin a segfault occured:
Setting up sasl2-bin (2.1.22.dfsg1-24) ...
DB->get: method not permitted before handle's open method
/var/lib/dpkg/info/sasl2-bin.postinst: line 17: 21765 Done
5 matches
Mail list logo