Summary: | Silly bug in ebuild for kde-i18n for KDE 3.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Federico Zenith <federico.zenith> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | VERIFIED FIXED | ||
Severity: | major | CC: | gentoo-bugs |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | new kde-i18n ebuild |
You're right - fixed in portage. Not fixed in Portage. The directory is right, now, but the filename also changed, to be kde-i18n-de-3.2.tar.bz2 whereas it still should be kde-i18n-de-3.2.0.tar.bz2. Created attachment 24991 [details]
new kde-i18n ebuild
This ebuild Works For Me. As noted, I did not state clear enough in the first
message that, whereas files on the kde servers are marked with "3.2.0", the
directories are only marked "3.2".
ebuild works for me, after manually copying the digest file from the old kde-i18n ebuild over. Forgot to reopen bug... otherwise nobody will be looking here. try it now - i think i have it fixed. I confirm it works fine now. |
The folder where portage searches for files in ftp servers does not exist. While files have been labelled blah_blah-3.2.0.tar.bz2, the folder is named pub/kde/stable/3.2/src/kde-i18n, and not pub/kde/stable/3.2.0/src/kde-i18n . Blame the KDE guys for messing it up if you want. Check, for istance, $ ftp download.au.kde.org > cd /pub/kde/stable > ls Reproducible: Always Steps to Reproduce: 1.ACCEPT_KEYWORDS=~x86 emerge kde-i18n 2. 3. Actual Results: Long series of failed-download messages, always stating "No such directory `pub/kde/stable/3.2.0/src/kde-i18n'." Expected Results: Downloaded and installed kde-i18n.