Bug#904608: Support specifying upstream VCS location in debian/control

To: Sean Whitton <spwhitton@spwhitton.name>, 904608@bugs.debian.org
Cc: Iain Lane <laney@debian.org>
Subject: Bug#904608: Support specifying upstream VCS location in debian/control
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
Date: Tue, 14 Aug 2018 18:29:44 +0100
Message-id: <[🔎] 23411.4488.372625.237829@chiark.greenend.org.uk>
Reply-to: Ian Jackson <ijackson@chiark.greenend.org.uk>, 904608@bugs.debian.org
In-reply-to: <876011ytkd.fsf@silentflame.com>
References: <153253525830.27622.8340367610423650225.reportbug@nightingale> <877eliyffm.fsf@silentflame.com> <20180726012052.GB217613@aiede.svl.corp.google.com> <20180726082156.korxnhhfmwpvq7zi@nightingale> <876011ytkd.fsf@silentflame.com> <153253525830.27622.8340367610423650225.reportbug@nightingale>

Sean Whitton writes ("Bug#904608: Support specifying upstream VCS location in debian/control"):
> No-one needs to do that extra work anytime soon.  Policy lags best
> practices.  The fact that debian/upstream/metadata is already being used
> to store a URI to the upstream repository for a large number of packages
> counts as standardisation, in Debian Policy terms.  You can refer to it
> in tools that you write.

YAML is utterly awful.  The spec is gigantic.  We should not
perpetuate it.

Ian.

Reply to:

Prev by Date: Bug#883950: Next steps on "[GPL-3+]" proposal
Next by Date: Bug#883950: Next steps on "[GPL-3+]" proposal
Previous by thread: Processed: reassign 905930 to developers-reference
Next by thread: Bug#906139: debian-policy: versioned depends on libjs-sphinxdoc unsatisfiable on stretch
Index(es):
- Date
- Thread