Summary: | "Invalid binary package..." when using emerge as user | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sascha G. <s.geschwandtner> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 136244, 187293 |
Description
Sascha G.
2006-08-09 05:55:49 UTC
So the check needs to run only as root, got it. The umask is automatically set to 022 by emerge. Did you create those packages with quickpkg or something? (In reply to comment #2) > The umask is automatically set to 022 by emerge. Did you create those packages > with quickpkg or something? Yes, I did use quickpkg. Sorry I didn't mention that. In svn r4210 quickpkg now forces umask 022 (just like emerge does). This has been released in 2.1.1_pre5. In portage-2.1.3_rc5, this behaves a little differently. See bug #182428 for details. |