Gentoo Archives: gentoo-dev

From: Thomas Cort <tcort@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: RFC: AT emerge info cruft > attachments on bugs.g.o
Date: Fri, 11 Aug 2006 13:43:59
Message-Id: 20060811094053.09b0dfe7.tcort@gentoo.org
In Reply to: [gentoo-dev] Re: RFC: AT emerge info cruft > attachments on bugs.g.o by gentoo@faulhammer.org (Christian 'Opfer' Faulhammer)
1 On 11 Aug 2006 00:00:00 +0000
2 gentoo@××××××××××.org (Christian 'Opfer' Faulhammer) wrote:
3
4 > Tach Jeroen, 0x2B859DE3 (PGP-PK-ID)
5 >
6 > Jeroen Roovers schrieb:
7 > > One solution might be to open your own AT bug, make the stabilisation
8 > > bug depend on it, and use the AT bug to have ATs post their `emerge
9 > > info`. Then, when testing and stabilisation is finished for your arch,
10 > > close the AT bug and remove your alias from the stabilisation bug's CC
11 > > list. I for one could live with this solution to the problem, which I
12 > > hope you understand by now.
13 >
14 > This sounds quite interesting...maybe some arch devs should comment on
15 > that. The only problem I see is when two ATs test at the same time and
16 > open two separate bugs for the same arch. And another problem: Other
17 > arches don't see the problems in the depending bug and are unlikely to
18 > comment on it.
19
20 Besides the points you mentioned, it would create a lot of bug
21 spam. There would be the "a new bug depends on this bug" e-mail when
22 the AT files the bug, then there would be the "a bug that depends on this
23 bug has changed state" e-mail when the arch dev closes the AT's
24 bug, and then there would be the e-mail from the arch dev when he/she
25 comments on the original bug saying "arch-xyz stable"
26
27 -Thomas