Re: Getting notified on broken deps from updates-testing

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

 



On Mon, Nov 11, 2019 at 5:02 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote:
>
> On Sun, Nov 10, 2019 at 4:24 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
> >
> > On Sun, Nov 10, 2019 at 06:06:22PM +0100, Fabio Valentini wrote:
> > > On Fri, Nov 8, 2019 at 10:24 AM Vít Ondruch <vondruch@xxxxxxxxxx> wrote:
> > > >
> > > > I think that the basic problem is that the "broken dependencies" emails
> > > > are not sent anymore even for Rawhide. This is big loss.
> > >
> > > If you think that the weekly "broken dependencies" reports were
> > > useful, I could set that up again.
> > > After all, I already have the data, and write out reports in markdown format.
> > >
> > > It would be pretty easy to also generate a plain text version and then
> > > just send that to the devel list on a weekly basis.
> > > However, for updates-testing reports to be useful, weekly would
> > > probably be not frequently enough (most updates only sit in -testing
> > > for 7 days, after all).
> > >
> > > The code, data, and reports in easily viewable markdown format are here:
> > > https://pagure.io/fedora-health-check
> >
> > Perhaps you might be willing to look at integrating this with the
> > updates push composes and/or rawhide? We never got the old spam-o-matic
> > working with more than just x86_64...
> >
> > https://pagure.io/releng/issue/6365
> > https://pagure.io/releng/issue/7931
> > (and possibly others/prs)
> >
>
> Fabio's script also only validates on x86_64. I still don't get why
> dnf repoclosure is so broken when querying alternative
> architectures...
>
> When I wrote the DNF port to spam-o-matic, I made sure it worked, and
> it did when I wrote it. Unfortunately something in DNF broke, and I'm
> not sure exactly what or how. But there's been significant changes in
> architecture handling in the past 8 months, so maybe it'll work
> properly now?

I've adapted my script to check all architectures now (and I think it
works correctly).
I'm using --forcearch and "--arch foo" to make sure it uses the
correct repository and queries the correct arches.
So the data I'll be generating later today will include broken deps
for all arches.

Fabio

> --
> 真実はいつも一つ!/ Always, there's only one truth!
> _______________________________________________
> 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