From: Panos Alevropoulos <panos@gnu.org>
To: 66033@debbugs.gnu.org
Subject: bug#66033: Package name conflict for "helm"
Date: Sat, 16 Sep 2023 17:39:07 +0300 [thread overview]
Message-ID: <20230916143907.5ol7glnlamfbywvj@artix.localdomain> (raw)
Hi,
There seems to be a recently introduced package name conflict.
There are two packages named "helm". One is is the package manager for Kubernetes and the other is a synthesizer. I noticed after upgrading and helm suddenly jumped from 0.9.0 to 3.12.3. `guix install helm@0.9.0` restores helm-lv2 as a temp fix.
I suggest the latter be renamed "helm-lv2" to fix the issue.
Panos
next reply other threads:[~2023-09-18 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 14:39 Panos Alevropoulos [this message]
2023-10-12 20:52 ` bug#66033: Package name conflict for "helm" John Kehayias via Bug reports for GNU Guix
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=20230916143907.5ol7glnlamfbywvj@artix.localdomain \
--to=panos@gnu.org \
--cc=66033@debbugs.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.
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).