This is an automated email from the git hooks/post-receive script. guillem pushed a commit to branch main in repository dpkg.
View the commit online: https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=d69617a242d7e6cb91702832543d3e8f1ea83f2e commit d69617a242d7e6cb91702832543d3e8f1ea83f2e Author: Guillem Jover <[email protected]> AuthorDate: Sat Jan 17 14:54:42 2026 +0100 Dpkg::Source::Package::V2: Print Bug-<Vendor> in patch template instead of vendor specific ones There is no need to list possible vendors, where we are currently not being exhaustive anyway, when we can simply put a template for the field. The vendor code is already filling this field if it finds any match. --- scripts/Dpkg/Source/Package/V2.pm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/scripts/Dpkg/Source/Package/V2.pm b/scripts/Dpkg/Source/Package/V2.pm index 0e5429c3b..f9d90b49b 100644 --- a/scripts/Dpkg/Source/Package/V2.pm +++ b/scripts/Dpkg/Source/Package/V2.pm @@ -722,8 +722,7 @@ are templates for supplementary fields that you might want to add: Origin: (upstream|backport|vendor|other), (<patch-url>|commit:<commit-id>) Bug: <upstream-bugtracker-url> -Bug-Debian: https://bugs.debian.org/<bugnumber> -Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber> +Bug-<Vendor>: <vendor-bugtracker-url> Forwarded: (no|not-needed|<patch-forwarded-url>) Applied-Upstream: <version>, (<commit-url>|commit:<commid-id>) Reviewed-By: <name and email of someone who approved/reviewed the patch> -- Dpkg.Org's dpkg
