Your message dated Tue, 27 Aug 2013 20:47:11 +0200
with message-id <[email protected]>
and subject line Re: Bug#719701: [PATCH] allow Vcs-Upstream-* tags
has caused the Debian Bug report #719701,
regarding [PATCH] allow Vcs-Upstream-* tags
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
719701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719701
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Severity: wishlist
Tags: patch
Dear maintainer,
the attached patch allows the Vcs-Upstream-* tags:
Just as the existing Vcs-* tags, these point to a version control
repository (and corresponding browser), but for the upstream repository
instead of the Debian packaging repository.
Thanks in advance for merging.
>From 65f237e8f935055b82455c408587687cfc6633f8 Mon Sep 17 00:00:00 2001
From: Michael Stapelberg <[email protected]>
Date: Wed, 14 Aug 2013 14:10:18 +0200
Subject: [PATCH] allow Vcs-Upstream-* tags
Just as the existing Vcs-* tags, these point to a version control
repository (and corresponding browser), but for the upstream repository
instead of the Debian packaging repository.
---
scripts/Dpkg/Control/FieldsCore.pm | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/scripts/Dpkg/Control/FieldsCore.pm b/scripts/Dpkg/Control/FieldsCore.pm
index 44d90d1..ef21dc1 100644
--- a/scripts/Dpkg/Control/FieldsCore.pm
+++ b/scripts/Dpkg/Control/FieldsCore.pm
@@ -315,6 +315,33 @@ our %FIELDS = (
'Vcs-Svn' => {
allowed => ALL_SRC,
},
+ 'Vcs-Upstream-Browser' => {
+ allowed => ALL_SRC,
+ },
+ 'Vcs-Upstream-Arch' => {
+ allowed => ALL_SRC,
+ },
+ 'Vcs-Upstream-Bzr' => {
+ allowed => ALL_SRC,
+ },
+ 'Vcs-Upstream-Cvs' => {
+ allowed => ALL_SRC,
+ },
+ 'Vcs-Upstream-Darcs' => {
+ allowed => ALL_SRC,
+ },
+ 'Vcs-Upstream-Git' => {
+ allowed => ALL_SRC,
+ },
+ 'Vcs-Upstream-Hg' => {
+ allowed => ALL_SRC,
+ },
+ 'Vcs-Upstream-Mtn' => {
+ allowed => ALL_SRC,
+ },
+ 'Vcs-Upstream-Svn' => {
+ allowed => ALL_SRC,
+ },
'Vendor' => {
allowed => CTRL_FILE_VENDOR,
},
--
1.7.10.4
--- End Message ---
--- Begin Message ---
Hi Guillem,
Guillem Jover <[email protected]> writes:
> On Wed, 2013-08-14 at 15:08:16 +0200, Michael Stapelberg wrote:
>> Guillem Jover <[email protected]> writes:
>> > Currently there's already several possible places this information can
>> > be listed, adding yet another one does not help matters. There's also
>> > proposals around to unify upstream information in a single place,
>> > either
>
>> Can you point me to these proposals please?
>
> The information currently could be found in debian/copyright,
> debian/README.source, debian/rules get-orig-source target, the
> proposal to extend the debian/watch file [0] and the draft proposal
> of debian/upstream (DEP12) [1].
>
> [0] <https://lists.debian.org/debian-devel/2009/04/msg00087.html>
> [1] <https://lists.debian.org/debian-project/2013/01/msg00004.html>
>
> Also while looking for these I stumbled over an old proposal for
> exactly this which I had forgotten:
>
> <http://lists.debian.org/debian-devel/2011/04/msg00356.html>
>
> Given the above I'm tempted to just tag this wontfix for now and close
> it as long as there's no consensus on the project about the best place
> to put this. Meanwhile, for experimenting purposes one can always use
> XS- field specifiers.
Agreed, thus closing the relevant bugs. Thanks.
--
Best regards,
Michael
--- End Message ---
