Why are those packages upgrade to the same version?

Why are those packages upgrade to the same version?

[Fis Trivial]

When I did
$ guix package -u
I got the following messages:

--
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
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

substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
The following derivations will be built:
   /gnu/store/53lvhnd82v489r6f4b79kwqsc945vjxj-profile.drv
   /gnu/store/xjfchzq9ai9gmp93b941v3gn7906hz5g-xdg-mime-database.drv
   /gnu/store/cswpjnavr4zlsj7dilpz0ncind956zdp-gtk-icon-themes.drv
   /gnu/store/9gimd8h1nl9mpgcf8676zixdl9xb5v4z-info-dir.drv
   /gnu/store/8dappm5anabp657wajxgzdca78kbmlfm-ghc-package-cache.drv
   /gnu/store/3i8n5zdddkda84dj1q5li15xyp0qmjz0-gtk-im-modules.drv
   /gnu/store/32nfyq57dpdhka16293dqbvzxy4x86q4-fonts-dir.drv
   /gnu/store/26b5pi9i2wycxin1cmjsc4lhgw4flihh-ca-certificate-bundle.drv
   /gnu/store/0hqha5s8g8jp16c14y3jlawp47kxmh1n-xdg-desktop-database.drv
   /gnu/store/alm1j6qhdm2jbh43mg5kwd4hbns0nkv3-manual-database.drv
Creating manual page database...
374 entries processed in 0.4 s
warning: collision encountered: /gnu/store/p3yi7w2wv66h078bb0y36pk5yyw6xr00-gtk-icon-themes/share/icons/hicolor/icon-theme.cache /gnu/store/z8l01npp6izd8dirslwrddy6c2dnajvg-gparted-0.30.0/share/icons/hicolor/icon-theme.cache
warning: arbitrarily choosing /gnu/store/p3yi7w2wv66h078bb0y36pk5yyw6xr00-gtk-icon-themes/share/icons/hicolor/icon-theme.cache
28 packages in profile
--

The process didn't download anything and I didn't see any actual action been performed. Out of curiosity, I tried
it again `$ guix package -u`, and then got the following message:

--
guix package: warning: package 'rtags' no longer exists
guix package: warning: package 'aMule' no longer exists
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
--

Again, it shows a bunch of packages to be upgraded, but the upgraded version are the same with the old version.
And the last line of the message says that "nothing to be done".

Is this a normal case or it's a bug?

Re: Why are those packages upgrade to the same version?

[Efraim Flashner]

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

On Mon, Jan 01, 2018 at 05:07:33PM +0000, Fis Trivial wrote:
> When I did
> $ guix package -u
> I got the following messages:
> 
> --
> substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
> 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
> 
> substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
> substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
> The following derivations will be built:
>    /gnu/store/53lvhnd82v489r6f4b79kwqsc945vjxj-profile.drv
>    /gnu/store/xjfchzq9ai9gmp93b941v3gn7906hz5g-xdg-mime-database.drv
>    /gnu/store/cswpjnavr4zlsj7dilpz0ncind956zdp-gtk-icon-themes.drv
>    /gnu/store/9gimd8h1nl9mpgcf8676zixdl9xb5v4z-info-dir.drv
>    /gnu/store/8dappm5anabp657wajxgzdca78kbmlfm-ghc-package-cache.drv
>    /gnu/store/3i8n5zdddkda84dj1q5li15xyp0qmjz0-gtk-im-modules.drv
>    /gnu/store/32nfyq57dpdhka16293dqbvzxy4x86q4-fonts-dir.drv
>    /gnu/store/26b5pi9i2wycxin1cmjsc4lhgw4flihh-ca-certificate-bundle.drv
>    /gnu/store/0hqha5s8g8jp16c14y3jlawp47kxmh1n-xdg-desktop-database.drv
>    /gnu/store/alm1j6qhdm2jbh43mg5kwd4hbns0nkv3-manual-database.drv
> Creating manual page database...
> 374 entries processed in 0.4 s
> warning: collision encountered: /gnu/store/p3yi7w2wv66h078bb0y36pk5yyw6xr00-gtk-icon-themes/share/icons/hicolor/icon-theme.cache /gnu/store/z8l01npp6izd8dirslwrddy6c2dnajvg-gparted-0.30.0/share/icons/hicolor/icon-theme.cache
> warning: arbitrarily choosing /gnu/store/p3yi7w2wv66h078bb0y36pk5yyw6xr00-gtk-icon-themes/share/icons/hicolor/icon-theme.cache
> 28 packages in profile
> --
> 
> The process didn't download anything and I didn't see any actual action been performed. Out of curiosity, I tried
> it again `$ guix package -u`, and then got the following message:
> 
> --
> guix package: warning: package 'rtags' no longer exists
> guix package: warning: package 'aMule' no longer exists
> 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
> --
> 
> Again, it shows a bunch of packages to be upgraded, but the upgraded version are the same with the old version.
> And the last line of the message says that "nothing to be done".
> 
> Is this a normal case or it's a bug?

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.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

Re: Why are those packages upgrade to the same version?

[Fis Trivial]

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).

Re: Why are those packages upgrade to the same version?

[ng0]

[-- 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 --]

Re: Why are those packages upgrade to the same version?

[Niall Dooley]

On 3 January 2018 at 16:42, ng0 <ng0@n0.is> wrote:
> "Your installed software packages are all up-to-date, no upgrades necessary.
> Nothing to be done."

Yes, this is a big improvement.

I would also suggest if the above (improved) statement is true and so
displayed then statements like the following are
misleading and should not be displayed. That is a statement like the
following should only be displayed if a package(s)
is(are) to be upgraded and perhaps then only list those that would be
updated and not all the user may have installed.

>> 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

Regards,

Niall

Re: Why are those packages upgrade to the same version?

[Fis Trivial]

> 
> 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?

Re: Why are those packages upgrade to the same version?

[Fis Trivial]

I got it now. It's caused by a missing package definition. Sorry for bothering.