From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 29088@debbugs.gnu.org
Subject: bug#29088: Superseded package is not rebuild if native dependency changes
Date: Tue, 31 Oct 2017 23:27:09 +0100 [thread overview]
Message-ID: <87inevvtqa.fsf@gnu.org> (raw)
In-Reply-To: <5bd582ba-60c7-f1bd-dad7-ae15c162a9d2@crazy-compilers.com> (Hartmut Goebel's message of "Tue, 31 Oct 2017 18:32:45 +0100")
Hi,
Hartmut Goebel <h.goebel@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’.
next prev parent reply other threads:[~2017-10-31 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 17:32 bug#29088: Superseded package is not rebuild if native dependency changes Hartmut Goebel
2017-10-31 22:27 ` Ludovic Courtès [this message]
2017-11-01 8:39 ` Hartmut Goebel
2017-11-01 23:14 ` Ludovic Courtès
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=87inevvtqa.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29088@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).