Crash is caused by an uninitialized variable being freed, see upstream bug report. Reproducible: Always Upstream has removed 5.2.11, fix released as 5.2.12.
1) Please post your `emerge --info' output in a comment. 2) Please attach command output, gdb backtrace and other information to help clarify the nature of the crashes.
I have probably worded the subject incorrectly. This is just a notice that within two days from the release of 5.2.11, upstream found a bug causing a crash; therefore upstream has pulled 5.2.11 and released 5.2.12 with a fix. There is nothing for Gentoo to do here apart from bumping the package, or at least masking 5.2.11 so that no one else is bitten by this (I have been, hence the report).
(In reply to comment #2) > I have probably worded the subject incorrectly. > > This is just a notice that within two days from the release of 5.2.11, > upstream found a bug causing a crash; therefore upstream has pulled 5.2.11 > and released 5.2.12 with a fix. > > There is nothing for Gentoo to do here apart from bumping the package, or at > least masking 5.2.11 so that no one else is bitten by this (I have been, > hence the report). Fixed. Thanks for reporting. +*bacula-5.2.12 (16 Sep 2012) + + 16 Sep 2012; Thomas Beierlein <tomjbe@gentoo.org> -bacula-5.2.11.ebuild, + +bacula-5.2.12.ebuild: + Bug fix version bump. Drop version 5.2.11 withdrawn by upstream. Thanks + Andrea +
