GNU bug report logs - #61676
package transformations not honored working from a manifest

Previous Next

Package: guix;

Reported by: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Date: Tue, 21 Feb 2023 13:24:02 UTC

Severity: normal

Tags: wontfix

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

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

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#61676; Package guix. (Tue, 21 Feb 2023 13:24:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Maxim Cournoyer <maxim.cournoyer <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 21 Feb 2023 13:24:02 GMT) Full text and rfc822 format available.

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

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: bug-guix <bug-guix <at> gnu.org>
Subject: package transformations not honored working from a manifest
Date: Tue, 21 Feb 2023 08:23:51 -0500
Hi Guix,

I was trying to simplify the Jami packaging tooling using the latest
recursive '--with-source' transformation, like so (in a Makefile):

--8<---------------cut here---------------start------------->8---
define guix-pack-command
guix pack -C xz -f deb -f extras/packaging/gnu-linux/guix/guix-pack-manifest.scm -v3 \
  --with-source=libjami@$(RELEASE_VERSION)=$(RELEASE_TARBALL_FILENAME) \
  --with-patch=libjami=extras/packaging/gnu-linux/guix/patches/jami-disable-integration-tests.patch \
  --with-source=jami@$(RELEASE_VERSION)=$(RELEASE_TARBALL_FILENAME) \
  -S /usr/bin/jami=bin/jami \
  -S /usr/share/applications/jami.desktop=share/applications/jami.desktop \
  -S /usr/share/icons/hicolor/scalable/apps/jami.svg=share/icons/hicolor/scalable/apps/jami.svg \
  -S /usr/share/icons/hicolor/48x48/apps/jami.png=share/icons/hicolor/48x48/apps/jami.png \
  -S /usr/share/metainfo/jami.appdata.xml=share/metainfo/jami.appdata.xml \
  --postinst-file=extras/packaging/gnu-linux/guix/guix-pack-deb.postinst
endef
--8<---------------cut here---------------end--------------->8---

But noticed that --with-source and --with-patch were not effective for
the jami-with-certs customized package provided by the
guix-pack-manifest.scm manifest.

It seems to me that the rewriting options should be honored on any
packages being manipulated, whether they come from the Guix collection,
a file, a manifest or another means.

-- 
Thanks,
Maxim




Information forwarded to bug-guix <at> gnu.org:
bug#61676; Package guix. (Tue, 21 Feb 2023 22:50:02 GMT) Full text and rfc822 format available.

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 61676 <at> debbugs.gnu.org
Subject: Re: bug#61676: package transformations not honored working from a
 manifest
Date: Tue, 21 Feb 2023 23:49:35 +0100
Hi,

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:

> I was trying to simplify the Jami packaging tooling using the latest
> recursive '--with-source' transformation, like so (in a Makefile):
>
> define guix-pack-command
> guix pack -C xz -f deb -f extras/packaging/gnu-linux/guix/guix-pack-manifest.scm -v3 \
>   --with-source=libjami@$(RELEASE_VERSION)=$(RELEASE_TARBALL_FILENAME) \
>   --with-patch=libjami=extras/packaging/gnu-linux/guix/patches/jami-disable-integration-tests.patch \
>   --with-source=jami@$(RELEASE_VERSION)=$(RELEASE_TARBALL_FILENAME) \
>   -S /usr/bin/jami=bin/jami \
>   -S /usr/share/applications/jami.desktop=share/applications/jami.desktop \
>   -S /usr/share/icons/hicolor/scalable/apps/jami.svg=share/icons/hicolor/scalable/apps/jami.svg \
>   -S /usr/share/icons/hicolor/48x48/apps/jami.png=share/icons/hicolor/48x48/apps/jami.png \
>   -S /usr/share/metainfo/jami.appdata.xml=share/metainfo/jami.appdata.xml \
>   --postinst-file=extras/packaging/gnu-linux/guix/guix-pack-deb.postinst
> endef

Interesting!  :-)

> But noticed that --with-source and --with-patch were not effective for
> the jami-with-certs customized package provided by the
> guix-pack-manifest.scm manifest.

Indeed, that’s expected.

