On Wed, 2015-04-08 at 14:56 +0200, drago01 wrote: > > > It is not so simple, you have to test all combinations for packages > > requiring an updated package and all the packages there requires > > someting > > provided by previous version of the package, with thousend of > > packages and > > multiple packages providing the same stuff, it is an almost > > impossible task. > > Did you even read what I wrote? Did you read what Tim wrote? He pointed out that you are only answering one half of the question that needs answering, and it's by far the easier half. Yes, it's relatively easy to check if each package in a proposed update push is installable. What's much harder is to check whether pushing that packages makes *any other package in the distribution* non-installable. If you send an update that bumps the soname of a library, for instance, *that update itself* won't fail a depcheck which just checks if that package can be installed. You somehow need your depcheck to know to try and install various packages that depend on your update and see if *they* work OK. (The question of what package is 'to blame' for a dependency issue is not always entirely straightforward, either; it's not always quite as simple as 'take the apparently-offending update out'). It's hard to see how you build a perfect dep check other than trying to solve the deps of *every single package in the distro* against every proposed update. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
