When I attempt to update 'net-misc/ltsp-core-4.0', I get problems fetching the files 'ltsp-getltscfg-0.02-0-i386.tgz' and 'ltsp-pci_scan-0.02-0-i386.tgz'. The digest for the ebuild indicates different checksums and file sizes than what is available from both the ltsp main site (http://www.ltsp.org/) and several of the US download mirrors. I get the following values for the files: old: MD5 431b3afe8c6e62004387dcc846c43918 ltsp-getltscfg-0.02-0-i386.tgz 13752 new: MD5 bb3bd081883d97ea6dc0957e8104c2c4 ltsp-getltscfg-0.02-0-i386.tgz 13607 old: MD5 d5134a153c710fe6cd73178a67ba5974 ltsp-pci_scan-0.02-0-i386.tgz 2614 new: MD5 4735103a372cf791cb9840c77b7a415f ltsp-pci_scan-0.02-0-i386.tgz 2463 After modifying the digest with the "new" values, everything fetches OK. Reproducible: Always Steps to Reproduce: 1. emerge -f ltsp-core 2. get errors attempting to resume download - "file is already complete" 3. check project homepage and learn that sizes don't match digest for ebuild 4. fetch files manually, generate MD5 sums and update digest. 5. emerge -f ltsp-core -- now works OK
it seems that they updated the files, but not the version number, i'll include the new files in a new version later, for now the old files are still on gentoo mirrors.
While we are obviously unable to prevent another project from slipstreaming updates, I'm afraid I do not agree with your solution. If all mirrors specified in make.conf are unavailable (as was the case for me), then you will end up fetching the new files from the ltsp.org site or one of its mirrors, which will cause the problem I reported. I feel that the current ebuild should be replaced with a new version and the old one removed along with a purge of the files replaced by the slipstream update from all Gentoo mirrors. My 2 cents.
we have our mirrors to workaround such situations, there are alot of packages that doesn't exist upstream anymore but on our mirrors, so you have to use our mirrors.
