emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#47479: closed (inkscape retains a reference to imagemagick, even tho


From: GNU bug Tracking System
Subject: bug#47479: closed (inkscape retains a reference to imagemagick, even though it is in native-inputs)
Date: Mon, 22 Jan 2024 01:16:02 +0000

Your message dated Sun, 21 Jan 2024 20:15:02 -0500
with message-id <87jzo26ueh.fsf@gmail.com>
and subject line Re: bug#47479: inkscape retains a reference to imagemagick, 
even though it is in native-inputs
has caused the debbugs.gnu.org bug report #47479,
regarding inkscape retains a reference to imagemagick, even though it is in 
native-inputs
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
47479: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47479
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: inkscape retains a reference to imagemagick, even though it is in native-inputs Date: Mon, 29 Mar 2021 18:33:10 +0200 User-agent: Evolution 3.34.2
Hi Guix,

On
$ guix --version
> guix (GNU Guix) 510e24f973a918391d8122fd6ad515c0567bf23e

with
$ guix graph --type=references inkscape

it can be seen inkscape retains the reference to imagemagick,
even though imagemagick is in native-inputs.

Greetings,
Maxime.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- Subject: Re: bug#47479: inkscape retains a reference to imagemagick, even though it is in native-inputs Date: Sun, 21 Jan 2024 20:15:02 -0500 User-agent: Gnus/5.13 (Gnus v5.13)
Hello,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hi Leo et al.,
>
> Leo Famulari <leo@famulari.name> writes:
>
>> 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.

Closing!

-- 
Thanks,
Maxim


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]