Bug 2334057 - nickle-2.102 is available
Summary: nickle-2.102 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nickle
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-12-25 07:31 UTC by Upstream Release Monitoring
Modified: 2025-02-01 08:06 UTC (History)
1 user (show)

Fixed In Version: nickle-2.102-1.fc42 nickle-2.102-1.el8 nickle-2.102-1.el9 nickle-2.102-1.fc41 nickle-2.102-1.el10_0 nickle-2.102-1.fc40
Clone Of:
Environment:
Last Closed: 2025-01-23 03:28:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2024-12-25 07:31:31 UTC
Releases retrieved: 2.102
Upstream release that is considered latest: 2.102
Current version/release in rawhide: 2.101-1.fc42
URL: http://nickle.org/release/

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


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

Comment 1 Fedora Update System 2025-01-23 03:25:25 UTC
FEDORA-2025-5681a36ba8 (nickle-2.102-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5681a36ba8

Comment 2 Fedora Update System 2025-01-23 03:28:10 UTC
FEDORA-2025-5681a36ba8 (nickle-2.102-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2025-01-23 05:38:02 UTC
FEDORA-2025-dd24d7e33f (nickle-2.102-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-dd24d7e33f

Comment 4 Fedora Update System 2025-01-23 05:38:03 UTC
FEDORA-2025-e2cdc71100 (nickle-2.102-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-e2cdc71100

Comment 5 Fedora Update System 2025-01-23 05:38:04 UTC
FEDORA-EPEL-2025-e2b77e798d (nickle-2.102-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e2b77e798d

Comment 6 Fedora Update System 2025-01-24 00:21:01 UTC
FEDORA-EPEL-2025-ab2daddd17 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-2025-ab2daddd17

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

Comment 7 Fedora Update System 2025-01-24 02:37:31 UTC
FEDORA-2025-e2cdc71100 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-e2cdc71100`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-e2cdc71100

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

Comment 8 Fedora Update System 2025-01-24 02:38:33 UTC
FEDORA-2025-dd24d7e33f 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-2025-dd24d7e33f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-dd24d7e33f

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

Comment 9 Fedora Update System 2025-01-24 02:51:24 UTC
FEDORA-EPEL-2025-8c015a8fe7 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-8c015a8fe7

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

Comment 10 Fedora Update System 2025-01-24 02:51:32 UTC
FEDORA-EPEL-2025-e2b77e798d 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-2025-e2b77e798d

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

Comment 11 Fedora Update System 2025-02-01 04:52:56 UTC
FEDORA-EPEL-2025-ab2daddd17 (nickle-2.102-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 2025-02-01 04:57:21 UTC
FEDORA-EPEL-2025-e2b77e798d (nickle-2.102-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 13 Fedora Update System 2025-02-01 05:40:09 UTC
FEDORA-2025-e2cdc71100 (nickle-2.102-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 14 Fedora Update System 2025-02-01 05:59:31 UTC
FEDORA-EPEL-2025-8c015a8fe7 (nickle-2.102-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2025-02-01 08:06:47 UTC
FEDORA-2025-dd24d7e33f (nickle-2.102-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.