From: nonchip <nonchip@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: go-ipfs: addition of vsv breaks upgradeability
Date: Sun, 24 Jan 2021 10:04:33 +0100 [thread overview]
Message-ID: <20210124090433.UilqksggtvuMZo7UD-nrnDRqcCGB3Jw19LZ2PeFWoL4@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: 681 bytes --]
New comment by nonchip on void-packages repository
https://github.com/void-linux/void-packages/issues/28135#issuecomment-766314428
Comment:
after maldrige "informed" me that (contrary to EVERYTHING the handbook says btw) my problem 1 was caused by me being so silly and using `/etc/sv` for it's allegedly intended purpose, combined with the fact that this change was, again, undocumented, i managed to temporarily move my old service out of the way and solve problem 2 by porting everything over to the new user using a horrible bunch of `mv`s and `chowns`.
next time PLEASE figure out what `INSTALL` files are for before introducing such a change in a mere package revision.
prev parent reply other threads:[~2021-01-24 9:04 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 ` [ISSUE] [CLOSED] " nonchip
2021-01-24 9:04 ` nonchip [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=20210124090433.UilqksggtvuMZo7UD-nrnDRqcCGB3Jw19LZ2PeFWoL4@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).