Example: # emerge --update mozilla >>> emerge (1 of 1) net-www/mozilla-1.3-r2 to / [...] !!! No message digest entry found for file "enigmail-0.74.3.tar.gz." !!! Most likely a temporary problem. Try 'emerge rsync' again later. !!! If you are certain of the authenticity of the file then you may type !!! the following to generate a new digest: !!! ebuild /usr/portage/category/package/package-version.ebuild digest Now, it shouldn't be too difficult to change the last line above to be the actual line people must type. I.e. in this case: !!! ebuild /usr/portage/net-www/mozilla/mozilla-1.3-r2.ebuild digest based on the information the ebuild process has about the current state at that point. And it saves people a) having to dig up the correct path and b) getting it wrong a couple of times. Reproducible: Always Steps to Reproduce: 1. 2. 3.
The current message for missing digests is: Calculating dependencies ...done! >>> emerge (1 of 1) dev-libs/libsilt-0.4 to / !!! No package digest file found: /usr/portage/local/dev-libs/libsilt/files/digest-libsilt-0.4 !!! Type "ebuild foo.ebuild digest" to generate it.
Created attachment 19172 [details, diff] Patch against portage.py for better error messages In the cases of a missing digest file or a missing digest line within an existing digest file, this patch will show the proper command line to use to fix the problem to the user. Standard portage today does a cop out and prints either Type 'ebuild foo.ebuild digest' or ' !!! ebuild /usr/portage/category/package/package-version.ebuild digest' depending on what's missing. Just trying to add some user friendliess to emerge, it's sorely needed.
See previous message for attached patch for an example implementation of what I originally suggested. Please note that I've looked at portage.py for exactly two minutes, and may not have grabbed the relevant ebuild-info from the "correct" variable. Oh yeah, could someone please keep this Marius Mauch guy from closing bugs/enhancement requests with some random irrelevant comment with no bearing on the case? Sorry for double post, didn't see a way of toggling Reopen bug when attaching a file here.
We don't want to get personal here, do we ? The summary of the bug is "Show correct digest path" which I thought was the current situation as shown by my comment. After your comment I checked that again and saw that I only checked the case when the digest is missing, not the one when the digest is wrong. Sorry for that. Also doesn't make much sense to stop portage devs from closing portage bugs. I was recently checking the portage bug list (that is a long list) for old bugs that were either fixed without closing the bug (like IMO this one) or that weren't valid anymore. If you think I was wrong closing a bug please send me a mail with the bug number and why you think it should stay open. Also unified patches are generally preferred, but I think this one is simple enough to apply manually.
bah - just detected this ugly bug myself - isn't the severity a bit low!? portage .... :|
I think it's dangerous that normal(not dev) user makes digest file. So it should be another message. example: "Please emerge sync again or post bugzilla if you don't understant the error reason.".
No. If it's missing, it says 'emerge sync, or fix it'. Providing and easy way/endorsement of violating security is not something I am interested in including. Tab completion is an ally and there are easier ways of dealing with these issues if you take a little time to figure it out.
*** Bug 44414 has been marked as a duplicate of this bug. ***
