Comment 2 for bug 1825448

> please could you assess this against the concerns raised in the thread here

Please correct me if I'm mischaracterizing your argument, but basically you are saying that this update will cause all users to perform a deb download that has no impact on the code they are running.

I'm afraid I don't see the merit of your argument at all, if it is in fact simply about additional end-user downloads. Unless I'm misunderstanding it, that has no impact at all to end-users besides download bandwidth and time; end-users will not have to spend any additional time actually doing anything because of this update.

Compare that to what sru uploaders (and sru approvers) must do each time this package's autopkgtests fail - it wastes extremely valuable time looking at autopkgtest failures, figuring out why they failed, finding this bug (if they don't already know about it) and justifying why the autopkgtest regression should be ignored.

Alternately, this test could be hinted to completely ignore it for all reverse-depends autopkgtest runs, but IMO that's even worse - you're intentionally preventing the reverse-depends autopkgtest run from actually doing its job, of making sure that other package changes don't cause regressions in this package.

Can you explain in more detail why you believe it's better to leave broken autopkgtests broken?