| 1 |
On 10/20/2013 06:18 PM, Markos Chandras wrote: |
| 2 |
> On 10/19/2013 06:43 PM, Tom Wijsman wrote: |
| 3 |
|
| 4 |
>> P.S.: It is interesting to see the effects of AutoRepoman beating |
| 5 |
>> people to filing bugs, maybe I should write AutoNotifyman as a |
| 6 |
>> response to not having the chance to file the bug in a reasonable |
| 7 |
>> time frame. |
| 8 |
> |
| 9 |
> The AutoRepoman script is there just for convenience. You shouldn't |
| 10 |
> take it too seriously and go filing bugs like crazy. |
| 11 |
|
| 12 |
Every dependency-warning it creates is a failure of one or more devs to |
| 13 |
check dependencies and reverse-dependencies or the effects of |
| 14 |
package.mask'ing or removing ebuilds. |
| 15 |
|
| 16 |
They should not happen, yet I file on average one or two bugs a day |
| 17 |
because of this. |
| 18 |
(And most affected are the "big minor arches", arm/hppa/ppc, as they |
| 19 |
have the largest set of keyworded packages and the least amount of devs |
| 20 |
proportionally. It's not nice to keep breaking their stuff ...) |
| 21 |
|
| 22 |
> The affected |
| 23 |
> packages can slowly be fixed. It's not like they are totally broken |
| 24 |
> but it's more like of another way to tell you that a few QA problems |
| 25 |
> exist and that it would be nice to fix them whenever you find some time. |
| 26 |
|
| 27 |
You mean situations where there is user-visible breakage in the |
| 28 |
dependency graphs? |
| 29 |
|
| 30 |
If I were a member of the QA team (which for various reasons I've never |
| 31 |
been allowed to be, which is quite hilarious) I'd ask you to remember |
| 32 |
the "repoman || die" motto we beat into every new recruit and/or ask you |
| 33 |
to honourably disable your commit privileges. |
Archives