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.
acorn
5.5.3+ds3-3 6.2.1+ds+~cs11.24.3-1
adlibtracker2
- 2.4.24-1
altermime
0.3.10-10 0.3.10-11
android-platform-build
1:8.1.0+r23-2 1:8.1.0+r23-3.1
apertium
3.6.1-1 3.6.1-1
apertium-isl-eng
- 0.1.0~r66083-3
apertium-lex-tools
0.2.3-1 0.2.3-1
apertium-mk-bg
- 0.2.0~r49489-3
apriltag
0.10.0-6 0.10.0-6
aspell-ta
20040424-1-1 20040424-1-2.1
assimp
5.0.1~ds0-1 5.0.1~ds0-2
astrometry.net
0.78+dfsg-3 0.78+dfsg-3
atitvout
- 0.4-13
atropos
1.1.24+dfsg-1 1.1.24+dfsg-1
augur
- 6.4.2-2
autoproject
0.20-11 0.20-12
avogadrolibs
1.93.0-3 1.93.0-3
beagle
5.1-191125+dfsg-1 5.1-200324+dfsg-1
billiard
3.6.1.0-1 3.6.3.0-1
biosig4c++
- 1.9.5-1
bitstruct
3.7.0-2 8.9.0-1
blackbox
0.70.1-37 0.70.1-38
blender
2.81.a+dfsg-5 2.82.a+dfsg-1
blueman
2.1.2-1 2.1.2-1
borgbackup
1.1.10-2 1.1.11-5
btrfs-progs
5.4.1-2 5.4.1-2
budgie-extras
0.94.0-1 1.0.0-1
bzr
- 2.7.0+bzr6622+brz
caffe
1.0.0+git20180821.99bd997-5 1.0.0+git20180821.99bd997-5
ceph
14.2.7-1 14.2.8-2
certmonger
0.79.6-2 0.79.9-1
cftime
1.1.0+ds-1 1.1.1.2+ds-1
cg3
1.3.1-2 1.3.1-2
chake
0.20-1 0.21.1-1
chemps2
1.8.9-1 1.8.9-1
cloud-init
20.1-1 20.1-2
codemirror-js
5.52.0-1 5.52.0-2
conda-package-handling
1.6.0-2 1.6.0-2
continuity
- 0.0~git20200107.26c1120-1
cross-toolchain-base
44 45
cross-toolchain-base-mipsen
2 10
cross-toolchain-base-ports
36 37
csound
1:6.13.0~dfsg-3 1:6.13.0~dfsg-3
cwiid
0.6.00+svn201-4 0.6.00+svn201-5
datalad
0.12.2-2 0.12.4-2
ddskk
16.3-1 16.3-2
debian-cloud-images
0.0.1 0.0.3
debian-keyring
2020.02.02 2020.03.24
deja-dup
40.5-1 40.6-1
digitools
- 1.03-1.2