From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: nmap: update to 7.93
Date: Tue, 10 Jan 2023 18:26:11 +0100 [thread overview]
Message-ID: <20230110172611._DJzVwLkO6NndL0XRqHWagwoTDoYKbQXWeHdjvUhApU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41520@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
There's a merged pull request on the void-packages repository
nmap: update to 7.93
https://github.com/void-linux/void-packages/pull/41520
Description:
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures:
- x86_64-musl
- aarch64 (crossbuild)
- armv7l (crossbuild)
#### Notes
- There were some licensing issues (see #27866). While nmap version 7.90, 7.91 and 7.92 could have been distributed using the old (good) license, 7.93 is the first nmap release which comes exclusively under the custom "Nmap Public Source License" (NPSL) [[1]]. ~~However, the issues with previous versions of this license seem to have been solved in version 0.94 (of the license). Fedora added it to their list of "Good Licenses" [[2]].~~ Fedora as well as Gentoo both have nmap version 7.93 in their repos [[3],[4]].
- `openssl.patch` fixes nmap issue 2516.
- `gcc12.patch` seems not to be needed anymore.
[1]: https://nmap.org/npsl/
[2]: https://fedoraproject.org/wiki/Licensing:Main
[3]: https://src.fedoraproject.org/rpms/nmap
[4]: https://packages.gentoo.org/packages/net-analyzer/nmap
Edit: strike claims about the new license \*sigh\*, typo
prev parent reply other threads:[~2023-01-10 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 17:06 [PR PATCH] " pascal-huber
2023-01-09 15:44 ` leahneukirchen
2023-01-09 17:22 ` [PR PATCH] [Updated] " pascal-huber
2023-01-09 17:23 ` pascal-huber
2023-01-10 15:32 ` [PR REVIEW] " leahneukirchen
2023-01-10 15:38 ` [PR PATCH] [Updated] " pascal-huber
2023-01-10 15:39 ` [PR REVIEW] " pascal-huber
2023-01-10 17:26 ` leahneukirchen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230110172611._DJzVwLkO6NndL0XRqHWagwoTDoYKbQXWeHdjvUhApU@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).