Bug#1131015: mention Files-Excluded/Included-* in copyright-format-1.0.xml

Simon Josefsson <[email protected]> Tue, 17 Mar 2026 15:07:57 +0100
Newsgroups gmane.linux.debian.devel.policy
Message-ID <87a4w6pn0i.fsf__7181.12785122997$1773756597$gmane$org@josefsson.org>
Bill Allombert <[email protected]> writes:

> On Tue, Mar 17, 2026 at 02:31:30PM +0100, Simon Josefsson wrote:
>> Bill Allombert <[email protected]> writes:
>> 
>> >> Although what do you mean packaging tools shouldn't require the use of
>> >> copyright-format?  There is no requirement here, everything is opt-in.
>> >> The patch document these to be optional fields, for those who want to
>> >> use them as they are supported by uscan and mk-origtargz.
>> >
>> > Getting uscan to call mk-origtargz to remove files requires using the new
>> > copyright-format. Otherwise the maintainer need to call mk-origtargz
>> > manually. We should do better.
>> 
>> I'm not sure I follow here.  How?  From a design point of view, having a
>> Files Excluded/Included wildcard list seems like a reasonable approach.
>> And people will need to opt-in to use some mechanism, or do things
>> manually.
>
> mk-origtargz does not process Files-Excluded in debian/copyright if
> debian/copyright is not in the new copyright-format.

Right.  Would you want it to behave in any other way?

If someone dislikes the new copyright-format, they can do things
manually.  Or come up with a new specification how to do things, and try
to gain adoption of that.  There is no direct conflict with any of that
compared to documenting the current approach.

>> Is your concern that the existing fields hi-jack the debian/copyright
>> file, when those fields could have been put in a different file?
>
> Indeed.

Thanks for clarifying.

I see your point, and can sympathize, but I think this is a case where
the current situation is not perfect, but it so widely used and fixing
all those occurances is a lot of work compared to merely document and
accept what is currently used and working.

If there would be some actual substantial GAIN from changing all Files-*
in debian/copyright to using some new format, that is a better argument,
but even then I see no problem to document the current approach.

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

iQNoBAEWCgMQFiEEo8ychwudMQq61M8vUXIrCP5HRaIFAmm5YD0UHHNpbW9uQGpv
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/kdFojqoAP4rugJ7kfrW
YJIpMR7G3DL4DIO6+L9dmLAXb7ODsKVAVQD/YzjG8rI1+SWHdhPGutE2zbSHlHRc
FYf3uhNk2jTTvgQ=
=LXnd
-----END PGP SIGNATURE-----