Please, keword app-portage/g-sorcery for these arches: ~alpha ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~ppc-aix ~x86-fbsd ~hppa-hpux ~ia64-hpux ~x86-interix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x64-solaris ~x86-solaris It is a dependency of app-portage/layman with USE g-sorcery set. When keywording, please, unmask g-sorcery USE for layman on per-arch basis.
(In reply to Jauhien Piatlicki from comment #0) > Please, keword app-portage/g-sorcery for these arches: > > ~alpha ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc > ~ppc-aix ~x86-fbsd ~hppa-hpux ~ia64-hpux ~x86-interix ~amd64-linux > ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x64-solaris > ~x86-solaris > > It is a dependency of app-portage/layman with USE g-sorcery set. When > keywording, please, unmask g-sorcery USE for layman on per-arch basis. Why didn't you drop the layman keywords as you should have?
Fixed that for you.
@Jeroen Roovers: I'm not a maintainer of layman, so I do not touch its keywords. Devan Franchini has masked g-sorcery USE instead, so this USE can be unmasked only on the arches g-sorcery is keyworded on.
Yeah, since it was an optional dep, I thought the USE flag should be masked rather than drop all keywords in layman. g-sorcery needs layman for it to be keyworded, but layman didn't need g-sorcery except for the overlay types it creates ebuilds for. Either way, Keyword please :)
Also, I'm on the tools-portage mailing list/herd, so no need for me to get dup emails. :)
(In reply to Brian Dolbec from comment #4) > Yeah, since it was an optional dep, I thought the USE flag should be masked > rather than drop all keywords in layman. g-sorcery needs layman for it to > be keyworded, but layman didn't need g-sorcery except for the overlay types > it creates ebuilds for. I really don't get why this needs to be repeated over and over on such a regular basis: Keywording new dependencies that are masked by USE flags can be done in two ways, whichever is MORE EFFICIENT: A) Drop the keywords on the ebuild that requires the new dependency. This touches a SINGLE file (disregarding ChangeLog): the ebuild that requires the new dependency. B) If that is inconvenient, because many other ebuilds in turn rely on the new ebuild, THEN you mask the USE flag instead, which involves touching a couple more files in profiles/ but is more efficient than touch all those other ebuilds. Resolving the bug means that for each arch, testing requires: A1) adding two atoms to package.keywords (or whatever its "nom du jour" is) A2) enabling the new USE flag. B1) adding two atoms to package.keywords (or whatever its "nom du jour" is) (since usually the new parent ebuild is still unstable) B2) enabling the new USE flag. B3) unmasking the new USE flag Keywording itself requires: A1) keywording two ebuilds. (ekeyword(1) does this very quickly and reliably) B1) keywording one ebuild and manually editing package.use.mask in one (or more) (sub-)profiles to mask the new USE flag (which might need to be revised later and adds to the general cruft in profiles), or alternatively B2) manually editing package.use.mask in one (or more) (sub-)profiles to mask the new USE flag (overlaying the general package.use.mask already in place, which might need to be revised later and adds to the general cruft in profiles). In this case the former is obviously the preferable solution, as it involves no manual editing of profiles, no cruft in the profiles, and touches as few files as possible.
Marked ~hppa.
keyworded ~ppc and ~ppc64
Added ~arm keyword.
~ia64 done
~alpha done
~sparc done
~s390 added to 2.3 during bug #539366 USE="g-sorcery" is masked on s390
~arm64 is already there.
missing latest g-sorcery keywords for ~alpha and ~ia64. readding.
An automated check of this bug failed - repoman reported dependency errors (9 lines truncated): > dependency.bad app-portage/g-sorcery/g-sorcery-0.2.1-r1.ebuild: DEPEND: ~ia64(default/linux/ia64/17.0) ['dev-python/pymongo[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]'] > dependency.bad app-portage/g-sorcery/g-sorcery-0.2.1-r1.ebuild: RDEPEND: ~ia64(default/linux/ia64/17.0) ['dev-python/pymongo[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]'] > dependency.bad app-portage/g-sorcery/g-sorcery-0.2.1-r1.ebuild: DEPEND: ~ia64(default/linux/ia64/17.0/desktop) ['dev-python/pymongo[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]']
An automated check of this bug failed - repoman reported dependency errors (19 lines truncated): > dependency.bad dev-python/pymongo/pymongo-3.5.1.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0) ['dev-python/pykerberos[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]', '>=dev-db/mongodb-2.6.0'] > dependency.bad dev-python/pymongo/pymongo-3.5.1.ebuild: RDEPEND: ~alpha(default/linux/alpha/13.0) ['dev-python/pykerberos[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]'] > dependency.bad dev-python/pymongo/pymongo-3.5.1.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0/desktop) ['dev-python/pykerberos[python_targets_pypy(-)?,python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)]', '>=dev-db/mongodb-2.6.0']
Dropping dev-python/pymongo-3.5.1 back as it needs mongo (and dev-lang/go).
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f61a029c373747c08fc51a0fc27d70a31fb9479a commit f61a029c373747c08fc51a0fc27d70a31fb9479a Author: Sergei Trofimovich <slyfox@gentoo.org> AuthorDate: 2018-03-18 10:58:15 +0000 Commit: Sergei Trofimovich <slyfox@gentoo.org> CommitDate: 2018-03-18 10:58:15 +0000 profiles/arch/ia64: mask app-portage/g-sorcery[bson], bug #524040 app-portage/g-sorcery[bson] requires dev-lang/go in it's toolchain dependency (via app-admin/mongo-tools). Bug: https://bugs.gentoo.org/524040 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> profiles/arch/ia64/package.use.mask | 4 ++++ 1 file changed, 4 insertions(+)}
~ia64 keyworded
added ~mips
Keyworded on ~alpha.
SuperH port disbanded.
Unable to check for sanity: > no match for package: app-portage/layman-2.4.2-r1
All sanity-check issues have been resolved
Sanity check failed: > app-portage/layman-2.4.3 > depend ~m68k exp profile default/linux/m68k/17.0 (1 total) > dev-vcs/subversion > rdepend ~m68k exp profile default/linux/m68k/17.0 (1 total) > >=dev-python/pyGPG-0.2 > >=dev-vcs/subversion-1.5.4[http(+)] > dev-vcs/darcs > dev-vcs/git > dev-vcs/mercurial > app-portage/g-sorcery-0.2.1-r1 > depend ~m68k exp profile default/linux/m68k/17.0 (1 total) > dev-python/pymongo[-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),python_targets_python3_6(-),python_targets_python3_7(-),python_targets_python3_8(-)] > dev-vcs/git > rdepend ~m68k exp profile default/linux/m68k/17.0 (1 total) > dev-python/pymongo[-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),python_targets_python3_6(-),python_targets_python3_7(-),python_targets_python3_8(-)] > dev-vcs/git > depend ~ppc-macos exp profile prefix/darwin/macos/10.4/ppc (2 total) > dev-lang/python:3.6 > dev-lang/python:3.7 > dev-lang/python:3.8 > dev-python/pymongo[-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),python_targets_python3_6(-),python_targets_python3_7(-),python_targets_python3_8(-)] > sys-apps/portage[-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),python_targets_python3_6(-),python_targets_python3_7(-),python_targets_python3_8(-)] > rdepend ~ppc-macos exp profile prefix/darwin/macos/10.4/ppc (2 total) > dev-lang/python:3.6 > dev-lang/python:3.7 > dev-lang/python:3.8 > dev-python/pymongo[-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),python_targets_python3_6(-),python_targets_python3_7(-),python_targets_python3_8(-)] > sys-apps/portage[-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),python_targets_python3_6(-),python_targets_python3_7(-),python_targets_python3_8(-)]
seems we are good here
Unable to check for sanity: > no match for package: app-portage/g-sorcery-0.2.2
I'm not going to keyword this for m68k. The tests need Subversion, which is a bit of a keywording nightmare. I gather layman is effectively dead these days anyway.
