>>> Downloading ftp://ftp.perforce.com/perforce/r03.1//doc/man/p4d.1 --15:38:37-- ftp://ftp.perforce.com/perforce/r03.1/doc/man/p4d.1 => `/usr/portage/distfiles/p4d.1' Resolving ftp.perforce.com... done. Connecting to ftp.perforce.com[209.209.49.104]:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /perforce/r03.1/doc/man ... done. ==> PASV ... done. ==> RETR p4d.1 ... done. Length: 4,529 (unauthoritative) 100%[====================================>] 4,529 42.12K/s ETA 00:00 15:38:38 (42.12 KB/s) - `/usr/portage/distfiles/p4d.1' saved [4529] !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: beb021d573de8a161220067ce3874405 >>> your file's digest: 99137d11102c457fd2e32838cf221a9e Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge perforce Actual Results: The digest does not match the downloaded file. Expected Results: The digest should match the downloaded file. ;) My portage tree is current - looks like the file on their FTP was updated and nobody noticed.
The file on the FTP server was changed on Jan 19th. I'll contact Perforce's support team and ask them to confirm that the updated file is legitimate before updating Portage. Best regards, Stu
Still haven't heard back from Perforce - which is most unusual. I've contacted them again.
Closing - digests have been updated.
If anyone ran into the above problem and tries to emerge perforce now that this bug is closed, you will run into a problem with your p4ftpd digest mismatching. Steps to fix: rm /usr/portage/distfiles/p4* emerge perforce
