Control: reassign -1 python-selenium
Control: affects -1 chromium
Control: severity -1 serious
Hello Francesco,
Am 08.03.25 um 11:07 schrieb Francesco Ballarin:
Hi,
there was a recent upload
[2025-03-06] Accepted chromium 134.0.6998.35-1~deb12u1 (source amd64 all) into
stable-security (Debian FTP Masters) (signed by: Andres Salomon)
to stable-security which upgraded chromium from 133 to 134. Unfortunately, it
seems that such an upgrade has broken python3-selenium, which hasn't been
upgraded in stable since 4.8.3+dfsg-1, March 2023.
I'd say it's more the other way around.
The current version of python3-selenium isn't compatible any more with
the version of Chromium and also with Firefox. So it's not that the
update of the Chromium package has broken your environment.
This can be easy discovered if one is looking into the Debian CI.
https://ci.debian.net/packages/p/python-selenium/stable/amd64/
A solution for now might be to add a breaks/conflicts in Chromium
against the current version of python3-selenium.
I had to add similar solutions like this to Thunderbird in the past.
Paul Gevers from the RT and I had a conversion about such issues a while
ago. The final solution would be for me to remove python3-selenium from
the archive as it's currently broken and unusable, or someone is
stepping up and tries to provide a fixed version of python3-selenium for
bookworm.
I currently don't have time to look into this, therefore the version in
unstable would need to get an update first. Unfortunately Selenium is a
quickly moving target at the moment and for a while. Upstream is moving
some parts and bindings/dependencies to Rust. My knowledge in this
language is very poor to promise anything.
--
Regards
Carsten
