| Summary: | perofmring emerge -S causes a [no/bad digest] error | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Dave Shanker <dshanker> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | minor | CC: | bradn2 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
*** Bug 28062 has been marked as a duplicate of this bug. *** |
I noticed that if you perform a search emerge -S, you will get a [no/bad digest] error. I tried performing the search on multiple ebuilds and also as root and another user assigned to the portage group. Every package that portage finds contains the error. Now if I perform a emerge -p on the ebuild, I'm presented with the correct information. It's really not that important, but it should be fixed. I'm running portage-2.0.48-r1 and I've included an output screen. Reproducible: Always Steps to Reproduce: 1. emerge -S <anypackage> 2. 3. Actual Results: emerge -S objdump Searching... [ Results for search key : objdump ] [ Applications found : 1 ] * dev-util/examiner-0.5 Latest version available: 0.5 Latest version installed: [ Not Installed ] Size of downloaded files: [no/bad digest] Homepage: http://www.academicunderground.org/examiner/ Description: Examiner is an application that utilizes the objdump command to disassemble and comment foreign executable binaries I use emerge -S gtk to reproduce the problem as there are alot of ebuilds that match. All of them have the same error.