| 1 |
"Robin H. Johnson" <robbat2@g.o> said: |
| 2 |
> On Sun, Oct 19, 2008 at 12:32:44PM -0700, Alec Warner wrote: |
| 3 |
> > What if my herd email address is different from my bugzie address? |
| 4 |
> > Can I have both in herds.xml? What if my herd address *isn't* a |
| 5 |
> > bugzie account, will the world end? |
| 6 |
> |
| 7 |
> I don't know any herd where the herd email is not the same as the |
| 8 |
> bugzie email. Why would this case arise anyway? The mail aliases reside |
| 9 |
> on dev, and the duplication doesn't make sense. |
| 10 |
|
| 11 |
the gentopia guys seem to have this annoying scheme: herd email is |
| 12 |
utopia@g.o while bugzi account is gentopia@g.o |
| 13 |
|
| 14 |
> |
| 15 |
> > How can we automatically detect when developers make mistakes in |
| 16 |
> > editing herds.xml? |
| 17 |
> |
| 18 |
> There is a validation CGI in Bugzie, I created it for when somebody (I |
| 19 |
> forgot who) was checking all of the metadata and herd emails |
| 20 |
> previously, which we should probably automated. |
| 21 |
|
| 22 |
for me. i have started using it today.. thanks! |
| 23 |
|
| 24 |
> |
| 25 |
> > > 1. For handling <herd>no-herd</herd>, we should add an entry into |
| 26 |
> > > herds.xml to catch it (maintainer-needed <at> g.o). Every herd |
| 27 |
> > > listed in an ebuild MUST be in herds.xml. |
| 28 |
> > |
| 29 |
> > You and I both know this is not going to be true. Complicated |
| 30 |
> > solution; make Repoman do it. Certainly it is the 'correct' thing to |
| 31 |
> > do; however I don't expect it to get implemented or deployed quickly. |
| 32 |
> > Hacky solution: run script on osprey that tries to validate tree |
| 33 |
> > metadata against herds.xml and annoy herds who forgot to add |
| 34 |
> > themselves. |
| 35 |
> |
| 36 |
> Yes, automation is useful here. |
| 37 |
|
| 38 |
very few packages do not have a herd; no ebuilds have a wrong herd listed, |
| 39 |
but there are tons of other errors in our metadata... |
Archives