Summary: | sys-apps/portage -: running ebuild install twice makes portage complain about pre-stripped files | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | jer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
Petteri Räty (RETIRED)
2006-09-02 23:51:25 UTC
Created attachment 95813 [details]
emerge --info
(In reply to comment #0) > >>> It appears that ndiswrapper has already been tested; skipping. > >>> It appears that 'ndiswrapper-1.23' is already installed; skipping. > >>> Remove '/var/tmp/portage/ndiswrapper-1.23/.installed' to force install. > man: > > QA Notice: pre-stripped files found: > /var/tmp/portage/ndiswrapper-1.23/image/sbin/loadndisdriver > strip: i686-pc-linux-gnu-strip --strip-unneeded Maybe that behavior is okay? If you remove the .installed file then it will force the install phase to run again and replace those stripped binaries. I suppose we could skip the qa check if the .installed file exists. We'd have to move he .installed check to the python side and that's annoying because all of the similar checks are currently done on the bash side in ebuild.sh. Or maybe remove .installed if the user calls `ebuild install` explicitly (like I did for test). *** Bug 283415 has been marked as a duplicate of this bug. *** I don't really view this as supported or a bug. |