Re: Do we need a "No broken deps" Objective?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Nov 25, 2019 at 2:08 PM Igor Gnatenko
<ignatenkobrain@xxxxxxxxxxxxxxxxx> wrote:
>
> Hey Fabio,

Hey Igor!

> 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.

Yes, I know, I'm using repoclosure. Sadly, fixing DNF's handling of
some rich deps is outside my area of expertise ;)
But I can whitelist rich deps that are actually satisfiable in fedora
(as I started to do for some things that I know are actually
satisfiable).

> Do you want to check for FTI/FTBFS or that all dependencies are
> present in Fedora?

FTI <=> (missing dependencies in binary package and/or conflicting deps)
FTBFS <=> (missing dependencies in source package and/or actually
fails to build for other reasons)

Checking FTI caused by conflicting dependencies is outside the scope
of my checks for now, and checking FTBFS issues is already covered
elsewhere.
So for now, I'm only checking for missing/broken dependencies.

Fabio

> On Mon, Nov 25, 2019 at 1:23 PM Fabio Valentini <decathorpe@xxxxxxxxx> 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@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
> _______________________________________________
> 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
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux