From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: base-files-0.142_11: /run must not be a directory
Date: Mon, 11 Apr 2022 16:20:33 +0200 [thread overview]
Message-ID: <20220411142033.MY9O3dKzSJG5rgmBSB7kzHyRKAFMYCm6--klQifixhc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36634@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/36634#issuecomment-1095113654
Comment:
The error message is wrong, its about `/var/run` which should be a symlink and not a directory. It does not automatically delete /var/run to replace it since that would require recursively deleting files in it, which we can't really do, it contains user data and deleting that automatically at runtime might be bad.
So deleting /var/run and replacing it with a symlink to `../run` would be the solution to it.
next prev parent reply other threads:[~2022-04-11 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 10:24 [ISSUE] " sakhmatd
2022-04-11 14:20 ` Duncaen [this message]
2022-04-11 23:43 ` sakhmatd
2022-07-17 2:14 ` github-actions
2022-07-17 11:05 ` [ISSUE] [CLOSED] " Duncaen
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=20220411142033.MY9O3dKzSJG5rgmBSB7kzHyRKAFMYCm6--klQifixhc@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).