Hello, On Sun, Sep 07, 2014 at 12:51:53PM +0200, Jakub Wilk wrote: > * Paul Wise <p...@debian.org>, 2014-09-07, 17:38: > >>We should probably also monitor package conflicts. We made a big fuss > >>about node vs nodejs (and rightly so); but I bet that we have lots of > >>other package pairs in the archive that can't be co-installed for no > >>good reason. > > > >We have this already: > > > >https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=edos-file-overwrite;users=trei...@debian.org > >https://qa.debian.org/dose/file-overwrites.html > > Nah, I meant packages that do declare that they can't be co-installed.
Jakub is right, the bugs that I am tracking on [1] concern only cases where there is no conflict declared in the metadata, yet the two packages fail to install together. Having said that, it might be possible to use dose-debcheck to do the check you have in mind. Maybe you can spare me reading the 139 messages in the bug report and tell me what precisely you need: Is it that every single package can be installed using only packages of the same or higher priority ? -Ralf. [1] https://qa.debian.org/dose/file-overwrites.html -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140907154514.gb1...@seneca.home.org
