From: SorrelArticulata <SorrelArticulata@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] lighttpd: Update fails, "Directory not empty" /etc/sv/lighttpd/log/supervise
Date: Fri, 17 Feb 2023 01:26:07 +0100 [thread overview]
Message-ID: <20230217002607.Owf_NmJbYHKnqLhgDZ2j1iX0-neA69raGHyD0W5gYI0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42303@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
Closed issue by SorrelArticulata on void-packages repository
https://github.com/void-linux/void-packages/issues/42303
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.6_1 x86_64 AuthenticAMD notuptodate FFFFFFFFFFFFFFFFFF
### Package(s) Affected
lighttpd-1.4.69_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Unpacks correctly when updated.
### Actual behaviour
```
# xbps-install -Su
...snip...
libvtv-devel-12.2.0_1: updating to 12.2.0_2 ...
libvtv-devel-12.2.0_2: unpacking ...
libvtv-devel-32bit-12.2.0_1: updating to 12.2.0_2 ...
libvtv-devel-32bit-12.2.0_2: unpacking ...
libykpiv-2.3.0_1: updating to 2.3.0_2 ...
libykpiv-2.3.0_2: unpacking ...
libykpiv-devel-2.3.0_1: updating to 2.3.0_2 ...
libykpiv-devel-2.3.0_2: unpacking ...
lighttpd-1.4.68_1: updating to 1.4.69_1 ...
lighttpd-1.4.69_1: unpacking ...
ERROR: lighttpd-1.4.69_1: [unpack] failed to extract file `./etc/sv/lighttpd/log/supervise': Directory not empty
ERROR: lighttpd-1.4.69_1: [unpack] failed to extract files: Directory not empty
ERROR: lighttpd-1.4.69_1: [unpack] failed to unpack files from archive: Directory not empty
Transaction failed! see above for errors.
#
```
### Workaround
```
# sv stop lighttpd
# rm -r /etc/sv/lighttpd/log/supervise
# xbps-install -u
# sv start lighttpd
```
prev parent reply other threads:[~2023-02-17 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 6:51 [ISSUE] " SorrelArticulata
2023-02-16 9:07 ` classabbyamp
2023-02-16 9:09 ` SorrelArticulata
2023-02-16 18:18 ` Duncaen
2023-02-16 18:18 ` Duncaen
2023-02-17 0:26 ` SorrelArticulata
2023-02-17 0:26 ` SorrelArticulata [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=20230217002607.Owf_NmJbYHKnqLhgDZ2j1iX0-neA69raGHyD0W5gYI0@z \
--to=sorrelarticulata@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).