On Mon, Mar 9, 2020 at 5:57 PM Bruno Wolff III <bruno@xxxxxxxx> wrote: > > On Fri, Mar 06, 2020 at 21:35:52 +0100, > Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > >Hi all, > > > >With the fedora 32 release drawing near, it might be a good time to > >check if any of your packages still have broken dependencies in the > >fedora 32 (+testing) repositories. I've been working on just the thing > >you need: (snip) > Is there interest in also reporting packages that should be conflicting > but aren't? These are annoying because they fail after the transaction > is set and have to be manually dealt with. This is currently out of scope, because it's not reported by DNF repoclosure / repoquery. I'm also not sure how you would detect that from the package metadata ... query all packages for their file contents, and then show conflicts when two packages own the same file, but do not explicitly Conflict? I think that's probably too simplistic ... Fabio > For example: > > Running transaction test > The downloaded packages were saved in cache until the next successful transaction. > You can remove cached packages by executing 'dnf clean packages'. > Error: Transaction test error: > file /usr/bin/slideshow from install of racket-7.4-2.fc32.x86_64 conflicts with file from package batik-slideshow-1.11-3.fc32.noarch > file /usr/share/man/fr/man1/blackbox.1.gz from install of blackbox-0.76-1.fc33.x86_64 conflicts with file from package man-pages-fr-3.70-20.fc32.noarch > file /usr/share/man/fr/man1/bsetroot.1.gz from install of blackbox-0.76-1.fc33.x86_64 conflicts with file from package man-pages-fr-3.70-20.fc32.noarch > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
