From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nmap: revert to 7.80 due to licensing issues
Date: Tue, 12 Jan 2021 20:54:38 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27866@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
There is a new pull request by Piraty against master on the void-packages repository
https://github.com/Piraty/void-packages nmap-revert-to-7.80-due-to-license-issues
https://github.com/void-linux/void-packages/pull/27866
nmap: revert to 7.80 due to licensing issues
nmap >= 7.90 is distributed under a modified license that many consider
problematic.
https://github.com/nmap/nmap/issues/2199
Gentoo bug: https://bugs.gentoo.org/749390
Debian bug: https://bugs.debian.org/972216
Guix discussion: https://lists.gnu.org/archive/html/guix-devel/2020-10/msg00227.html
Along, link against libssh2 instead of using the bundled version.
A patch file from https://github.com/void-linux/void-packages/pull/27866.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nmap-revert-to-7.80-due-to-license-issues-27866.patch --]
[-- Type: text/x-diff, Size: 1919 bytes --]
From ef5788a0b0af802b0db5e4e2bb990aa7b0d92556 Mon Sep 17 00:00:00 2001
From: Piraty <piraty1@inbox.ru>
Date: Tue, 12 Jan 2021 20:44:03 +0100
Subject: [PATCH] nmap: revert to 7.80 due to licensing issues
nmap >= 7.90 is distributed under a modified license that many consider
problematic.
https://github.com/nmap/nmap/issues/2199
Gentoo bug: https://bugs.gentoo.org/749390
Debian bug: https://bugs.debian.org/972216
Guix discussion: https://lists.gnu.org/archive/html/guix-devel/2020-10/msg00227.html
Along, link against libssh2 instead of using the bundled version.
---
srcpkgs/nmap/template | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/nmap/template b/srcpkgs/nmap/template
index 7d46635229b..db5d413cfb1 100644
--- a/srcpkgs/nmap/template
+++ b/srcpkgs/nmap/template
@@ -1,17 +1,19 @@
# Template file for 'nmap'
pkgname=nmap
-version=7.91
-revision=1
+reverts="7.90_1 7.91_1"
+version=7.80
+revision=2
build_style=gnu-configure
configure_args="--without-ndiff --with-openssl --with-zenmap $(vopt_with lua liblua)"
hostmakedepends="python"
-makedepends="libpcap-devel libressl-devel pcre-devel $(vopt_if lua lua53-devel)"
+makedepends="libpcap-devel libressl-devel libssh2-devel pcre-devel
+ $(vopt_if lua lua53-devel)"
short_desc="Utility for network discovery and security auditing"
maintainer="Piraty <piraty1@inbox.ru>"
license="custom:nmap"
homepage="https://nmap.org"
distfiles="https://nmap.org/dist/nmap-${version}.tar.bz2"
-checksum=18cc4b5070511c51eb243cdd2b0b30ff9b2c4dc4544c6312f75ce3a67a593300
+checksum=fcfa5a0e42099e12e4bf7a68ebe6fde05553383a682e816a7ec9256ab4773faa
python_version=2
build_options="lua"
@@ -22,7 +24,7 @@ alternatives="
nc:nc.1:/usr/share/man/man1/ncat.1"
post_install() {
- vlicense LICENSE
+ vlicense COPYING
# do not use bundled certificates, use only system ones
rm -f ${DESTDIR}/usr/share/ncat/ca-bundle.crt
next reply other threads:[~2021-01-12 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 19:54 Piraty [this message]
2021-01-12 20:07 ` [PR PATCH] [Merged]: " the-maldridge
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27866@inbox.vuxu.org \
--to=piraty@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).