On Sun, Sep 29, 2013 at 8:14 PM, hasufell <[email protected]> wrote: > On 09/30/2013 12:54 AM, Andreas K. Huettel wrote: >> Am Sonntag, 29. September 2013, 23:41:03 schrieb hasufell: >>> It seems this happens more frequently these days, so I'd like to >>> remind people to check stable reverse deps before stabilizing a >>> library, especially when this is a non-maintainer stablereq. >>> >>> Arch teams do not test them, so this is the business of the >>> maintainer or the dev who requested stabilization. >> >> Arch testing includes testing of reverse deps. If that's not the >> case, arch teams are not doing their job. >> > > I'd have to search the irc logs, but afair I was told so by ago. > > CCing him if I am wrong.
If you aren't wrong, that might be why Ago is about the only one stabilizing libraries... :) It probably makes sense for arch teams to test a few reverse dependencies as the FAQ suggests. If we want them all tested, then it would make a lot more sense to have a tinderbox or other automated testing tools of some sort. Even then, we won't get much more than compile testing, or whatever test suites the packages happen to come with. I haven't really seen any sign of widespread breakage though. I'm sure some issues slip through, but short of having automated testing I doubt we'll ever do better than that. Rich
