Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1270959 > unrolled thread
| Started by | Soren Stoutner <soren@debian.org> |
|---|---|
| First post | 2025-11-20 18:10 +0100 |
| Last post | 2025-11-20 20:20 +0100 |
| Articles | 2 — 1 participant |
Back to article view | Back to linux.debian.bugs.dist
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#1121060: version of dependency on ruby-selenium-webdriver has to be adjusted Soren Stoutner <soren@debian.org> - 2025-11-20 18:10 +0100
Bug#1121060: version of dependency on ruby-selenium-webdriver has to be adjusted Soren Stoutner <soren@debian.org> - 2025-11-20 20:20 +0100
| From | Soren Stoutner <soren@debian.org> |
|---|---|
| Date | 2025-11-20 18:10 +0100 |
| Subject | Bug#1121060: version of dependency on ruby-selenium-webdriver has to be adjusted |
| Message-ID | <LTgkp-eqoi-7@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Control: retitle -1 Missing upper-limit constraints in debain/control. On Thursday, November 20, 2025 3:34:47 AM Mountain Standard Time Jörg-Volker Peetz wrote: > Package: redmine > Version: 6.0.6+ds-3 > Severity: normal > > Dear Soren, dear Debian Ruby Team, > > the upgrade to this version fails since the version of > ruby-selenium-webdriver redmine depends on, has to be adopted. The error > message reads > > Could not find compatible versions > > Because every version of selenium-webdriver depends on rubyzip >= 1.2.2, < 3.0 > and Gemfile depends on rubyzip ~> 3.2.2, > selenium-webdriver cannot be used. > So, because Gemfile depends on selenium-webdriver >= 4.4.0, > version solving has failed. > > The version of ruby-selenium-webdriver has to be adjusted in "Depends" > and the Gemfile of redmine. I don’t think that is the core of the problem. The current version of selenium-webdriver is 4.38.0, which is satisfied by the >= 4.4.0 constraint. Rather, I think the cause of the problem is that redmine is caught up in the auto-upperlimit-ruby-zip transition, but doesn’t know about it. https://release.debian.org/transitions/html/auto-upperlimit-ruby-zip.html I think I am going to place upper-limit constraints in debian control to match those in the Gemfile, which should allow Debian to add redmine to the list of these types of transitions. That won’t fix the problem immediately, but it will fix it in the future once the version with the upper-limit constraints has migrated to testing. -- Soren Stoutner soren@debian.org
[toc] | [next] | [standalone]
| From | Soren Stoutner <soren@debian.org> |
|---|---|
| Date | 2025-11-20 20:20 +0100 |
| Message-ID | <LTimd-erGq-1@gated-at.bofh.it> |
| In reply to | #1270959 |
[Multipart message — attachments visible in raw view] — view raw
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 soren@debian.org
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web