From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] base-files-0.142_11: /run must not be a directory
Date: Sun, 17 Jul 2022 13:05:55 +0200 [thread overview]
Message-ID: <20220717110555.dYm2Vrgy7JQEZd_qLzOzsGtIP-04wv8xXNj8hvCtWpw@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: 2015 bytes --]
Closed issue by sakhmatd on void-packages repository
https://github.com/void-linux/void-packages/issues/36634
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. -->
### System
* xuname:
```
Void 5.13.19_1 x86_64 GenuineIntel notuptodate rrrmFFFFF
```
* package:
```
base-files-0.142_11
```
### Expected behavior
Should install as normal.
### Actual behavior
Displays the following output before exiting:
```
Name Action Version New version Download size
base-files update 0.142_11 0.142_12 -
Size required on disk: 239KB
Space available on disk: 81GB
Do you want to continue? [Y/n] y
[*] Verifying package integrity
base-files-0.142_12: verifying RSA signature...
[*] Collecting package files
base-files-0.142_12: collecting files...
base-files-0.142_11: collecting files...
[*] Unpacking packages
base-files-0.142_11: updating to 0.142_12 ...
base-files-0.142_12: unpacking ...
Creating system directories/symlinks...
/run must not be a directory, exiting!
ERROR: base-files-0.142_12: [unpack] INSTALL script failed to execute pre ACTION: Operation not permitted
ERROR: base-files-0.142_12: [unpack] failed to unpack files from archive: Operation not permitted
Transaction failed! see above for errors.
```
### Steps to reproduce the behavior
`xbps-install -f base-files` or `xbps-install -Suv`.
Currently prevents me from a full upgrade.
Due to /run being needed by runit and various daemons, I can't temporarily remove/move the folder to see if it helps the package install (Device or resource busy on attempt).
Here are the current contents of /run:
```
agetty.reload blkid cups docker lock lvm runit sshd.pid udev utmp
avahi-daemon bluealsa dbus initramfs log mount samba sudo user xtables.lock
```
prev parent reply other threads:[~2022-07-17 11:05 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
2022-04-11 23:43 ` sakhmatd
2022-07-17 2:14 ` github-actions
2022-07-17 11:05 ` Duncaen [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=20220717110555.dYm2Vrgy7JQEZd_qLzOzsGtIP-04wv8xXNj8hvCtWpw@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).