BSD-2-Clause with 'in this position and unchanged' addition? libarchive

Simon Josefsson <[email protected]> Wed, 03 Sep 2025 11:56:15 +0200
Newsgroups gmane.linux.debian.devel.legal
Message-ID <[email protected]>
Hi

While working on Tarsnap's that embeds a copy of 'libarchive' I noticed
a discrepency in the BSD-2-Clause boiler plate of libarchive.

Compare https://sources.debian.org/src/libarchive/3.7.4-4/libarchive/archive.h

...
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
...

with

https://sources.debian.org/src/libarchive/3.7.4-4/libarchive/archive_write_disk_private.h

...
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer
 *    in this position and unchanged.
 * 2. Redistributions in binary form must reproduce the above copyright
...

Note the added line with 'in this position and unchanged'.

I don't see this mentioned in debian/copyright which I assume is a
problem that ought to be fixed:

https://sources.debian.org/src/libarchive/3.7.4-4/debian/copyright

The license seems similar in spirit to the BSD-2-Clause-first-lines
license:

https://spdx.org/licenses/BSD-2-Clause-first-lines.html

The only classification of this variant that I can find is this one:

https://scancode-licensedb.aboutcode.org/bsd-unchanged

The FSF, OSI, and SPDX does not appear to recognize/discuss this
variant, or at least I cannot find it on their sites.

Questions:

1) Is the license DFSG-compliant?

2) Must the license text including that sentence be mentioned in
debian/copyright?

3) Is it correct to use a 'BSD-2-Clause' keyword that expanded to a pure
BSD-2-Clause license text (i.e., without the sentence), or must a new
stanza (e.g., 'BSD-2-Clause-unchanged') be used that expands to the
appropriate blurb include the missing sentence?

I'm guessing Yes, Yes, and BSD-2-Clause-unchanged, but that would just
be my opinion.

/Simon
signature.asc (application/pgp-signature, 1.2 KB)
-----BEGIN PGP SIGNATURE-----

iQNoBAEWCAMQFiEEo8ychwudMQq61M8vUXIrCP5HRaIFAmi4EMAUHHNpbW9uQGpv
c2Vmc3Nvbi5vcmfCHCYAmDMEXJLOtBYJKwYBBAHaRw8BAQdACIcrZIvhrxDBkK9f
V+QlTmXxo2naObDuGtw58YaxlOu0JVNpbW9uIEpvc2Vmc3NvbiA8c2ltb25Aam9z
ZWZzc29uLm9yZz6IlgQTFggAPgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgBYh
BLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XQkBQkNZGbwAAoJENc89jjFPAa+BtIA
/iR73CfBurG9y8pASh3cbGOMHpDZfMAtosu6jbpO69GHAP4p7l57d+iVty2VQMsx
+3TCSAvZkpr4P/FuTzZ8JZe8BrgzBFySz4EWCSsGAQQB2kcPAQEHQOxTCIOaeXAx
I2hIX4HK9bQTpNVei708oNr1Klm8qCGKiPUEGBYIACYCGwIWIQSx0r0Tdb7LeEz0
+MTXPPY4xTwGvgUCZ9F0SgUJDWRmSQCBdiAEGRYIAB0WIQSjzJyHC50xCrrUzy9R
cisI/kdFogUCXJLPgQAKCRBRcisI/kdFoqdMAQCgH45aseZgIrwKOvUOA9QfsmeE
8GZHYNuFHmM9FEQS6AD6A4x5aYvoY6lo98pgtw2HPDhmcCXFItjXCrV4A0GmJA4J
ENc89jjFPAa+wUUBAO64fbZek6FPlRK0DrlWsrjCXuLi6PUxyzCAY6lG2nhUAQC6
qobB9mkZlZ0qihy1x4JRtflqFcqqT9n7iUZkCDIiDbg4BFySz2oSCisGAQQBl1UB
BQEBB0AxlRumDW6nZY7A+VCfek9VpEx6PJmdJyYPt3lNHMd6HAMBCAeIfgQYFggA
JgIbDBYhBLHSvRN1vst4TPT4xNc89jjFPAa+BQJn0XTSBQkNZGboAAoJENc89jjF
PAa+0M0BAPPRq73kLnHYNDMniVBOzUdi2XeF32idjEWWfjvyIJUOAP4wZ+ALxIeh
is3Uw2BzGZE6ttXQ2Q+DeCJO3TPpIqaXDAAKCRBRcisI/kdFotcFAQDFTRU+fpcH
kZBZGeeit0xa9QSZ2TH3uZiZLqBL2bHmAQEAyI7ImrfJmLMVt5DcEA12Bk7h1S8F
hQrAx82IR9J/7wY=
=SDGx
-----END PGP SIGNATURE-----