Excuses for landing-to-byzantium
These packages fail to migrate from the landing suite(s) to the byzantium suite.
Migration issues can happen for many reasons, most commonly a package failed to
build on an architecture, will break other packages in the target suite or depends on packages which need to migrate first.
The details page for each migration will give more information on why a package is not migrating.
adlibtracker2
- 2.4.24-1
airlift-airline
- 0.7-3
allure
0.8.3.0-3 0.9.5.0-1
alt-ergo
2.0.0-6 2.0.0-7
altos
1.9.4-1 1.9.4-2
ampliconnoise
1.29-8 1.29-9
anorack
0.2.4-1 0.2.7-1
ant-contrib
1.0~b3+svn177-11 1.0~b3+svn177-12
apache-curator
- 2.7.1-3
apt
2.1.8 2.1.10
arbtt
- 0.10.2-0.2
arpalert
- 2.0.12-4
autodep8
0.23 0.24
ax25-tools
- 0.0.10-rc5+git20190411+3595f87-3
axc
- 0.3.3-1
ayatana-indicator-messages
0.6.1-1 0.6.2-1
ayatana-indicator-printers
0.1.9-3 0.1.10-1
bandwidthd
- 2.0.1+cvs20090917-12
bash-completion
1:2.10-2 1:2.11-1
bcel
6.4.1-1 6.5.0-1
binutils64
- 1+c3
binutils-bpf
- 2
buildstream
1.4.1-1 1.4.3-0.1
bundlewrap
4.0.0-1 4.1.0-1
cairo-ocaml
1:1.2.0-8 1:1.2.0-8
castxml
0.3.3-3 0.3.4-2
ccextractor
- 0.88+ds1-1
certmonger
- 0.79.11-1
charliecloud
0.9.10-1 0.16-3
coccinelle
1.0.8.deb-2 1.0.8.deb-3
cpphs
1.20.8-3 1.20.9.1-1
cpputest
3.8-7 4.0-2
cross-toolchain-base-mipsen
10 11
ctwm
3.7-4 3.7-5
debconf-kde
1.0.3-3 1.0.3-4
debian-hamradio
0.5 0.7
debian-installer-netboot-images
20190702+deb10u4 20190702+deb10u5
debug-me
- 1.20190926-2
digitools
- 1.03-1.2
dirb
2.22+dfsg-4 2.22+dfsg-5
django-ranged-response
0.2.0-2 0.2.0-4.1
dkimpy
1.0.4-1 1.0.5-1
eclipse-cdt
9.9.0-3 9.9.0-4
entangle
2.0-2 3.0-1
fcitx
1:4.2.9.7-4 1:4.2.9.8-1
fcitx5-material-color
- 0.0~git20200729.321f214-2
fcitx-qt5
1.2.4+git20200609-1 1.2.5-1
fenix-plugins
- 0.0.20070803-8
flatpak
1.8.1-1 1.8.1-2
fnfx
- 0.3-16