GNU bug report logs - #29088
Superseded package is not rebuild if native dependency changes

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29088 in the body.
You can then email your comments to 29088 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Hartmut Goebel <h.goebel <at> crazy-compilers.com>
To: bug-guix <bug-guix <at> gnu.org>
Subject: Superseded package is not rebuild if native dependency changes
Date: Tue, 31 Oct 2017 18:32:45 +0100

Hi,

the package "gpgmepp" depends on native input "extra-cmake-modules".
However if the alter is changed, gpgmepp is not rebuild.

How to reproduce

    git checkout master # important: without
    http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29087 applied

    ./pre-inst-env guix build gpgmepp

now apply http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29087

    ./pre-inst-env guix build extra-cmake-modules # the package changed
    by patch 29087

    ./pre-inst-env guix build gpgmepp
    guix build: package 'gpgmepp' has been superseded by 'gpgme'
    /gnu/store/ky8p7lllm9h9sv1zy0f742r1cc6qbd1l-gpgme-1.9.0

This does *not* rebuild gpgmepp, but simply return the old store-path.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel <at> crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Message #8 received at 29088 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel <at> crazy-compilers.com>
Cc: 29088 <at> debbugs.gnu.org
Subject: Re: bug#29088: Superseded package is not rebuild if native dependency
 changes
Date: Tue, 31 Oct 2017 23:27:09 +0100

Hi,

Hartmut Goebel <h.goebel <at> crazy-compilers.com> skribis:

> the package "gpgmepp" depends on native input "extra-cmake-modules".
> However if the alter is changed, gpgmepp is not rebuild.
>
> How to reproduce
>
>     git checkout master # important: without
>     http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29087 applied
>
>     ./pre-inst-env guix build gpgmepp
>
> now apply http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29087
>
>     ./pre-inst-env guix build extra-cmake-modules # the package changed
>     by patch 29087
>
>     ./pre-inst-env guix build gpgmepp
>     guix build: package 'gpgmepp' has been superseded by 'gpgme'
>     /gnu/store/ky8p7lllm9h9sv1zy0f742r1cc6qbd1l-gpgme-1.9.0
>
> This does *not* rebuild gpgmepp, but simply return the old store-path.

Superseded packages cannot be built/installed unwillingly.  In the
example above, what you built is “gpgme”, not “gpgmepp”, which is why
any changes to “gpgmepp” had no effect.

To force a build of the superseded package, you can run:

  guix build -e '(@ (gnu packages kde-frameworks) gpgmepp)'

But again, the intended meaning of superseded packages is that they are
superseded and must no longer be used.

So to me this can be closed as “not a bug.”

HTH!

Ludo’.

Message #11 received at 29088 <at> debbugs.gnu.org (full text, mbox):

From: Hartmut Goebel <h.goebel <at> crazy-compilers.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 29088 <at> debbugs.gnu.org
Subject: Re: bug#29088: Superseded package is not rebuild if native dependency
 changes
Date: Wed, 1 Nov 2017 09:39:14 +0100

Am 31.10.2017 um 23:27 schrieb Ludovic Courtès:
> Superseded packages cannot be built/installed unwillingly.  In the
> example above, what you built is “gpgme”, not “gpgmepp”, which is why
> any changes to “gpgmepp” had no effect.

IC. Indeed I missed that a different package was build. So I agree, this
is not a bug.

But i suggest to emit a more verbose message in this case, e.g.:

guix build: package 'gpgmepp'
will not be build, since it       <<--- new
has been superseded by 'gpgme'.
'gpgme' will be build instead.    <<--- new

Or (maybe easier to implement:
guix build: package 'gpgmepp' has been superseded by 'gpgme'.
Thus 'gpgme' will be build instead of 'gpgmepp'.        <<--- new

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel <at> crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

Message #14 received at 29088 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel <at> crazy-compilers.com>
Cc: 29088 <at> debbugs.gnu.org
Subject: Re: bug#29088: Superseded package is not rebuild if native dependency
 changes
Date: Thu, 02 Nov 2017 00:14:06 +0100

Hi Hartmut,

Hartmut Goebel <h.goebel <at> crazy-compilers.com> skribis:

> Am 31.10.2017 um 23:27 schrieb Ludovic Courtès:
>> Superseded packages cannot be built/installed unwillingly.  In the
>> example above, what you built is “gpgme”, not “gpgmepp”, which is why
>> any changes to “gpgmepp” had no effect.
>
> IC. Indeed I missed that a different package was build. So I agree, this
> is not a bug.
>
> But i suggest to emit a more verbose message in this case, e.g.:
>
> guix build: package 'gpgmepp'
> will not be build, since it       <<--- new
> has been superseded by 'gpgme'.
> 'gpgme' will be build instead.    <<--- new
>
> Or (maybe easier to implement:
> guix build: package 'gpgmepp' has been superseded by 'gpgme'.
> Thus 'gpgme' will be build instead of 'gpgmepp'.        <<--- new

I see your point, but I’m not entirely convinced.  :-)  After all, the
name that appears, be it at the end of ‘guix build’ or in the profile
created by ‘guix package’, is “gpgme”, not “gpgmepp”.

We could make the messages more verbose, but in general it’s unclear
that it would help.

However, that’s another situation where colored output could help make
useful messages more visible.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.