From: Dmitry Alexandrov <dag@gnui.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: python-pip is broken after updates
Date: Tue, 26 May 2020 04:00:47 +0300 [thread overview]
Message-ID: <eer77bnk.dag@gnui.org> (raw)
In-Reply-To: <20200525061153.GB17182@E5400> (Efraim Flashner's message of "Mon, 25 May 2020 09:11:53 +0300")
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Efraim Flashner <efraim@flashner.co.il> wrote:
> On Mon, May 25, 2020 at 01:34:18AM +0300, Dmitry Alexandrov wrote:
>> znavko@disroot.org wrote:
>>> protonvpn installs own client written on python3 requiring pip3. It works fine after installation under root.
>>> Could you … make some advices?
>>
>> Guix aside, I definitely could advise you to stop using obscure ad-hoc software, that has to be run with superuser rights, when itʼs not necessary. And in your case itʼs not.
>
> This is certainly not useful advice.
I have another experience. Quite a few people found an idea, that many services can be easily (in fact, sometimes even _easier_) be used without installing any ad-hoc branded software, new to them. (Welcome to 2020. ;-).
> It's not up to you to determine which software is appropriate and acceptable for another user to run.
How have your thought shifted from from ‘advise’ to ‘determine’, I wonder?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-05-26 1:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 15:55 python-pip is broken after updates znavko
2020-05-24 22:34 ` Dmitry Alexandrov
2020-05-25 6:11 ` Efraim Flashner
2020-05-26 1:00 ` Dmitry Alexandrov [this message]
2020-05-25 15:46 ` znavko
2020-05-26 1:08 ` Avoiding ad-hoc provider-branded OpenVPN clients (was: python-pip is broken after updates) Dmitry Alexandrov
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eer77bnk.dag@gnui.org \
--to=dag@gnui.org \
--cc=efraim@flashner.co.il \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).