On Sun, Jan 26, 2014 at 04:12:31PM +0100, gregor herrmann wrote: > Since 2.14.1, uscan now uses debian/upstream/signing-key.* for the > upstream signatures. > > This seems to conflict with the debian/upstream file, as decribed in > https://wiki.debian.org/UpstreamMetadata > http://dep.debian.net/deps/dep12/
I think it was an unfortunate choice for DEP-12 to claim the debian/upstream name as a file instead of transitioning from debian/upstream-metadata.yml to debian/upstream/…. I hadn't heard about this file until you mentioned, but I had multiple people make the suggestion of placing the signing key under debian/upstream/ and some suggest that it would be nice to move the watch file there. There are existing source packages, although only 9 from my quick search, using debian/upstream/ already, which may or may not be in conflict with claiming debian/upstream/ as a place to keep “interesting” information about the upstream project. I realize this is a far cry from the ~280 source packages using debian/upstream as a file, however, I think it makes more sense to have debian/upstream/ (directory) rather than debian/upstream (file). That allows for the possibility of placing other content under the namespace instead of solely what fits into the metadata that DEP-12 describes. My inclination is to mark this wontfix and offer some cycles to help transition DEP-12 related stuff to something that's compatible with devscripts' changes. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <james...@debian.org>
signature.asc
Description: Digital signature