From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add netcat-openbsd. [v2]
Date: Wed, 22 Jun 2016 22:43:15 +0000 [thread overview]
Message-ID: <20160622224315.GA17885@shadowwalker> (raw)
In-Reply-To: <87r3bolxyn.fsf@gnu.org>
On 2016-06-22(11:23:28PM+0200), Ludovic Courtès wrote:
> Hi!
>
> ng0 <ng0@we.make.ritual.n0.is> skribis:
>
> > * gnu/packages/admin.scm (netcat-openbsd): New variable.
> > * patches/netcat-openbsd-0001-port-to-linux-with-libbsd.patch,
> > patches/netcat-openbsd-0002-connect-timeout.patch,
> > patches/netcat-openbsd-0003-get-sev-by-name.patch,
> > patches/netcat-openbsd-0004-poll-hup.patch,
> > patches/netcat-openbsd-0005-send-crlf.patch,
> > patches/netcat-openbsd-0006-quit-timer.patch,
> > patches/netcat-openbsd-0007-udp-scan-timeout.patch,
> > patches/netcat-openbsd-0008-verbose-numeric-port.patch,
> > patches/netcat-openbsd-0009-dccp-support.patch,
> > patches/netcat-openbsd-0010-serialized-handling-multiple-clients.patch,
> > patches/netcat-openbsd-0011-misc-failures-and-features.patch: New files.
>
> Sorry for joining late, but I think 11 non-trivial patches is not OK (we
> have the policy of not keeping non-trivial patches, unless they fix an
> immediate bug or a Guix-specific issue.)
>
> Is there an upstream for this package?
The upstream is the debian port to linux of the nc binary of OpenBSD
(see in code comment on upstream), mentioned in the package.
As I understand the binary in OpenBSD compared to Debian, and to what
Gentoo, Archlinux, Debian (and possibly every other distro) use, this
is the defacto upstream. Maybe many of those patches are not necessary
in OpenBSD, but all the Linux ports use them.
So those are bug fixes and a minority of feature fixes.
I could try to get in contact with the person who wrote the patches
in 2012 and/or the current Debian maintainer and see if they ever
tried to push the generic changes back to OpenBSD.
Second choice, I ask Debian to merge those patches into their upstream,
the tarball I downloaded did not have those patches applied.
If I can get a reason/feedback on any of these and it turns out that we
need those patches, would an exception from the policy be okay?
I can look at what they add and further comment or provide comment by
Debian upstream on why they are needed.
> Thanks,
> Ludo’.
>
--
♥Ⓐ ng0
For non-prism friendly talk find me on
psyced.org / loupsycedyglgamf.onion
next prev parent reply other threads:[~2016-06-22 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 0:07 [PATCH] gnu: Add netcat-openbsd ng0
2016-06-22 4:52 ` Leo Famulari
2016-06-22 8:14 ` ng0
2016-06-22 8:33 ` ng0
2016-06-22 11:00 ` [PATCH] gnu: Add netcat-openbsd. [v2] ng0
2016-06-22 21:23 ` Ludovic Courtès
2016-06-22 22:43 ` ng0 [this message]
2016-06-24 11:53 ` Ludovic Courtès
2016-07-08 16:24 ` ng0
2016-06-22 22:46 ` ng0
2016-08-04 8:26 ` ng0
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160622224315.GA17885@shadowwalker \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).