| 1 |
Would make a very nice QA measure. Any outdated/broken ebuild could be |
| 2 |
auto reported to bugzilla and removed in 72 hours if no responce. |
| 3 |
|
| 4 |
I think gentoo really needs QA measures of this sort. Like in debian, |
| 5 |
packages get moved up from unstable to testing automatically if no |
| 6 |
critical reports were made for 2 weeks. |
| 7 |
|
| 8 |
This could have really great potential. Tests can be added to the |
| 9 |
script to track new discovered problems, then repoman can be tied down |
| 10 |
on the same system as this periodic test. |
| 11 |
|
| 12 |
Very nice idea indeed. Any chance we could see the code? |
| 13 |
|
| 14 |
On Sun, 31 Oct 2004 10:25:25 +0100, Henrik Brix Andersen |
| 15 |
<brix@g.o> wrote: |
| 16 |
> Hi, |
| 17 |
> |
| 18 |
> On Sat, 2004-10-30 at 16:53, Daniel Ahlberg wrote: |
| 19 |
> > This is an automatically created email message. |
| 20 |
> > http://gentoo.tamperd.net/stable has just been updated with 8758 ebuilds. |
| 21 |
> |
| 22 |
> Could someone please explain to me what the above mentioned site can be |
| 23 |
> used for? |
| 24 |
> |
| 25 |
> I've checked the site a few times, but my email isn't even listed in the |
| 26 |
> drop-down list, and the package entries for packages maintained by the |
| 27 |
> mobile herd (to which I am enslaved) are not exactly up-to-date. |
| 28 |
> |
| 29 |
> Sincerely, |
| 30 |
> Brix |
| 31 |
> -- |
| 32 |
> Henrik Brix Andersen <brix@g.o> |
| 33 |
> Gentoo Linux |
| 34 |
> |
| 35 |
> |
| 36 |
> |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives