Re: Getting notified on broken deps from updates-testing

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

 



On Sun, Nov 10, 2019 at 11:57 PM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
>
> On 10. 11. 19 18:06, 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
> >
> > Fabio
>
> I believe, it might be useful to get and "instant" e-mail once a package I
> maintain has broken dependency but it was OK before.
>
> Aka you snapshot the data, regenerate it again, do a diff and send only new
> packages.
>
> Otherwise it would just be spam to most of the maintainers, it's just too many.

Yes, that's exactly what I had in mind. Currently there's way too many
broken dependencies to notify everybody about everything.
You can already see the snapshot diffs in the git repo on pagure
(although I'm relying on the git history to store old diffs, and keep
only the latest one).

For example, here you can see yesterday's diff for fedora-31-updates-testing:
https://pagure.io/fedora-health-check/blob/6791a6d/f/changes/diff-31-testing.json

(I'd have linked the diff for rawhide, but it's too big to be useful
for human consumption.)

Fabio

> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> _______________________________________________
> 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