Summary: | sys-apps/openrc-0.11.8: fails to build with ncurses[tinfo] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | OpenRC Team <openrc> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | b.r.longbons, jlec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 457530 |
Description
Diego Elio Pettenò (RETIRED)
2013-02-28 19:56:44 UTC
*** This bug has been marked as a duplicate of bug 455912 *** Uhm no, this can't be fixed by 0.12, as it's currently broken in stable.. I fixed stable openrc to require ncurses without the tinfo use flag. (In reply to comment #3) > I fixed stable openrc to require ncurses without the tinfo use flag. This is not a fix! Nearly everyone is using openrc, so one is basically unable to install a package depending on tinfo. Isn't it possible to backport that fix to the current package? Or are you planning to release openrc-0.12 soon? Please don't break the whole system to "fix" your broken package. (In reply to comment #5) > Please don't break the whole system to "fix" your broken package. Technically, the tinfo use flag on ncurses should have gone through ~arch first since it changed the ncurses API so we could catch thingslike this *before* they hit stable. (In reply to comment #4) > (In reply to comment #3) > > I fixed stable openrc to require ncurses without the tinfo use flag. > > This is not a fix! Nearly everyone is using openrc, so one is basically > unable to install a package depending on tinfo. According to flameeyes (the reporter of this bug) I had two options to fix it. I could either make openrc depend on ncurses[-tinfo] or I could release 0.11.9 with this fix in it to ~arch and request a fast stable. > Isn't it possible to backport that fix to the current package? Or are you > planning to release openrc-0.12 soon? 0.12 will be coming farely soon, but probably not for a week or so. Like I said above, backporting would really end up being a new release (0.11.9) which would have to go from ~arch to stable. @flameeyes: What is your position on this,do you want me to release0.11.9 with this fix? I can either fast stable or with your permission commit directly to stable. Or, should we wait for 0.12? (In reply to comment #7) the ebuild is incorrect. it should only DEPEND on ncurses[-tinfo], not RDEPEND. fix that and the rest should be fine to wait until next revbump. |