Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 399837 - portage-2.2.0_alpha84: no message on corrupt distfile
Summary: portage-2.2.0_alpha84: no message on corrupt distfile
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 377365
  Show dependency tree
 
Reported: 2012-01-23 14:06 UTC by Toei Rei
Modified: 2022-10-20 02:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Toei Rei 2012-01-23 14:06:23 UTC
It would be nice to have a message like $file corrupt instead of just fetching again. -> manually fetched distfiles

Reproducible: Always

Steps to Reproduce:
1. have broken tarball in distfiles
2. emerge
Actual Results:  
emerge just tries to fetch the file again

Expected Results:  
emerge should merrily print something somewhere like 'file corrupt, refetching
Comment 1 Zac Medico gentoo-dev 2012-01-24 00:40:05 UTC
It says something like this:

  Refetching... File renamed to '$DISTDIR/$FILE._checksum_failure_.XXXX'

I guess we could make it specify exactly which checksums don't match. Saying that the file is "corrupt" may not be completely accurate, it's possible that file is correct and the digest is wrong (albeit unlikely).
Comment 2 Toei Rei 2012-01-24 07:55:15 UTC
Sorry, Zac, I didn't see a message; not even in the emerge-fetch.log.
Maybe because of fetching happened in the background?

ELOG Mail message was also quite misleading for me: unpacking failed