Gentoo Archives: gentoo-dev

From: James Le Cuirot <chewi@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] ebuild life cycle review
Date: Sat, 11 Apr 2020 15:53:52
Message-Id: 20200411165339.53f4aae7@symphony.aura-online.co.uk
In Reply to: Re: [gentoo-dev] ebuild life cycle review by Jonas Stein
1 On Fri, 10 Apr 2020 18:21:00 +0200
2 Jonas Stein <jstein@g.o> wrote:
3
4 > > I would like to leave a suggestion for Gentoo portage ebuild review.
5 > > Since there are some ebuilds in portage that become outdated for more
6 > > than one year when there are new versions available, maybe could be
7 > > possible to add a new step in Gentoo QA service to generate an alarm
8 > > (send email to project and CI leaders) to request a human review.
9 >
10 > This service does already exist. Everybody can use repology [1], euscan
11 > [2] and others.
12 >
13 > Bumping a package needs time - especially for testing. I work a lot on
14 > our bug tracker and my impression is that automatic bugs for a bump
15 > request are contra productive. We already have many important, but easy
16 > to fix open bugs.
17 > Automatic tickets for packages will flood bugzilla with tickets for
18 > unused packages and bind additional manpower.
19
20 Totally agree. I have already used euscan, and nowadays repology, and
21 they're very useful for keeping on top of the stuff I directly
22 maintain. I can also use them for the wider games team but there's a
23 mountain of work to do there and that's not even counting the constant
24 flood of largely automated bug reports we already get every day. I just
25 do what I can.
26
27 --
28 James Le Cuirot (chewi)
29 Gentoo Linux Developer

Replies

Subject Author
Re: [gentoo-dev] ebuild life cycle review Samuel Bernardo <samuelbernardo.mail@×××××.com>