From: Phil Beadling <phil@beadling.co.uk>
To: guix-devel@gnu.org
Subject: --with-source version not honored?
Date: Wed, 20 Oct 2021 10:18:02 +0100 [thread overview]
Message-ID: <CAOvsyQsqCN-2w11=FL5DqH3oXXt2S2Cy7rMEXGNdVqWAVHNuzw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]
Hi all,
I'm using the following incantation:
guix build
--with-source=foobar@9.5.0=/opt/thirdparty/foobar/foobar950_beta/linux64
<--with-source=gurobipy@9.5.0=/opt/thirdparty/gurobi/gurobi950_beta/linux64>
foobar
However the package build is failing with:
(copy-file "lib/libfoobar.so.9.0.1" "/gnu/store/gkawzac…")
In procedure copy-file: No such file or directory
That is the new version number 9.5.0 is not written to every place when
transforming the original package (version 9.0.1). I think only the
package-version is updated, but the other package components are not then
regenerated, meaning that if they use the package-version as an input we
get a disjoint package.
In the example above I use version like so:
*(add-after 'install 'install-foobar-library
(lambda* (#:key outputs #:allow-other-keys)
(let* ((dir (string-append (assoc-ref outputs "out")
"/lib/python3.8/site-packages/foobar/"))
(lib-to-install (string-append
"libfoobar.so." ,version))*
But ",version" is not updated, nor is it updated if I change this to call
(package-version foobar).
If I drop into Guile I can see this a bit more clearly by writing a
manifest - the code below gives exactly the same error however when the
package-version is displayed it correctly responds with 9.5.0.
Not sure if this should be considered a bug, or if there is a lazy way of
evaluating version so avoid the problem - I think it's unexpected from a
practicioners point of view as packages end up inconsistent.
I presume I can manually replace the arguments section of the package in
the manifest to workaround this - is there a standard way of doing this?
Any ideas or clarifications welcome!
Cheers,
Phil.
*(use-modules (guix transformations) (guix packages))(define
transform ;; The package transformation procedure.
(options->transformation '((with-source .
"gurobipy@9.5.0=/opt/thirdparty/foobar/foobar950_beta/linux64"))))(define
my-package (transform (specification->package "foobar")))(display
(package-version my-package)) ;; this will display version
9.5.0(newline)(packages->manifest (list my-package)) ;; building this will
fail because copy-file still looks for 9.0.1*
[-- Attachment #2: Type: text/html, Size: 4382 bytes --]
next reply other threads:[~2021-10-20 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 9:18 Phil Beadling [this message]
2021-10-20 11:08 ` --with-source version not honored? Julien Lepiller
2021-10-20 11:48 ` zimoun
2021-10-20 19:46 ` Phil
2021-10-21 10:18 ` zimoun
2021-10-21 20:22 ` Ludovic Courtès
2021-10-21 21:17 ` zimoun
2021-10-23 10:04 ` Phil
2021-10-24 12:11 ` Phil Beadling
2021-10-29 14:02 ` Ludovic Courtès
2021-10-20 19:25 ` Phil
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='CAOvsyQsqCN-2w11=FL5DqH3oXXt2S2Cy7rMEXGNdVqWAVHNuzw@mail.gmail.com' \
--to=phil@beadling.co.uk \
--cc=guix-devel@gnu.org \
/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).