package-plan on bookworm
Hello, I try to test the current package plan on bookworm but I end up with this error
Creating fake global package db
Testing packages in 1 different groups
Running cabal-install (group default)...
Cabal install failed:
Warning: the --global flag is deprecated -- it is generally considered a bad
idea to install packages into the global store
cabal: Could not resolve dependencies:
[__0] next goal: Agda (user goal)
[__0] rejecting: Agda-2.6.4.3, Agda-2.6.4.1, Agda-2.6.4 (constraint from
command line flag requires ==2.6.3)
[__0] trying: Agda-2.6.3
[__1] trying: base-4.15.1.0/installed-4.15.1.0 (dependency of Agda)
[__2] next goal: dbus (user goal)
[__2] rejecting: dbus-1.3.6, dbus-1.3.5, dbus-1.3.4, dbus-1.3.3, dbus-1.3.2,
dbus-1.3.1, dbus-1.3.0 (constraint from command line flag requires ==1.2.29)
[__2] rejecting: dbus-1.2.29 (conflict: base==4.15.1.0/installed-4.15.1.0,
dbus => base>=4.16 && <5)
[__2] skipping: dbus-1.2.28, dbus-1.2.27, dbus-1.2.26, dbus-1.2.25,
dbus-1.2.24 (has the same characteristics that caused the previous version to
fail: excludes 'base' version 4.15.1.0)
[__2] rejecting: dbus-1.2.23, dbus-1.2.22, dbus-1.2.21, dbus-1.2.19,
dbus-1.2.18, dbus-1.2.17, dbus-1.2.16, dbus-1.2.15.1, dbus-1.2.14,
dbus-1.2.13, dbus-1.2.12, dbus-1.2.11, dbus-1.2.10, dbus-1.2.9, dbus-1.2.8,
dbus-1.2.7, dbus-1.2.6, dbus-1.2.5, dbus-1.2.4, dbus-1.2.3, dbus-1.2.2,
dbus-1.2.1, dbus-1.1.1, dbus-1.1.0, dbus-1.0.1, dbus-1.0.0, dbus-0.10.15,
dbus-0.10.14, dbus-0.10.13, dbus-0.10.12, dbus-0.10.11, dbus-0.10.10,
dbus-0.10.9.2, dbus-0.10.9.1, dbus-0.10.9, dbus-0.10.8, dbus-0.10.7,
dbus-0.10.6, dbus-0.10.5, dbus-0.10.4, dbus-0.10.3, dbus-0.10.2, dbus-0.10.1,
dbus-0.10 (constraint from command line flag requires ==1.2.29)
[__2] fail (backjumping, conflict set: base, dbus)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: base, dbus, Agda
Use of uninitialized value $_[0] in join or string at /usr/share/perl5/File/Slurp.pm line 321.
29 error(s) in total.
The salsa-CI seems to be happy with the current package plan.
https://salsa.debian.org/haskell-team/package-plan/-/pipelines/699313
So my question is it mendatory to prepare package only on unstable .
thanks
Fred
Reply to: