releng

#11634 release-monitoring seems to miss some upstream releases
Closed: upstream by zlopez. Opened by marcindulak.

Closed: upstream
Reopen Issue
  • Describe the issue

Discussed at https://bugzilla.redhat.com/show_bug.cgi?id=2232417

It looks like some numpy (maybe also other components) releases are not reflected on bugzilla.

For example, there is 1.25.2 release 2023-07-31 listed on https://release-monitoring.org/project/2509/, but I don't find it in bugzilla comment search https://bugzilla.redhat.com/buglist.cgi?columnlist=product%2Ccomponent%2Cassigned_to%2Cstatus%2Csummary%2Clast_change_time%2Cseverity%2Cpriority&component=numpy&list_id=13298697&longdesc=1.25.2&longdesc_type=allwordssubstr&order=status%2C%20priority%2C%20assigned_to%2C%20id%2C%20&product=Fedora&query_format=advanced

Is my search correct? I find some other components this way (for example elk 8.4.21).

  • If we cannot complete your request, what is the impact?

I've seen similar issues where I've noticed an upstream tag in git for a release but not an associated bug report.

The issue here is that there was mapping for Fedora missing in release-monitoring.org, at least that is what I see in https://packages.fedoraproject.org/pkgs/numpy/python3-numpy/ (the-new-hotness is the component filing in the bugs on bugzilla) and it uses the mapping to match the project in release-monitoring.org with actual package. However it doesn't fill in the versions retrospectively, so if the update is thrown out because something is missing it never be reported again.

the-new-hotness is also comparing only the latest version (version that is considered latest by the release-monitoring.org, so if the version retrieved is not the latest in release-monitoring.org it wouldn't be even compared with the version in MDApi).

So... should this be refiled upstream? or is this just not a bug due to the way things work? or ?

It will be best to move this upstream, I probably have a way to fix this in the-new-hotness. @marcindulak Please fill an issue in the-new-hotness

Metadata Update from @zlopez:
- Issue close_status updated to: upstream
- Issue status updated to: Closed (was: Open)

https://github.com/fedora-infra/the-new-hotness/issues/580
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.