Summary: | sys-apps/portage-2.2_rc67: every run, portage wants to reinstall the same binary | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jacob Godserv <jacobgodserv> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
automake:1.10 /var/db/pkg entry
automake-1.10.3.tbz2 |
Description
Jacob Godserv
2010-08-23 23:22:06 UTC
Created attachment 244309 [details]
automake:1.10 /var/db/pkg entry
This is automake:1.10's /var/db/pkg entry. The binpkg is uploading next.
Created attachment 244311 [details]
automake-1.10.3.tbz2
Wow. So I rebuilt automake:1.11 because I realized it's not in the binary repo, even though it's installed, and now I don't get this anymore. I think I kind of understand why portage was behaving like this. Still, it'd be nice to get a warning, similar to a block error. Nevermind. Automake:1.10 binpkg still wants to be reinstalled constantly, no matter how many times I rebuild it (as stated) or whether newer versions of automake are installed. |