From: 38github <38github@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] wireplumber-0.4.11_2 [unpack] failed to extract file [....]
Date: Tue, 20 Sep 2022 23:34:44 +0200 [thread overview]
Message-ID: <20220920213444.gBjRaRSX-VaAueoMUrAcQLc_hOk1-gmIPI4nbj_dZb8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39362@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
Closed issue by 38github on void-packages repository
https://github.com/void-linux/void-packages/issues/39362
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.19_1 x86_64 GenuineIntel notuptodate rFF
### Package(s) Affected
wireplumber-0.4.11_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Unpack and succeed.
### Actual behaviour
wireplumber-0.4.11_2: unpacking ...
ERROR: wireplumber-0.4.11_2: [unpack] failed to extract file `./etc/sv/wireplumber/supervise': Directory not empty
ERROR: wireplumber-0.4.11_2: [unpack] failed to extract files: Directory not empty
ERROR: wireplumber-0.4.11_2: [unpack] failed to unpack files from archive: Directory not empty
Transaction failed! see above for errors.
### Steps to reproduce
1. sudo xbps-install -Su
2. I choose 'Yes' to install the packages
3. It starts the process.
4. Fails
next prev parent reply other threads:[~2022-09-20 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 11:00 [ISSUE] " 38github
2022-09-19 11:23 ` paper42
2022-09-20 21:34 ` 38github [this message]
2022-09-20 21:34 ` 38github
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=20220920213444.gBjRaRSX-VaAueoMUrAcQLc_hOk1-gmIPI4nbj_dZb8@z \
--to=38github@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).