When trying to compile xfree-4.3.0-r2, the build stops when the md5 for XFree86-4.3.0-patches-1.0.8.tar.bz can't be found in the digest (as 1.1.1 is expected). Changing all occurences of "XFree86-${PV}-patches-${PATCH_VER}.tar.bz2" to "XFree86-4.3.0-patches-${PATCH_VER}.tar.bz2" in the .ebuild fixes this. I have no idea why the ${PV} substitution would be breaking this file reference on my machine. Can anyone confirm this? Reproducible: Always Steps to Reproduce: 1. emerge /usr/portage/x11-base/xfree/xfree-4.3.0-r2.ebuild Actual Results: Digest error on XFree86-4.3.0-patches-1.0.8.tar.bz2 Expected Results: The ebuild compiles.
I had no such problem. Could it be a portage bug ? The portage version I use is 2.0.46-r12
I'm using portage-2.0.47-r10.
maybe your portage cache got corrupt emerge sync && emerge regen if still fails: rm -rf /var/cache/edb/dep/* emerge sync try again
Nope, neither of those worked. I had already tried emerge regen, but not deleting the files in /var/cache/edb/dep. I looked at the xfree-4.3.0-r2 file in /var/cache/edb/dep after deleting them and emerge sync'ing, and it contains a reference to "mirror://gentoo/XFree86-4.3.0 -patches-1.0.8.tar.bz2" in it. Is this file generated locally, or am I possibly pulling a corrupt version from my rsync server?
I've just had this problem installing a new version, i.e one that has never had X on it at all. Something's out of sync, /usr/portage/metadata/ perhaps? I think the /var/cache/edb is a simple copy from metadata at emerge sync time. Touching the /usr/portage/xfree-4.3.0-r2.ebuild made it fetch 1.1.1 and stop trying to use 1.0.8.
nick: please watch comment #5
i can confirm this ebuild: PATCH_VER="1.1.1" metacache mirror://gentoo/XFree86-4.3.0-patches-1.0.8.tar.bz2
I can confirm, touching the ebuild makes it compile properly. After doing this, /var/cache/edb/dep/x11-base/xfree-4.3.0-r2 correctly lists mirror://gentoo/XFree86-4.3.0-patches-1.1.1.tar.bz, but metadata is still incorrect.
manually updated rsync1.us emerge sync should be ok (this is just a work-around)
Ok, I've emerge synced again, and the ebuild will now go by patches-1.1.1 properly, but now it is failling on sis_drv_src_060403-1.tar.gz (the ebuild references sis_drv_src_130403-1.tar.gz) Once again, touching the ebuild allows the build to proceed normally.
now seems to be ok patches 1.1.2 and sis are in metacache