[gentoo-amd64] Re: sys-apps/util-linux-2.14.2

[Duncan]

Thanasis <thanasis@××××××××××.org> posted 4992A645.1010903@××××××××××.org,
excerpted below, on  Wed, 11 Feb 2009 12:19:49 +0200:

>>>> Emerging (1 of 1) sys-apps/util-linux-2.14.2
[snip]
>  * Failed Patch: util-linux-ng-2.14.1-20081015.diff !

$ ls -l  /pkg/All/util-linux-2.14.2.tbz2
-rw-r--r-- 1 root root 595884 2009-02-10 07:24 
/pkg/All/util-linux-2.14.2.tbz2
$

It obviously merged fine here.  That's the FEATURES=buildpkg package date.

Maybe it has to do with USE flags?  If you got a corrupted diff, it would 
have failed the integrity/checksums tests, so it can't be that.  FWIW, 
here are my USE flags (emerge -vp output):


[ebuild   R   ] sys-apps/util-linux-2.14.2  USE="slang unicode
 -crypt -loop-aes -nls -old-linux (-selinux) (-uclibc)" 0 kB

I looked up my log from the emerge and indeed, there are no patches 
applied, so the one your log shows is either a USE flag dependent patch 
or it changed without a version bump and I happened to get it either 
before the patch was applied or after it was removed.

... Yes indeed!  Checking the ebuild, I see the following:

[if the version isn't the -9999 live git version]

SRC_URI="mirror://kernel/linux/utils/util-linux-ng/v${PV:0:4}/
${MY_P}.tar.bz2
loop-aes? ( http://loop-aes.sourceforge.net/updates/util-linux-
ng-2.14.1-20081015.diff.bz2 )"

So it only tries to apply that diff if USE=loop-aes.  Also, not the 
versioning on the diff.  Obviously the code section that patch is against 
changed between .1 and .2, so the diff against .1 no longer applies.

If you don't need the encrypted loop-aes support, try changing your USE 
flag.  If you do, it looks like you have to wait until someone fixes the 
patch -- assuming it's not been merged into the mainline code, a good 
reason for the patch not to apply!

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman