Confirmed locally that pinning ruby-concurrent to 1.3.4 in the build chroot leads to a successful build. This workaround was suggested here[0].
The issue does not appear in debian builds[1] probably because at build time the debian archive already had ruby-activesupport version 2:7.2.2.1+dfsg-6. This bug was fixed in 7.1[2]. The questing archive has ruby-activesupport at version 2:6.1.7.3+dfsg-7. The initial build for ruby-activesupport 7.* in debian happened when ruby-concurrent was still at 1.3.4-1~exp1 in the debian archive[3]. Potential solution here seems to be to somehow build rails with ruby- concurrent 1.3.4 from questing/universe, once rails 7.2.2 and associated binary packages are in the archive, rebuild rails with the latest ruby- concurrent in questing-proposed/universe. [0]: https://stackoverflow.com/a/79361034 [1]: https://buildd.debian.org/status/logs.php?pkg=rails&ver=2%3A7.2.2.1%2Bdfsg-7&arch=all&suite=sid [2]: https://github.com/rails/rails/issues/54260#issuecomment-2594962172 [3]: https://buildd.debian.org/status/logs.php?pkg=rails&ver=2%3A7.2.2.1%2Bdfsg-1%7Eexp1&arch=all&suite=experimental ** Bug watch added: github.com/rails/rails/issues #54260 https://github.com/rails/rails/issues/54260 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2112113 Title: [p-m] rails in questing-proposed FTBFS on amd64 due to use of undeclared dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rails/+bug/2112113/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
