From: Tobias Scherbaum <dertobi123@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for how to handle stable ebuilds
Date: Mon, 17 Nov 2008 19:08:39 +0100 [thread overview]
Message-ID: <1226945319.3939.30.camel@homer.ob.libexec.de> (raw)
In-Reply-To: <20081115130210.GA4219@pluto>
[-- Attachment #1: Type: text/plain, Size: 2222 bytes --]
Matti Bickel wrote:
> Tobias Scherbaum <dertobi123@gentoo.org> wrote:
> > What if this would break deps or it's a very common package for example
> > belonging to the set of system packages?
>
> Then the maintainer moans and does nothing. I guess that's where the
> "MAY" part from above comes in. Policy should not be an excuse to stop
> thinking. And if i break a user system when i drop my stable keywords,
> IMHO i'm violating the 'work as pleasently and efficiently as possible'
> bit of our philosophy.
That would people require to use common sense. The past has shown that
people tend to have different views of what common sense might be in a
given case. Therefore policy in that aspect needs to be as clear and
understandable as possible to avoid unnecessary discussions.
> So bottom-line: i'm very much in favour of your solution to question #1.
> And i'd like to stress the "automatic" bit. Yes, we can get access to
> tinderboxes. But last i looked, this involved tracking down the person
> responsible for it, asking for access and doing everything you need to
> get your package to compile. Well, i'm lazy, so i didn't do it.
>
> Automatic tinderbox testing would very much help in the process. Maybe
> someone can write a script so that once a maintainer opens/gives his OK
> to a stable bug, automatic testing could be started and the results
> posted back to the bug?
Sounds like a very good and doable idea to me. Process might be as easy
as CC'ing a arch-tinderbox on a bug, a script does parse the bug number
out of the mail being sent out and using gatt it catches the ebuild to
test, compiles it and reports back a) failure/success, b) error log as
attachment if it fails plus c) if there was a test-phase.
Might be just a quick hack using pybugz and gatt :)
> After the timeframe (30 days? 60? I don't know, and it's not important
> at this point) maintainers could move to stable their package themself
> IF the automatic tests indicate success AND no arch member has spoken
> up.
Agreed.
Tobias
--
Gentoo Linux - Die Metadistribution
http://www.mitp.de/5941
http://www.metadistribution.eu
https://www.xing.com/profile/Tobias_Scherbaum
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-17 18:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 18:13 [gentoo-dev] Proposal for how to handle stable ebuilds Mark Loeser
2008-11-10 18:23 ` Ciaran McCreesh
2008-11-10 18:23 ` Mart Raudsepp
2008-11-10 20:32 ` Steev Klimaszewski
2008-11-10 21:16 ` Jeremy Olexa
2008-11-10 21:57 ` Santiago M. Mola
2008-11-11 0:24 ` Jose Luis Rivero
2008-11-11 1:13 ` Mark Loeser
2008-11-11 9:31 ` Jose Luis Rivero
2008-11-11 1:21 ` Richard Freeman
2008-11-11 8:56 ` Peter Volkov
2008-11-11 10:18 ` Jose Luis Rivero
2008-11-11 13:49 ` Ferris McCormick
2008-11-11 16:06 ` [gentoo-dev] " Duncan
2008-11-11 16:24 ` Jeroen Roovers
2008-11-11 17:26 ` Duncan
2008-11-11 17:55 ` Ferris McCormick
2008-11-11 18:12 ` Jeroen Roovers
2008-11-11 21:03 ` Duncan
2008-11-13 17:38 ` [gentoo-dev] " Tobias Scherbaum
2008-11-15 13:02 ` Matti Bickel
2008-11-17 18:08 ` Tobias Scherbaum [this message]
2008-11-17 19:03 ` [gentoo-dev] " Duncan
2008-12-11 5:35 ` [gentoo-dev] " Donnie Berkholz
2008-11-17 0:38 ` [gentoo-dev] " Ryan Hill
2008-11-17 15:10 ` Daniel Gryniewicz
2008-11-18 1:08 ` Ryan Hill
2008-11-18 16:57 ` Daniel Gryniewicz
2008-11-18 17:50 ` Ciaran McCreesh
2008-11-18 20:31 ` Daniel Gryniewicz
2008-11-18 21:18 ` Ryan Hill
2008-11-18 22:04 ` Daniel Gryniewicz
2008-11-18 22:45 ` Ryan Hill
2008-11-30 22:59 ` Ryan Hill
2008-12-01 7:49 ` Peter Volkov
2008-12-11 5:37 ` [gentoo-dev] " Donnie Berkholz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1226945319.3939.30.camel@homer.ob.libexec.de \
--to=dertobi123@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox