fedora-infrastructure

#7330 Missing BZs from release-monitoring for rust crates
Closed: Duplicate Opened by jistone.

Closed: Duplicate
Reopen Issue
  • Describe what you need us to do:

Investigate why we're not getting bugs for new versions of rust-* packages, even though release-monitoring.org does have them.

For example, it noted libz-sys 1.0.25 yesterday, but we have no bug filed.
https://release-monitoring.org/project/15436/

Another case, we have a bug for pest 2.0.0 on Oct 1, updated to 2.0.1 on Oct 2, but hasn't updated for 2.0.2 which release-monitoring found on Oct 22.
https://bugzilla.redhat.com/show_bug.cgi?id=1634824
https://release-monitoring.org/project/16417/

  • When do you need this? (YYYY/MM/DD)

  • When is this no longer needed or useful? (YYYY/MM/DD)

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

Rust crates will have to be manually checked for available updates.

cc @zlopez

This is probably linked to this issue: https://pagure.io/fedora-infrastructure/issue/7294

We are currently working to move Anitya (release-monitoring.org) from fedmsg to fedora-messaging. This should prevent the loss of messages.

7294 is about GDPR -- I suppose you meant to link #7313?

@jistone
Yes, you are right. I didn't noticed I linked the wrong issue.

Yes, this is the same issue as 7313.

Metadata Update from @kevin:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Lowest
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.