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.

a7xpg

0.11.dfsg1-10 0.11.dfsg1-10

abiword

3.0.2-9 3.0.2-9

abyss

2.1.5-7 2.2.3-1

accerciser

3.34.0-1 3.34.1-2

accountsservice

0.6.45-2 0.6.55-1

adacontrol

1.20r7-3 1.21r3-3

adlibtracker2

- 2.4.24-1

aegisub

3.2.2+dfsg-4 3.2.2+dfsg-5

akonadi4

1.13.0-12 -

alfred

2018.2-1 2018.2-1

almanah

0.11.1-2 0.11.1-5

alsa-lib

1.1.8-1 1.1.8-2

altree

1.3.1-7 1.3.1-7

amanda

1:3.5.1-2 1:3.5.1-2

amule

1:2.3.2-5 1:2.3.2-6

android-file-transfer

- 3.9+dfsg-1

android-platform-frameworks-data-binding

2.2.2-3 -

android-platform-tools-analytics-library

2.2.2-2 -

android-platform-tools-base

2.2.2-3 -

aoflagger

2.13.0-1 2.14.0-2

apertium

3.5.2-1 3.5.2-1

apitrace

7.1+git20170623.d38a69d6+repack-3 8.0+repack-2

apngasm

2.7-2 2.91-1

apt

1.8.2 1.8.4

aptitude

0.8.11-7 0.8.12-1

aqsis

1.8.2-11 1.8.2-11

aria2

1.34.0-4 1.35.0-1

armadillo

1:9.600.5+dfsg-1 1:9.800.1+dfsg-1

asl

0.1.7-2 0.1.7-2

assimp

4.1.0~dfsg-5 4.1.0~dfsg-7

atitvout

- 0.4-13

atk1.0

2.34.0-1 2.34.1-1

atril

1.20.3-1 1.22.2-1

at-spi2-atk

2.30.0-5 2.34.1-1

at-spi2-core

2.30.0-7 2.34.0-3

attica

0.4.2-2 -

attr

1:2.4.48-4 1:2.4.48-5

audiocd-kio

4:17.08.3-1 4:19.08.2-1

augustus

3.3.2+dfsg-2 3.3.3+dfsg-2

authres

1.2.0-1 1.2.0-2

automoc

1.0~version-0.9.88-5 -

balboa

1.0-3 2.0.0+ds-3

baloo-kf5

5.54.0-1 5.62.0-2

baloo-widgets

4:18.08.1-1 4:19.08.1-1

bambootracker

0.1.5-1 0.2.4-1

baresip

0.6.1-1 0.6.1-1

barnowl

1.10-1 1.10-1

base-installer

1.190 1.191

beagle

5.1-190824+dfsg-2 5.1-190921+dfsg-1

bedops

2.4.35+dfsg-1 2.4.36+dfsg-2