Re: How to properly handle contradicting licenses in a single file (aclocal.m4)

Simon Josefsson <[email protected]> Wed, 03 Jun 2026 14:20:45 +0200
Newsgroups gmane.linux.debian.devel.legal
Message-ID <[email protected]>
--=-=-=
Content-Type: text/plain

Marc Haber <[email protected]> writes:

> On Wed, Jun 03, 2026 at 01:50:29PM +0200, Santiago Vila wrote:
>>In your example:
>>
>>permissive  +  GPL 2 or later  +  GPL 3 or later  =  GPL 3 or later
>
> Do we have documented which licenses include others? Or do I need to
> have a doctorate in international copyright law to be a Debian
> Developer?

I merged several licenses into one (LGPLv2+, GPLv2+, GPLv3+) into GPLv3+
because upstream licensing for 'globalplatform' was inconsistent, and
was told by DFSG team to not merge things but to provide all upstream
copyright notices and license headers.  Working out the mess (further
complicated by OpenSSL exceptions) is still in progress together with
upstream.  I'm not sure this preference in Debian is documented fully,
and it would be useful to clarify.  For simplicity I have had a desire
to merge a bunch of (L)GPL licensed code simply as GPLv3+ to save time
and reduce complexity, but this doesn't seem permitted.  It is legally
fine, (L)GPL+ code normally allows consumers to upgrade to latest
version and Debian is permitted to use code under a upgraded license.

/Simon

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQNoBAEWCgMQFiEEo8ychwudMQq61M8vUXIrCP5HRaIFAmogHB0UHHNpbW9uQGpv
c2Vmc3Nvbi5vcmfCHCYAmDMEXJLOtBYJKwYBBAHaRw8BAQdACIcrZIvhrxDBkK9f
V+QlTmXxo2naObDuGtw58YaxlOu0JVNpbW9uIEpvc2Vmc3NvbiA8c2ltb25Aam9z
ZWZzc29uLm9yZz6IlgQTFggAPgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgBYh
BLHSvRN1vst4TPT4xNc89jjFPAa+BQJp4fWRBQkOa+rdAAoJENc89jjFPAa+hWIA
/1lQvrJeGlQq50lP6tm99D1zDy7J1tQ3ha4x0Jx7rkFTAP9hpUKuTvm6m1fXyiZV
YZlu2+Id/Dq3CIAZvNF+XEr2BLgzBFySz4EWCSsGAQQB2kcPAQEHQOxTCIOaeXAx
I2hIX4HK9bQTpNVei708oNr1Klm8qCGKiPUEGBYIACYCGwIWIQSx0r0Tdb7LeEz0
+MTXPPY4xTwGvgUCaeCW1wUJDmqLVgCBdiAEGRYIAB0WIQSjzJyHC50xCrrUzy9R
cisI/kdFogUCXJLPgQAKCRBRcisI/kdFoqdMAQCgH45aseZgIrwKOvUOA9QfsmeE
8GZHYNuFHmM9FEQS6AD6A4x5aYvoY6lo98pgtw2HPDhmcCXFItjXCrV4A0GmJA4J
ENc89jjFPAa+s7AA+gIIHpBApDpcDj1sKhzDngmpvwQf0VkHme6s+EG7qSgpAQDe
/XMrU0c0Pa3ji85cMqZhvzJOFI/soe662lzL0QY3Bbg4BFySz2oSCisGAQQBl1UB
BQEBB0AxlRumDW6nZY7A+VCfek9VpEx6PJmdJyYPt3lNHMd6HAMBCAeIfgQYFggA
JgIbDBYhBLHSvRN1vst4TPT4xNc89jjFPAa+BQJp4JbXBQkOaottAAoJENc89jjF
PAa+RNUA/2faQO/nFT06E+MlhlQdo/0chlQXC5TZMPTVvVBFwoLOAP9xLJK0ow5E
jTzYJB4K810AL/Iv6PEOAEgA4cPTHVlbCQAKCRBRcisI/kdFosR2AP9sADwg+5FJ
AgLCBQkztSVHaeUvrRRQSYKn8cnAPHTHawD+JJ6ygUSfu1R6e0BgvaBLa+232rAK
0CL4VJljScqJcQk=
=pESB
-----END PGP SIGNATURE-----
--=-=-=--