On Sun, Jan 08, 2017 at 11:42:31AM -0800, Russ Allbery wrote: > We probably should just make a 1.1 standard with various other proposed > fixes
Yes. > but in the meantime, I propose the attached patch as a stopgap > for the next release. This just documents that either URI is valid and > both refer to the same format. > > It's not strictly correct to do this as a revision of the 1.0 standard, > but since it's backwards-compatible, I don't think it should pose any > practical problems. Please do it, I second this. > +<programlisting>Format: > https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/</programlisting> > + </para> > + <para> > + The original version of this specification used the non-https > + version of this URL as its URI, namely: > <programlisting>Format: > http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/</programlisting> > + Both versions are valid and refer to the same specification, and > + parsers should interpret both as referencing the same format. The > + https URI is preferred due to Debian's general move towards using > + https for all project URLs. I'd not say "Debian's general move towards using https for all projet URLs", because it's hardly a Debian thing that plain text http is bad, and I don't think a specification format is the place to explain it. IMHO just drop that whole sentece; saying that both values are allowed is already enough, no need to explain further. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
