My best guess is there was an update to one of the underlying libraries I did not notice (note that this was on Sid, so frequent updates).
Other option would be that the error only happens if the functionality fails (e.g. Google blocking the request), so the full error trace is shown, meaning that the urllib error is not fatal, and is only shown when the functionality actually fails. I replied to the bug because trying to reproduce it some time after raising it (and retrying now), I get the expected behavior and not the error... On Tue, 3 Mar 2020, 09:32 Raphael Hertzog, <hert...@debian.org> wrote: > On Fri, 28 Feb 2020, Jonas Andradas wrote: > > new updates performed along the day fixed the issue... sorry for > reporting it > > too soon! > > What updates? It seems weird that this issue would fix itself. > > Cheers, > -- > ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org> > ⣾⠁⢠⠒⠀⣿⡁ > ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ > ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS >
