Bug 1991184 - nmap-7.92 is available
Summary: nmap-7.92 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nmap
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Martin Osvald 🛹
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2020663 (view as bug list)
Depends On:
Blocks: 2020453
TreeView+ depends on / blocked
 
Reported: 2021-08-08 00:42 UTC by Upstream Release Monitoring
Modified: 2022-03-26 15:00 UTC (History)
7 users (show)

Fixed In Version: nmap-7.92-1.fc35 nmap-7.92-1.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-25 16:51:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 7.92 (#1991184) (1.03 KB, patch)
2021-08-08 00:42 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2021-08-08 00:42:36 UTC
Latest upstream release: 7.92
Current version/release in rawhide: 7.91-8.fc35
URL: https://nmap.org/

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://fedoraproject.org/wiki/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/2096/

Comment 1 Upstream Release Monitoring 2021-08-08 00:42:42 UTC
Created attachment 1811946 [details]
[patch] Update to 7.92 (#1991184)

Comment 2 Upstream Release Monitoring 2021-08-08 00:47:57 UTC
the-new-hotness/release-monitoring.org's scratch build of nmap-7.92-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=73477550

Comment 3 Mark McLoughlin 2022-02-22 15:25:30 UTC
*** Bug 2020663 has been marked as a duplicate of this bug. ***

Comment 4 Mark McLoughlin 2022-02-22 15:26:55 UTC
7.92 will resolve #2020453

Comment 5 Fedora Update System 2022-02-23 13:34:59 UTC
FEDORA-2022-d48d5031c8 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d48d5031c8

Comment 6 Fedora Update System 2022-02-23 13:46:28 UTC
FEDORA-2022-db05340ff9 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-db05340ff9

Comment 7 Fedora Update System 2022-02-23 16:08:30 UTC
FEDORA-2022-db05340ff9 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-db05340ff9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-db05340ff9

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

Comment 8 Fedora Update System 2022-02-24 01:45:20 UTC
FEDORA-2022-d48d5031c8 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d48d5031c8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d48d5031c8

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

Comment 9 Fedora Update System 2022-02-25 16:51:52 UTC
FEDORA-2022-db05340ff9 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2022-03-26 15:00:13 UTC
FEDORA-2022-d48d5031c8 has been pushed to the Fedora 36 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.