Summary: | net-libs/wt-3.2.2 - Aborting due to QA concerns: 4 files installed in /tmp/portage/net-libs/wt-3.2.2/image///tmp/portage/net-libs/wt-3.2.2/image/ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Wood <peter.wood> |
Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED WONTFIX | ||
Severity: | QA | CC: | 0xd34df00d, bass_dr, ostroffjh, peter.wood, proxy-maint, treecleaner |
Priority: | Normal | Keywords: | PMASKED |
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | Pending removal: 2016-09-20 | ||
Package list: | Runtime testing required: | --- | |
Attachments: | wt-3.3.6.ebuild |
Description
Peter Wood
2012-08-09 23:06:39 UTC
I'm seeing the same here, on two different systems. Still the same here, too. While I don't use wt (I tried it a while ago, and only played with it) this bug is about 3.2.2, the current version in portage is 3.3.4, and 3.3.6 has been released upstream in July. Does this bug still apply to the current version? I don't recall getting these errors emerging 3.3.4. When I have time (likely not for two weeks) I'll try re-emerging just to confirm. Created attachment 444150 [details]
wt-3.3.6.ebuild
Jack is right, this bug is invalid.
I could take care of wt, I am not using it extensively.
Here is an ebuild for 3.3.6
CCing proxy-maintainers Works for me just fine with 3.3.4:
>>> Completed installing wt-3.3.4 into /var/tmp/portage/net-libs/wt-3.3.4/image/
* Final size of build directory: 224848 KiB
* Final size of installed tree: 105400 KiB
* QA Notice: This ebuild installs into paths that should be created at runtime.
* To fix, simply do not install into these directories. Instead, your package
* should create dirs on the fly at runtime as needed via init scripts/etc...
*
* var/run
* var/run/wt
This is a different issue I guess, and given that wt doesn't have any init scripts and the applications using it aren't supposed to be run as root, this is perhaps a sane thing to do.
What about all the other opened bugs against this package? :/ removed |