From: Pierre Neidhardt <ambrevar@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: `guix package -u` upgrades packages to themselves
Date: Wed, 11 Apr 2018 15:10:34 +0530 [thread overview]
Message-ID: <87vacyytbh.fsf@gmail.com> (raw)
In-Reply-To: <878t9unoat.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
Sorry if I was confusing: the output remains the same after upgrade.
I can repeat the command indefinitely, it keep "upgrading" the same set
of packages as per the output (but it does not actually do anything).
--
Pierre Neidhardt
This restaurant was advertising breakfast any time. So I ordered
french toast in the renaissance.
- Steven Wright, comedian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-04-11 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 7:59 `guix package -u` upgrades packages to themselves Pierre Neidhardt
2018-04-11 8:24 ` Ricardo Wurmus
2018-04-11 9:40 ` Pierre Neidhardt [this message]
2018-04-11 12:24 ` Martin Castillo
2018-04-24 8:32 ` Ludovic Courtès
2018-04-12 8:37 ` Chris Marusich
2018-04-12 9:00 ` Ricardo Wurmus
2018-04-13 6:14 ` Chris Marusich
2018-04-13 6:19 ` Pierre Neidhardt
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=87vacyytbh.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.
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).