Summary: | `emerge <tbz2file>` fails | ||
---|---|---|---|
Product: | Portage Development | Reporter: | SpanKY <vapier> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155723, 472746 |
Description
SpanKY
![]() Ran fixpackages lately? i highly doubt that's the issue this will happen if your PKGDIR is completely empty and if you generate a tbz2 pkg right then and there Emerge by path is broken, do the binpkging properly. then fix the emerge by path :P it's not like you need any information from the path to the tbz2 ... all the CATEGORY, PN, PV, etc... information is stored inside of the tarball The hilarious part is this is also triggered if you delete PKGDIR in the middle of a long sequence of merging. I was upgrading my Ultra 2 and I had previously removed my 36 gig /home drive, so I have no space for binpkgs and forgot to remove the FEATURE. So I rm -rf'd /home/packages to make sure / didn't fill up. Sure enough the next package died horribly with the same error. In order to support this a virtual repository could be generated to contain binary packages that are given on the command line. This approach would allow the resolver to view the package as coming from a repo so that it doesn't have to treat it as a special case. |