On 26/03/22 at 23:36 +0100, Tino Didriksen wrote: > This was an expected failure due to new incompatible tool packages, and > same goes for all the other Apertium-related FTBFS. > > How can one prevent such a slew of superfluous automatic bugs from being > filed? Is there a way to mark packages as "will be updated, just waiting > for deps in NEW queue"?
Hi Tino, First, I don't mind filing those bugs. I try to avoid filing useless bugs, but generally, when the number of affected packages is relatively low, investigating the root cause and determining if/where a bug should be filed is quite hard, and it's simpler to stick to the fact that a package fails to build, and file a bug for each package. Note that: - it's easy to identify all bugs there were filed using the BTS usertag - sometimes, the full set of failures is nontrivial to identify from the maintainer's POV, so filing all bugs also has some value to clearly identify the scope. However, if you know that a set of packages FTBFS due to a change in another package, you could document it using a single bug against the breaking package, marking all affected packages as "affects" in the BTS. Lucas
