Missing Notifications

[Scott Talbert]

Hi,

What happened to the broken dependency notification emails?

Also, it seems that Anitya has not been creating bugs for new upstream 
releases for several months.  The problem doesn't seem to be with Anitya 
as it knows about the new releases, but somewhere else in the chain.  I 
thought I had found a bug for this somewhere but now I can't find it.

Scott

[Neal Gompa]

On Sun, Oct 28, 2018 at 11:52 AM Scott Talbert <swt(a)techie.net&gt; wrote:
>  Hi,
>
>  What happened to the broken dependency notification emails?
>  
I rewrote spam-o-matic to use DNF, and it was finally merged ~2 months ago[1].

The releng team has since activated it without sending any mail[2],
but hopefully they'll start sending mail soon...

[1]: https://pagure.io/releng/c/240fc9a8b7425edcb1919426dd4f0ec2ae00f64a
[2]: https://pagure.io/pungi-fedora/c/b6f658b99d7c8fc79826e342bf27ede33d1ad74d

>  Also, it seems that Anitya has not been creating bugs for new
> upstream
>  releases for several months.  The problem doesn't seem to be with Anitya
>  as it knows about the new releases, but somewhere else in the chain.  I
>  thought I had found a bug for this somewhere but now I can't find it.
>  
I don't know about this, but I have encountered the problem as well...



-- 
真実はいつも一つ！/ Always, there's only one truth!

[Scott Talbert]

On Sun, 28 Oct 2018, Neal Gompa wrote:

> > Hi,
> >
> > What happened to the broken dependency notification emails?
> >
>
>  I rewrote spam-o-matic to use DNF, and it was finally merged ~2 months ago[1].
>
>  The releng team has since activated it without sending any mail[2],
>  but hopefully they'll start sending mail soon...
>
>  [1]: https://pagure.io/releng/c/240fc9a8b7425edcb1919426dd4f0ec2ae00f64a
>  [2]: https://pagure.io/pungi-fedora/c/b6f658b99d7c8fc79826e342bf27ede33d1ad74d 
Thanks for your work.  I miss my spam.  :)

Scott

[Kevin Fenzi]

On 10/28/18 8:01 AM, Scott Talbert wrote:
>  Hi,
>  
>  What happened to the broken dependency notification emails? 
They got broken a while back by rich deps, then the script was
re-written entirely and re-enabled, but we haven't re-enabled the emails
yet due to release taking up everyones time.

Here's an example:

https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-2018102...

Hopefully we can enable emails soon.

>  Also, it seems that Anitya has not been creating bugs for new
> upstream
>  releases for several months.  The problem doesn't seem to be with Anitya
>  as it knows about the new releases, but somewhere else in the chain.  I
>  thought I had found a bug for this somewhere but now I can't find it. 
This was/is due to a combination of issues. First there was a problem
with it's checking script where it would error out early on and just
never check a lot of things, then once that was fixed, there's been
github api limits, then now there's some issue with the fedmsgs it's
emitting not getting to the app that files the bugs. ;( It's now being
moved to our new messaging bus in hopes of fixing that issue.

I think: https://github.com/release-monitoring/anitya/issues/638 is the
issue tracking this.

kevin

[Vít Ondruch]

Dne 29. 10. 18 v 23:31 Kevin Fenzi napsal(a):
>  On 10/28/18 8:01 AM, Scott Talbert wrote:
> > Hi,
> >
> > What happened to the broken dependency notification emails?
>  They got broken a while back by rich deps, then the script was
>  re-written entirely and re-enabled, but we haven't re-enabled the emails
>  yet due to release taking up everyones time.
>
>  Here's an example:
>
>
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-2018102...

This does not look like "broken dependencies" but just dependencies.


V.


>  Hopefully we can enable emails soon.
>
> > Also, it seems that Anitya has not been creating bugs for new upstream
> > releases for several months.  The problem doesn't seem to be with Anitya
> > as it knows about the new releases, but somewhere else in the chain.  I
> > thought I had found a bug for this somewhere but now I can't find it.
>  This was/is due to a combination of issues. First there was a problem
>  with it's checking script where it would error out early on and just
>  never check a lot of things, then once that was fixed, there's been
>  github api limits, then now there's some issue with the fedmsgs it's
>  emitting not getting to the app that files the bugs. ;( It's now being
>  moved to our new messaging bus in hopes of fixing that issue.
>
>  I think: https://github.com/release-monitoring/anitya/issues/638 is the
>  issue tracking this.
>
>  kevin
>
>
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]