From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package libtls-3.3.4_1 contains netcat
Date: Sat, 18 Sep 2021 23:54:13 +0200 [thread overview]
Message-ID: <20210918215413.CxFtxoJsvPAczWKxYaL9b5Jt-KFR6u5e1U31PPu4ee0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32976@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Closed issue by 4ricci on void-packages repository
https://github.com/void-linux/void-packages/issues/32976
Description:
* xuname:
Void 5.13.15_1 x86_64 GenuineIntel uptodate rrFFFFFFFFFFFFFFFFFFFF
* package:
libtls-3.3.4_1
Package `libtls` should not provide `nc`, as this is provided by `libressl-netcat` subpackage.
Since version 3.3.4, `xbps-query -f libtls` also shows these files:
```
/usr/bin/nc
/usr/share/man/man1/nc.1
```
which are not even declared as alternatives, thus breaking the `/usr/bin/nc` symlink.
I noted that the netcat binaries provided by the two packages don't have the same checksum, but they should be the same thing.
prev parent reply other threads:[~2021-09-18 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 22:29 [ISSUE] " 4ricci
2021-09-18 21:39 ` 4ricci
2021-09-18 21:54 ` 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=20210918215413.CxFtxoJsvPAczWKxYaL9b5Jt-KFR6u5e1U31PPu4ee0@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).