On Friday, November 24, 2023 2:57:33 AM MST Norwid Behrnd wrote:
> 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
>
> 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?
I am likely not the best person to answer this question as I have minimal experience uploading to backports, but when I recently did so for electrum I used bookworm-backports and it went through without issue.
https://tracker.debian.org/media/packages/e/electrum/changelog-4.4.6dfsg-1bpo121
https://tracker.debian.org/pkg/electrum
My understanding is that Lintian is not programmed to understand backports, and you can usually safely ignore any Lintain warnings specific to backported versions as long as the corresponding versions in testing are Lintian clean.
--
Soren Stoutner
soren@stoutner.com
Attachment:
signature.asc
Description: This is a digitally signed message part.