* Niels Thykier <ni...@thykier.net>, 2012-07-17, 20:03:
It would also be quite interesting, although much harder to determine, whether there are any scenarios where such a dependency would result in a non-free package being installed by default. If, for example, there's a dependency on foo | foo-nonfree and some packages conflict with foo but not with foo-nonfree such that a dependency resolver may pull in foo-nonfree in preference.
[...]
I suspect installability checking of all packages should find them if they are there. One run with non-free+contrib and one without - the "newly" uninstallable between the two runs should be set you are looking for.
I played with dose-debcheck a bit. It turns out that (at least for i386) every currently uninstallable package in main is also uninstallable within main+contrib+non-free.
It does not catch issues like "foo-nonfree | foo", but they would be caught by your other query.
That's right. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120717181448.ga6...@jwilk.net
