Last time I checked, it was basically checking only the first part of "with" richop. I believe it is still broken the same way.
On Thu, Nov 28, 2019, 17:33 Fabio Valentini <decatho...@gmail.com> wrote: > On Mon, Nov 25, 2019 at 2:08 PM Igor Gnatenko > <ignatenkobr...@fedoraproject.org> wrote: > > > > Hey Fabio, > > (snip) > > > There is a problem with the code. You seem to run either repoquery or > > repoclosure inside. However, that does not really check rich > > dependencies correctly. > > To follow up on this: It turns out DNF's repoclosure *does* correctly > report broken dependencies, even for rich dependencies (or it's not as > broken as we thought). > Checking a random sample of the reported "broken rich dependencies" > manually, it turned out every single one I checked was *actually > unsatisfiable*, and not caused by a DNF / repoclosure bug. > > Fabio > > > Do you want to check for FTI/FTBFS or that all dependencies are > > present in Fedora? > > > > On Mon, Nov 25, 2019 at 1:23 PM Fabio Valentini <decatho...@gmail.com> > wrote: > > > > > > Hi everybody, > > > > > > I'm a bit concerned about the growing number of broken dependencies in > > > fedora, which leads to non-installable (FTI) and un-buildable (FTBFS) > > > packages. For rawhide [0], I see almost 400 source packages and almost > > > 200 x86_64 packages with broken deps. Especially the number of source > > > packages with broken dependencies has steadily been growing since 29. > > > > > > With a bit of effort, a lot of these broken packages could be fixed > > > quite easily, but it would still need a coordinated effort by a group > > > of people. I think an Objective would fit for that purpose. > > > > > > Fabio > > > > > > PS: Feel free to browse the data in the linked pagure repo. I'm > > > regenerating it daily with the latest state of all fedora branches. If > > > somebody is interested in getting notified about any of their packages > > > getting broken deps (for example, in -testing, before things get > > > broken in stable), I can work out some kind of automatic (opt-in) > > > notification system :) > > > > > > [0]: > https://pagure.io/fedora-health-check/blob/master/f/reports/report-rawhide.md > > > _______________________________________________ > > > devel mailing list -- devel@lists.fedoraproject.org > > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > > 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@lists.fedoraproject.org > > _______________________________________________ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > 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@lists.fedoraproject.org > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
