Summary: | dev-python/pivy lastrite request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ian Delaney (RETIRED) <idella4> |
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: | normal | CC: | djc, tomwij, treecleaner |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ian Delaney (RETIRED)
2012-12-12 09:56:40 UTC
1) You have power to assign bugs yourself. Please use it 2) You can treeclean it yourself. You have the power to do it. the process is documented in treecleaners page For more information, see http://www.gentoo.org/proj/en/qa/bug-wranglers which explains how to handle new bugs in details. In this particular case `equery m pivy` yields "Maintainer: maintainer-needed@gentoo.org". A summary for assignment for in-tree packages: If there are specific instructions in the metadata, follow them. If there is only a herd, assign to the herd. If there are maintainers, assign it to the first maintainer. CC all the remaining maintainers and herds listed in the metadata. For keyword descriptions, see https://bugs.gentoo.org/describekeywords.cgi Regarding freecad (also maintainer-needed), what should we do? Revert it to use bundled lib or treeclean it too? 1) dead upstream does not necessarily qualify a package to be treecleaned, see app-admin/verynice which is more than 10 years old. 2) if there are still packages that need this, it must not be treecleaned 3) treecleaning the reverse dependencies because we want to treeclean this is wrong 4) reverting a proper fix because we want to treeclean this, is also wrong but... as someone said the bundled copy is modified we should check with upstream what has been modified. Maybe the unbundling already broke something in freecad. The origin of Ian "nominating" this for treecleaning is bug 425584 (looks like it breaks with gcc-4.7) well, that is fixable, see bug 448614 (In reply to comment #6) > well, that is fixable, see bug 448614 Nice, in that case I agree this can be kept a bit more Now that gcc-4.7 issue is solved this is wontfix for now |