> It seems to me that the rewriting options should be honored on any
> packages being manipulated, whether they come from the Guix collection,
> a file, a manifest or another means.

I’m not convinced; I think manifests should be interpreted literally.

Incidentally, changing that would likely break existing workflows…

Ludo’.




Information forwarded to bug-guix <at> gnu.org:
bug#61676; Package guix. (Wed, 22 Feb 2023 01:22:01 GMT) Full text and rfc822 format available.

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

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 61676 <at> debbugs.gnu.org
Subject: Re: bug#61676: package transformations not honored working from a
 manifest
Date: Tue, 21 Feb 2023 20:20:56 -0500
Hi Ludo!

Ludovic Courtès <ludo <at> gnu.org> writes:

[...]

>> But noticed that --with-source and --with-patch were not effective for
>> the jami-with-certs customized package provided by the
>> guix-pack-manifest.scm manifest.
>
> Indeed, that’s expected.
>
>> It seems to me that the rewriting options should be honored on any
>> packages being manipulated, whether they come from the Guix collection,
>> a file, a manifest or another means.
>
> I’m not convinced; I think manifests should be interpreted literally.

Perhaps I do not have the full picture in my head, but if someone calls
'guix pack -m my-manifest.scm
--with-source=some-package=the-source.tar.gz', it'd seem the
--with-source option pretty useless in this case if it doesn't touch the
manifest's packages graph.  It'd rather it error out with a message
like: "package rewriting options have no effects for manifests",
although I'd rather it was possible.

Is there another alternative for the use case I'm after?  The only other
option available seems to be to extend the GUIX_PACKAGE_PATH with a
module and to use -e '(@@ (my module) jami-with-certs)'; would the
jami-with-certs graph get rewritten then?

I also got bit by #61684, which muddied the waters some more :-)

-- 
Thanks,
Maxim




Information forwarded to bug-guix <at> gnu.org:
bug#61676; Package guix. (Wed, 22 Feb 2023 09:25:01 GMT) Full text and rfc822 format available.

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 61676 <at> debbugs.gnu.org
Subject: Re: bug#61676: package transformations not honored working from a
 manifest
Date: Wed, 22 Feb 2023 10:23:55 +0100
Hello,

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:

> Ludovic Courtès <ludo <at> gnu.org> writes:
>
> [...]
>
>>> But noticed that --with-source and --with-patch were not effective for
>>> the jami-with-certs customized package provided by the
>>> guix-pack-manifest.scm manifest.
>>
>> Indeed, that’s expected.
>>
>>> It seems to me that the rewriting options should be honored on any
>>> packages being manipulated, whether they come from the Guix collection,
>>> a file, a manifest or another means.
>>
>> I’m not convinced; I think manifests should be interpreted literally.
>
> Perhaps I do not have the full picture in my head, but if someone calls
> 'guix pack -m my-manifest.scm
> --with-source=some-package=the-source.tar.gz', it'd seem the
> --with-source option pretty useless in this case if it doesn't touch the
> manifest's packages graph.  It'd rather it error out with a message
> like: "package rewriting options have no effects for manifests",
> although I'd rather it was possible.
>
> Is there another alternative for the use case I'm after?  The only other
> option available seems to be to extend the GUIX_PACKAGE_PATH with a
> module and to use -e '(@@ (my module) jami-with-certs)'; would the
> jami-with-certs graph get rewritten then?

How about using transformations right into your manifest?  Would that
work for you?

There’s a one-to-one mapping from command-line options to
‘options->transformation’ (info "(guix) Defining Package Variants").

Ludo’.




Information forwarded to bug-guix <at> gnu.org:
bug#61676; Package guix. (Wed, 22 Feb 2023 17:53:02 GMT) Full text and rfc822 format available.

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

From: Simon Tournier <zimon.toutoune <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>, Maxim Cournoyer
 <maxim.cournoyer <at> gmail.com>
Cc: 61676 <at> debbugs.gnu.org
Subject: Re: bug#61676: package transformations not honored working from a
 manifest
Date: Wed, 22 Feb 2023 14:53:54 +0100
Hi,

