[PATCH] In the Artanis package the propagated input of guile-json is conflicting with guix, and no series of guix upgrades or guix installs seems to fix this. Therefore, I moved guile-json from a propagated input to an input, which solves the issue, but may not be ideal for people who don't wish to keep multiple copies of guile-json

  • Open
  • quality assurance status badge
Details
4 participants
  • Blake Shaw
  • Leo Famulari
  • Ludovic Courtès
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Blake Shaw
Severity
normal

Debbugs page

B
B
Blake Shaw wrote on 26 Oct 2021 05:46
(address . guix-patches@gnu.org)(name . Blake Shaw)(address . blake@nonconstructivism.com)
20211026124602.28283-1-blake@nonconstructivism.com
---
gnu/packages/guile-xyz.scm | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

Toggle diff (30 lines)
diff --git a/gnu/packages/guile-xyz.scm b/gnu/packages/guile-xyz.scm
index 355b23f57e..2d08739287 100644
--- a/gnu/packages/guile-xyz.scm
+++ b/gnu/packages/guile-xyz.scm
@@ -169,14 +169,14 @@ (define-public artanis
(inputs
`(("guile" ,guile-3.0)
("nspr" ,nspr)
- ("nss" ,nss)))
+ ("nss" ,nss)
+ ("guile-json" ,guile-json-3)))
;; FIXME the bundled csv contains one more exported procedure
;; (sxml->csv-string) than guile-csv. The author is maintainer of both
;; projects.
;; TODO: Add guile-dbi and guile-dbd optional dependencies.
(propagated-inputs
- `(("guile-json" ,guile-json-3)
- ("guile-readline" ,guile-readline)
+ `(("guile-readline" ,guile-readline)
("guile-redis" ,guile-redis)))
(native-inputs
`(("bash" ,bash) ;for the `source' builtin
@@ -4870,4 +4870,4 @@ (define-public guile-netlink
It provides a generic library for writing implementations of a netlink
protocol, a low-level rtnetlink implementation that uses that library and a
high-level API for network management that uses rtnetlink.")
- (license license:gpl3+)))
+ (license license:gpl3+)))
--
2.32.0
L
L
Leo Famulari wrote on 26 Oct 2021 10:46
(name . Blake Shaw)(address . blake@nonconstructivism.com)(address . 51415@debbugs.gnu.org)
YXg++2hgOfTHsSxG@jasmine.lan
On Tue, Oct 26, 2021 at 07:46:02PM +0700, Blake Shaw via Guix-patches via wrote:
Toggle quote (6 lines)
> In the Artanis package the propagated input of guile-json is
> conflicting with guix, and no series of guix upgrades or guix installs
> seems to fix this. Therefore, I moved guile-json from a propagated
> input to an input, which solves the issue, but may not be ideal for
> people who don't wish to keep multiple copies of guile-json

Thanks for the report... can you share the warnings or error messages
that you are seeing?

It's likely that guile-json is propagated for a good reason, and that
not propagating it would cause problems for artanis users. Maybe there
is another way to solve the problem that you're experiencing.
L
L
Ludovic Courtès wrote on 8 Nov 2021 13:08
Re: bug#51415: [PATCH] In the Artanis package the propagated input of guile-json is conflicting with guix, and no series of guix upgrades or guix installs seems to fix this. Therefore, I moved guile-json from a propagated input to an input, which solves the issue, but may not be ideal for people who don't wish to keep multiple copies of guile-json
(name . Leo Famulari)(address . leo@famulari.name)
87sfw6nyn6.fsf_-_@gnu.org
Hi,

Leo Famulari <leo@famulari.name> skribis:

Toggle quote (10 lines)
> On Tue, Oct 26, 2021 at 07:46:02PM +0700, Blake Shaw via Guix-patches via wrote:
>> In the Artanis package the propagated input of guile-json is
>> conflicting with guix, and no series of guix upgrades or guix installs
>> seems to fix this. Therefore, I moved guile-json from a propagated
>> input to an input, which solves the issue, but may not be ideal for
>> people who don't wish to keep multiple copies of guile-json
>
> Thanks for the report... can you share the warnings or error messages
> that you are seeing?

I think the problem Blake describes is this:

Toggle snippet (13 lines)
$ guix install artanis guix -p /tmp/test
La jenaj pakoj estos instalataj:
artanis 0.5
guix 1.3.0-11.014f1b6

guix install: error: profile contains conflicting entries for guile-json
guix install: error: first entry: guile-json@4.5.2 /gnu/store/lxbvzmdcv82ik37z4np3c45p11iic7qx-guile-json-4.5.2
guix install: error: ... propagated from guix@1.3.0-11.014f1b6
guix install: error: second entry: guile-json@3.5.0 /gnu/store/6s765nvcy77cla92wxzwhakglzlpv362-guile-json-3.5.0
guix install: error: ... propagated from artanis@0.5
hint: Try upgrading both `guix' and `artanis', or remove one of them from the profile.

Removing Guix from that profile solves the problem:

Toggle snippet (12 lines)
$ guix install artanis -p /tmp/test
La jena pako estos instalata:
artanis 0.5

La jena derivaĵo estos konstruata:
/gnu/store/jgd870rpvgxjqnlbsnlqya0libg1107v-profile.drv

building profile with 1 package...

[...]

Toggle quote (4 lines)
> It's likely that guile-json is propagated for a good reason, and that
> not propagating it would cause problems for artanis users. Maybe there
> is another way to solve the problem that you're experiencing.

Yeah, though it seems that the ‘wrap-art’ phase already does the right
thing.

Blake, could you confirm that Artanis is still usable after this change,
even when guile-json is not around in GUILE_LOAD_PATH?

Thanks,
Ludo’.
M
M
Maxim Cournoyer wrote on 3 Jan 2023 14:34
(name . Blake Shaw)(address . blake@nonconstructivism.com)
87mt6zxn6s.fsf_-_@gmail.com
Hello Blake,

[...]

Toggle quote (3 lines)
> Blake, could you confirm that Artanis is still usable after this change,
> even when guile-json is not around in GUILE_LOAD_PATH?

Friendly ping, regarding the above question from Ludovic.

--
Thanks,
Maxim
M
M
Maxim Cournoyer wrote on 3 Jan 2023 14:34
control message for bug #51415
(address . control@debbugs.gnu.org)
87lemjxn6l.fsf@gmail.com
tags 51415 + moreinfo
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 51415@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 51415
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch