all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27261@debbugs.gnu.org
Subject: bug#27261: guix package -u should warn about non-existent packages
Date: Mon, 26 Jun 2017 14:32:54 -0400	[thread overview]
Message-ID: <20170626183254.GA14748@jasmine.lan> (raw)
In-Reply-To: <87zicv89fk.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

On Mon, Jun 26, 2017 at 10:01:03AM +0200, Ludovic Courtès wrote:
> Could you check whether “guix package -A syncthing” shows it there?  The
> warning should appear as soon as we’re upgrading a package that’s
> missing.

I get no results when I do `./pre-inst-env guix package -A syncthing`
from the repo where I removed qsyncthingtray.

`guix package -A syncthing` shows a result for qsyncthingtray, because
that is a "plain" Guix, from `guix pull`, set up as described in Binary
Installation:

$ ls -l $(which guix)
lrwxrwxrwx 1 root staff 54 Aug 14  2015 /usr/local/bin/guix -> /var/guix/profiles/per-user/root/guix-profile/bin/guix
$ ls -l ~/.config/guix/latest 
lrwxrwxrwx 1 leo leo 55 Jun 25 19:19 /home/leo/.config/guix/latest -> /gnu/store/jbrn4pixmrqmqk8jmx533cnqhjhm17sb-guix-latest

But, that's not the Guix that I expect to be queried for packages. Maybe
there is some unexpected interaction between the various copies of Guix?

I'll try this on GuixSD today or tomrrow.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-06-26 18:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06  0:48 bug#27261: guix package -u should warn about non-existent packages Mark H Weaver
2017-06-25 20:30 ` Ludovic Courtès
2017-06-25 23:53   ` Leo Famulari
2017-06-26  8:01     ` Ludovic Courtès
2017-06-26 18:32       ` Leo Famulari [this message]
2017-06-26 18:51         ` Marius Bakke
2017-06-27 13:56           ` Ludovic Courtès
2017-06-27 19:41         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170626183254.GA14748@jasmine.lan \
    --to=leo@famulari.name \
    --cc=27261@debbugs.gnu.org \
    --cc=ludo@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 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.