From: Vagrant Cascadian <vagrant@debian.org>
To: "Ricardo Wurmus" <rekado@elephly.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, "Sławomir Lach" <slawek@lach.art.pl>
Subject: Re: The way to promote GUIX package manager
Date: Sun, 06 Feb 2022 10:54:51 -0800 [thread overview]
Message-ID: <87ee4frfk4.fsf@contorta> (raw)
In-Reply-To: <87bkzl2gd7.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]
On 2022-02-05, Ricardo Wurmus wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
>> Vagrant Cascadian <vagrant@debian.org> skribis:
>>
>>> The main two issues I'm aware of are...
>>>
>>> Issue with "guix pull" from the guix 1.2 version:
>>>
>>> https://bugs.debian.org/1001833
>>
>> I believe this was fixed:
>>
>> https://issues.guix.gnu.org/52694
Great, will try it again!
> Last week (or maybe two weeks ago, but no sooner than that) I ran “sudo
> apt install guix” on a laptop with Debian and I followed the advice to
> pull to the commit corresponding to 1.3.0.
That definitely worked a while back when I followed up to the Debian
bug, but guix always seems to have some new surprises in store!
> Every time at the end I got this git error: “the requested type does not
> match the type in the ODB”.
>
> Would it have been any different had I pulled directly to the latest
> version…? Or is this unrelated?
I'll have to verify again...
> (In the end I removed the Debian package and installed with
> https://guix.gnu.org/install.sh; this was trickier than it should have
> been, because the Debian package left behind a broken init service and
> some state that I deleted manually.)
There is a difference on Debian between removed and purged, sounds like
you just removed it:
apt --purge remove PACKAGE
should have done what you wanted, and if it didn't, bugs reports would
be appreciated...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-02-06 19:06 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
2022-02-05 13:54 ` Ludovic Courtès
2022-02-05 20:39 ` Ricardo Wurmus
2022-02-06 18:54 ` Vagrant Cascadian [this message]
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=87ee4frfk4.fsf@contorta \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
--cc=slawek@lach.art.pl \
/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).