all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>,  47479-done@debbugs.gnu.org
Subject: bug#47479: inkscape retains a reference to imagemagick, even though it is in native-inputs
Date: Sun, 21 Jan 2024 23:07:18 -0500	[thread overview]
Message-ID: <87cytu6mfd.fsf_-_@gmail.com> (raw)
In-Reply-To: <handler.47479.D47479.170588611628229.notifdone@debbugs.gnu.org> (GNU bug Tracking System's message of "Mon, 22 Jan 2024 01:16:02 +0000")

Hello,

[...]

>>> On Tue, Mar 30, 2021 at 04:55:13AM -0400, Mark H Weaver wrote:
>>>> I see now that I'm using an older version, although I would have
>>>> preferred the newer one.  I refer to the variable name 'inkscape' from
>>>> my manifest file, and I expected that to point to the latest stable
>>>> version.  However, it seems that one must use the 'inkscape-1.0'
>>>> variable to get the latest stable version.  That's seems suboptimal.
>>>> 
>>>> I wonder if the 'inkscape' variable should be renamed 'inkscape/stable'
>>>> (for use in packages such as 'dblatex/stable'), and then 'inkscape'
>>>> could be repurposed to point to the latest stable version.  Thoughts?
>>>
>>> I think we should do this, or even remove the old Inkscape package now.
>>>
>>> I'm guessing the reason for keeping the older release series is that
>>> the Inkscape save-file format changed?
>>
>> The reason inksape@0.92 is still kept around is becauseInkscape@1
>> doesn't build on ARM (more accurately, one of its dependencies,
>> lib2geom, doesn't).  It's been a while since I looked at the issue, and
>> it seems there may have been some activity in lib2geom upstream to try
>> to address the problem, so we should revisit it.
>
> That's not relevant anymore, but our current inkscape 1.2 depends on
> imagemagick still.  Seeing how it now links directly to it, I've added
> it to inputs as well in commit 552ebc47af and pushed to core-updates.

I've applied some patches from Maxime and refined my understanding of
what this was about; it was not just about retaining a reference to
imagemagick listed from native-inputs, it was about retaining a
reference to imagemagick for the *stable* variant of inkscape/stable,
which meant we couldn't use the imagemagick/stable insecure variant.

Tentatively fixed in b4a6b1ba93844d7373c58237cb0b742352dec954 ("gnu:
inkscape/stable: Build stable variant without imagemagick support.")
which builds on a series from Maxime Devos.  I haven't caught up with
rebuilding core-updates yet to validate it truly works, but we'll see
soon.

Thanks, Maxime!

-- 
Maxim




      parent reply	other threads:[~2024-01-22  4:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 16:33 bug#47479: inkscape retains a reference to imagemagick, even though it is in native-inputs Maxime Devos
2021-03-29 21:16 ` Mark H Weaver
2021-03-30  7:19   ` Efraim Flashner
2021-03-30  8:55     ` Mark H Weaver
2021-03-30 12:02       ` Efraim Flashner
2021-03-30 15:38       ` Leo Famulari
2021-03-30 22:48         ` Mark H Weaver
2021-03-31  5:30           ` Leo Famulari
2021-03-31  7:52             ` Mark H Weaver
2021-04-06 14:15         ` Maxim Cournoyer
2024-01-22  1:15           ` Maxim Cournoyer
     [not found] ` <handler.47479.D47479.170588611628229.notifdone@debbugs.gnu.org>
2024-01-22  4:07   ` Maxim Cournoyer [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cytu6mfd.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=47479-done@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.