| Summary: | =gnome-extra/chrome-gnome-shell-10: keyword request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | nE0sIghT <ykonotopov> |
| Component: | Keywording | Assignee: | nE0sIghT <ykonotopov> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gnome, proxy-maint, radhermit |
| Priority: | Normal | Keywords: | KEYWORDREQ |
| Version: | unspecified | Flags: | stable-bot:
sanity-check+
|
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: |
=dev-util/valgrind-3.13.0-r1
=app-misc/jq-1.5-r3
=gnome-extra/chrome-gnome-shell-10
=gnome-base/gnome-shell-3.24.3
|
Runtime testing required: | No |
| Bug Depends on: | |||
| Bug Blocks: | 613786, 616698 | ||
|
Description
nE0sIghT
2016-05-18 16:30:01 UTC
Sorry, forgot ~arm64 (same keywords as for www-client/chromium supported) Target keywords: ~arm, ~arm64 arm64 doesn't even have gnome-shell, so doesn't make sense to keyword yet (that said, I will work on gnome-shell in the future and then likely circle back to chrome-gnome-shell). We need matching keywords visibility than gnome-base/gnome-shell, or USE=browser-extension package.use.mask'ed on gnome-shell for your arch An automated check of this bug failed - repoman reported dependency errors (22 lines truncated):
> dependency.bad gnome-extra/chrome-gnome-shell/chrome-gnome-shell-8.1.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0) ['app-misc/jq']
> dependency.bad gnome-extra/chrome-gnome-shell/chrome-gnome-shell-8.1.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0/desktop) ['app-misc/jq']
> dependency.bad gnome-extra/chrome-gnome-shell/chrome-gnome-shell-8.1.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0/desktop/gnome) ['app-misc/jq']
Adding gnome-shell version that dropped keywords due to this. sanity-check+ pending ACK on keywording of app-misc/jq and addition of it to package list by its maintainer - CCing him. radhermit said "feel free to do whatever you want/need" "as long as you know what you're doing"; so adding app-misc/jq to package list. It has failing tests though, so maybe nE0sIghT would like to look into that ;) Meanwhile at your (arch team) discretion An automated check of this bug failed - repoman reported dependency errors (7 lines truncated):
> dependency.bad app-misc/jq/jq-1.5-r2.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0) ['dev-util/valgrind']
> dependency.bad app-misc/jq/jq-1.5-r2.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0/desktop) ['dev-util/valgrind']
> dependency.bad app-misc/jq/jq-1.5-r2.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0/desktop/gnome) ['dev-util/valgrind']
Adding valgrind to make stable-bot happy, as I'm not sure how else to have this show up to getatoms.py users... Obviously you can't keyword it, but would have to package.use.mask test on app-misc/jq instead for your profile, if jq retains its valgrind test dep or something. The delays from architecture teams here is now blocking security cleanup of gnome-shell. Valgrind does not support Alpha (and I suspect it doesn't support ia64 etc. either), so what are our options? USE-mask "browser-extension" for the whole arch? (In reply to Tobias Klausmann from comment #11) > Valgrind does not support Alpha (and I suspect it doesn't support ia64 etc. > either), so what are our options? USE-mask "browser-extension" for the whole > arch? See comment #9 An automated check of this bug failed - the following atom is unknown: gnome-base/gnome-shell-3.22.3-r1 Please verify the atom list. ia64 keyworded. masked app-misc/jq[test] due to unported valgrind on ia64. The only hurdle was bug #624356 ~ppc64 keyworded. Had to go after latest =gnome-base/gnome-shell-3.24.3 ~ppc keyworded An automated check of this bug failed - the following atom is unknown: gnome-base/gnome-shell-3.22.3-r2 Please verify the atom list. It's taken 10 months or so to act here, so of course the list is outdated by now, but it's a keywording one. So just updated it to latest now. An automated check of this bug succeeded - the previous repoman errors are now resolved. Keyworded on ~alpha. ~arm done |
