So they should be coming thru aready.

I haven't been able to locate a package thats mapped in rpmfusion that has an update however.

There's no archives, datagrepper has everything since fedmsg existed in it.

https://apps.fedoraproject.org/datagrepper/raw?topic=org.release-monitoring.prod.anitya.project.version.update

shows all the recent updates.

That said. I looked at there should be a message for gst-plugins-bad that maps to rpmfusion, and I can't seem to see it. Not sure what is going on. ;(

Perhaps @pingou or @abompard or @jcline could see what is going on...

heya @pingou , @abompard , @jcline : any hints on what may be happening here that I could investigate maybe? Thanks :)

I can't explain the missing messages in datagrepper (fedmsg being flaky?), but I just added https://release-monitoring.org/project/17560/ and forced a version check, and release-monitoring.org published a message. I saw it running:

import zmq
sock = zmq.Context().socket(zmq.SUB)
sock.setsockopt(zmq.SUBSCRIBE, b'')
sock.connect('tcp://release-monitoring.org:9940')
while True:
    print(sock.recv_multipart())

And datagrepper has it: https://apps.fedoraproject.org/datagrepper/id?id=2018-f89d8a96-5c20-4d91-b4ea-ca9cb2699d28&is_raw=true&size=extra-large.

Yeh, it runs. I've seen messages for other packages, but I cannot find any related to RPMFusion somehow---packages do have it set as their distribution etc.

Hmm. If you can find a package for which the above test doesn't work, that would be helpful. If you don't see a message from that script, it's an issue with release-monitoring. If you do, but can't find it in datagrepper, it's a datagrepper issue.

Maybe it is just that nobody added gst-plugins-bad to release-monitoring https://release-monitoring.org/projects/search/?pattern=gst-plugins-bad+ - addition happens manually.

Hmm. If you can find a package for which the above test doesn't work, that would be helpful. If you don't see a message from that script, it's an issue with release-monitoring. If you do, but can't find it in datagrepper, it's a datagrepper issue.

Ah, thanks. I'll investigate this when I find a cycle to spare.

Maybe it is just that nobody added gst-plugins-bad to release-monitoring https://release-monitoring.org/projects/search/?pattern=gst-plugins-bad+ - addition happens manually.

Yeh, but there are lots of projects that are added and mapped to rpmfusion. MPD, for example has also seen updates: https://release-monitoring.org/project/14864/

This is the complete list of projects: https://release-monitoring.org/distro/RPM%20Fusion/?page=1

I think there's something going on with that distro...

https://release-monitoring.org/distro/RPM%20Fusion/ gives me a 500 error. ;(

Perhaps you can file this upstream at github release-monitoring?

@kevin this is already known issue and reported here https://github.com/release-monitoring/anitya/issues/709

About the rpm-fusion updates. Anitya is sending notification about every update, but as said above the mapping to RPM Fusion must be done manually.

Ah ha. ok.

I will close this then in favor of the upstream report and hopefully we can get it fixed up.

@kevin this is already known issue and reported here https://github.com/release-monitoring/anitya/issues/709
About the rpm-fusion updates. Anitya is sending notification about every update, but as said above the mapping to RPM Fusion must be done manually.

Can you please clarify what you mean by "mapping must be done manually"? They are mapped in anitya, as I pointed out for MPD. What additional mapping is needed?

@ankursinha
So the anitya updates fedmsg messages should be sent than. I thought you are missing only the mapping to RPM Fusion.
I'm not sure what you are missing?

Here is the one with RPM Fusion mapping - https://apps.fedoraproject.org/datagrepper/id?id=2019-ed4a23b1-9662-498d-b396-884085c7d2b6&is_raw=true&size=extra-large