On 25/11/16 17:51, Jason Zaman wrote: >> Automation >> ========== >> >> It's easy to forget to check that all the required dependencies are in >> stable before filing a stabilisation test, but this wastes the actioning >> developer's time. I have prepared a bot that repoman checks the list of >> atoms and flags the bug appropriately. This allows easy filtering out of >> broken requests. > > This part would need to take into account DEPENDS ON in the bug too. > When I file my xfce lists I dep on the gnome stable bug since I need > the gtk stuff and if that isnt taken into account, repoman would just > die.
The bot will either try its best to take into account bug dependencies, or otherwise just give up and skip such a bug. > I just realized there is another rare issue that we may have to take > into account. Some sets of packages *must* be stablized in lockstep. For > regular sets of packages like eg xfce if you leave off a bunch of the > extras its no big deal. > Eg for SELinux, the policy packages must all be stabilized all at > once because they depend on each other (I think perl is like this too?). > > We would need a way for maintainers to ask for testing without actually > committing. The maintainer can wait till everything is done and commit > everything at once himself. Some flag to make the tatt script skip the > step would be enough I think. Do you have a bug number handy so I can double check how the process normally looks?
