Public bug reported:
Please remove scram 0.16.2-4 (binaries: scram, scram-gui) from stonking-
proposed.
scram was already removed from questing in April 2025 ("Debian #1106620,
ftbfs, no rdeps"). The 0.16.2-4 sync has been stuck in -proposed for 374
days with no binaries on any architecture:
- All builds are in Dependency wait on libxml2.9-dev. That is a Debian-only
compatibility copy of the old libxml2 created because scram does not build with
libxml2 >= 2.14; Ubuntu does not have it (stonking has libxml2 2.15.4). Debian
itself treats this as release-critical: #1116433 "scram: build-depends on
libxml2.9" (serious).
- It also FTBFS with boost 1.90 in Debian: #1129858 (serious).
Reverse dependencies checks:
$ reverse-depends -r stonking src:scram
Package not published in specified release
$ reverse-depends -r stonking -b src:scram
Package not published in specified release
(reverse-depends only looks at the release pocket, where scram is not
published.) Checking the stonking and stonking-proposed Packages/Sources
indexes for all components directly: no package depends, pre-depends or
build-depends on scram or scram-gui. The only reference is science-
engineering (debian-science metapackage), which merely Recommends scram.
It is still available in noble and plucky; this request is only for
stonking-proposed. It can come back through a sync once Debian ports it
to the current libxml2.
** Affects: scram (Ubuntu)
Importance: Undecided
Status: Fix Released
** Tags: remove-candidate
** Tags added: remove-candidate
** Changed in: scram (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2170320
Title:
Remove scram from stonking-proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scram/+bug/2170320/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
