From: sbromberger <sbromberger@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: ipsvd, socklog-ucspi
Date: Thu, 29 Dec 2022 06:45:23 +0100 [thread overview]
Message-ID: <20221229054523.Bj8fjcvHJHwioPlOVUvb95G2Nzj2Vl2JVahUW7Iat_Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41321@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
New comment by sbromberger on void-packages repository
https://github.com/void-linux/void-packages/pull/41321#issuecomment-1367040711
Comment:
> Packaging ipsvd is fine, I'd not change the depends for socklog as this is a mode that's rarely used.
The problem is that the current installation of socklog is broken precisely because it assumes `tcpsvd` is available, and it's not. As I see it, the options are either
1. package `ipsvd` and make it a dependency,
2. change socklog dependency to include djb's `ucspi-tcp` package (might also need tcp6) and change the syntax in the `socklog-ucspi` run file,
3. disable / remove `socklog-ucspi`, and/or
4. modify the manpage to clarify that it won't work unless you install and configure a valid tcpserver implementation separate from the official manpage guidelines.
Just out of interest - how do we know it's rarely used? (Just due to the lack of a previous issue?)
next prev parent reply other threads:[~2022-12-29 5:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 0:13 [PR PATCH] socklog: depend on ipsvd for ucspi-tcp service kruceter
2022-12-28 0:25 ` [PR PATCH] [Updated] " kruceter
2022-12-28 0:27 ` kruceter
2022-12-28 19:47 ` leahneukirchen
2022-12-28 19:48 ` leahneukirchen
2022-12-28 20:58 ` [PR PATCH] [Updated] " kruceter
2022-12-29 3:00 ` New packages: ipsvd, socklog-ucspi sbromberger
2022-12-29 5:44 ` sbromberger
2022-12-29 5:45 ` sbromberger [this message]
2022-12-29 5:45 ` sbromberger
2022-12-29 8:00 ` kruceter
2022-12-29 16:32 ` leahneukirchen
2022-12-29 16:58 ` sbromberger
2022-12-29 22:32 ` kruceter
2022-12-29 22:33 ` [PR PATCH] [Updated] " kruceter
2023-01-02 15:19 ` [PR PATCH] [Merged]: " leahneukirchen
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=20221229054523.Bj8fjcvHJHwioPlOVUvb95G2Nzj2Vl2JVahUW7Iat_Y@z \
--to=sbromberger@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).