Bug 2267423 - veristat-0.3.1 is available
Summary: veristat-0.3.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: veristat
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-02 09:08 UTC by Upstream Release Monitoring
Modified: 2024-03-23 00:27 UTC (History)
2 users (show)

Fixed In Version: veristat-0.3.1-1.fc41 veristat-0.3.1-1.el9 veristat-0.3.1-1.fc39 veristat-0.3.1-1.fc38 veristat-0.3.1-1.el8 veristat-0.3.1-1.fc40
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-04 19:47:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2024-03-02 09:08:12 UTC
Releases retrieved: 0.3.1
Upstream release that is considered latest: 0.3.1
Current version/release in rawhide: 0.3-2.fc40
URL: https://github.com/libbpf/veristat

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/369821/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/veristat

Comment 1 Fedora Update System 2024-03-04 17:37:37 UTC
FEDORA-2024-6196bae4d0 (veristat-0.3.1-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-6196bae4d0

Comment 2 Fedora Update System 2024-03-04 19:27:56 UTC
FEDORA-2024-1d136cf579 (veristat-0.3.1-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-1d136cf579

Comment 3 Fedora Update System 2024-03-04 19:27:57 UTC
FEDORA-EPEL-2024-ae735c708a (veristat-0.3.1-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-ae735c708a

Comment 4 Fedora Update System 2024-03-04 19:27:58 UTC
FEDORA-EPEL-2024-55d326bfca (veristat-0.3.1-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-55d326bfca

Comment 5 Fedora Update System 2024-03-04 19:27:58 UTC
FEDORA-2024-5441943cc3 (veristat-0.3.1-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-5441943cc3

Comment 6 Fedora Update System 2024-03-04 19:47:17 UTC
FEDORA-2024-6196bae4d0 (veristat-0.3.1-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2024-03-05 01:08:41 UTC
FEDORA-2024-1d136cf579 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-1d136cf579`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1d136cf579

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2024-03-05 01:10:34 UTC
FEDORA-2024-6260ac16cc has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6260ac16cc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6260ac16cc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2024-03-05 01:58:46 UTC
FEDORA-2024-5441943cc3 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-5441943cc3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-5441943cc3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2024-03-05 02:22:08 UTC
FEDORA-EPEL-2024-55d326bfca (veristat-0.3.1-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2024-03-05 02:41:18 UTC
FEDORA-EPEL-2024-ae735c708a has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-ae735c708a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2024-03-13 01:24:19 UTC
FEDORA-2024-1d136cf579 (veristat-0.3.1-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2024-03-13 01:48:26 UTC
FEDORA-2024-6260ac16cc (veristat-0.3.1-1.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2024-03-13 02:35:49 UTC
FEDORA-EPEL-2024-ae735c708a (veristat-0.3.1-1.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2024-03-23 00:27:57 UTC
FEDORA-2024-5441943cc3 (veristat-0.3.1-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.