On Tuesday 18 of August 2009, David Haller wrote:
It's more about being able to look up "who might get hit by an update".
Something like being able to notify dependent packagers... The deps are all there. Being able to send a message like
"Hey all you guys that use this package, I'm gonna update to version x.y.z. Be prepared. This update may be tricky. Digestive-end-products might hit the air-moving-device. Set your OBS-builds to disabled, run a testbuild with only one of them, or preferrably a local build, once the update's done. File a bug as usual to ... if the testbuild fails."
to all packagers of dependent packages (and only those), would be quite nice to have.
I agree that being able to find this out would be nice, but it wouldn't help in this case. If this would happen everytime, everybody would learn to ignore these mails by the 50th one at the latest, which for some packages could be within a month. Do people really care that much that libattr has been upgraded from 2.4.43 to 2.4.44 and as a result most probably nothing interesting happens at all? That a minor version upgrade of a library broke some application is unfortunate, but, assuming the developers of Boost are not a bunch of crazy retards who do it just for the fun of it, it's simply a bug and that can happen. -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak@suse.cz , l.lunak@kde.org Lihovarska 1060/12 tel: +420 284 084 672 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org