Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Joonas Niilola
Hey, On 12/9/19 10:17 AM, Michał Górny wrote: > Hello, > > I think the policies proposed in GLEP 81 [1] were overenthusiastic > and they don't stand collision with sad Gentoo developer reality. > Instead of improving the quality of resulting packages, they rather > hamper their adoption and

Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Michał Górny
On Mon, 2019-12-09 at 13:48 -0800, Alec Warner wrote: > On Mon, Dec 9, 2019 at 12:17 AM Michał Górny wrote: > > > Hello, > > > > I think the policies proposed in GLEP 81 [1] were overenthusiastic > > and they don't stand collision with sad Gentoo developer reality. > > Instead of improving the

[gentoo-dev] Last rites: dev-util/kelbt

2019-12-09 Thread Aaron Bauman
# Aaron Bauman (2019-12-10) # EAPI=4, dead upstream, can't locate new home # Removal in 30 days dev-util/kelbt -- Cheers, Aaron signature.asc Description: PGP signature

Re: [gentoo-dev] Last rites: dev-tex/dvi2tty

2019-12-09 Thread Aaron Bauman
On Mon, Dec 09, 2019 at 07:43:23PM -0500, Aaron Bauman wrote: > # Aaron Bauman (2019-12-09) > > # EAPI=4, unmaintained upstream and Gentoo is versions behind > > # Removal in 30 days

[gentoo-dev] Last rites: dev-utils/idutils

2019-12-09 Thread Aaron Bauman
# Aaron Bauman (2019-12-10) # EAPI=4, fails to build # Removal in 30 days dev-util/idutils -- Cheers, Aaron signature.asc Description: PGP signature

[gentoo-dev] Last rites: mozconfig-v6.60.eclass

2019-12-09 Thread David Seifert
# @DEAD # All consumers are gone. Removal in 14 days

[gentoo-dev] Last rites: games-mods.eclass

2019-12-09 Thread David Seifert
# @DEAD # All consumers are gone. # Bug #156882, #574642, #637740. Removal in 14 days.

[gentoo-dev] Last rites: media-sound/vitunes

2019-12-09 Thread David Seifert
# David Seifert (2019-12-10) # Abandoned upstream, broken ncurses linking, last release 8 years ago. # Bug #677742, #696228. Removal in 30 days. media-sound/vitunes

[gentoo-dev] Last rites: media-sound/mhwaveedit

2019-12-09 Thread David Seifert
# David Seifert (2019-12-10) # Build broken for over 3 years, GTK 2, quasi-abandoned upstream. # Bug #490574, #699914. Removal in 30 days. media-sound/mhwaveedit

[gentoo-dev] Last rites: dev-libs/boost-numpy

2019-12-09 Thread David Seifert
# David Seifert (2019-12-10) # Never keyworded, only worked with specific versions of boost that are # gone, integrated into boost as dev-libs/boost[python,numpy] nowadays. # Removal in 7 days. dev-libs/boost-numpy

[gentoo-dev] Last rites: dev-tex/dvi2tty

2019-12-09 Thread Aaron Bauman
# Aaron Bauman (2019-12-09) # EAPI=4, unmaintained upstream and Gentoo is versions behind # Removal in 30 days dev-tex/dvi2tty -- Cheers, Aaron signature.asc Description: PGP

[gentoo-dev] Last rites: dev-db/hyperdex and dev-libs/cityhash

2019-12-09 Thread Aaron Bauman
# Aaron Bauman (2019-12-09) # EAPI=4, unmaintained upstream, rdep as well # Removal in 30 days. Open bugs #552934 dev-libs/cityhash

Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Alec Warner
On Mon, Dec 9, 2019 at 12:17 AM Michał Górny wrote: > Hello, > > I think the policies proposed in GLEP 81 [1] were overenthusiastic > and they don't stand collision with sad Gentoo developer reality. > Instead of improving the quality of resulting packages, they rather > hamper their adoption

Re: [gentoo-dev] Removal of old DTDs

2019-12-09 Thread Ulrich Mueller
> On Tue, 03 Dec 2019, Ulrich Mueller wrote: > There are some DTDs in data/dtd.git which were needed for the old XML > pages. Apparently the following are no longer used: >gleps.dtd >metadoc.dtd >project.dtd (not to be confused with projects.dtd which is in use) >userinfo.dtd

Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Thomas Deutschmann
On 2019-12-09 19:48, Ulrich Mueller wrote: >> On Mon, 09 Dec 2019, Thomas Deutschmann wrote: > >> Like said, if an ID is already taken for any reason on user's system, >> that's not a problem. acct-* can handle that... there's nothing like a >> collision. > > You can call it "collision" or

