all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, MutoShack <shack@muto.ca>
Subject: Re: Guix on a foreign distro (Mint) - List of packages is outdated and	not updatable
Date: Tue, 23 Apr 2019 09:36:30 +0200	[thread overview]
Message-ID: <8B304934-3334-4435-9ED4-EED604EC3294@lepiller.eu> (raw)
In-Reply-To: <8736m8lccn.fsf@muto.ca>

Le 23 avril 2019 22:02:00 GMT+02:00, MutoShack <shack@muto.ca> a écrit :
>I've been using Guix for a while on my Mint 19.1 machine. When Nano 4.0
>came out as a Guix package I was excited, so I ran:
>'guix pull && guix package -u'
>on my machine. It pulled Nano 2.9.3 from mirror.hydra.gnu.org (I
>recently had Nano 3.4 installed, which means Guix downgraded my
>package)
>
>My laptop computer, running GuixSD, pulled Nano 4.0 (and other new
>packages) perfectly fine.
>
>Running
>'/path/to/guix-daemon --substitute-urls="https://ci.guix.info"'
>and pulling yields the same result.
>Deleting '~/.config' on both user & root, then letting 'guix pull'
>regenerate them also did nothing.
>
>I tried changing my generation and deleting old generations.
>I tried the good old "RTFM" and "STFW" methods (reading info and
>websearching), but I could not find an answer. Maybe I misunderstood
>the
>information I found.

Hi, this sounds like you're not using she right guix, like a guix installed in your profile. If that's the case, every time you "upgrade", you actually downgrade guix itself and the packages it knoos about.

Make sure that ~/.config/guix/current/bin tomes first in your $PATH and run "hash guix" to make sure your shell refers to the right guix.

  reply	other threads:[~2019-04-23  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 20:02 Guix on a foreign distro (Mint) - List of packages is outdated and not updatable MutoShack
2019-04-23  7:36 ` Julien Lepiller [this message]
2019-04-23 19:26   ` melon
2019-05-06  2:57     ` Chris Marusich

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=8B304934-3334-4435-9ED4-EED604EC3294@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    --cc=shack@muto.ca \
    /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.