On Wed, 22 Feb 2023 at 10:23, Ludovic Courtès <ludo <at> gnu.org> wrote:

> How about using transformations right into your manifest?  Would that
> work for you?

Maxim reported a related issue [1]:

    bug#61684: can't compose 'with-patch' with 'with-source'

1: <http://issues.guix.gnu.org/msgid/87mt56gac6.fsf <at> gmail.com>

Cheers,
simon




Information forwarded to bug-guix <at> gnu.org:
bug#61676; Package guix. (Wed, 22 Feb 2023 18:37:01 GMT) Full text and rfc822 format available.

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

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Simon Tournier <zimon.toutoune <at> gmail.com>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 61676 <at> debbugs.gnu.org
Subject: Re: bug#61676: package transformations not honored working from a
 manifest
Date: Wed, 22 Feb 2023 13:36:07 -0500
Hi Simon and Ludovic,

Simon Tournier <zimon.toutoune <at> gmail.com> writes:

> Hi,
>
> On Wed, 22 Feb 2023 at 10:23, Ludovic Courtès <ludo <at> gnu.org> wrote:
>
>> How about using transformations right into your manifest?  Would that
>> work for you?
>
> Maxim reported a related issue [1]:
>
>     bug#61684: can't compose 'with-patch' with 'with-source'
>
> 1: <http://issues.guix.gnu.org/msgid/87mt56gac6.fsf <at> gmail.com>

Yes, that's the one impeding what I'd like to do in the manifest I use;
see
https://review.jami.net/c/jami-client-qt/+/23978/2/extras/packaging/gnu-linux/guix/guix-pack-manifest.scm
for some of the issues encountered in an actual use case.

-- 
Thanks,
Maxim




Information forwarded to bug-guix <at> gnu.org:
bug#61676; Package guix. (Wed, 01 Mar 2023 15:54:02 GMT) Full text and rfc822 format available.

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 61676 <at> debbugs.gnu.org
Subject: Re: bug#61676: package transformations not honored working from a
 manifest
Date: Wed, 01 Mar 2023 16:53:00 +0100
Hi,

Ludovic Courtès <ludo <at> gnu.org> skribis:

> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:

[...]

>> It seems to me that the rewriting options should be honored on any
>> packages being manipulated, whether they come from the Guix collection,
>> a file, a manifest or another means.
>
> I’m not convinced; I think manifests should be interpreted literally.
>
> Incidentally, changing that would likely break existing workflows…

Consequently, my inclination would be to close this issue as “wontfix”.

WDYT?

Ludo’.




Reply sent to Maxim Cournoyer <maxim.cournoyer <at> gmail.com>:
You have taken responsibility. (Wed, 01 Mar 2023 17:03:02 GMT) Full text and rfc822 format available.

Notification sent to Maxim Cournoyer <maxim.cournoyer <at> gmail.com>:
bug acknowledged by developer. (Wed, 01 Mar 2023 17:03:02 GMT) Full text and rfc822 format available.

Message #28 received at 61676-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 61676-done <at> debbugs.gnu.org
Subject: Re: bug#61676: package transformations not honored working from a
 manifest
Date: Wed, 01 Mar 2023 12:01:53 -0500
Hi Ludovic,

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hi,
>
> Ludovic Courtès <ludo <at> gnu.org> skribis:
>
>> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
>
> [...]
>
>>> It seems to me that the rewriting options should be honored on any
>>> packages being manipulated, whether they come from the Guix collection,
>>> a file, a manifest or another means.
>>
>> I’m not convinced; I think manifests should be interpreted literally.
>>
>> Incidentally, changing that would likely break existing workflows…
>
> Consequently, my inclination would be to close this issue as “wontfix”.
>
> WDYT?

Sounds reasonable; we can focus our energy on trying to improve #61684 instead.

-- 
Thanks,
Maxim




Added tag(s) wontfix. Request was from Ludovic Courtès <ludo <at> gnu.org> to control <at> debbugs.gnu.org. (Fri, 03 Mar 2023 10:55:02 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Fri, 31 Mar 2023 11:24:10 GMT) Full text and rfc822 format available.

This bug report was last modified 363 days ago.

Previous Next


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