Hi,
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 can link
commits similarly to how we do it on wiki.
Add 'git' user. UID 196 is used on Arch Linux for gitolite which serves
the same purpose as 'git' in Gentoo.
Note that since we have multiple git hosting providers in Gentoo,
and they use disjoint home directories, we need to use USE flags to
control the provider used. Upon switching flags, the
Add 'git' group. UID 196 is used on Arch Linux for gitolite which
serves the same purpose as 'git' in Gentoo.
Signed-off-by: Michał Górny
---
acct-group/git/git-0.ebuild | 8
acct-group/git/metadata.xml | 8
2 files changed, 16 insertions(+)
create mode 100644 acct-group/git/
Signed-off-by: Michał Górny
---
www-apps/gitea/gitea-1.8.3-r1.ebuild | 102 +++
1 file changed, 102 insertions(+)
create mode 100644 www-apps/gitea/gitea-1.8.3-r1.ebuild
diff --git a/www-apps/gitea/gitea-1.8.3-r1.ebuild
b/www-apps/gitea/gitea-1.8.3-r1.ebuild
new file mo
Signed-off-by: Michał Górny
---
dev-vcs/gitolite/gitolite-3.6.11-r1.ebuild | 90 ++
dev-vcs/gitolite/gitolite-.ebuild | 22 ++
2 files changed, 95 insertions(+), 17 deletions(-)
create mode 100644 dev-vcs/gitolite/gitolite-3.6.11-r1.ebuild
diff --git a/dev-vcs/g
Signed-off-by: Michał Górny
---
.../gitolite-gentoo-3.6.6.1-r2.ebuild | 93 +++
.../gitolite-gentoo-.ebuild | 25 +
2 files changed, 98 insertions(+), 20 deletions(-)
create mode 100644 dev-vcs/gitolite-gentoo/gitolite-gentoo-3.6.6.1-r2.ebuild
diff
On Sat, 2019-08-17 at 09:06 +0200, Michał Górny wrote:
> Hi,
>
> Here's v2 of my proposed format.
Also example usage:
get user/group named 'adm'
$ awk '$1 == "adm"' uid-gid.txt
adm 3 4 baselayout
get records for UID 3:
$ awk '$2 == 3' uid-gid.txt
adm
> 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, "operat
> 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 er
On Sat, 2019-08-17 at 10:52 +0200, Ulrich Mueller wrote:
> > > > > > 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 t
Ühel kenal päeval, R, 16.08.2019 kell 19:58, kirjutas Thomas
Deutschmann:
> Hi,
>
> I like the idea. This will allow the following change in workflow:
>
> When you now want to last-rite app-misc/foo for example, you would
> schedule a CI run. I.e. create a pull request against Gentoo
> repository
On 8/17/19 4:54 AM, Michał Górny wrote:
> On Sat, 2019-08-17 at 10:52 +0200, Ulrich Mueller wrote:
>>
>> 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 f
On 8/17/19 2:36 AM, Eray Aslan wrote:
>
> For the record, it wasnt me who wrote those acct-user ebuilds.
Apologies, I checked the metadata and assumed that I missed these as
part of your patch series. In any case, I'm not trying to throw blame
around -- this is all new and we're still figuring it
On 8/17/19 12:29 AM, Haelwenn (lanodan) Monnier wrote:
>
> Any reason why sharing home directories isn't simply forbidden?
> This is sure to blow on us at some point if there is shared home directories.
>
> ...
>
> Shouldn't this be owned instead of writable? I'm pretty sure we can
> have case
On 8/17/19 4:35 AM, Ulrich Mueller wrote:
>
>> 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, "operator" (and "toor" on BSD) share /root
> with the root user.
>
Let me f
# Aaron Bauman (2019-08-17)
# Unmaintained, outstanding sec vuln bug #540360
# Lots of new versions upstream. Removal in 30 days.
dev-embedded/bitbake
--
Cheers,
Aaron
signature.asc
Description: PGP signature
# Aaron Bauman (2019-08-17)
# Outstanding sec vuln bug #544228. No releases from upstream
# Upstream still has not addressed the bug. Removal in 30 days.
dev-python/restkit
--
Cheers,
Aaron
signature.asc
Description: PGP signature
On Sat, 17 Aug 2019 10:35:29 +0200
Ulrich Mueller wrote:
> For example, "nobody" lives in /var/empty but cannot write to it, and
> that dir is owned by root.
What ensures that the permissions on /var/empty are correct for this
scenario?
Possibly having acct-* create a /var/lib/nobody or a /var/
# Aaron Bauman (2019-08-17)
# Relies on vulnerable automake:1.10
# Removal in 30 days
games-simulation/crrcsim
--
Cheers,
Aaron
signature.asc
Description: PGP signature
# Aaron Bauman (2019-08-17)
# Relies on vulnerable automake:1.10
# Removal in 30 days
games-simulation/crrcsim
media-gfx/pixie
--
Cheers,
Aaron
signature.asc
Description: PGP signature
# Aaron Bauman (2019-08-17)
# Relies on vulnerable automake:1.10
# Removal in 30 days
games-simulation/crrcsim
media-gfx/pixie
net-irc/eiwic
--
Cheers,
Aaron
signature.asc
Description: PGP signature
# Aaron Bauman (2019-08-17)
# Relies on vulnerable automake:1.10
# Removal in 30 days
games-simulation/crrcsim
media-gfx/pixie
net-irc/eiwic
net-misc/openrdate
--
Cheers,
Aaron
signature.asc
Description: PGP signature
On Fri, Aug 16, 2019 at 10:10 AM Michał Górny wrote:
>
> Hi,
>
> leio asked me yesterday for the possibility of marking packages
> as deprecated, so that CI would issue warnings when other packages
> depend on them. I think that's quite a good idea, so I'd like to
> propose a simple implementatio
On Fri, Aug 16, 2019 at 07:10:27PM +0200, Michał Górny wrote:
> Hi,
>
> leio asked me yesterday for the possibility of marking packages
> as deprecated, so that CI would issue warnings when other packages
> depend on them. I think that's quite a good idea, so I'd like to
> propose a simple implem
On Wed, 2019-08-07 at 19:10 +0200, Michał Górny wrote:
> Allow a special value of '-1' to dynamically assign UID/GID for the user
> or group. This is intended to be used in overlays where proper
> assignment does not take place but whose owners wish to switch to acct-*
> packages.
>
> While techn
Hi, Jaco.
On Thu, 2019-08-01 at 21:04 +0200, Jaco Kroon wrote:
> Looking at the new eclasses for acct-user and acct-group.
>
> These enforce that a group and user id should be set.
>
> This is not a requirement for enewuser nor enewgroup.
>
> As a further discrepancy, the user eclass requires >
On Sat, 2019-05-18 at 09:00 +0200, Michał Górny wrote:
> USE=colord is used in 11 packages consistently. Make it a global USE
> flag using the description from GNOME packages, and remove redundant
> local definitions.
>
> The local definition in x11-libs/gtk+ is left as it clarifies that
> the fl
On Sat, 2019-08-17 at 09:42 -0400, Michael Orlitzky wrote:
> On 8/17/19 4:54 AM, Michał Górny wrote:
> > On Sat, 2019-08-17 at 10:52 +0200, Ulrich Mueller wrote:
> > > Shouldn't there be a blocker against dev-vcs/gitolite{,-gentoo}
> > > (and vice versa)? These packages cannot be installed at the s
Add 'git' group. UID 196 is used on Arch Linux for gitolite which
serves the same purpose as 'git' in Gentoo.
Signed-off-by: Michał Górny
---
acct-group/git/git-0.ebuild | 8
acct-group/git/metadata.xml | 8
2 files changed, 16 insertions(+)
create mode 100644 acct-group/git/
Add 'git' user. UID 196 is used on Arch Linux for gitolite which serves
the same purpose as 'git' in Gentoo.
Note that since we have multiple git hosting providers in Gentoo,
and they use disjoint home directories, we need to use USE flags to
control the provider used. Upon switching flags, the
Signed-off-by: Michał Górny
---
www-apps/gitea/gitea-1.8.3-r1.ebuild | 104 +++
1 file changed, 104 insertions(+)
create mode 100644 www-apps/gitea/gitea-1.8.3-r1.ebuild
diff --git a/www-apps/gitea/gitea-1.8.3-r1.ebuild
b/www-apps/gitea/gitea-1.8.3-r1.ebuild
new file mo
Signed-off-by: Michał Górny
---
dev-vcs/gitolite/gitolite-3.6.11-r1.ebuild | 91 ++
dev-vcs/gitolite/gitolite-.ebuild | 23 ++
2 files changed, 97 insertions(+), 17 deletions(-)
create mode 100644 dev-vcs/gitolite/gitolite-3.6.11-r1.ebuild
diff --git a/dev-vcs/g
Signed-off-by: Michał Górny
---
.../gitolite-gentoo-3.6.6.1-r2.ebuild | 94 +++
.../gitolite-gentoo-.ebuild | 26 ++---
2 files changed, 100 insertions(+), 20 deletions(-)
create mode 100644 dev-vcs/gitolite-gentoo/gitolite-gentoo-3.6.6.1-r2.ebuild
diff
On 8/17/19 4:43 PM, Michał Górny wrote:
>>
>> I realize we'd have to tell people how to rename the account to support
>> upgrades -- but is there some other reason to keep the shared "git" name?
>
> The argument I've been told is that users expect 'git@...' to work
> as remote URI on their boxes.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
# Georgy Yakovlev (2019-08-17)
# Unmaintained both upstream and in gentoo, author retired
# Removal in 30 days
sys-kernel/bliss-initramfs
@fearedbliss retired a while ago.
upstream page[1] litreally says:
"This project is no longer in development.
> 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 ca
36 matches
Mail list logo
