From: AluminumTank <AluminumTank@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] `vsv` not creating `log/supervise` when `log/run` is a symlink
Date: Wed, 21 Jul 2021 01:35:05 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32076@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
New issue by AluminumTank on void-packages repository
https://github.com/void-linux/void-packages/issues/32076
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### Affected packages:
At minimum, those that have `log/run` symlinked to `/usr/bin/vlogger`. Current list below.
* bluez
* caddy
* dhcp
* go-ipfs
* lldpd
* minidlna
* synapse
* vnstat
* yggdrasil
* znc
* moby
### Expected behavior
Package should include a symlink from `/etc/sv/<pkgname>/log/supervise` to `/run/runit/supervise.<pkgname>-log` if `log/run` is present in the service directory passed to vsv.
### Actual behavior
The `log/supervise` symlink is missing.
### Steps to reproduce the behavior
Just run `xls <pkgname>` on any of the packages in the list above and see that they are missing the `log/supervise` symlink.
next reply other threads:[~2021-07-20 23:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 23:35 AluminumTank [this message]
2021-07-23 11:44 ` leahneukirchen
2021-08-02 16:49 ` AluminumTank
2021-08-02 17:34 ` AluminumTank
2021-10-07 18:18 ` Duncaen
2021-10-07 18:19 ` Duncaen
2021-10-29 13:40 ` [ISSUE] [CLOSED] " leahneukirchen
2021-10-29 13:44 ` leahneukirchen
2021-10-29 15:14 ` dkwo
2021-10-29 15:15 ` dkwo
2021-10-29 15:20 ` TinfoilSubmarine
2021-10-29 15:31 ` dkwo
2021-10-29 15:32 ` TinfoilSubmarine
2021-10-29 15:33 ` Duncaen
2021-10-29 15:33 ` Duncaen
2021-10-29 15:34 ` dkwo
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-32076@inbox.vuxu.org \
--to=aluminumtank@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).