From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: upgrading blueman & docker fails "Directory not empty"
Date: Fri, 12 Nov 2021 23:08:34 +0100 [thread overview]
Message-ID: <20211112220834.G9tNACmR7sEw_qt-YxRhhTLAup1hntzIfarHOhvGJBk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33815@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/33815#issuecomment-967661799
Comment:
In normal cases the supervise "directory" is actually a symlink pointing to something like `/run/runit/supervise.$service`, this avoids runit writing temporary stuff to the filesystem at `/etc`.
What happened to some services was due to a bug in `xbps-src` this symlink was not created for the log services whose run file was a symlink to something, in this case `vlogger`.
This bug was fixed and those packages now contain this symlink. But since they did not previously and runit created the supervise directory, which also was not tracked by xbps we run into this problem.
xbps does not recursively delete previously untracked files, so because this directory is untracked and contains files, manual intervention is required once, once for those 12 services iirc.
next prev parent reply other threads:[~2021-11-12 22:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 17:11 [ISSUE] " linde12
2021-10-29 17:18 ` Duncaen
2021-10-29 17:27 ` [ISSUE] [CLOSED] " linde12
2021-10-29 17:27 ` linde12
2021-11-12 21:57 ` jchook
2021-11-12 22:07 ` Duncaen
2021-11-12 22:08 ` Duncaen [this message]
2021-11-12 22:08 ` Duncaen
2021-11-12 22:10 ` Duncaen
2021-11-12 22:10 ` Duncaen
2021-11-12 22:11 ` Duncaen
2021-11-12 22:35 ` jchook
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=20211112220834.G9tNACmR7sEw_qt-YxRhhTLAup1hntzIfarHOhvGJBk@z \
--to=duncaen@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).