From: Vagrant Cascadian <vagrant@debian.org>
To: Yasuaki Kudo <yasu@yasuaki.com>, Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, "Sławomir Lach" <slawek@lach.art.pl>
Subject: Re: The way to promote GUIX package manager
Date: Wed, 26 Jan 2022 15:38:24 -0800 [thread overview]
Message-ID: <878rv23w5r.fsf@ponder> (raw)
In-Reply-To: <AB1CBFA0-25C3-407B-8379-22E9B6AB0F90@yasuaki.com>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
On 2022-01-27, Yasuaki Kudo wrote:
> Does Guix really run out of the box in Debian?
>
> I have never tried it but my friend Debian expert friend keeps telling me that:
>
> * Just apt-get installing Guix doesn't work
What doesn't work?
The main two issues I'm aware of are...
Issue with "guix pull" from the guix 1.2 version:
https://bugs.debian.org/1001833
The workaround is to first pull to the guix 1.3 commit.
The other issue has to do with incompatible glib versions in guix and
Debian:
https://bugs.debian.org/988260
I'm not aware of a workaround there other than sticking with either Guix
or Debian for the affected packages.
So I'll admit the experience is not absolutely free of surprises, but
that's the generally the case of using any foreign package manager...
If there are other issues specific to the Guix packages in Debian,
please file bugs in the Debian bug tracking system; it's a great way to
contribute back to the community!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-01-26 23:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 11:09 The way to promote GUIX package manager Sławomir Lach
2022-01-26 21:38 ` Ricardo Wurmus
2022-01-26 22:40 ` Yasuaki Kudo
2022-01-26 22:42 ` Ricardo Wurmus
2022-01-26 23:15 ` Yasuaki Kudo
2022-01-27 23:35 ` Bengt Richter
2022-01-27 23:55 ` Yasuaki Kudo
2022-01-28 1:43 ` David Pirotte
2022-01-28 14:48 ` Bengt Richter
2022-01-26 23:38 ` Vagrant Cascadian [this message]
2022-02-05 13:54 ` Ludovic Courtès
2022-02-05 20:39 ` Ricardo Wurmus
2022-02-06 18:54 ` Vagrant Cascadian
2022-02-06 19:19 ` Ricardo Wurmus
2022-02-14 17:23 ` Ludovic Courtès
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=878rv23w5r.fsf@ponder \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=slawek@lach.art.pl \
--cc=yasu@yasuaki.com \
/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).