From: Maxime Devos <maximedevos@telenet.be>
To: bo0od <bo0od@riseup.net>, Julien Lepiller <julien@lepiller.eu>
Cc: 47748@debbugs.gnu.org
Subject: bug#47748: Packages which cant be find/removed by guix remove
Date: Thu, 15 Apr 2021 20:04:16 +0200 [thread overview]
Message-ID: <607e61d554b9eb6dedf6c9d3acf2ce414fe8d3c1.camel@telenet.be> (raw)
In-Reply-To: <f8e5135f-aead-29b9-34e6-106155d40a27@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
On Thu, 2021-04-15 at 09:37 +0000, bo0od wrote:
> > guix remove: error: package 'm17n-lib' not found in profile
> > Hint: All users have their own profiles. To remove packages from the
> profile
> > of the root user, run "sudo guix remove PACKAGES" or equivalent.
>
> yeah very nice one, except that "sudo guix remove package" doesnt work :(
I suggested two hints. What do you think of the second hint:
Hint: On Guix System, packages can defined in the operating system declaration.
These are not affected by "guix remove PACKAGES".
I don't know if it applies to your exact situation though (not following
the discussion very closely).
> This is how its done in debian/fedora, for e.g this is what debian error
> give if apt needs root rights to delete a package:
>
> "user@host:~$ apt remove hexchat
> E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13:
> Permission denied)
> E: Unable to acquire the dpkg frontend lock
> (/var/lib/dpkg/lock-frontend), are you root?"
>
> This is what it shows in Fedora: [...]
In that case, my first hint would have been informative, no?
I don't see what you are trying to show here.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-04-15 18:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 12:46 bug#47748: Packages which cant be find/removed by guix remove bo0od
2021-04-14 0:28 ` Julien Lepiller
2021-04-14 2:44 ` Mark H Weaver
2021-04-14 10:34 ` Julien Lepiller
2021-04-14 16:07 ` Mark H Weaver
2021-04-16 14:52 ` Mark H Weaver
2021-04-14 16:31 ` bo0od
2021-04-14 18:42 ` Mark H Weaver
2021-04-15 9:26 ` bo0od
2021-04-15 19:34 ` Mark H Weaver
2021-04-16 2:45 ` bo0od
2021-04-14 18:44 ` Maxime Devos
2021-04-15 9:37 ` bo0od
2021-04-15 18:04 ` Maxime Devos [this message]
2021-04-16 2:58 ` bo0od
2021-04-14 18:48 ` Julien Lepiller
2021-04-15 10:16 ` bo0od
2021-04-15 11:03 ` Julien Lepiller
2021-04-16 2:11 ` bo0od
2021-04-16 3:41 ` Leo Famulari
2021-04-16 4:37 ` bo0od
2021-04-16 7:23 ` Leo Famulari
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=607e61d554b9eb6dedf6c9d3acf2ce414fe8d3c1.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=47748@debbugs.gnu.org \
--cc=bo0od@riseup.net \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).