From: bbb ee <blasforr@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 56371@debbugs.gnu.org
Subject: bug#56371: Can't remove a package present in profil
Date: Tue, 5 Jul 2022 13:03:11 +0200 [thread overview]
Message-ID: <CALNLCmVWj9nOqYYeWN6VhqS3RFS5jrBc48v0SuMh0SrwXzj8ug@mail.gmail.com> (raw)
In-Reply-To: <CALNLCmWUHVHtsu9B0tsbZJsRwpTgbnqF54R_-02HSXCVFyZ6_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
Control: close #56371
Le mar. 5 juil. 2022 à 12:46, bbb ee <blasforr@gmail.com> a écrit :
> close #56371
>
> Le mar. 5 juil. 2022 à 12:46, bbb ee <blasforr@gmail.com> a écrit :
>
>> Thanks for the tip!
>>
>> Le lun. 4 juil. 2022 à 07:04, Julien Lepiller <julien@lepiller.eu> a
>> écrit :
>>
>>> It's not a bug, because you don't have icedtea in your profile, but
>>> icedtea:jdk. Guix is picky with outputs. Try "guix remove icedtea:jdk" :)
>>>
>>> On July 3, 2022 7:25:46 PM GMT+02:00, bbb ee <blasforr@gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I have icedtea installed in my current profil, but `guix package
>>>> remove` doesn't find it.
>>>> ```
>>>> $ guix package -p ~/.guix-profile -I | grep icedtea
>>>> icedtea 3.19.0 jdk
>>>> /gnu/store/5k7lsz61p8fq37c9x5p9xalryjxk31bs-icedtea-3.19.0-jdk
>>>> $ guix package -p ~/.guix-profile -r icedtea
>>>> guix package: error: package 'icedtea' not found in profile
>>>> ```
>>>>
>>>> It is a bug?
>>>>
>>>
[-- Attachment #2: Type: text/html, Size: 2127 bytes --]
next prev parent reply other threads:[~2022-07-05 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 17:25 bug#56371: Can't remove a package present in profil bbb ee
2022-07-04 5:04 ` Julien Lepiller
2022-07-05 10:46 ` bbb ee
2022-07-05 10:46 ` bbb ee
2022-07-05 11:03 ` bbb ee [this message]
2022-07-08 7:13 ` paren--- via Bug reports for GNU Guix
2022-07-13 9:02 ` bbb ee
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=CALNLCmVWj9nOqYYeWN6VhqS3RFS5jrBc48v0SuMh0SrwXzj8ug@mail.gmail.com \
--to=blasforr@gmail.com \
--cc=56371@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.