Bug#719702: marked as done ([PATCH] Describe Vcs-Upstream-* tags)
Your message dated Tue, 27 Aug 2013 20:47:11 +0200
with message-id <x661ur55u8.fsf@midna.lan>
and subject line Re: Bug#719701: [PATCH] allow Vcs-Upstream-* tags
has caused the Debian Bug report #719702,
regarding [PATCH] Describe 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 owner@bugs.debian.org
immediately.)
--
719702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719702
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: developers-reference
Severity: wishlist
Tags: patch
Dear maintainer,
the attached patch describes the Vcs-Upstream-* tags. See also
http://bugs.debian.org/719701 and
http://bugs.debian.org/719699
Thanks in advance for merging.
Index: best-pkging-practices.dbk
===================================================================
--- best-pkging-practices.dbk (revision 10221)
+++ best-pkging-practices.dbk (working copy)
@@ -412,10 +412,29 @@
</screen>
</section>
+<section id="s6.2.5.3">
+<title>Vcs-Upstream-Browser</title>
+<para>
+Value of this field should be a <literal>http://</literal> URL pointing to a
+web-browsable copy of the upstream Version Control System repository, if
+available.
+</para>
+<para>
+The information is meant to be useful for the final user, willing to browse the
+latest upstream work (e.g. when looking for an upstream fix for a bug).
+</para>
</section>
+<section id="s6.2.5.4">
+<title>Vcs-Upstream-*</title>
+Value of this field should be the same as in <xref linkend="s6.2.5.2"/>, but
+for the upstream repository instead of the Debian packaging.
</section>
+</section>
+
+</section>
+
<section id="bpp-debian-changelog">
<title>Best practices for <filename>debian/changelog</filename></title>
<para>
--- End Message ---
--- Begin Message ---
Hi Guillem,
Guillem Jover <guillem@debian.org> writes:
> On Wed, 2013-08-14 at 15:08:16 +0200, Michael Stapelberg wrote:
>> Guillem Jover <guillem@debian.org> 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 ---
Reply to: