> On Tue, 10 Dec 2019, Michał Górny wrote:
> -Version: 1
> +Version: 1.1
It's a significant change, so should be version 2, I guess?
> -This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
> +This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
> On Tue, 10 Dec 2019, Aaron Bauman wrote:
> # Aaron Bauman (2019-12-09)
> # EAPI=4, unmaintained upstream and Gentoo is versions behind
> # Removal in 30 days
> dev-tex/dvi2tty
Since I had originally submitted this package in bug 50876, I can take
maintainership of it.
@maksbotan: Your
>>>>> 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 whic
> 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
> 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
> 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
>>>>> 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 explici
> 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
>>>>> On Sun, 08 Dec 2019, Ulrich Mueller wrote:
> | We had skipped allocation for 492 and 493, because they're used for
> | oprofile and oidentd in Archlinux, and we have these packages too.
Anyway, stunnel is 341 now, and 492 is (provisionally) reserved
for oprofile.
U
> On Sun, 08 Dec 2019, Anthony G Basile wrote:
>>> Okay, I'm requesting UID/GID = 492/492. I'm committing in a sec.
>>
>> That's the ID used by arch for oprofile, so it's a bad choice.
> I give up! How am I supposed to know what to choose if it isn't
> requested in the uid-git.txt file?
> On Sun, 08 Dec 2019, Anthony G Basile wrote:
> Okay, I'm requesting UID/GID = 492/492. I'm committing in a sec.
That's the ID used by arch for oprofile, so it's a bad choice.
Ulrich
signature.asc
Description: PGP signature
> On Sat, 07 Dec 2019, Thomas Deutschmann wrote:
> just wondering if you have seen https://bugs.gentoo.org/532264#c24.
> If this is still valid, is your change really needed?
I have. IIUC it is a special case for one ebuild and cannot be
generalised.
Ulrich
signature.asc
Description: PGP
> On Sat, 07 Dec 2019, Sergei Trofimovich wrote:
>> # The user wants us to leave things be.
>> -if [[ -n ${DONT_MOUNT_BOOT} ]] ; then
>> +if [[ -n ${I_KNOW_WHAT_I_AM_DOING} ]] ; then
>> return 0
>> fi
> The rest of patch looks ok but I find
> On Fri, 06 Dec 2019, Michał Górny wrote:
>> reaching pkg_pretend() at all. Furthermore, with the "mount-sandbox"
> Did you mean: pkg_preinst?
Of course.
>> -if [[ "${ROOT:-/}" != "/" ]] ; then
>> +if [[ ${ROOT:-/} != "/" ]] ; then
> I suppose you can unquote RHS too since it
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
Unless anybody speaks up who is still using them, I'm going
> On Thu, 28 Nov 2019, Michał Górny wrote:
>> The difference is that there is now a QA warning for something that
>> is perfectly within the spec. Maybe the extra verboseness would be
>> enough, but the eqawarn line should be omitted? It doesn't provide
>> any info that isn't already present
> On Wed, 27 Nov 2019, Michael Orlitzky wrote:
> This now disagrees with the PMS algorithm, doesn't it?
The difference is that there is now a QA warning for something that is
perfectly within the spec. Maybe the extra verboseness would be enough,
but the eqawarn line should be omitted? It
> On Wed, 27 Nov 2019, Anthony G Basile wrote:
> 2) For net-vpn/tor
> tor uid = 493
> tor gid = 493
We had skipped allocation for 492 and 493, because they're used for
oprofile and oidentd in Archlinux, and we have these packages too.
I'd suggest UID and GID 43 for tor (following
> On Wed, 27 Nov 2019, Michał Górny wrote:
> Update the skel variable order to place S immediately after SRC_URI.
> This seems to be a growing trend, and is quite reasonable given that
> S usually matches the archive name, and e.g. if SRC_URI uses MY_P,
> then S usually uses it as well:
>
> On Tue, 26 Nov 2019, Thomas Deutschmann wrote:
> 500...999 is currently marked as "reserved" but this shouldn't block
> this assignment, should it?
It does.
> Therefore I am requesting uid and gid 818, both named "jenkins", for
> dev-util/jenkins-bin.
signature.asc
Description: PGP
# Ulrich Müller (2019-11-26)
# Upstream says: "Elib has been decommissioned as a separate package
# since its useful functions have long since been included in Emacs."
# Last release in 1995. Byte-compilation fails with Emacs 27.
# Masked for removal in 30 days. Bug #701160.
app-emacs/elib
> On Sun, 24 Nov 2019, Sergei Trofimovich wrote:
> I interpreted 'reserved' as 'free to use' on
> https://wiki.gentoo.org/wiki/Project:Quality_Assurance/UID_GID_Assignment
> Can you tweak it to someting other than 'reserved' so it would be clear?
That's what the "Notes" column was
> On Sun, 24 Nov 2019, Sergei Trofimovich wrote:
> I've effectively reserved space for 1000 users for each of them:
> - 3..30999
> - 31000..31000
> and using only 10 of each.
That's inside the UID_MIN..UID_MAX range which should be reserved for
assignment on users' systems. Can't you
> On Tue, 19 Nov 2019, Daniele Rondina wrote:
> Ubuntu uses UID 105 and GID 109.
> I see that both are free, can i proceed with these?
Any good reason for using a different ID for user and group?
Redhat and Fedora use UID and GID 95 for radiusd, which appears to be
free, too.
Ulrich
> On Sun, 17 Nov 2019, rudi wrote:
> Is there a way to un-last-rite this package? It's more of a toy (like
> cowsay and lolcat) than anything, however some of the formatting
> options can be very nice when you set up borders and the like.
[Please don't top-post.]
> On Nov 16, 2019 20:29,
> On Fri, 15 Nov 2019, Michael Orlitzky wrote:
> Two things on that page are outright wrong:
> 1. If the package has stable keywords, they should be moved to the
> new revision without dropping. To commit the ebuild, repoman
> commit --straight-to-stable option should be used.
>
This installs firmware for the Intel® Centrino® Wireless-N 1000 device.
I no longer have any hardware to test it.
The package is somewhat redundant, because sys-kernel/linux-firmware
installs the same files. (Same for all other sys-firmware/iwl*-ucode
packages.)
Ulrich
signature.asc
> On Thu, 14 Nov 2019, Joakim Tjernlund wrote:
> And pkg move will move all pkgs within sys-libs/ncurses ?
Yes, "move" only accepts (qualified) package names without versions.
> Or could portage move only sys-libs/ncurses-5.9-r5 to
> sys-libs/ncurses-compat-5.9-r5 ?
No.
Ulrich
For some reason, the list has replaced my Reply-To header pointing
to gentoo-project by one pointing to gentoo-dev.
Please send any replies to the gentoo-project mailing list, so that the
discussion will be in one place.
Ulrich
signature.asc
Description: PGP signature
> On Wed, 06 Nov 2019, Michał Górny wrote:
> # Old EAPI 0 graphics-related packages.
> #
> # media-gfx/aoi was last bumped in Nov 2009. It is still actively
> # developed upstream, and it's waiting for a bump since Dec 2009.
> # It suffers from bundled dependencies (#177026).
> #
> #
>>>>> On Tue, 29 Oct 2019, Michał Górny wrote:
> On Tue, 2019-10-29 at 14:09 +0100, Ulrich Mueller wrote:
>> > What if the file is hosted at a non-standard tcp port upstream
>> > (like http://example.org:8080/)? The devmanual says that it _must_
>> > b
>>>>> On Tue, 29 Oct 2019, Ulrich Mueller wrote:
>>>>> On Tue, 29 Oct 2019, Michał Górny wrote:
>> The file should be placed in SRC_URI, and emirrordist will take care
>> of fetching it.
> What if the file is hosted at a non-standard tcp
>>>>> On Tue, 29 Oct 2019, Michał Górny wrote:
> On Tue, 2019-10-29 at 13:23 +0100, Ulrich Mueller wrote:
>> So, what has to be be done to have it appear in the proper place?
>> Should the file be placed in a subdir of /space/distfiles-local/?
>> That seems to
> On Tue, 29 Oct 2019, Michał Górny wrote:
> Dnia October 29, 2019 9:34:01 AM UTC, Fabian Groffen
> napisał(a):
>> /space/distfiles-local is no longer copied to the mirrors? or just
>> not copied in the subdir-hierarchy?
> The latter.
So, what has to be be done to have it appear in the
> On Mon, 28 Oct 2019, Andreas Sturmlechner wrote:
> News-Item-Format: 1.0
I'm aware that it's not required by policy to use the newest format,
but is there any particular reason for not using 2.0?
More generally, can we deprecate News-Item-Format 1.0?
Ulrich
signature.asc
Description:
> On Thu, 24 Oct 2019, Michał Górny wrote:
> +in 2⁴ = 16 directories), and each of this directories would have
s/this/these/ (This was there before, but can be corrected while at it.)
> +The implementations are only required to support cutoffs being multiples
s/The
> On Tue, 22 Oct 2019, Jaco Kroon wrote:
> I also agree with others that it used to be easy to get distfiles as
> and when needed, so an alternative structure could mirror that of the
> portage tree itself, in other words "cat/pkg/distfile".
Not a good idea, because some distfiles are shared
> On Mon, 21 Oct 2019, Michał Górny wrote:
> This also removes most of the other options that are irrelevant or even
> undesirable to distfile fetching, that is:
> - '-r' since we always fetch a single file, so recursive operation is
> unnecessary
> - '-p', '-o', '-g' since we want to
> On Mon, 21 Oct 2019, Joshua Kinard wrote:
> - altfont is licensed under "GNU General Public License" (version ??)
> - achemso is licensed under "The LaTeX Project Public License 1.3c"
> - arraysort is licensed under "The LaTeX Project Public License 1.2"
> - amsfonts is licensed
> On Sun, 20 Oct 2019, David Seifert wrote:
>> > - [[ -n ${DOCS} ]] && { dodoc ${DOCS} || die "docs installation
>> > failed" ; } # TODO old EAPI cleanup
>> > + einstalldocs
>> >
>> ># install common docs
>> > - for commondoc in COPYRIGHT README{,.md,.txt} NEWS AUTHORS BUGS
>> >
> On Sun, 20 Oct 2019, David Seifert wrote:
> - if [[ -e fonts.alias ]]; then
> - doins fonts.alias || die "failed to install
> fonts.alias" # TODO old EAPI cleanup
> - fi
> + [[ -e fonts.alias ]] && doins fonts.alias
> fi
> }
> On Wed, 16 Oct 2019, William Hubbs wrote:
> Please read the links I posted before --specifically the comments
> from Rob.
You mean this?
http://lists.busybox.net/pipermail/busybox/2010-December/074114.html
It only says that "in 1974 [...] everything was statically linked", but
not
> On Tue, 15 Oct 2019, Michał Górny wrote:
> On Tue, 2019-10-15 at 16:47 -0400, Mike Gilbert wrote:
>> Maybe you should join the project? Especially if you are making major
>> contributions.
> Are you suggesting that I join the project and start committing
> without review, or disregarding
> On Wed, 16 Oct 2019, William Hubbs wrote:
> Back in the day, the s in /sbin and /usr/sbin meant static, not super
> user. All binaries in those directories were statically linked.
Where have you found that statement? The "s" stands for "system",
not for "static". See for example [1].
> On Fri, 11 Oct 2019, Thomas Deutschmann wrote:
> Tilde expansion only happens when string to expand starts with "~" but
> this is not the case here (string starts with "https...").
I stand corrected.
> On Thu, 10 Oct 2019, Michał Górny wrote:
> Wasn't ALLARCHES supposed to be applied only if a previous version had
> a stable keyword on the arch in question? I.e. if it has been tested
> by arch team at least once?
Yes, but the same would apply to most of the elisp code that is shipped
Most packages in the app-emacs category have stabilize-allarches in
their metadata because they are arch independent. However, their
keywords don't reflect this and differ from package to package, mostly
for historical reasons.
So, I would like to mass keyword all ebuilds in app-emacs (as far as
> On Wed, 09 Oct 2019, Craig Andrews wrote:
> I would like to reserve UID/GID 545 for deluge (net-p2p/deluge).
> We currently use dynamic UID/GIDs.
> As far as I can tell, UID/GID 545 is free [1]
> [1] https://api.gentoo.org/uid-gid.txt
No, there's this line:
- 500..999 500..999
> On Thu, 10 Oct 2019, Mike Pagano wrote:
> + GENPATCHES_URI+=" ${use_cond_start}$(echo
> https://dev.gentoo.org/~{mpagano,whissi}/dist/genpatches/${tarball})${use_cond_end}"
The ~ should be backslash-escaped or quoted, otherwise it will be
expanded if there's a user mpagano or whissi on
> On Wed, 09 Oct 2019, Mike Pagano wrote:
> - GENPATCHES_URI+="
> ${use_cond_start}mirror://gentoo/${tarball}${use_cond_end}"
> + GENPATCHES_URI+="
> ${use_cond_start}https://dev.gentoo.org/~mpagano/dist/genpatches/${tarball}${use_cond_end}
>
> +
# Ulrich Müller (2019-10-01)
# Fails byte-compilation with recent Emacs versions.
# Homepage and SRC_URI are gone. Upstream package
# is unmaintained, according to EmacsWiki.
# Masked for removal in 30 days. Bug #666836.
app-emacs/mode-compile
signature.asc
Description: PGP signature
> On Sun, 29 Sep 2019, Michał Górny wrote:
> Why is it useful? In my opinion, the most important point is that it
> stops third parties from sniffing what the Gentoo hosts are fetching
> and using this information against them.
It won't hide the fact that a connection was established. Also,
> On Wed, 25 Sep 2019, Luke Dashjr wrote:
> There is no standard UID number for this purpose, and other distros
> don't appear to have it assigned in their lists either. 493 was just
> the highest one <500 available.
Archlinux uses 492 and 493 for packages that we also have, so we skipped
> On Tue, 24 Sep 2019, Matt Turner wrote:
> Just responding because the absurdity of this angers me, to be honest.
> See if you notice anything funny about the URL:
> https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html
What do you mean? Should we localise it, because translations
> On Tue, 24 Sep 2019, Jason Zaman wrote:
> The "GPL-2.0" one is deprecated:
> https://spdx.org/licenses/GPL-2.0.html
> If SPDX moved to having two names "-only" and "-or-later" then we
> should too.
The main problem is that we will always have licenses that are not in
their list. So if
> On Sun, 22 Sep 2019, Matt Turner wrote:
> An idea to consider: use SPDX license identifiers (see
> https://spdx.org/licenses/)
> For GPL 2 they are "GPL-2.0-only" and "GPL-2.0-or-later"
Yeah, they have a history of using silly names. What does 2.0 mean?
There is no such version of the
> On Sun, 22 Sep 2019, Matt Turner wrote:
> We are all aware. But the point is to explicitly put "-only" in the
> LICENSE metadata so that ebuild authors are less likely to confuse
> GPL-2 vs GPL-2+.
I don't see how renaming could possibly help with that.
>> Plus, it would result in
> On Sat, 21 Sep 2019, Michał Górny wrote:
> I'd like to propose to employ a more systematic method of resolving this
> problem. I would like to add additional explicit 'GPL-n-only' licenses,
> and discourage using short 'GPL-n' in favor of them. The end result
> would be three licenses per
> On Sat, 21 Sep 2019, Michał Górny wrote:
> That's my initial thought as well but I'm going to check them, just in
> case. That is, unless the proposal is rejected.
Please check this, before we are going to decide on it.
Ulrich
signature.asc
Description: PGP signature
> On Sat, 21 Sep 2019, Michał Górny wrote:
> We currently have @BINARY-REDISTRIBUTABLE license group that somewhat
> concerns RESTRICT=bindist. I think it'd be reasonable to introduce
> a matching group concerning RESTRICT=mirror.
This would be a superset of @BINARY-REDISTRIBUTABLE, I
> On Sat, 21 Sep 2019, Michał Górny wrote:
> TL;DR: I'd like to replace 'GPL-2' with 'GPL-2-only' etc., having
> the former trigger QA warning asking the dev to double-check if it's
> 'GPL-2-only' or 'GPL-2+'.
This has been discussed before. There is no such license as GPL-2-only.
Ulrich
> On Sun, 15 Sep 2019, Michał Górny wrote:
> The eclass is currently used by exactly one ebuild which is at EAPI 5.
> Let's restrict allowed EAPIs just to 5 and 7, to cover a reasonable
> upgrade path for that ebuild while blocking proliferation of old
> EAPIs.
This is a pointless change,
> On Fri, 13 Sep 2019, Patrick McLean wrote:
> Something's presence in the tree does not mean that you are required
> to install it. A package's presence in the tree really has little to
> zero effect on any user that does not use the package.
I wonder if that's always true. Distros adopting
> On Fri, 13 Sep 2019, Manoj Gupta wrote:
> Thanks for the review. I did it this way to make this an exact copy of
> tc-ld-is-gold function above it except the LLD checks.
> Should I also change the tc-ld-is-gold function?
Good question. Presumably the eclass maintainers should have the
> On Fri, 13 Sep 2019, Manoj Gupta wrote:
>> LLD is a new linker for LLVM project.
>> Add tc-ld-is-lld helper to be able to detect it.
>>
>> Signed-off-by: Manoj Gupta
>> ---
>> eclass/toolchain-funcs.eclass | 30 ++
>> 1 file changed, 30 insertions(+)
>>
>> diff
> On Mon, 09 Sep 2019, William Hubbs wrote:
> There is another option I want to try which is adding "go mod vendor"
> to src_unpack for go packages.
That's pretty much a no-go for a regular Gentoo package, because it
would circumvent checksum verification, and would require network access
at
> On Sun, 08 Sep 2019, Michał Górny wrote:
> Here's a better list, containing intersection of x86-only + EAPI 0:
> media-video/maven-poke
> net-misc/netprofiles-ims
> sys-boot/psoload
AFAICS, these three are not redistributable (with wrong LICENSE info
in their ebuilds) and have dead
>>>>> On Fri, 06 Sep 2019, Ulrich Mueller wrote:
> # Ulrich Müller (2019-09-06)
> # Unmaintained upstream, last release in 2006.
> # Use app-emacs/mediawiki as replacement.
> # Masked for removal in 30 days, bug #693598.
> app-emacs/wikipedia-mode
Unmasked agai
# Ulrich Müller (2019-09-06)
# Unmaintained upstream, last release in 2006.
# Use app-emacs/mediawiki as replacement.
# Masked for removal in 30 days, bug #693598.
app-emacs/wikipedia-mode
signature.asc
Description: PGP signature
> On Wed, 04 Sep 2019, Michał Górny wrote:
> +# Copyright 2019 Gentoo Authors
> +# Distributed under the terms of the GNU General Public License v2
> +
> +# @ECLASS: sgml-catalog-r1.eclass
> +# @MAINTAINER:
> +# Michał Górny
> +# @AUTHOR:
> +# Michał Górny
> +# @BLURB: Functions for
>>>>> On Sat, 31 Aug 2019, Ulrich Mueller wrote:
> AFAICS, 484 would be the next free number (when counting down from 499).
I just see that i2pd has 470, maybe take the adjacent 471?
signature.asc
Description: PGP signature
> On Sat, 31 Aug 2019, Tharrvik wrote:
> `net-vpn/i2p` currently adds a "i2p" user and group with a random
> uid/gid; it needs to run a daemon. I'm the proxy-maint for it so I
> created acct-{user,group}/i2p and assigned 493:493 which are free
> according to
# Ulrich Müller (2019-08-30)
# Last visible upstream activity in 2013. Doesn't work with Emacs 24.3
# or newer. Byte-compilation of newest upstream version 1.3.1 fails.
# Masked for removal in 30 days, bug #693118.
app-emacs/identica-mode
signature.asc
Description: PGP signature
# Ulrich Müller (2019-08-26)
# A more recent version of thumbs.el is distributed
# as part of GNU Emacs proper.
# Masked for removal in 30 days, bug #692882.
app-emacs/thumbs
signature.asc
Description: PGP signature
> On Fri, 23 Aug 2019, Alexey 'Alexxy' Shvetsov wrote:
> В письме от пятница, 23 августа 2019 г. 22:39:29 MSK пользователь
> Mike Gilbert написал:
>> I think we are trying to avoid using 500 too 999 for the time being.
>> Can you pick another number lower than 500?
> uid/gid 500 was used
> On Fri, 23 Aug 2019, The Bit Pit wrote:
> I selected UID 103 since my system used it before digital ATSC signals
> were available in the USA.
Archlinux uses 103 for minio, so better choose something different.
AFAICS, next free UID would be 484 (counting from 499 downwards).
> On Sat, 17 Aug 2019, Michał Górny wrote:
> Here's v2 of my proposed format. Two changes:
> 1. I've changed the 'header line' to start with '#!', so comment
> stripping normally takes care of it without having to do extra work.
> 2. I've allowed Markdown syntax in note field, so that we
> On Sat, 17 Aug 2019, Michał Górny wrote:
> +RDEPEND="${COMMON_DEPEND}
> + dev-vcs/git"
Shouldn't there be a blocker against dev-vcs/gitolite{,-gentoo}
(and vice versa)? These packages cannot be installed at the same time,
and I guess that a direct blocker would result in a friendlier
> On Sat, 17 Aug 2019, Michael Orlitzky wrote:
> 1 Avoid using an ACCT_USER_HOME that belongs to another package.
> 2 No two acct-user packages should define the same ACCT_USER_HOME.
These two points are not fulfilled by the users that currently belong
to baselayout. For example,
From: Arfrever Frehtes Taifersar Arahesis
Date: Mon, 13 May 2019 16:30:15 +0200
Print warning if usage of swap appears to be needed.
Closes: https://bugs.gentoo.org/569966
Signed-off-by: Arfrever Frehtes Taifersar Arahesis
Signed-off-by: Ulrich Müller
---
eclass/check-reqs.eclass | 22
> On Thu, 15 Aug 2019, Mike Gilbert wrote:
> + # Path might be missing due to INSTALL_MASK, etc.
> + # https://bugs.gentoo.org/691478
> + if [[ -e "${ED}/${ACCT_USER_HOME#/}" ]]; then
> + fowners "${ACCT_USER_HOME_OWNER}"
> On Tue, 13 Aug 2019, Michael Orlitzky wrote:
> The devmanual is probably wrong,
> https://bugs.gentoo.org/485356
> but no one agrees on how exactly to change it.
Thanks for reminding us of that bug. :) Read my comments #13 and #16.
Ulrich
signature.asc
Description: PGP signature
> On Tue, 13 Aug 2019, Matt Turner wrote:
> +# Even though xz-utils are in @system, they must still be added to DEPEND;
> see
> +#
> https://archives.gentoo.org/gentoo-dev/msg_a0d4833eb314d1be5d5802a3b710e0a4.xml
I didn't understand that argument in 2011, and I understand it even
less in
> On Sun, 11 Aug 2019, William Hubbs wrote:
> Well, I suppose it wouldn't be a problem if we don't care about
> alignment, but that is not readable either really right?
> For example, (completely making up uid/gid numbers), this is totally
> valid.
> root 0 0 baselayout this is from
> On Sat, 10 Aug 2019, William Hubbs wrote:
> I propose using a colon like we do in /etc/passwd:
> root:0:0:baselayout:
> bin:1:1:baselayout:some notes go here
Please no. I thought the purpose of this exercise was to have a format
that is human readable, and not something with strange
> On Wed, 07 Aug 2019, Michał Górny wrote:
> On Tue, 2019-08-06 at 13:41 +0200, Jaco Kroon wrote:
>> Attaching. It seems for some reason if I inline the patches they don't
>> come through. If I mail to myself only it works just fine.
> Actually, I think it should be changed the other way
> On Wed, 07 Aug 2019, Mikle Kolyada wrote:
> +Both ``acct-group`` and ``acct-user`` eclasses have the ``KEYWORDS``
> +variable predefined, keywords must not be altered locally via ebuilds.
> +
GLEP 81 doesn't specify anything about the implementation. In fact,
it neither requires that it
> On Wed, 07 Aug 2019, Eray Aslan wrote:
> So do we ask acct-group/input to change their GID? why add an already
> used fixed gid to baselayout in the first place (and one that is used on
> other distros as well)? whats the thinking here?
> or we can change dovecot uid/gid. I dont mind but
> On Wed, 07 Aug 2019, Eray Aslan wrote:
> I would like to reserve UID/GID 484 for dovenull (net-mail/dovecot).
> Arch uses uid 74 for dovenull while Redhat uses next available.
Wouldn't it make sense to keep dovecot and dovenull together, i.e. use
97 for dovecot and 98 for dovenull?
> On Mon, 05 Aug 2019, Mike Gilbert wrote:
> I would like to reserve UID/GID 102 for polkitd (sys-auth/polkit).
> This is the same ID used by Arch Linux.
+1
Can everyone please switch to this style of RFC?
I am getting tired of looking at trivial acct-{user,group} ebuilds and
metadata
> On Tue, 06 Aug 2019, Lars Wendler wrote:
> +ACCT_GROUP_ID=104
Collides with Arch's nm-openconnect (which we have as
net-vpn/networkmanager-openconnect).
signature.asc
Description: PGP signature
> On Tue, 06 Aug 2019, Lars Wendler wrote:
> -ACCT_GROUP_ID=210
> +ACCT_GROUP_ID=103
Note that 103 will collide with Arch's "minio" user and group. We have
that package too, as net-fs/minio.
Ulrich
signature.asc
Description: PGP signature
> On Tue, 06 Aug 2019, Kent Fredric wrote:
>> Can you give an example of a maintainer in the watcher \ upstream set?
> all maintainers who aren't upstream are just maintainers
> all maintainers who are upstream are just maintainers
> all maintainers are watchers
> So:
> { watcher {
> On Tue, 06 Aug 2019, Kent Fredric wrote:
> All fit within
> , but not all
> fits within
Can you give an example of a maintainer in the watcher \ upstream set?
Ulrich
signature.asc
Description: PGP signature
> On Sun, 04 Aug 2019, Conrad Kostecki wrote:
> +DESCRIPTION="An user for the FHEM perl server for house automation"
s/An user/A user/
> +ACCT_USER_ID="489"
Any particular rationale for this ID? AFAICS, the next available one
would be 491 (if we reserve 492 and 493 for oprofile and
> On Sat, 03 Aug 2019, Michał Górny wrote:
>> Upstream developers can be listed already now in the
>> description (per GLEP 68). Should they be listed twice now, only to
>> indicate that they are to be CCed on bugs?
> This is happening already. I'm not saying it's perfect but I don't see
>
> On Sat, 03 Aug 2019, Thomas Deutschmann wrote:
> + [[ -r ${configfile} ]] ||
> configfile=${base}/${CHOST:+"${CHOST}/"}${check}
Long line.
signature.asc
Description: PGP signature
> On Sat, 03 Aug 2019, Thomas Deutschmann wrote:
> + ewarn "provide a configuration file in
> ${PORTAGE_CONFIGROOT%/}/etc/portage/savedconfig/${CATEGORY}/${PN}"
Long line.
signature.asc
Description: PGP signature
> On Sat, 03 Aug 2019, Thomas Deutschmann wrote:
> +# @ECLASS-VARIABLE: _SAVEDCONFIG_CONFIGURATION_FILE
31 chars? Seems excessive for a name of a private variable.
> +# Restores the configuration saved ebuild previously potentially with user
> edits.
If have trouble understanding this
> On Fri, 02 Aug 2019, Michał Górny wrote:
> Add two new maintainer types: 'proxied' for proxied maintainers,
> and 'watcher' for people who wish to be CC-ed on bugs but are not
> maintainers (e.g. upstream developers).
Upstream developers can be listed already now in the
description (per
601 - 700 of 2165 matches
Mail list logo
