ah -- info is there (missed it among numerous) CCs https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736760
citing: 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/ In general I would not mind collecting all the upstream information under debian/upstream/ But it would have made much more sense if e.g. debian/watch should have been renamed into e.g. debian/upstream/origin -- then I would have seen point of uscan using now debian/upstream/signing-key.*. Now such a rename in uscan is IMHO only brings even more confusion among "debian/" files (debian/watch which uses debian/upstream/signing-key.*). On Sat, 22 Feb 2014, Yaroslav Halchenko wrote: > Have I missed the background? > is debian/watch getting renamed to debian/upstream -- where is the > "conflict"? -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140222154807.gg5...@onerussian.com
