On 02/12/2011 09:58 PM, meino.cra...@gmx.de wrote:
Hi,
this morning I got this while emergeing util-linux:
>>> Emerging (1 of 1) sys-apps/util-linux-2.19
* util-linux-2.19.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [
ok ]
* util-linux-ng-2.18-20100706.diff.bz2 RMD160 SHA1 SHA256 size ;-) ... [
ok ]
* Package: sys-apps/util-linux-2.19
* Repository: gentoo
* Maintainer: base-sys...@gentoo.org
* USE: amd64 cramfs crypt elibc_glibc kernel_linux loop-aes multilib nls
perl userland_GNU
>>> Unpacking source...
>>> Unpacking util-linux-2.19.tar.bz2 to
/var/tmp/portage/sys-apps/util-linux-2.19/work
>>> Unpacking util-linux-ng-2.18-20100706.diff.bz2 to
/var/tmp/portage/sys-apps/util-linux-2.19/work
>>> Source unpacked in /var/tmp/portage/sys-apps/util-linux-2.19/work
>>> Preparing source in
/var/tmp/portage/sys-apps/util-linux-2.19/work/util-linux-2.19 ...
* Applying util-linux-ng-2.18-20100706.diff ...
* Failed Patch: util-linux-ng-2.18-20100706.diff !
* (
/var/tmp/portage/sys-apps/util-linux-2.19/work/util-linux-ng-2.18-20100706.diff
)
*
* Include in your bugreport the contents of:
*
*
/var/tmp/portage/sys-apps/util-linux-2.19/temp/util-linux-ng-2.18-20100706.diff.out
That diff.out file shows that the patch being applied is grossly broken for
version 2.19.
If you really need the loop-aes useflag, you'll just have to wait for the
gentoo dev to fix
the ebuild. Otherwise, just unset the loop-aes flag. Dunno if there is a bug
report open
for this, but there should be.