From: Fis Trivial <ybbs.daans@hotmail.com>
To: "ng0@n0.is" <ng0@n0.is>, "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Why are those packages upgrade to the same version?
Date: Wed, 3 Jan 2018 16:57:08 +0000 [thread overview]
Message-ID: <MWHPR16MB0063237C5B638D13977ADB74921E0@MWHPR16MB0063.namprd16.prod.outlook.com> (raw)
In-Reply-To: <20180103164217.xzye2jnhpocv7fgn@abyayala>
>
> Well that's easy to explain, nothing changed if "nothing to be done" is displayed.
> So if you have problems with the message, what kind of message do you think would
> be easier to understand if no packages need to be updated?
>
> Maybe a little more in detail, like:
>
> "Your installed software packages are all up-to-date, no upgrades necessary.
> Nothing to be done."
>
Thanks for the reply. The problem I encountered is that guix shows a list of packages
to be upgraded, but didn't upgrade them as it should.
I just found out that the problem was caused by missing packages definitions. I
installed a few software packaged myself using `guix package -f ...` but didn't
add the recipes to GUIX_PACKAGE_PATH.
Then Guix failed to upgrade any other packages from official repo(and report false
upgrade list). After exporting GUIX_PACKAGE_PATH, problem was resolved.
I should have thought of it earlier. But maybe this can be added to the doc?
next prev parent reply other threads:[~2018-01-03 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 17:07 Why are those packages upgrade to the same version? Fis Trivial
2018-01-02 9:07 ` Efraim Flashner
2018-01-03 16:06 ` Fis Trivial
2018-01-03 16:42 ` ng0
2018-01-03 16:54 ` Niall Dooley
2018-01-03 16:57 ` Fis Trivial [this message]
2018-01-03 16:26 ` Fis Trivial
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=MWHPR16MB0063237C5B638D13977ADB74921E0@MWHPR16MB0063.namprd16.prod.outlook.com \
--to=ybbs.daans@hotmail.com \
--cc=help-guix@gnu.org \
--cc=ng0@n0.is \
/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).