Can running the couple of `dch --bpo` and `dpkg-buildpackage -us -uc -sa -D` equally qualify as "good enough" for an upload?
As an experiment with an instance of trixie / currently branch testing, I noticed the default suggestion by `dch --bpo` results the entry of "bookworm-backports" both in the changelog and and the .changes file ```changes Format: 1.8 Date: Fri, 24 Nov 2023 10:32:06 +0100 Source: ruby-mdl Binary: markdownlint ruby-mdl Architecture: source all Version: 0.13.0-4~bpo12+1 Distribution: bookworm-backports Urgency: medium Maintainer: Norwid Behrnd <nbeh...@protonmail.com> Changed-By: Norwid Behrnd <nbeh...@protonmail.com> Description: markdownlint - Markdown lint tool ruby-mdl - Markdown lint tool - transitional dummy package Changes: ruby-mdl (0.13.0-4~bpo12+1) bookworm-backports; urgency=medium . * Rebuild for bookworm-backports. Checksums-Sha1: 71ef3966e20054e76 ... ``` Submission of the new .changes file to a local check by lintian then reports an error ``` $ lintian ruby-mdl_0.13.0-4~bpo12+1_amd64.changes N: E: ruby-mdl changes: bad-distribution-in-changes-file bookworm-backports N: N: You've specified an unknown target distribution for your upload in the N: debian/changelog file. It is possible that you are uploading for a different N: distribution than the one Lintian is checking for. In that case, passing N: --profile $VENDOR may fix this warning. N: N: Note that the distributions non-free and contrib are no longer valid. You'll N: have to use distribution unstable and Section: non-free/xxx or Section: N: contrib/xxx instead. N: N: Please refer to Distribution (Section 5.6.14) in the Debian Policy Manual for N: details. N: N: Visibility: error N: Show-Always: no N: Check: fields/distribution ... ``` On the other hand, your suggested edit to "stable-backports" in the changelog and a subsequent `dpkg-buildpackage -us -uc -sa -D` yielded a .changes file for which lintian did not report this (nor an other) error. Based on this observation, is this approach good enough for a later upload and RFS via mentors.debian.net?
