On Thursday, November 20, 2025 11:54:00 AM Mountain Standard Time Jörg-Volker Peetz wrote: > I just wanted to add, that also upgrading the ruby-selenium-webdriver package > from 4.4.0-1 to 4.38.0-1 makes redmine here working again. > Maybe redmine needs a lower limit for ruby-selenium-webdriver ?
That is an artifact of the fact that ruby-selenium-webdriver is also part of the auto-upperlimit-ruby-zip transition. To see this, open the following link and click on the “good” checkbox. https://release.debian.org/transitions/html/auto-upperlimit-ruby-zip.html Basically, the older version of ruby-selenium-webdriver is sufficient for redmine, but you cannot install the necessary version of ruby-zip unless you upgrade ruby-selenium-webdriver to a version supported by the current version of ruby-zip. If you are running testing or unstable, apt is smart enough to figure this out automatically. But if you are cherry-picking packages for a stable environment, you will need to handle this yourself. Adding appropriate constraints to debian/control will make redmine appear in future transition trackers for changes like these. It will also prevent it from migrating from unstable to testing in an uninstallable way, which currently it will do in the next two days, because all of the necessary packages can currently only be satisfied in unstable, but Debian doesn’t know that. Note that fixing this in unstable, which I plan to do today, will not prevent the migration, because the version in testing needs these constraints to work. But it will fix the problem for the future. -- Soren Stoutner [email protected]
signature.asc
Description: This is a digitally signed message part.
