Bug 2486102 - ack-3.10.0 is available
Summary: ack-3.10.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ack
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bill Pemberton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-07 17:30 UTC by Upstream Release Monitoring
Modified: 2026-06-17 08:24 UTC (History)
3 users (show)

Fixed In Version: ack-3.10.0-1.fc44 ack-3.10.0-1.fc43
Clone Of:
Environment:
Last Closed: 2026-06-16 01:02:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 3.10.0 (#2486102) (584 bytes, patch)
2026-06-07 17:30 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2026-06-07 17:30:00 UTC
Releases retrieved: 3.10.0
Upstream release that is considered latest: 3.10.0
Current version/release in rawhide: 3.9.0-5.fc44
URL: http://search.cpan.org/dist/ack/

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


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

Comment 1 Upstream Release Monitoring 2026-06-07 17:30:05 UTC
Created attachment 2144607 [details]
Update to 3.10.0 (#2486102)

Comment 2 Upstream Release Monitoring 2026-06-07 17:36:24 UTC
the-new-hotness/release-monitoring.org's scratch build of ack-3.10.0-1.fc43.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=146350149

Comment 3 Fedora Update System 2026-06-08 00:07:47 UTC
FEDORA-2026-bb708e11d7 (ack-3.10.0-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-bb708e11d7

Comment 4 Fedora Update System 2026-06-08 00:18:16 UTC
FEDORA-2026-45190a3b6b (ack-3.10.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-45190a3b6b

Comment 5 Fedora Update System 2026-06-08 01:08:48 UTC
FEDORA-2026-bb708e11d7 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-bb708e11d7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-bb708e11d7

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

Comment 6 Fedora Update System 2026-06-09 01:29:01 UTC
FEDORA-2026-45190a3b6b has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-45190a3b6b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-45190a3b6b

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

Comment 7 Fedora Update System 2026-06-16 01:02:44 UTC
FEDORA-2026-bb708e11d7 (ack-3.10.0-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-06-17 08:24:46 UTC
FEDORA-2026-45190a3b6b (ack-3.10.0-1.fc43) has been pushed to the Fedora 43 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.