When emerging kde 3.2.0 it fails with being unable to locate and download the files. After investigation this is due to the ${PV} variable putting 3.2.0 into the download path. KDE have chosen to use 3.2 instead on their mirrors, example: ftp://download.kde.org/pub/kde/stable/3.2 instead of ftp://download.kde.org/pub/kde/stable/3.2.0 I proved this by manually editing the ebuild file for arts 1.2.0 to the correct download path, and it downloaded and compiled no problem. This can be easily fixed if you rename the ebuilds with 3.2.0 in their filename to 3.2 from what I can see. Reproducible: Always Steps to Reproduce: 1. Unmask the kde 3.2.0 ebuilds 2. CD to /usr/portage/kde-base/kde 3. emerge -u ./kde-3.2.0.ebuild Actual Results: emerge reports it cannot download the required packages Expected Results: Should download, compile and install as expected
fixed it about 10 minutes ago - thanks for the report.
How long does it usually take for the fix to propagate to the rsync mirrors?
i think most mirrors resync every 30 minutes, so it may take from 30-90 minutes.
Thanks :)
caleb, kdelibs still needs to be fixed (it doesn't use kde-dist.eclass). My cvs tree is too old so repoman fails, else I'd do it myself
done and done. thanks.
