From: Anachron <Anachron@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Cannot update bash: REMOVE script failed to execute pre ACTION
Date: Sun, 16 Jun 2024 13:55:42 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50847@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
New issue by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/50847
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.83_1 aarch64 Unknown notuptodate rFFFFFFF
### Package(s) Affected
bash-5.2.21_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
It should be possible to update bash from bash-5.2.21_1 to bash-5.2.21_2.
### Actual behaviour
Errors out with
```
bash-5.2.21_1: updating to 5.2.21_2 ...
ERROR: bash-5.2.21_2: [remove] REMOVE script failed to execute pre ACTION: No such file or directory
ERROR: bash-5.2.21_2: failed to remove package: No such file or directory
ERROR: bash-5.2.21_2: [trans] failed to update package `No such file or directory'
Transaction failed! see above for errors.
```
### Steps to reproduce
1. Run `xbps-install -Su`
2. Receive error
next reply other threads:[~2024-06-16 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 11:55 Anachron [this message]
2024-06-16 12:03 ` Anachron
2024-06-16 12:07 ` Anachron
2024-06-16 12:07 ` [ISSUE] [CLOSED] " Anachron
2024-06-16 13:23 ` Duncaen
2024-06-16 13:54 ` Anachron
2024-06-16 14:01 ` Duncaen
2024-06-16 14:01 ` Duncaen
2024-06-16 14:11 ` Anachron
2024-06-16 14:11 ` Anachron
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-50847@inbox.vuxu.org \
--to=anachron@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).