Comment 18 for bug 1877792

Okay, thanks for the explanation! Normally these kind of cosmetic bugs are not really SRU material by themselves - the SRU policy is quite strict about what kind of fixes are to be backported to stable series. That being said, we can look into special circumstances like this one here.

With both the packages being in main and never before getting any SRU updates, I think we can do a one-off SRU for such a low priority bug. I think it's important for users to have confidence in our packages, and if such warnings make them switch from our official repositories to pip, I think our LTSes would merit from such a fix.