Summary: | kdelibs-4.4.3 checksum failure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Volker Hemmann <volkerarmin> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | d.gerstner |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Volker Hemmann
2010-05-05 13:34:30 UTC
I confirm this bug. I think that's what you got for using purposely masked packages (masked because before official KDE SC release). Please don't :P Indeed kdelibs tarball has been updated just before official release. it was still a bug - and thus not 'invalid'. Or are bug reports for masked packages suddenly verboten? (In reply to comment #3) > it was still a bug - and thus not 'invalid'. Or are bug reports for masked > packages suddenly verboten? > open ftp.kde.org and check checksumm of its tarball. Its the same as in portage so bug is invalid ls -lh kdelibs-4.4.3.tar.bz2 -rw-r--r-- 1 14M 5. Mai 10:49 kdelibs-4.4.3.tar.bz2 md5sum kdelibs-4.4.3.tar.bz2 bd2122af41660bfff642bd077ef798a2 kdelibs-4.4.3.tar.bz2 md5sum /var/portage/distfiles/kdelibs-4.4.3.tar.bz2 bd2122af41660bfff642bd077ef798a2 /var/portage/distfiles/kdelibs-4.4.3.tar.bz2 I fetched the one in my homedir just this morning, after I saw your post. As you see, the md5sums are identical. And I had to recreate the manifest. Closing the bug as 'fixed' is ok. But invalid is simply not. we close bugs to the state of the tree, and it was fixed already in the tree, thus the bug is invalid, normaly if noone would be aware of this issue we would fix it in cvs after this bug was created and then close this bug as fixed. Cheers. still not 'invalid'. I did emerge sync - saw failure. Since I downloaded everything in advance. And I was not the only one. So when I opened it it was a valid bug. That it was already fixed just not at the mirrors makes it a closed one - but not invalid. |