Bug 2517126

Summary: nnn-5.3 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: nnnAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: eclipseo, vtrefny
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nnn-5.3-1.fc46 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-08-17 09:14:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Update to 5.3 (#2517126) none

Description Upstream Release Monitoring 2026-08-15 17:28:44 UTC 
Releases retrieved: 5.3
Upstream release that is considered latest: 5.3
Current version/release in rawhide: 5.2-2.fc45
URL: https://github.com/jarun/nnn

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/nnn
Comment 1 Upstream Release Monitoring 2026-08-15 17:28:49 UTC 
Created attachment 2154638 [details]
Update to 5.3 (#2517126)
Comment 2 Upstream Release Monitoring 2026-08-15 17:34:19 UTC 
the-new-hotness/release-monitoring.org's scratch build of nnn-5.3-1.fc44.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=149137484
Comment 3 Fedora Update System 2026-08-17 09:23:56 UTC 
FEDORA-2026-d5ab08d6bf (nnn-5.3-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-d5ab08d6bf
Comment 4 Fedora Update System 2026-08-17 09:24:09 UTC 
FEDORA-2026-7ab20715e6 (nnn-5.3-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-7ab20715e6
Comment 5 Fedora Update System 2026-08-18 01:30:05 UTC 
FEDORA-2026-d5ab08d6bf 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-d5ab08d6bf`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d5ab08d6bf

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2026-08-18 01:55:58 UTC 
FEDORA-2026-7ab20715e6 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-7ab20715e6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-7ab20715e6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2026-08-26 01:02:34 UTC 
FEDORA-2026-7ab20715e6 (nnn-5.3-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 8 Fedora Update System 2026-08-26 01:12:34 UTC 
FEDORA-2026-d5ab08d6bf (nnn-5.3-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.