Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: `vsv` not creating `log/supervise` when `log/run` is a symlink
Date: Fri, 29 Oct 2021 17:14:38 +0200	[thread overview]
Message-ID: <20211029151438.TWoABo--6hnuWOH2vzVEhJKX9EjyvRwJYc3hZap3CkU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32076@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

New comment by dkwo on void-packages repository

https://github.com/void-linux/void-packages/issues/32076#issuecomment-954824908

Comment:
Ehm, this actually breaks things for me
```
$ xi -S bluez
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/nonfree/x86_64-musl-repodata' ...

Name    Action    Version           New version            Download size
libical install   -                 3.0.10_1               -
bluez   install   -                 5.62_2                 -

Size required on disk:        5932KB
Space available on disk:       121GB

Do you want to continue? [Y/n]

[*] Verifying package integrity
libical-3.0.10_1: verifying RSA signature...
bluez-5.62_2: verifying RSA signature...

[*] Collecting package files
libical-3.0.10_1: collecting files...
bluez-5.62_2: collecting files...

[*] Unpacking packages
libical-3.0.10_1: unpacking ...
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.
```

  parent reply	other threads:[~2021-10-29 15:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 23:35 [ISSUE] " AluminumTank
2021-07-23 11:44 ` leahneukirchen
2021-08-02 16:49 ` AluminumTank
2021-08-02 17:34 ` AluminumTank
2021-10-07 18:18 ` Duncaen
2021-10-07 18:19 ` Duncaen
2021-10-29 13:40 ` [ISSUE] [CLOSED] " leahneukirchen
2021-10-29 13:44 ` leahneukirchen
2021-10-29 15:14 ` dkwo [this message]
2021-10-29 15:15 ` dkwo
2021-10-29 15:20 ` TinfoilSubmarine
2021-10-29 15:31 ` dkwo
2021-10-29 15:32 ` TinfoilSubmarine
2021-10-29 15:33 ` Duncaen
2021-10-29 15:33 ` Duncaen
2021-10-29 15:34 ` dkwo

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=20211029151438.TWoABo--6hnuWOH2vzVEhJKX9EjyvRwJYc3hZap3CkU@z \
    --to=dkwo@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).