no known regressions
amd64 done
x86 stable
This bug depends on resolution of #350399
Arches, please wait until bug 350399 is resolved.
ppc stable
if you want blocker bugs, you need to mark them so
arm stable
It seems one more bug has turned up: bug #278784 (at least similar symptoms, most probably a different cause), the post_mount commands are not run.
It seems to me that comment #25 from bug 350399 and my comment #8 on 278784 are basically the same observation. Also Note: this is 1.1.3-r1 and not 1.1.3-r2
Please ignore the last part about the version in my last comment. I forgot to sync the machine I'm working on right now.
i already told you -- that bug is not a regression. thus "one more bug has turned up" has no bearing on stabilization never versions since it already applies to the current stable.
I can't compile cryptsetup-1.1.3-r3. It failed with: libtool: link: i686-pc-linux-gnu-gcc -Wall -march=prescott -O2 -pipe -fomit-frame-pointer -static -Wl,-O1 -o cryptsetup cryptsetup-cryptsetup.o -Wl,--as-needed ../lib/.libs/libcryptsetup.a -luuid -L/lib -ldevmapper /usr/lib/libudev.a -L/usr/lib /usr/lib/libgcrypt.a /usr/lib/libgpg-error.so /usr/lib/libpopt.a /usr/lib/gcc/i686-pc-linux-gnu/4.4.4/../../../../i686-pc-linux-gnu/bin/ld: attempted static link of dynamic object `/usr/lib/libgpg-error.so' collect2: ld returned 1 exit status make[2]: *** [cryptsetup] Error 1 make[2]: Leaving directory `/var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/work/cryptsetup-1.1.3/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/work/cryptsetup-1.1.3' make: *** [all] Error 2 emake failed * ERROR: sys-fs/cryptsetup-1.1.3-r3 failed: * emake failed * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 3547: Called _eapi2_src_compile * ebuild.sh, line 654: Called die * The specific snippet of code: * emake || die "emake failed" * * If you need support, post the output of 'emerge --info =sys-fs/cryptsetup-1.1.3-r3', * the complete build log and the output of 'emerge -pqv =sys-fs/cryptsetup-1.1.3-r3'. * The complete build log is located at '/var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/temp/environment'. * S: '/var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/work/cryptsetup-1.1.3' >>> Failed to emerge sys-fs/cryptsetup-1.1.3-r3, Log file: >>> '/var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/temp/build.log' * Messages for package sys-fs/cryptsetup-1.1.3-r3: * ERROR: sys-fs/cryptsetup-1.1.3-r3 failed: * emake failed * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 3547: Called _eapi2_src_compile * ebuild.sh, line 654: Called die * The specific snippet of code: * emake || die "emake failed" * * If you need support, post the output of 'emerge --info =sys-fs/cryptsetup-1.1.3-r3', * the complete build log and the output of 'emerge -pqv =sys-fs/cryptsetup-1.1.3-r3'. * The complete build log is located at '/var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/temp/environment'. * S: '/var/tmp/portage/sys-fs/cryptsetup-1.1.3-r3/work/cryptsetup-1.1.3'
Downgrade libgpg-error to stable version 1.7 from 1.10 fixed the problem.
do not post bug reports here. file new bugs and mark them as blocking this. however, your issue is not relevant to stabilization.
ppc64 stable
Stable for HPPA.
alpha/ia64/s390/sh/sparc stable, closing
