The latest changes to /usr/portage/eclass/kernel-2.eclass break the mm-sources ebuilds. On 2005-04-05 I sucessfull install mm-sources-2.6.12_rc2-r1. Its digest says: MD5 32cbdc71085177bf867bfcbe41bb349b patch-2.6.12-rc2.bz2 3403237 MD5 f00fd1b5a80f52baf9d1d83acddfa325 linux-2.6.11.tar.bz2 37075679 MD5 af6f37a08ab846d4a6679d52178f87c5 2.6.12-rc2-mm1.bz2 1924196 Today I wanted to install mm-sources-2.6.12_rc2-r2 by coping the -r1 ebuild. This did not work because it was downloading 2.6.11-rc2-mm2.bz2 instead of 2.6.12-rc2-mm2.bz2. This error ist not cause by the renaming, as using the command # ebuild mm-sources-2.6.12_rc2-r1.ebuild digest results in the following digest: MD5 32cbdc71085177bf867bfcbe41bb349b patch-2.6.12-rc2.bz2 3403237 MD5 f00fd1b5a80f52baf9d1d83acddfa325 linux-2.6.11.tar.bz2 37075679 MD5 9c70fb0a2effe85035653e94033d7c50 2.6.11-rc2-mm1.bz2 1905516 The old ebuild is also downloading the wrong patch. As it did work on 5. April and in the meantime there where changes on the kernel-2 eclass regarding the handling of the version numbers (2.6.11.x), I suspect the error was introduced there. I do not know if the mm-sources ebuild or the kernel-2 eclass is broken, but right now the latest versions do not work together. Reproducible: Always Steps to Reproduce: 1.emerge --sync 2.emerge =sys-kernel/mm-sources-2.6.12_rc2-m1 Actual Results: Downloads 2.6.11-rc2-mm1.bz2 Expected Results: Download of 2.6.12-rc2-mm1.bz2 CVS-Version kernel-2.eclass: 1.117 2005/04/07 18:06:52 CVS-Version mm-sources-2.6.12_rc2-r1.ebuild: 1.1 2005/04/05 13:48:35
these digests should have been fixed by now. Please emerge sync again and re-test.
Fixing the digest will not solve the problem. In my view it would even be worst, because the digest failure clearly shows what is work. bardioc mm-sources # ebuild mm-sources-2.6.12_rc2-r1.ebuild unpack >>> md5 src_uri ;-) patch-2.6.12-rc2.bz2 >>> md5 src_uri ;-) linux-2.6.11.tar.bz2 !!! No message digest entry found for file "2.6.11-rc2-mm1.bz2." !!! Most likely a temporary problem. Try 'emerge sync' again later. !!! If you are certain of the authenticity of the file then you may type !!! the following to generate a new digest: !!! ebuild /usr/portage/category/package/package-version.ebuild digest bardioc mm-sources # The error still is, that emerge trys to use 2.6.11-rc2-mm1.bz2 instead of 2.6.12-rc2-mm1.bz2 . And this fact is obvious, if you compare the files in the (old) digest against the error message. With the fixed digest (I did sync, but still got the old digest) it will stead fail somewhere applying the patch. Which could the theory also be cause by a damage patch installation or a bad mm-patch.
I can confirm this problem. Made a fresh emerge sync and tried to emerge latest mm-sources (2.6.12-rc2-r1, also tried to copy to -r2 as it's newer). But it seems as if emerge tries to patch 2.6.11-r2-mm1 against 2.6.12-rc2.
I get the same errors about digests and I just did a fresh install a couple hours ago
Revision 1.118 of eclass/kernel-2.eclass checked in by johnm on Sun Apr 10 21:17:16 2005 UTC fixes this issue. mm-sources-2.6.12_rc2-r1.ebuild will still fail, because of the "fix" of the digest. Please revert this to the original digest.
