Hi folks,
I'm learning the Debian BTS and control operations, and am trying to
merge three RC bugs that relate to a common cause (#1031293, #1031443,
#1031449).
It seems difficult to get the order of the 'affects' list to match in
each of the bugs, seemingly a requirement for them to merge
succes
On Fri, 17 Feb 2023 at 17:17, Russ Allbery wrote:
> Generally for stuff like this just use forcemerge, which sets the metadata
> of all of the other bugs to match the first one.
Thank you, Russ - forcemerge worked, and the bugs are now merged.
On Tue, 28 Feb 2023 15:51:20 +0100, Patrice wrote:
> I tried using Debian CodeSearch to look for
> other possible wrong cases like those and here is for instance a list
> of candidates to check:
> https://codesearch.debian.net/search?q=%5B12%5D%26%3E%5B12%5D&literal=0
Nice thinking, and good finds
On Wed, 1 Mar 2023 at 15:53, Patrice Duroux wrote:
>
> Great, I will give a look at shellcheck.
Thanks - if it can also detect these problems, then -- after waiting a
little while for any suggestions and confirmation from
debian-lint-maint (cc'd) -- it might be worth filing a bug against
lintian
Package: lintian
Followup-For: Bug #1033294
X-Debbugs-Cc: patrice.dur...@gmail.com, debian-qa@lists.debian.org
As guidance for potential contributors: it looks like the logic for the
existing 'python-module-in-wrong-location' check (mentioned in the mailing list
thread) is here:
https://sources.d
5 matches
Mail list logo
