Deferring all of these to the next cycle; no syncs before the stonking release.
Nothing in stonking needs the new versions. Every reverse dependency in the release pocket (puppetserver, puppetdb, bidi, the trapperkeeper-* plugins, ring-defaults/headers/ssl/json, metrics, rbac-client, ...) is satisfied by the current trapperkeeper 4.0.2, ring 1.8.2, ring-mock 0.4.0, compojure 1.6.0 and comidi 0.3.2. Their constraints are unversioned or at most >= 3.2.0-2 / >= 1.6.2-4 / >= 0.3.1 / >= 1.5.0. The only packages needing the newer versions are the stuck ones themselves. The version jumps are large (trapperkeeper 4 -> 5, ring 1.8 -> 1.15, ring-mock 0.4 -> 0.6, compojure 1.6 -> 1.7, comidi 0.3 -> 1.1). They sit under the puppetserver/puppetdb stack, which makes them too risky for the day before release. After release, sync ring-clojure 1.15.5-4 (or later), trapperkeeper- clojure 5.0.6-x and comidi-clojure 1.1.4-1. ring-mock and compojure should then build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2170797 Title: Clojure stack stuck in stonking-proposed (slf4j 2.x, typesafe-config rename): needs syncs of newer Debian versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/comidi-clojure/+bug/2170797/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
