While preparing to add an snapshot integrity check section to the handbook, I downloaded the files "portage-latest.tar.bz2" and "portage-latest.tar.bz2.md5sum" from OSUOSL. However, the md5sum didn't work: $ md5sum -c portage-latest.tar.bz2.md5sum md5sum: portage-20060521.tar.bz2: No such file or directory portage-20060521.tar.bz2: FAILED open or read md5sum: WARNING: 1 of 1 listed file could not be read Looks like it's trying to find the snapshot from yesterday (5-21) instead of whatever today's is/will be (5-22).
When -latest was created, 0521 *was* the current. portage-20060521.tar.bz2 22-May-2006 01:58 27M portage-latest.tar.bz2 22-May-2006 01:58 27M
(In reply to comment #0) > $ md5sum -c portage-latest.tar.bz2.md5sum > md5sum: portage-20060521.tar.bz2: No such file or directory You should first `mv portage-latest.tar.bz2 portage-20060521.tar.bz2` if you want that command to work correctly. The 20060522 snapshot hasn't been made yet.
closing because everthing is normal...
I'm going to make special portage-latest.tar.bz2.md5sum files on the server side in order to make it easy on users.
Created attachment 87300 [details, diff] make `md5sum -c portage-latest.tar.bz2.md5sum` work as expected I've applied this patch, so `md5sum -c portage-latest.tar.bz2.md5sum` will work from now on.
It's fixed.