Re: [gentoo-dev] Package up for grabs: app-arch/unar

2019-12-09 Thread Dennis Schridde
On Montag, 9. Dezember 2019 13:03:02 CET Hanno Böck wrote: > It's an archive unpacker written in objective C, which makes it > dependency-heavy (particularly requires gcc compiled with objc). > I originally got interested because it was the only free unpacker > capable of handling modern rar

Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Ulrich Mueller
> On Mon, 09 Dec 2019, Thomas Deutschmann wrote: > Like said, if an ID is already taken for any reason on user's system, > that's not a problem. acct-* can handle that... there's nothing like a > collision. You can call it "collision" or something else, the fact is that in this scenario, the

Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Thomas Deutschmann
On 2019-12-09 18:47, Ulrich Mueller wrote: > One problem with that is that at some time user.eclass dynamically > allocated IDs starting at 101 upwards, and later this was changed to 999 > downwards (at different times for UIDs and GIDs). So for existing > systems you can expect some range above

Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Ulrich Mueller
> On Mon, 09 Dec 2019, Thomas Deutschmann wrote: > Make complete SYS_UID_MIN - SYS_UID_MAX range available for GLEP 81. > The only argument/reason I am aware of, "but 501-999 could be used by > system" (Dynamic allocation by user.eclass), isn't strong enough from my > POV because system

Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Thomas Deutschmann
Hi, I fully agree with #3. But I would go one step further: Make complete SYS_UID_MIN - SYS_UID_MAX range available for GLEP 81. The only argument/reason I am aware of, "but 501-999 could be used by system" (Dynamic allocation by user.eclass), isn't strong enough from my POV because system

Re: [gentoo-dev] [PATCH v4] mount-boot.eclass: Check if /boot is sane, but don't try to mount it.

2019-12-09 Thread Jaco Kroon
Hi, >> What about just checking "${EROOT}/boot" instead? > For what, existence? There may well be a "boot" directory present under > EROOT. (And we could check ${EROOT}/etc/fstab, but I don't think we > should open that can of worms. There's no reliable way to guess the > user's exact

[gentoo-dev] Package up for grabs: app-arch/unar

2019-12-09 Thread Hanno Böck
Hi, I'm no longer interested in maintaining app-arch/unar. It's an archive unpacker written in objective C, which makes it dependency-heavy (particularly requires gcc compiled with objc). I originally got interested because it was the only free unpacker capable of handling modern rar archives.

Re: [gentoo-dev] [PATCH v4] mount-boot.eclass: Check if /boot is sane, but don't try to mount it.

2019-12-09 Thread Ulrich Mueller
> On Mon, 09 Dec 2019, Jaco Kroon wrote: > Acked-by: Jaco Kroon OK, I can add this. >> +    if [[ ${EROOT:-/} != / ]] ; then >>          return 0 >>      fi > I don't use spaces in path names ... but what happens here if ROOT or > EPREFIX (and by implication EROOT) contains a space? No

Re: [gentoo-dev] [PATCH v4] mount-boot.eclass: Check if /boot is sane, but don't try to mount it.

2019-12-09 Thread Jaco Kroon
Hi Ulrich, I'm happy with this "as is", but there may be a few improvements still. By the way:  This improves the situation for mounted ro /boot by moving the check from preinst to pretend. For noauto /boot (I believe the default and recommended) this fixes things. This is the reason I decided

Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Ulrich Mueller
> On Mon, 09 Dec 2019, Ulrich Mueller wrote: >> a. split the UID/GID range into 'high' (app) and 'low' (system) >> assignments, 'high' being >=100 and 'low' <100 (matching Apache suEXEC >> defaults), > Good, but can we make these ranges more explicit please, like 100..499 > for "high" and

Re: [gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Ulrich Mueller
> On Mon, 09 Dec 2019, Michał Górny wrote: > My proposal would be to: > a. split the UID/GID range into 'high' (app) and 'low' (system) > assignments, 'high' being >=100 and 'low' <100 (matching Apache suEXEC > defaults), Good, but can we make these ranges more explicit please, like

[gentoo-dev] [RFC] Revisiting GLEP 81 (acct-*) policies (reviews, cross-distro syncing)

2019-12-09 Thread Michał Górny
Hello, I think the policies proposed in GLEP 81 [1] were overenthusiastic and they don't stand collision with sad Gentoo developer reality. Instead of improving the quality of resulting packages, they rather hamper their adoption and cause growing frustration. The problems I see today are: 1.