From: linde12 <linde12@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] upgrading blueman & docker fails "Directory not empty"
Date: Fri, 29 Oct 2021 19:11:23 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33815@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]
New issue by linde12 on void-packages repository
https://github.com/void-linux/void-packages/issues/33815
Description:
I'm having multiple weird issues today. First of all blueman-manager stopped working (all of a sudden i was missing dependencies like `gi` and `cairo`) so i thought i'd reinstall after an upgrade. What i did was:
```sh
xbps-remove blueman
xbps-install -Syu
```
After this it would start updaing packages but get stuck at the following:
```
bluez-5.61_1: updating to 5.62_2 ...
bluez-5.62_2: unpacking ...
ERROR: bluez-5.62_2: [unpack] failed to extract file `./etc/sv/bluetoothd/log/supervise': Directory not empty
ERROR: bluez-5.62_2: [unpack] failed to extract files: Directory not empty
ERROR: bluez-5.62_2: [unpack] failed to unpack files from archive: Directory not empty
Transaction failed! see above for errors.
```
I thought that was a weird error because obviously that directory is not empty because i still have bluez installed. However i uninstalled bluez as well because i did not want to spend any more time on this, but now i am getting a similar error from the `moby` package which is telling me that `/etc/sv/docker/log/supervise` also isn't empty which, again, it obviously isn't since i've installed docker previously.
```
moby-20.10.6_1: updating to 20.10.9_2 ...
moby-20.10.9_2: unpacking ...
ERROR: moby-20.10.9_2: [unpack] failed to extract file `./etc/sv/docker/log/supervise': Directory not empty
ERROR: moby-20.10.9_2: [unpack] failed to extract files: Directory not empty
ERROR: moby-20.10.9_2: [unpack] failed to unpack files from archive: Directory not empty
Transaction failed! see above for errors.
```
I'm wondering if anyone can help me shed some light on this. Blueman stopped working overnight and now i'm getting all these errors so i've got no idea whats going on.
### System
* xuname:
Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1
SSL_connect returned 1
Certificate verification failed for /C=US/O=Internet Security Research Group/CN=ISRG Root X1
SSL_connect returned 1
Void 5.13.19_1 x86_64 GenuineIntel uptodate rFFF
* package:
moby-20.10.6_2, bluez-5.62_2
### Expected behavior
blueman to not break out of nowhere & `xbps-install -Syu` to work.
### Actual behavior
`xbps-install -Syu` fails when upgrading previously installed packages related to services such as dockerd & bluetoothd
next reply other threads:[~2021-10-29 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 17:11 linde12 [this message]
2021-10-29 17:18 ` Duncaen
2021-10-29 17:27 ` [ISSUE] [CLOSED] " linde12
2021-10-29 17:27 ` linde12
2021-11-12 21:57 ` jchook
2021-11-12 22:07 ` Duncaen
2021-11-12 22:08 ` Duncaen
2021-11-12 22:08 ` Duncaen
2021-11-12 22:10 ` Duncaen
2021-11-12 22:10 ` Duncaen
2021-11-12 22:11 ` Duncaen
2021-11-12 22:35 ` jchook
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-33815@inbox.vuxu.org \
--to=linde12@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).