From: nonchip <nonchip@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] go-ipfs: addition of vsv breaks upgradeability
Date: Sun, 24 Jan 2021 10:03:05 +0100 [thread overview]
Message-ID: <20210124090305.VpK3wC65Re_GFnN15DyoYtLPLZY0Ic8wOS5jyelKgw0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28135@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
Closed issue by nonchip on void-packages repository
https://github.com/void-linux/void-packages/issues/28135
Description:
i already had a `ipfs` service before https://github.com/void-linux/void-packages/commit/65826688d9da8e9cb3c3f47c3c1862f46b327ae9, when trying to `xbps-install -Su` now it fails with:
```
go-ipfs-0.5.0_1: updating to 0.7.0_2 ...
go-ipfs-0.7.0_2: unpacking ...
ERROR: go-ipfs-0.7.0_2: [unpack] failed to extract file `./etc/sv/ipfs/supervise': Directory not empty
ERROR: go-ipfs-0.7.0_2: [unpack] failed to extract files: Directory not empty
ERROR: go-ipfs-0.7.0_2: [unpack] failed to unpack files from archive: Directory not empty
Transaction failed! see above for errors.
```
so 2 problems i have now:
* as far as I understand it, the `supervise` directory shouldn't fail the update when it's non-empty (guess that's related to it not having been a symlink before), which brings me to question 2:
* how would one migrate an already existing service+systemuser to the new ones introduced without any documentation whatsoever?
next prev parent reply other threads:[~2021-01-24 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 8:34 [ISSUE] go-ipfs: recent " nonchip
2021-01-24 9:03 ` go-ipfs: " nonchip
2021-01-24 9:03 ` nonchip [this message]
2021-01-24 9:04 ` nonchip
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=20210124090305.VpK3wC65Re_GFnN15DyoYtLPLZY0Ic8wOS5jyelKgw0@z \
--to=nonchip@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).