GNU bug report logs -
#41118
[PATCH] gnu: inkscape: Update to 1.0.
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 41118 in the body.
You can then email your comments to 41118 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Thu, 07 May 2020 03: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
guix-patches <at> gnu.org
.
(Thu, 07 May 2020 03:24:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello!
The following updates Inkscape to its 1.0 version. The test suite is
enabled and an effort is made to unbundle as much of 3rd party libraries
as possible (but more can be done, if you'd like to help: see the
comments in the patch).
The last patch of the series (Add libdepixelize) is added as a WIP, and
is included as a curiosity only (not intended to be merged in its
current state).
Enjoy!
Maxim
[0001-gnu-libsoup-Add-the-missing-PHP-dependency.patch (text/x-patch, attachment)]
[0002-gnu-Add-libsoup-minimal.patch (text/x-patch, attachment)]
[0003-gnu-Add-at-spi2-atk-minimal.patch (text/x-patch, attachment)]
[0004-gnu-at-spi2-atk-Use-at-spi2-core-minimal-to-break-a-.patch (text/x-patch, attachment)]
[0005-gnu-Add-gdl.patch (text/x-patch, attachment)]
[0006-gnu-Add-gdl-minimal.patch (text/x-patch, attachment)]
[0007-gnu-Add-lib2geom.patch (text/x-patch, attachment)]
[0008-gnu-plotutils-Build-libplotter.patch (text/x-patch, attachment)]
[0009-gnu-Add-pstoedit.patch (text/x-patch, attachment)]
[0010-gnu-Add-autotrace.patch (text/x-patch, attachment)]
[0011-gnu-Add-drm-tools.patch (text/x-patch, attachment)]
[0012-gnu-Add-libuemf.patch (text/x-patch, attachment)]
[0013-gnu-inkscape-Update-to-1.0.patch (text/x-patch, attachment)]
[0014-gnu-WIP-Add-libdepixelize.patch (text/x-patch, attachment)]
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Thu, 07 May 2020 04:39:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 41118 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi again,
Here's a v2 for the Inkscape 1.0 patch. It adds a couple optional
dependencies that are nice to have. Thanks to Nicolò Balzarotti who
shared another Inkscape 1.0 patch on guix-devel.
Maxim
[0013_V2-gnu-inkscape-Update-to-1.0.patch (text/x-patch, attachment)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Thu, 07 May 2020 15:21:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 41118 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Wed, May 06, 2020 at 11:23:10PM -0400, Maxim Cournoyer wrote:
> The following updates Inkscape to its 1.0 version. The test suite is
> enabled and an effort is made to unbundle as much of 3rd party libraries
> as possible (but more can be done, if you'd like to help: see the
> comments in the patch).
>
> The last patch of the series (Add libdepixelize) is added as a WIP, and
> is included as a curiosity only (not intended to be merged in its
> current state).
Thanks!
Too bad about the licensing issues... it seems like it might be a while
before they are resolved upstream. I think it's not totally correct to
say that the license of lib2geom is effectively GPL3+. Only the
copyright-holders of lib2geom can say that, right? The licenses are
effectively incoherent and I'd say the software is not something we have
the right to distribute :/ I'm no expert, however.
I did notice that Inkscape's COPYING has addressed this issue for a few
years, due to some files from copied GIMP, and reads: "As such, the
complete binaries of Inkscape are currently covered by the terms of GNU
GPL version 3 or later." Given that, I guess we are only waiting on
lib2geom to make a decision?
I saw the bug report on Inkscape's GitLab page [0], but I'm wondering if
there was actually any public discussion upstream, like on a mailing
list?
[0] https://gitlab.com/inkscape/inkscape/-/issues/784
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Thu, 07 May 2020 15:28:01 GMT)
Full text and
rfc822 format available.
Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Wed, May 06, 2020 at 11:23:10PM -0400, Maxim Cournoyer wrote:
> The following updates Inkscape to its 1.0 version. The test suite is
> enabled and an effort is made to unbundle as much of 3rd party libraries
> as possible (but more can be done, if you'd like to help: see the
> comments in the patch).
What commit do these patches apply to? I can't get patch 7 to apply to
either master or core-updates.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Thu, 07 May 2020 15:31:01 GMT)
Full text and
rfc822 format available.
Message #17 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Thu, May 07, 2020 at 11:27:32AM -0400, Leo Famulari wrote:
> What commit do these patches apply to? I can't get patch 7 to apply to
> either master or core-updates.
Sorry, false alarm! I wasn't actually applying them to my core-updates
tree. They do apply on core-udpates.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Fri, 15 May 2020 13:37:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 41118 <at> debbugs.gnu.org (full text, mbox):
Hello Leo!
Leo Famulari <leo <at> famulari.name> writes:
> On Wed, May 06, 2020 at 11:23:10PM -0400, Maxim Cournoyer wrote:
>> The following updates Inkscape to its 1.0 version. The test suite is
>> enabled and an effort is made to unbundle as much of 3rd party libraries
>> as possible (but more can be done, if you'd like to help: see the
>> comments in the patch).
>>
>> The last patch of the series (Add libdepixelize) is added as a WIP, and
>> is included as a curiosity only (not intended to be merged in its
>> current state).
>
> Thanks!
Thanks for having a look.
> Too bad about the licensing issues... it seems like it might be a while
> before they are resolved upstream. I think it's not totally correct to
> say that the license of lib2geom is effectively GPL3+. Only the
> copyright-holders of lib2geom can say that, right? The licenses are
> effectively incoherent and I'd say the software is not something we have
> the right to distribute :/ I'm no expert, however.
You're probably right, that this needs to be sorted upstream first.
> I did notice that Inkscape's COPYING has addressed this issue for a few
> years, due to some files from copied GIMP, and reads: "As such, the
> complete binaries of Inkscape are currently covered by the terms of GNU
> GPL version 3 or later." Given that, I guess we are only waiting on
> lib2geom to make a decision?
Yes, it seems only inertia is preventing a move to GPL v3+ as a whole,
which would be much clearer, but in the meantime, there's at least that
bit of text which means it's safe to distribute Inkscape under the GPL
v3+ license. Thanks for pointing that out to me!
> I saw the bug report on Inkscape's GitLab page [0], but I'm wondering if
> there was actually any public discussion upstream, like on a mailing
> list?
I've searched the mailing lists of both Inkscape and lib2geom, but
haven't found any recent discussion on the licensing topic.
> [0] https://gitlab.com/inkscape/inkscape/-/issues/784
I've attempted to stir up some action in that thread. A comment was
made by one of the Inkscape developer on the matter, directed to another
Inkscape developer:
> If a license change from GPLv2+ to GPLv3+ (of the raw Inkscape code)
> is something you're actually interested in you should probably make a
> comparison of pros and cons of either license (i.e. why would we as a
> project as well as possible re-users profit from upgrading to GPLv3+?
> What would we loose?) and post it to the mailing list. I don't think
> anybody feels particularly strong about keeping GPLv2 in principle,
> but a lot of effort was put in to keep our codebase compatible with it
> in the past, so there's some hesitation to just "throw that away"
> without having good reasons for doing so.
This was made here: https://gitlab.com/inkscape/inkscape/-/issues/784.
If you have a good grasp of the GPL v2 vs GPL v3 merits, perhaps it'd be
useful to them to to post that there. IIRC, I think the big new things
in GPL v3 were immunization to patent attacks (nice to have for
Inkscape) as well as preventing tivoization (this is not so applicable),
and clarifying that linking with GPL code means the whole should be GPL.
I'll re-read the licenses text in detail when I have a chance.
Anyway, if this doesn't move quickly enough, we could reluctantly build
Inkscape with its bundled lib2geom, which is a subset of the full
lib2geom and which doesn't link with GSL (IIRC).
Maxim
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Fri, 15 May 2020 14:44:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 41118 <at> debbugs.gnu.org (full text, mbox):
On Fri, May 15, 2020 at 09:36:13AM -0400, Maxim Cournoyer wrote:
> This was made here: https://gitlab.com/inkscape/inkscape/-/issues/784.
> If you have a good grasp of the GPL v2 vs GPL v3 merits, perhaps it'd be
> useful to them to to post that there. IIRC, I think the big new things
> in GPL v3 were immunization to patent attacks (nice to have for
> Inkscape) as well as preventing tivoization (this is not so applicable),
> and clarifying that linking with GPL code means the whole should be GPL.
> I'll re-read the licenses text in detail when I have a chance.
>
> Anyway, if this doesn't move quickly enough, we could reluctantly build
> Inkscape with its bundled lib2geom, which is a subset of the full
> lib2geom and which doesn't link with GSL (IIRC).
In <https://gitlab.com/inkscape/inkscape/-/issues/784#note_343293612>
they seem to demonstrate a misunderstanding about lib2geom's license.
That commenter thinks that lib2geom is GPL2+, when it's actually
LGPL-2.1 or MPL-1.1.
However, gnu.org says that LGPL-2.1 is compatible with GPL2 and GPL3. So
maybe it's fine; I don't know. I think we should ask FSF for advice
<https://www.fsf.org/licensing>.
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Sat, 16 May 2020 03:54:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 41118 <at> debbugs.gnu.org (full text, mbox):
Hello Leo,
Leo Famulari <leo <at> famulari.name> writes:
> On Fri, May 15, 2020 at 09:36:13AM -0400, Maxim Cournoyer wrote:
>> This was made here: https://gitlab.com/inkscape/inkscape/-/issues/784.
>> If you have a good grasp of the GPL v2 vs GPL v3 merits, perhaps it'd be
>> useful to them to to post that there. IIRC, I think the big new things
>> in GPL v3 were immunization to patent attacks (nice to have for
>> Inkscape) as well as preventing tivoization (this is not so applicable),
>> and clarifying that linking with GPL code means the whole should be GPL.
>> I'll re-read the licenses text in detail when I have a chance.
>>
>> Anyway, if this doesn't move quickly enough, we could reluctantly build
>> Inkscape with its bundled lib2geom, which is a subset of the full
>> lib2geom and which doesn't link with GSL (IIRC).
Actually, this doesn't help with the licensing incompatibility, given
that Inkscape already depends on the GPL v3+ GNU Scientific Library
(GSL) and that the bundled lib2geom sources within Inkscape make use of
GSL. I've pointed that here:
https://gitlab.com/inkscape/inkscape/-/issues/784#note_343667232.
> In <https://gitlab.com/inkscape/inkscape/-/issues/784#note_343293612>
> they seem to demonstrate a misunderstanding about lib2geom's license.
> That commenter thinks that lib2geom is GPL2+, when it's actually
> LGPL-2.1 or MPL-1.1.
I've brought this to their attention, thank you.
> However, gnu.org says that LGPL-2.1 is compatible with GPL2 and GPL3. So
> maybe it's fine; I don't know. I think we should ask FSF for advice
> <https://www.fsf.org/licensing>.
That's a good idea.
Maxim
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Sat, 16 May 2020 11:06:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 41118 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
> Hello Leo,
>
> Leo Famulari <leo <at> famulari.name> writes:
>
>> On Fri, May 15, 2020 at 09:36:13AM -0400, Maxim Cournoyer wrote:
>>> This was made here: https://gitlab.com/inkscape/inkscape/-/issues/784.
>>> If you have a good grasp of the GPL v2 vs GPL v3 merits, perhaps it'd be
>>> useful to them to to post that there. IIRC, I think the big new things
>>> in GPL v3 were immunization to patent attacks (nice to have for
>>> Inkscape) as well as preventing tivoization (this is not so applicable),
>>> and clarifying that linking with GPL code means the whole should be GPL.
>>> I'll re-read the licenses text in detail when I have a chance.
>>>
>>> Anyway, if this doesn't move quickly enough, we could reluctantly build
>>> Inkscape with its bundled lib2geom, which is a subset of the full
>>> lib2geom and which doesn't link with GSL (IIRC).
>
> Actually, this doesn't help with the licensing incompatibility, given
> that Inkscape already depends on the GPL v3+ GNU Scientific Library
> (GSL) and that the bundled lib2geom sources within Inkscape make use of
> GSL. I've pointed that here:
> https://gitlab.com/inkscape/inkscape/-/issues/784#note_343667232.
What exactly is the license incompatibility? As Leo points out,
LGPL2.1+ is compatible with GPL3. Your initial assessment that the
entire works become GPL3+ seems correct to me.
GNU has a handy chart that shows compatibility between the various GNU
licenses: <https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility>.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Sat, 16 May 2020 19:00:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 41118 <at> debbugs.gnu.org (full text, mbox):
Hey Marius!
Marius Bakke <mbakke <at> fastmail.com> writes:
> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
>
>> Hello Leo,
>>
>> Leo Famulari <leo <at> famulari.name> writes:
>>
>>> On Fri, May 15, 2020 at 09:36:13AM -0400, Maxim Cournoyer wrote:
>>>> This was made here: https://gitlab.com/inkscape/inkscape/-/issues/784.
>>>> If you have a good grasp of the GPL v2 vs GPL v3 merits, perhaps it'd be
>>>> useful to them to to post that there. IIRC, I think the big new things
>>>> in GPL v3 were immunization to patent attacks (nice to have for
>>>> Inkscape) as well as preventing tivoization (this is not so applicable),
>>>> and clarifying that linking with GPL code means the whole should be GPL.
>>>> I'll re-read the licenses text in detail when I have a chance.
>>>>
>>>> Anyway, if this doesn't move quickly enough, we could reluctantly build
>>>> Inkscape with its bundled lib2geom, which is a subset of the full
>>>> lib2geom and which doesn't link with GSL (IIRC).
>>
>> Actually, this doesn't help with the licensing incompatibility, given
>> that Inkscape already depends on the GPL v3+ GNU Scientific Library
>> (GSL) and that the bundled lib2geom sources within Inkscape make use of
>> GSL. I've pointed that here:
>> https://gitlab.com/inkscape/inkscape/-/issues/784#note_343667232.
>
> What exactly is the license incompatibility? As Leo points out,
> LGPL2.1+ is compatible with GPL3. Your initial assessment that the
> entire works become GPL3+ seems correct to me.
>
> GNU has a handy chart that shows compatibility between the various GNU
> licenses:
> <https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility>.
This helps! It indeed shows that's it's OK to copy code from a GPLv3+
project (link to) from a LGPL2.1+ code base, as long as the combined
work becomes GPLv3+.
What I wasn't sure, following the remark from Leo, was if this
permission was automatically granted to downstream users, without having
the upstream stating that yes, it indeed is OK to do so.
In retrospect, it would make sense that users are empowered to choose
the combination of their choice, as long as the effective license is
properly stated. I just find it confusing that upstream says 'this is
LGPLv2+', when in reality the combined product is necessarily GPLv3+.
Thanks for tipping in, Marius!
Maxim
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Thu, 28 May 2020 03:36:01 GMT)
Full text and
rfc822 format available.
Message #35 received at 41118 <at> debbugs.gnu.org (full text, mbox):
Hi Leo!
Leo Famulari <leo <at> famulari.name> writes:
> On Thu, May 07, 2020 at 11:27:32AM -0400, Leo Famulari wrote:
>> What commit do these patches apply to? I can't get patch 7 to apply to
>> either master or core-updates.
>
> Sorry, false alarm! I wasn't actually applying them to my core-updates
> tree. They do apply on core-udpates.
Did you have a chance to try this? With the licensing issue resolved
(it's OK to license the combined works as GPLv3+ for both lib2geom and
Inkscape), I'll be looking to merge this while it's still relatively
fresh :-).
I'll leave it another week, then merge it to staging if no one objects.
Maxim
Information forwarded
to
guix-patches <at> gnu.org
:
bug#41118
; Package
guix-patches
.
(Thu, 28 May 2020 13:40:01 GMT)
Full text and
rfc822 format available.
Message #38 received at 41118 <at> debbugs.gnu.org (full text, mbox):
On Wed, May 27, 2020 at 11:34:56PM -0400, Maxim Cournoyer wrote:
> Did you have a chance to try this? With the licensing issue resolved
> (it's OK to license the combined works as GPLv3+ for both lib2geom and
> Inkscape), I'll be looking to merge this while it's still relatively
> fresh :-).
No, I didn't try it... if it works for you, I'm sure it's okay. I'd
check for post-release major bugs before pushing since it's probably
been well-tested in other distros.
Reply sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
You have taken responsibility.
(Mon, 01 Jun 2020 03:15:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
bug acknowledged by developer.
(Mon, 01 Jun 2020 03:15:02 GMT)
Full text and
rfc822 format available.
Message #43 received at 41118-done <at> debbugs.gnu.org (full text, mbox):
Leo Famulari <leo <at> famulari.name> writes:
> On Wed, May 27, 2020 at 11:34:56PM -0400, Maxim Cournoyer wrote:
>> Did you have a chance to try this? With the licensing issue resolved
>> (it's OK to license the combined works as GPLv3+ for both lib2geom and
>> Inkscape), I'll be looking to merge this while it's still relatively
>> fresh :-).
>
> No, I didn't try it... if it works for you, I'm sure it's okay. I'd
> check for post-release major bugs before pushing since it's probably
> been well-tested in other distros.
I've made some edits to simplify the wording of some comments, made sure
to not cause a rebuild of many packages, and pushed to master (staging
is currently frozen) as a second inkscape-1.0 package.
Thank you, I'm closing this.
Maxim
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 29 Jun 2020 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 355 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.