Bug 2263974 - bgpq4-1.12 is available
Summary: bgpq4-1.12 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bgpq4
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-13 02:57 UTC by Upstream Release Monitoring
Modified: 2024-02-27 02:11 UTC (History)
1 user (show)

Fixed In Version: bgpq4-1.12-1.el8 bgpq4-1.12-1.fc38 bgpq4-1.12-1.el9 bgpq4-1.12-1.fc39 bgpq4-1.12-1.el7
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-02-26 00:31:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2024-02-13 02:57:51 UTC
Releases retrieved: 1.12
Upstream release that is considered latest: 1.12
Current version/release in rawhide: 1.11-4.fc40
URL: https://github.com/bgp/bgpq4

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/116791/


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

Comment 1 Fedora Update System 2024-02-17 18:17:21 UTC
FEDORA-EPEL-2024-31ebb5473f (bgpq4-1.12-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-31ebb5473f

Comment 2 Fedora Update System 2024-02-17 18:17:21 UTC
FEDORA-EPEL-2024-afb818fe4b (bgpq4-1.12-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-afb818fe4b

Comment 3 Fedora Update System 2024-02-17 18:17:22 UTC
FEDORA-2024-3642d7e331 (bgpq4-1.12-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-3642d7e331

Comment 4 Fedora Update System 2024-02-17 18:17:23 UTC
FEDORA-2024-2cb2806100 (bgpq4-1.12-1.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-2cb2806100

Comment 5 Fedora Update System 2024-02-17 18:17:23 UTC
FEDORA-EPEL-2024-de802bd6d9 (bgpq4-1.12-1.el7) has been submitted as an update to Fedora EPEL 7.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-de802bd6d9

Comment 6 Fedora Update System 2024-02-18 01:49:14 UTC
FEDORA-2024-3642d7e331 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-3642d7e331`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3642d7e331

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

Comment 7 Fedora Update System 2024-02-18 01:55:42 UTC
FEDORA-EPEL-2024-afb818fe4b 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-afb818fe4b

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

Comment 8 Fedora Update System 2024-02-18 02:00:01 UTC
FEDORA-EPEL-2024-31ebb5473f has been pushed to the Fedora EPEL 9 testing repository.

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

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

Comment 9 Fedora Update System 2024-02-18 02:32:50 UTC
FEDORA-2024-2cb2806100 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-2cb2806100`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-2cb2806100

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

Comment 10 Fedora Update System 2024-02-19 01:35:06 UTC
FEDORA-EPEL-2024-de802bd6d9 has been pushed to the Fedora EPEL 7 testing repository.

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

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

Comment 11 Fedora Update System 2024-02-26 00:31:10 UTC
FEDORA-EPEL-2024-afb818fe4b (bgpq4-1.12-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 12 Fedora Update System 2024-02-26 00:47:11 UTC
FEDORA-2024-2cb2806100 (bgpq4-1.12-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 13 Fedora Update System 2024-02-26 00:54:11 UTC
FEDORA-EPEL-2024-31ebb5473f (bgpq4-1.12-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 14 Fedora Update System 2024-02-26 01:12:26 UTC
FEDORA-2024-3642d7e331 (bgpq4-1.12-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 15 Fedora Update System 2024-02-27 02:11:50 UTC
FEDORA-EPEL-2024-de802bd6d9 (bgpq4-1.12-1.el7) has been pushed to the Fedora EPEL 7 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.