Bug#757274: devref: please point upstream to PTS subscription UI when forwarding bugs

"Serafeim (Serafi) Zanikolas" <[email protected]> Sun, 03 May 2026 21:51:56 +0200

Newsgroups	gmane.linux.debian.devel.policy
Message-ID	<DI9AXZQR56V8.1ALD3JSAER99G__29704.8061083601$1777838038$gmane$org@debian.org>

tag 757274 + patch
thanks

hi,

please find attached a patch.

thanks,
serafi

0001-developer-duties-pkgs-point-upstream-to-Debian-packa.patch (text/x-patch, 2.7 KB)

From 8a96e80f5a817023caa335498bbcf08711dbcf8f Mon Sep 17 00:00:00 2001
From: "Serafeim (Serafi) Zanikolas" <[email protected]>
Date: Sun, 3 May 2026 21:34:26 +0200
Subject: [PATCH] developer-duties, pkgs: point upstream to Debian package
 tracker subscriptions. Closes #757274.

---
 source/developer-duties.rst |  4 +++-
 source/pkgs.rst             | 13 +++++++------
 2 files changed, 10 insertions(+), 7 deletions(-)

diff --git a/source/developer-duties.rst b/source/developer-duties.rst
index 5ab0cff..e4c4271 100644
--- a/source/developer-duties.rst
+++ b/source/developer-duties.rst
@@ -90,7 +90,9 @@ with the upstream developers. Debian users will sometimes report bugs
 that are not specific to Debian to our bug tracking system. These bug
 reports should be forwarded to the upstream developers so that they can
 be fixed in a future upstream release. Usually it is best if you can do
-this, but alternatively, you may ask the bug submitter to do it.
+this, but alternatively, you may ask the bug submitter to do it. Ideally, you
+also get upstream to :ref:`subscribe <pkg-subscription>` for Debian Package
+Tracker notifications for their software in Debian.
 
 While it's not your job to fix non-Debian specific bugs, you may freely
 do so if you're able. When you make such fixes, be sure to pass them on
diff --git a/source/pkgs.rst b/source/pkgs.rst
index bd48444..5d7e992 100644
--- a/source/pkgs.rst
+++ b/source/pkgs.rst
@@ -725,12 +725,13 @@ Here's a list of steps that you may follow to handle a bug report:
    not able to fix it yourself, then tag the bug as ``help``. You can
    also ask for help on ``[email protected]`` or
    ``[email protected]``. If it's an upstream problem, you have
-   to forward it to the upstream author. Forwarding a bug is not enough,
-   you have to check at each release if the bug has been fixed or not.
-   If it has, you just close it, otherwise you have to remind the author
-   about it. If you have the required skills you can prepare a patch
-   that fixes the bug and send it to the author at the same time. Make
-   sure to send the patch to the BTS and to tag the bug as ``patch``.
+   to forward it to the upstream author (see also
+   :ref:`<upstream-coordination>`). Forwarding a bug is not enough, you have to
+   check at each release if the bug has been fixed or not. If it has, you just
+   close it, otherwise you have to remind the author about it. If you have the
+   required skills you can prepare a patch that fixes the bug and send it to the
+   author at the same time. Make sure to send the patch to the BTS and to tag
+   the bug as ``patch``.
 
 7. If you have fixed a bug in your local copy, or if a fix has been
    committed to the VCS repository, you may tag the bug as ``pending``
-- 
2.47.3

signature.asc (application/pgp-signature, 833 B)