From: ng0 <ng0@n0.is>
To: Fis Trivial <ybbs.daans@hotmail.com>
Cc: "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:42:17 +0000 [thread overview]
Message-ID: <20180103164217.xzye2jnhpocv7fgn@abyayala> (raw)
In-Reply-To: <MWHPR16MB00633B365CFDCE7BF3DA88BC921E0@MWHPR16MB0063.namprd16.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]
Fis Trivial transcribed 1.9K bytes:
>
>
> On 01/02/2018 05:07 PM, Efraim Flashner wrote:
>
> >
> > This is normal. The versions don't update but its possible that packages
> > in the dependency build tree might have changed, in which case the
> > resulting package you have would change.
> >
> > As for why it still shows the packages the second time I think its
> > related to the security grafts but I'm not sure.
> >
>
> I am not sure. After reading your reply, I did `guix pull` and `guix package -u` again.
> And got the following message (It's the same as in the last mail)
>
> --
> The following packages will be upgraded:
> cargo 0.23.0 → 0.23.0 /gnu/store/hcdrrvyhwf6nqw3iwn6k3rydpyqg771b-cargo-0.23.0
> python-autopep8 1.3.2 → 1.3.2 /gnu/store/q9blf18p0hz37rv8m3azm75mpl9g1n2p-python-autopep8-1.3.2
> python-flake8 2.5.4 → 2.5.4 /gnu/store/046p961g2d4k73qh9xj6zwn3vs34biwp-python-flake8-2.5.4
> clang 3.9.1 → 3.9.1 /gnu/store/pnjjq6anl7f71fcxqmrr081xjqm9l4wh-clang-3.9.1
> llvm 3.9.1 → 3.9.1 /gnu/store/qvhfk8905dic99xx29d8afcc7ay060gs-llvm-3.9.1
> meson 0.44.0 → 0.44.0 /gnu/store/n53zdnl4l3gm9sg15bfwxp0wdrwrvhg4-meson-0.44.0
> glibc-locales 2.25 → 2.25 /gnu/store/y81gbp5lrjiydj5xj7sczx73vnkprzkv-glibc-locales-2.25
>
> nothing to be done
> --
>
>
> And doing `guix package -u` (without pull) 2th, 3th ... the same message shows up again and again.
> It doesn't download anything or perform any upgrade (judging from the network monitor).
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."
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
WWW: https://n0.is/a/ :: https://ea.n0.is
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-03 16:42 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 [this message]
2018-01-03 16:54 ` Niall Dooley
2018-01-03 16:57 ` Fis Trivial
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180103164217.xzye2jnhpocv7fgn@abyayala \
--to=ng0@n0.is \
--cc=help-guix@gnu.org \
--cc=ybbs.daans@hotmail.com \
/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.