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

adwaita-qt

1.1.1-2 1.1.3-1

android-platform-external-libunwind

8.1.0+r23-3 10.0.0+r36-1

appdirs

1.4.3-2.1 1.4.4-1

ariba

2.14.4+ds-2.1 2.14.5+ds-1

atlas

3.10.3-9 3.10.3-10

atlas-ecmwf

0.20.2-1 0.20.2-2

autodep8

0.22 0.23

azure-cli

2.0.81+ds-5 2.6.0-1

bbswitch

0.8-8 0.8-9

bcache-tools

1.0.8-3 1.0.8-4

billiard

- 3.6.3.0-1

binclock

1.5-8 1.5-9

bind9-libs

1:9.11.18+dfsg-1 1:9.11.19+dfsg-1

binutils64

- 1+c3

bogl

0.1.18-14 0.1.18-15

bzr

- 2.7.0+bzr6622+brz

cataclysm-dda

0.E-2 0.E-1-1

cegui-mk2

- 0.8.7-6

celery

4.4.2-2 4.4.2-5

cellwriter

1.3.6-1 1.3.6-2

cl-anaphora

20180228-1 20190828.git018590d-1

clevis

- 13-2

clickhouse

18.16.1+ds-7 18.16.1+ds-7

cloud-init

20.1-2 20.2-2

cloudsql-proxy

1.13-1 1.17.0-3

clusterssh

4.14-1 4.15-1

codemirror-js

5.52.0-2 5.54.0-1

continuity

- 0.0~git20200107.26c1120-1

copyq

3.11.0-1 3.11.1-1

cppcheck

1.90-4 2.0-2

cruft

0.9.38 0.9.39

cyrus-imapd

3.0.13-5 3.2.0-5

darkradiant

2.7.0-1 2.8.0-1

dbab

1.3.3-2 1.5.01-1

debhelper

13 13.1

debian-edu-artwork

2.11.0.2-1 2.11.0.2-2

designate

1:9.0.0-3 1:10.0.0-3

diffoscope

144 145

digitools

- 1.03-1.2

disorderfs

0.5.9-2 0.5.10-1

dist

1:3.5-236-0.2 1:3.5-236-1

djtools

1.2.7 1.2.8

dnsdist

1.4.0-1 1.4.0-1

docker.io

19.03.7+dfsg1-2 19.03.7+dfsg1-3

duck

0.13 0.13.1

edbrowse

3.7.6-1 3.7.6-2

etbemon

1.3.4-2 1.3.4-3

etherape

0.9.18-3 0.9.19-1

euslisp

9.27+dfsg-3 9.27+dfsg-4