[gentoo-dev] Last rites: app-text/winefish, dev-tex/oesch
# Mikle Kolyada (2019-08-05) # dead upstream, does not work and compile #(bug #688006, bug #686630) # masked for removal in 14 days app-text/winefish dev-tex/oesch signature.asc Description: OpenPGP digital signature
[gentoo-dev] Packages up for grabs: dev-libs/libdbusmenu, dev-libs/libindicate
Back when ayatana herd was disbanded[1], KDE project remained as the only maintainers of these two: dev-libs/libdbusmenu dev-libs/libindicate At this point, there is not a single KDE related reverse dependency using them. Which is why we cede authority over them to someone else who might be interested, effective immediately. Possible candidates with revdeps are gnome, xfce. Open bugs: https://bugs.gentoo.org/469032 https://bugs.gentoo.org/691260 [1]: https://archives.gentoo.org/gentoo-dev/message/ 27d112d023bb4a75cca540570f6c3d38 Regards, Andreas
[gentoo-dev] UID/GID assignment for polkitd (102)
I would like to reserve UID/GID 102 for polkitd (sys-auth/polkit). This is the same ID used by Arch Linux.
Re: [gentoo-dev] [PATCH] metadata/layout.conf: Allow specific PROPERTIES and RESTRICT values
On 7/29/19 12:04 AM, Michał Górny wrote: > On Sun, 2019-07-28 at 23:59 -0700, Zac Medico wrote: >> Bug: https://bugs.gentoo.org/690786 >> --- >> metadata/layout.conf | 4 >> 1 file changed, 4 insertions(+) >> >> diff --git a/metadata/layout.conf b/metadata/layout.conf >> index 7ffc0ce6b72..c719c42513c 100644 >> --- a/metadata/layout.conf >> +++ b/metadata/layout.conf >> @@ -4,6 +4,10 @@ >> # For details on this file, see the layout.conf section of the >> # portage(5) man page. >> >> +# Allow specific PROPERTIES and RESTRICT values in ebuilds. >> +allow-properties = interactive live >> +allow-restrict = binchecks bindist fetch installsources mirror >> preserve-libs primaryuri splitdebug strip test userpriv > > If I were to bikeshed, I'd go for following suit with eapis-*, i.e.: > > properties-allowed = ... > restrict-allowed = ... Ok, done: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5c92ab3ce076c9fb710c6cdcba71bae224215f20 -- Thanks, Zac signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [PATCH] glep-0067: Add 'proxied' and 'watcher' maint types
On Sun, 04 Aug 2019 18:49:30 +0200 Ulrich Mueller wrote: > Alternatively, how about calling that type "upstream" instead of > "watcher"? Mostly, because the term "upstream" doesn't communicate any useful information about what it is expected to mean, and, it reduces the usefulness of this field to excluding people who might pass for "watcher" but don't pass for "upstream" There are already "upstream" fields in other parts of metadata.xml, but none of them indicate definitively if upstream should (or shouldn't) be CC'd on literally every bug. All fit within , but not all fits within pgpcs5t86egaB.pgp Description: OpenPGP digital signature
Re: [gentoo-dev] [PATCH] glep-0067: Add 'proxied' and 'watcher' maint types
On Sun, 04 Aug 2019 18:49:30 +0200 Ulrich Mueller wrote: > > And yes, I'm talking about real life situation when the only > > in the package left was this 'upstream watcher'. > > I suppose an alternative solution there would be to return to explicit > > logical marking as . > > Many metadata files have that anyway as a comment, which is far from > perfect. So yes, I'd say that explicit is better > than . > > Alternatively, how about calling that type "upstream" instead of > "watcher"? Hmm, actually, maybe what this calls for is a new tag, "", to denote involved entities that aren't maintainers, but need to be CC'd on bugs. e.g.: Therein, a package with no is unmaintained, but people in the CC list still get CC'd, and a package with neither or is a bug. Perhaps even stipulate a 3rd tag, which repoman enforces being present if the count of drops below 1, and indicates that the Assignment on bugzilla should be to maintainer-needed? pgpZgR9OZeQjL.pgp Description: OpenPGP digital signature
