Re: bug wrangling: strict ordering of 'affects' during merges?

2023-02-17 Thread James Addison
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.

Re: bug wrangling: strict ordering of 'affects' during merges?

2023-02-17 Thread Russ Allbery
James Addison writes: > 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 f

bug wrangling: strict ordering of 'affects' during merges?

2023-02-17 Thread James Addison
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