Generated: 2025.09.02 12:03:13 +0000
- -golang-github-flosch-pongo2.v4 (4.0.2-3 to -)
- Migration status for -golang-github-flosch-pongo2.v4 (4.0.2-3 to -): Will attempt migration (Any information below is purely informational)
- Additional info:
- Package not in kali-dev, will try to remove
- -golang-github-golang-protobuf-1-3 (1.3.5-4 to -)
- Migration status for -golang-github-golang-protobuf-1-3 (1.3.5-4 to -): Will attempt migration (Any information below is purely informational)
- Additional info:
- Package not in kali-dev, will try to remove
- -kdelibs4support (5.115.0-3 to -)
- Migration status for -kdelibs4support (5.115.0-3 to -): Will attempt migration (Any information below is purely informational)
- Additional info:
- Package not in kali-dev, will try to remove
- 7zip/armel (25.01+dfsg-2 to 25.01+dfsg-2)
- Migration status for 7zip/armel (25.01+dfsg-2 to 25.01+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- abootimg/armel (0.6-2 to 0.6-2)
- Migration status for abootimg/armel (0.6-2 to 0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- accountsservice/armel (23.13.9-7 to 23.13.9-7)
- Migration status for accountsservice/armel (23.13.9-7 to 23.13.9-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- acl/armel (2.3.2-2 to 2.3.2-2)
- Migration status for acl/armel (2.3.2-2 to 2.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- aesfix/armel (1.0.1-8 to 1.0.1-8)
- Migration status for aesfix/armel (1.0.1-8 to 1.0.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- afflib/armel (3.7.21-1 to 3.7.21-1)
- Migration status for afflib/armel (3.7.21-1 to 3.7.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- aflplusplus/armel (4.21c-5 to 4.21c-5)
- Migration status for aflplusplus/armel (4.21c-5 to 4.21c-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- aioquic/armel (1.2.0-1 to 1.2.0-1)
- Migration status for aioquic/armel (1.2.0-1 to 1.2.0-1): Will attempt migration (Any information below is purely informational)
- aircrack-ng/armel (1:1.7+git20230807.4bf83f1a-2 to 1:1.7+git20230807.4bf83f1a-2)
- Migration status for aircrack-ng/armel (1:1.7+git20230807.4bf83f1a-2 to 1:1.7+git20230807.4bf83f1a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- alsa-lib/armel (1.2.14-1 to 1.2.14-1)
- Migration status for alsa-lib/armel (1.2.14-1 to 1.2.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- alsa-tools/armel (1.2.14-1 to 1.2.14-1)
- Migration status for alsa-tools/armel (1.2.14-1 to 1.2.14-1): Will attempt migration (Any information below is purely informational)
- alsa-utils/armel (1.2.14-1 to 1.2.14-1)
- Migration status for alsa-utils/armel (1.2.14-1 to 1.2.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- android-platform-build/armel (1:10.0.0+r36-1.1 to 1:10.0.0+r36-1.1)
- Migration status for android-platform-build/armel (1:10.0.0+r36-1.1 to 1:10.0.0+r36-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- android-platform-tools/armel (34.0.5-12 to 34.0.5-12)
- Migration status for android-platform-tools/armel (34.0.5-12 to 34.0.5-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- android-sdk-meta/armel (28.0.2+12 to 28.0.2+12)
- Migration status for android-sdk-meta/armel (28.0.2+12 to 28.0.2+12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- anna/armel (1.99 to 1.99)
- Migration status for anna/armel (1.99 to 1.99): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- aom/armel (3.12.1-1 to 3.12.1-1)
- Migration status for aom/armel (3.12.1-1 to 3.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- apache2/armel (2.4.65-3 to 2.4.65-3)
- Migration status for apache2/armel (2.4.65-3 to 2.4.65-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- apparmor/armel (4.1.0-1 to 4.1.0-1)
- Migration status for apparmor/armel (4.1.0-1 to 4.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- apr-util/armel (1.6.3-3 to 1.6.3-3)
- Migration status for apr-util/armel (1.6.3-3 to 1.6.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- apr/armel (1.7.5-1 to 1.7.5-1)
- Migration status for apr/armel (1.7.5-1 to 1.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- argyll/armel (3.3.0+repack-1 to 3.3.0+repack-1)
- Migration status for argyll/armel (3.3.0+repack-1 to 3.3.0+repack-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ark/armel (4:25.04.3-1 to 4:25.04.3-1)
- Migration status for ark/armel (4:25.04.3-1 to 4:25.04.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- armadillo/armel (1:14.2.3+dfsg-1 to 1:14.2.3+dfsg-1)
- Migration status for armadillo/armel (1:14.2.3+dfsg-1 to 1:14.2.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- arp-scan/armel (1.10.0-2 to 1.10.0-2)
- Migration status for arp-scan/armel (1.10.0-2 to 1.10.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- arpack/armel (3.9.1-6 to 3.9.1-6)
- Migration status for arpack/armel (3.9.1-6 to 3.9.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- arpwatch/armel (2.1a15-9 to 2.1a15-9)
- Migration status for arpwatch/armel (2.1a15-9 to 2.1a15-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- assetfinder/armel (0.1.1-1 to 0.1.1-1)
- Migration status for assetfinder/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- astropy-healpix/armel (1.1.2-1 to 1.1.2-1)
- Migration status for astropy-healpix/armel (1.1.2-1 to 1.1.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: astropy-healpix/armel reproject (not considered)
- Invalidated by implicit-dependency
- astropy/armel (7.1.0-2 to 7.1.0-2)
- Migration status for astropy/armel (7.1.0-2 to 7.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- at-spi2-core/armel (2.57.1-1 to 2.57.1-1)
- Migration status for at-spi2-core/armel (2.57.1-1 to 2.57.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- atftp/armel (0.8.0-8 to 0.8.0-8)
- Migration status for atftp/armel (0.8.0-8 to 0.8.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- atril/armel (1.26.2-5 to 1.26.2-5)
- Migration status for atril/armel (1.26.2-5 to 1.26.2-5): Will attempt migration (Any information below is purely informational)
- attr/armel (1:2.5.2-3 to 1:2.5.2-3)
- Migration status for attr/armel (1:2.5.2-3 to 1:2.5.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- autossh/armel (1.4g-1 to 1.4g-1)
- Migration status for autossh/armel (1.4g-1 to 1.4g-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- avahi/armel (0.8-16 to 0.8-16)
- Migration status for avahi/armel (0.8-16 to 0.8-16): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- aws-crt-python/armel (0.24.0+dfsg-1 to 0.24.0+dfsg-1)
- Migration status for aws-crt-python/armel (0.24.0+dfsg-1 to 0.24.0+dfsg-1): Will attempt migration (Any information below is purely informational)
- axel/armel (2.17.14-2 to 2.17.14-2)
- Migration status for axel/armel (2.17.14-2 to 2.17.14-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- base-passwd/armel (3.6.7 to 3.6.7)
- Migration status for base-passwd/armel (3.6.7 to 3.6.7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: base-passwd/armel shadow (not considered)
- Invalidated by implicit-dependency
- bash/armel (5.2.37-2 to 5.2.37-2)
- Migration status for bash/armel (5.2.37-2 to 5.2.37-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bc/armel (1.07.1-4 to 1.07.1-4)
- Migration status for bc/armel (1.07.1-4 to 1.07.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bind9/armel (1:9.20.11-4 to 1:9.20.11-4)
- Migration status for bind9/armel (1:9.20.11-4 to 1:9.20.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- binutils-arm-none-eabi/armel (23 to 23)
- Migration status for binutils-arm-none-eabi/armel (23 to 23): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- binutils-gold/armel (2.44-2 to 2.44-2)
- Migration status for binutils-gold/armel (2.44-2 to 2.44-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing binutils-gold/2.44-2/armel from kali-rolling makes ghc/9.6.6-4/armel uninstallable
- binutils-mingw-w64/armel (12 to 12)
- Migration status for binutils-mingw-w64/armel (12 to 12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bitstruct/armel (8.20.0-2 to 8.20.0-2)
- Migration status for bitstruct/armel (8.20.0-2 to 8.20.0-2): Will attempt migration (Any information below is purely informational)
- bluetooth-data-tools/armel (1.28.2-1 to 1.28.2-1)
- Migration status for bluetooth-data-tools/armel (1.28.2-1 to 1.28.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: bluetooth-data-tools/armel habluetooth (not considered)
- Invalidated by implicit-dependency
- bluez-tools/armel (2.0~20170911.0.7cb788c-4 to 2.0~20170911.0.7cb788c-4)
- Migration status for bluez-tools/armel (2.0~20170911.0.7cb788c-4 to 2.0~20170911.0.7cb788c-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bluez/armel (5.82-1.1 to 5.82-1.1)
- Migration status for bluez/armel (5.82-1.1 to 5.82-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- boost-defaults/armel (1.83.0.2 to 1.83.0.2)
- Migration status for boost-defaults/armel (1.83.0.2 to 1.83.0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- boost1.83/armel (1.83.0-4.2 to 1.83.0-4.2)
- Migration status for boost1.83/armel (1.83.0-4.2 to 1.83.0-4.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- botan/armel (2.19.5+dfsg-4 to 2.19.5+dfsg-4)
- Migration status for botan/armel (2.19.5+dfsg-4 to 2.19.5+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- braa/armel (0.82-7 to 0.82-7)
- Migration status for braa/armel (0.82-7 to 0.82-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- breeze/armel (4:6.3.5-1 to 4:6.3.5-1)
- Migration status for breeze/armel (4:6.3.5-1 to 4:6.3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- brightnessctl/armel (0.5.1-3.1 to 0.5.1-3.1)
- Migration status for brightnessctl/armel (0.5.1-3.1 to 0.5.1-3.1): Will attempt migration (Any information below is purely informational)
- brotli/armel (1.1.0-2 to 1.1.0-2)
- Migration status for brotli/armel (1.1.0-2 to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bruteforce-luks/armel (1.4.0-4 to 1.4.0-4)
- Migration status for bruteforce-luks/armel (1.4.0-4 to 1.4.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bruteforce-salted-openssl/armel (1.4.2-4 to 1.4.2-4)
- Migration status for bruteforce-salted-openssl/armel (1.4.2-4 to 1.4.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bruteforce-wallet/armel (1.5.4-1 to 1.5.4-1)
- Migration status for bruteforce-wallet/armel (1.5.4-1 to 1.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bsd-finger/armel (0.17-17 to 0.17-17)
- Migration status for bsd-finger/armel (0.17-17 to 0.17-17): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bsdmainutils/armel (12.1.8 to 12.1.8)
- Migration status for bsdmainutils/armel (12.1.8 to 12.1.8): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: bsdmainutils/armel stardict (not considered)
- Invalidated by implicit-dependency
- btrfs-progs/armel (6.16-1 to 6.16-1)
- Migration status for btrfs-progs/armel (6.16-1 to 6.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- btscanner/armel (2.1-9 to 2.1-9)
- Migration status for btscanner/armel (2.1-9 to 2.1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bubblewrap/armel (0.11.0-2 to 0.11.0-2)
- Migration status for bubblewrap/armel (0.11.0-2 to 0.11.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- build-essential/armel (12.12 to 12.12)
- Migration status for build-essential/armel (12.12 to 12.12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bully/armel (1.4.00-2 to 1.4.00-2)
- Migration status for bully/armel (1.4.00-2 to 1.4.00-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- busybox/armel (1:1.37.0-6 to 1:1.37.0-6)
- Migration status for busybox/armel (1:1.37.0-6 to 1:1.37.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- buteo-syncfw/armel (0.11.10-1 to 0.11.10-1)
- Migration status for buteo-syncfw/armel (0.11.10-1 to 0.11.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- bzip2/armel (1.0.8-6 to 1.0.8-6)
- Migration status for bzip2/armel (1.0.8-6 to 1.0.8-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- c-blosc/armel (1.21.5+ds-1 to 1.21.5+ds-1)
- Migration status for c-blosc/armel (1.21.5+ds-1 to 1.21.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- (1.11-2 to 1.11-2)
- Migration status for cabextract/armel (1.11-2 to 1.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cadaver/armel (0.26+dfsg-2 to 0.26+dfsg-2)
- Migration status for cadaver/armel (0.26+dfsg-2 to 0.26+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cairo/armel (1.18.4-1 to 1.18.4-1)
- Migration status for cairo/armel (1.18.4-1 to 1.18.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- caja/armel (1.26.4-1 to 1.26.4-1)
- Migration status for caja/armel (1.26.4-1 to 1.26.4-1): Will attempt migration (Any information below is purely informational)
- calamares/armel (3.3.14-3 to 3.3.14-3)
- Migration status for calamares/armel (3.3.14-3 to 3.3.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- callaudiod/armel (0.1.10-1 to 0.1.10-1)
- Migration status for callaudiod/armel (0.1.10-1 to 0.1.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- capstone/armel (5.0.6-1 to 5.0.6-1)
- Migration status for capstone/armel (5.0.6-1 to 5.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- castxml/armel (0.6.11-1 to 0.6.11-1)
- Migration status for castxml/armel (0.6.11-1 to 0.6.11-1): Will attempt migration (Any information below is purely informational)
- ccrypt/armel (1.11-5 to 1.11-5)
- Migration status for ccrypt/armel (1.11-5 to 1.11-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cdebconf/armel (0.280 to 0.280)
- Migration status for cdebconf/armel (0.280 to 0.280): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cfitsio/armel (4.6.2-2 to 4.6.2-2)
- Migration status for cfitsio/armel (4.6.2-2 to 4.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- chatty/armel (0.8.7-2 to 0.8.7-2)
- Migration status for chatty/armel (0.8.7-2 to 0.8.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cherrytree/armel (1.2.0+dfsg-1 to 1.2.0+dfsg-1)
- Migration status for cherrytree/armel (1.2.0+dfsg-1 to 1.2.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- chkrootkit/armel (0.58b-5 to 0.58b-5)
- Migration status for chkrootkit/armel (0.58b-5 to 0.58b-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- chntpw/armel (140201-1.2 to 140201-1.2)
- Migration status for chntpw/armel (140201-1.2 to 140201-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cifs-utils/armel (2:7.4-1 to 2:7.4-1)
- Migration status for cifs-utils/armel (2:7.4-1 to 2:7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cisco7crack/armel (0.0~git20121221.f1c21dd-3 to 0.0~git20121221.f1c21dd-3)
- Migration status for cisco7crack/armel (0.0~git20121221.f1c21dd-3 to 0.0~git20121221.f1c21dd-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- clamav/armel (1.4.3+dfsg-1 to 1.4.3+dfsg-1)
- Migration status for clamav/armel (1.4.3+dfsg-1 to 1.4.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cmark-gfm/armel (0.29.0.gfm.13-4 to 0.29.0.gfm.13-4)
- Migration status for cmark-gfm/armel (0.29.0.gfm.13-4 to 0.29.0.gfm.13-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cmdliner/armel (1.3.0-2 to 1.3.0-2)
- Migration status for cmdliner/armel (1.3.0-2 to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cntlm/armel (0.92.3-1.3 to 0.92.3-1.3)
- Migration status for cntlm/armel (0.92.3-1.3 to 0.92.3-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- coinutils/armel (2.11.12+ds-1 to 2.11.12+ds-1)
- Migration status for coinutils/armel (2.11.12+ds-1 to 2.11.12+ds-1): Will attempt migration (Any information below is purely informational)
- colord/armel (1.4.7-3 to 1.4.7-3)
- Migration status for colord/armel (1.4.7-3 to 1.4.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- compiz/armel (2:0.8.18-8 to 2:0.8.18-8)
- Migration status for compiz/armel (2:0.8.18-8 to 2:0.8.18-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- conky/armel (1.22.2-1 to 1.22.2-1)
- Migration status for conky/armel (1.22.2-1 to 1.22.2-1): Will attempt migration (Any information below is purely informational)
- console-bridge/armel (1.0.1+dfsg2-3 to 1.0.1+dfsg2-3)
- Migration status for console-bridge/armel (1.0.1+dfsg2-3 to 1.0.1+dfsg2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- containerd/armel (1.7.24~ds1-8 to 1.7.24~ds1-8)
- Migration status for containerd/armel (1.7.24~ds1-8 to 1.7.24~ds1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- contourpy/armel (1.3.1-2 to 1.3.1-2)
- Migration status for contourpy/armel (1.3.1-2 to 1.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- coreboot/armel (24.12+dfsg-2 to 24.12+dfsg-2)
- Migration status for coreboot/armel (24.12+dfsg-2 to 24.12+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- coreutils/armel (9.7-3 to 9.7-3)
- Migration status for coreutils/armel (9.7-3 to 9.7-3): Will attempt migration (Any information below is purely informational)
- cosign/armel (2.5.0-2 to 2.5.0-2)
- Migration status for cosign/armel (2.5.0-2 to 2.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cowpatty/armel (4.8-3 to 4.8-3)
- Migration status for cowpatty/armel (4.8-3 to 4.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cpio/armel (2.15+dfsg-2 to 2.15+dfsg-2)
- Migration status for cpio/armel (2.15+dfsg-2 to 2.15+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cppunit/armel (1.15.1-4 to 1.15.1-4)
- Migration status for cppunit/armel (1.15.1-4 to 1.15.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- crack/armel (5.0a-17 to 5.0a-17)
- Migration status for crack/armel (5.0a-17 to 5.0a-17): Will attempt migration (Any information below is purely informational)
- cron/armel (3.0pl1-197 to 3.0pl1-197)
- Migration status for cron/armel (3.0pl1-197 to 3.0pl1-197): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: cron/armel mgetty (not considered)
- Invalidated by implicit-dependency
- crunch/armel (3.6-3 to 3.6-3)
- Migration status for crunch/armel (3.6-3 to 3.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cryptsetup-nuke-password/armel (8 to 8)
- Migration status for cryptsetup-nuke-password/armel (8 to 8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cryptsetup/armel (2:2.8.1-1 to 2:2.8.1-1)
- Migration status for cryptsetup/armel (2:2.8.1-1 to 2:2.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cups-filters/armel (1.28.17-6 to 1.28.17-6)
- Migration status for cups-filters/armel (1.28.17-6 to 1.28.17-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cups/armel (2.4.10-3 to 2.4.10-3)
- Migration status for cups/armel (2.4.10-3 to 2.4.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- curl/armel (8.15.0-1 to 8.15.0-1)
- Migration status for curl/armel (8.15.0-1 to 8.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- curlftpfs/armel (0.9.2-10 to 0.9.2-10)
- Migration status for curlftpfs/armel (0.9.2-10 to 0.9.2-10): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cutecom/armel (0.51.0-1 to 0.51.0-1)
- Migration status for cutecom/armel (0.51.0-1 to 0.51.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- cyrus-sasl2/armel (2.1.28+dfsg1-9 to 2.1.28+dfsg1-9)
- Migration status for cyrus-sasl2/armel (2.1.28+dfsg1-9 to 2.1.28+dfsg1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dash/armel (0.5.12-12 to 0.5.12-12)
- Migration status for dash/armel (0.5.12-12 to 0.5.12-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dav1d/armel (1.5.1-1 to 1.5.1-1)
- Migration status for dav1d/armel (1.5.1-1 to 1.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- db-defaults/armel (5.3.4 to 5.3.4)
- Migration status for db-defaults/armel (5.3.4 to 5.3.4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- db5.3/armel (5.3.28+dfsg2-9 to 5.3.28+dfsg2-9)
- Migration status for db5.3/armel (5.3.28+dfsg2-9 to 5.3.28+dfsg2-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dbus-fast/armel (2.44.1-1 to 2.44.1-1)
- Migration status for dbus-fast/armel (2.44.1-1 to 2.44.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: dbus-fast/armel habluetooth (not considered)
- Invalidated by implicit-dependency
- dbus-python/armel (1.4.0-1 to 1.4.0-1)
- Migration status for dbus-python/armel (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dbus/armel (1.16.2-2 to 1.16.2-2)
- Migration status for dbus/armel (1.16.2-2 to 1.16.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dc3dd/armel (7.3.1-3 to 7.3.1-3)
- Migration status for dc3dd/armel (7.3.1-3 to 7.3.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dcfldd/armel (1.9.3-2 to 1.9.3-2)
- Migration status for dcfldd/armel (1.9.3-2 to 1.9.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dconf/armel (0.40.0-5 to 0.40.0-5)
- Migration status for dconf/armel (0.40.0-5 to 0.40.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dcraw/armel (9.28-8 to 9.28-8)
- Migration status for dcraw/armel (9.28-8 to 9.28-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dctrl-tools/armel (2.24-3 to 2.24-3)
- Migration status for dctrl-tools/armel (2.24-3 to 2.24-3): Will attempt migration (Any information below is purely informational)
- debian-installer-utils/armel (1.155 to 1.155)
- Migration status for debian-installer-utils/armel (1.155 to 1.155): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- debianutils/armel (5.23.2 to 5.23.2)
- Migration status for debianutils/armel (5.23.2 to 5.23.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- desktop-file-utils/armel (0.28-1 to 0.28-1)
- Migration status for desktop-file-utils/armel (0.28-1 to 0.28-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- device-tree-compiler/armel (1.7.2-2 to 1.7.2-2)
- Migration status for device-tree-compiler/armel (1.7.2-2 to 1.7.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dictd/armel (1.13.1+dfsg-1 to 1.13.1+dfsg-1)
- Migration status for dictd/armel (1.13.1+dfsg-1 to 1.13.1+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: dictd/armel stardict (not considered)
- Invalidated by implicit-dependency
- diffutils/armel (1:3.10-4 to 1:3.10-4)
- Migration status for diffutils/armel (1:3.10-4 to 1:3.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dillo/armel (3.0.5-7.1 to 3.0.5-7.1)
- Migration status for dillo/armel (3.0.5-7.1 to 3.0.5-7.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dirb/armel (2.22+dfsg-7 to 2.22+dfsg-7)
- Migration status for dirb/armel (2.22+dfsg-7 to 2.22+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dislocker/armel (0.7.3+git20240607-3 to 0.7.3+git20240607-3)
- Migration status for dislocker/armel (0.7.3+git20240607-3 to 0.7.3+git20240607-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- disorderfs/armel (0.6.0-1 to 0.6.0-1)
- Migration status for disorderfs/armel (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- distorm3/armel (3.5.2b-3 to 3.5.2b-3)
- Migration status for distorm3/armel (3.5.2b-3 to 3.5.2b-3): Will attempt migration (Any information below is purely informational)
- distro-info/armel (1.14 to 1.14)
- Migration status for distro-info/armel (1.14 to 1.14): Will attempt migration (Any information below is purely informational)
- djvulibre/armel (3.5.28-2.2 to 3.5.28-2.2)
- Migration status for djvulibre/armel (3.5.28-2.2 to 3.5.28-2.2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: djvulibre/armel imagemagick (not considered)
- Invalidated by implicit-dependency
- dmitry/armel (1.3a-6 to 1.3a-6)
- Migration status for dmitry/armel (1.3a-6 to 1.3a-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dnsmap/armel (0.36-4 to 0.36-4)
- Migration status for dnsmap/armel (0.36-4 to 0.36-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dnsmasq/armel (2.91-1 to 2.91-1)
- Migration status for dnsmasq/armel (2.91-1 to 2.91-1): Will attempt migration (Any information below is purely informational)
- dnstracer/armel (1.9-8 to 1.9-8)
- Migration status for dnstracer/armel (1.9-8 to 1.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- docker-compose/armel (2.26.1-4 to 2.26.1-4)
- Migration status for docker-compose/armel (2.26.1-4 to 2.26.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- docker.io/armel (26.1.5+dfsg1-9 to 26.1.5+dfsg1-9)
- Migration status for docker.io/armel (26.1.5+dfsg1-9 to 26.1.5+dfsg1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dolphin/armel (4:25.04.3-1 to 4:25.04.3-1)
- Migration status for dolphin/armel (4:25.04.3-1 to 4:25.04.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dos2unix/armel (7.5.2-1 to 7.5.2-1)
- Migration status for dos2unix/armel (7.5.2-1 to 7.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dosfstools/armel (4.2-1.2 to 4.2-1.2)
- Migration status for dosfstools/armel (4.2-1.2 to 4.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dracut/armel (108-3 to 108-3)
- Migration status for dracut/armel (108-3 to 108-3): Will attempt migration (Any information below is purely informational)
- dragon/armel (4:25.04.0-3 to 4:25.04.0-3)
- Migration status for dragon/armel (4:25.04.0-3 to 4:25.04.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- driftnet/armel (1.5.0-0.2 to 1.5.0-0.2)
- Migration status for driftnet/armel (1.5.0-0.2 to 1.5.0-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- drkonqi/armel (6.3.4-1 to 6.3.4-1)
- Migration status for drkonqi/armel (6.3.4-1 to 6.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dssi/armel (1.1.1~dfsg0-7 to 1.1.1~dfsg0-7)
- Migration status for dssi/armel (1.1.1~dfsg0-7 to 1.1.1~dfsg0-7): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: dssi/armel ocaml-dssi (not considered)
- Invalidated by implicit-dependency
- dwarves/armel (1.30-1 to 1.30-1)
- Migration status for dwarves/armel (1.30-1 to 1.30-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- dwz/armel (0.15-1 to 0.15-1)
- Migration status for dwz/armel (0.15-1 to 0.15-1): Will attempt migration (Any information below is purely informational)
- e17/armel (0.27.1-1 to 0.27.1-1)
- Migration status for e17/armel (0.27.1-1 to 0.27.1-1): Will attempt migration (Any information below is purely informational)
- e2fsprogs/armel (1.47.2-3 to 1.47.2-3)
- Migration status for e2fsprogs/armel (1.47.2-3 to 1.47.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ed/armel (1.22.2-1 to 1.22.2-1)
- Migration status for ed/armel (1.22.2-1 to 1.22.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- efl/armel (1.28.1-1 to 1.28.1-1)
- Migration status for efl/armel (1.28.1-1 to 1.28.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- elfutils/armel (0.192-4 to 0.192-4)
- Migration status for elfutils/armel (0.192-4 to 0.192-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- elisa-player/armel (25.04.2-1 to 25.04.2-1)
- Migration status for elisa-player/armel (25.04.2-1 to 25.04.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- endeavour/armel (43.0-5 to 43.0-5)
- Migration status for endeavour/armel (43.0-5 to 43.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- engrampa/armel (1.26.2-5 to 1.26.2-5)
- Migration status for engrampa/armel (1.26.2-5 to 1.26.2-5): Will attempt migration (Any information below is purely informational)
- eom/armel (1.26.1-1 to 1.26.1-1)
- Migration status for eom/armel (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
- epiphany-browser/armel (48.5-2 to 48.5-2)
- Migration status for epiphany-browser/armel (48.5-2 to 48.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- esnacc/armel (1.8.1-5 to 1.8.1-5)
- Migration status for esnacc/armel (1.8.1-5 to 1.8.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- espeak-ng/armel (1.52.0+dfsg-5 to 1.52.0+dfsg-5)
- Migration status for espeak-ng/armel (1.52.0+dfsg-5 to 1.52.0+dfsg-5): Will attempt migration (Any information below is purely informational)
- espeak/armel (1.48.15+dfsg-3 to 1.48.15+dfsg-3)
- Migration status for espeak/armel (1.48.15+dfsg-3 to 1.48.15+dfsg-3): Will attempt migration (Any information below is purely informational)
- ethtool/armel (1:6.15-3 to 1:6.15-3)
- Migration status for ethtool/armel (1:6.15-3 to 1:6.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ettercap/armel (1:0.8.3.1-14 to 1:0.8.3.1-14)
- Migration status for ettercap/armel (1:0.8.3.1-14 to 1:0.8.3.1-14): Will attempt migration (Any information below is purely informational)
- evince/armel (48.1-4 to 48.1-4)
- Migration status for evince/armel (48.1-4 to 48.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- evolution-data-server/armel (3.56.2-3 to 3.56.2-3)
- Migration status for evolution-data-server/armel (3.56.2-3 to 3.56.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- exfatprogs/armel (1.2.9-1 to 1.2.9-1)
- Migration status for exfatprogs/armel (1.2.9-1 to 1.2.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- exif/armel (0.6.22-4 to 0.6.22-4)
- Migration status for exif/armel (0.6.22-4 to 0.6.22-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- exifprobe/armel (2.0.1+git20201230.eee65ff-2 to 2.0.1+git20201230.eee65ff-2)
- Migration status for exifprobe/armel (2.0.1+git20201230.eee65ff-2 to 2.0.1+git20201230.eee65ff-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- exiv2/armel (0.28.5+dfsg-1 to 0.28.5+dfsg-1)
- Migration status for exiv2/armel (0.28.5+dfsg-1 to 0.28.5+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- exo/armel (4.20.0-1 to 4.20.0-1)
- Migration status for exo/armel (4.20.0-1 to 4.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- expat/armel (2.7.1-2 to 2.7.1-2)
- Migration status for expat/armel (2.7.1-2 to 2.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- expect/armel (5.45.4-4 to 5.45.4-4)
- Migration status for expect/armel (5.45.4-4 to 5.45.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ext3grep/armel (0.10.2-6 to 0.10.2-6)
- Migration status for ext3grep/armel (0.10.2-6 to 0.10.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ext4magic/armel (0.3.2-15 to 0.3.2-15)
- Migration status for ext4magic/armel (0.3.2-15 to 0.3.2-15): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- extundelete/armel (0.2.4-3 to 0.2.4-3)
- Migration status for extundelete/armel (0.2.4-3 to 0.2.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- f2fs-tools/armel (1.16.0-1.1 to 1.16.0-1.1)
- Migration status for f2fs-tools/armel (1.16.0-1.1 to 1.16.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- faketime/armel (0.9.10+2024-06-05+gba9ed5b2-0.6 to 0.9.10+2024-06-05+gba9ed5b2-0.6)
- Migration status for faketime/armel (0.9.10+2024-06-05+gba9ed5b2-0.6 to 0.9.10+2024-06-05+gba9ed5b2-0.6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fatcat/armel (1.1.1-3 to 1.1.1-3)
- Migration status for fatcat/armel (1.1.1-3 to 1.1.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fcrackzip/armel (1.0-12 to 1.0-12)
- Migration status for fcrackzip/armel (1.0-12 to 1.0-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- feedbackd/armel (0.8.4-2 to 0.8.4-2)
- Migration status for feedbackd/armel (0.8.4-2 to 0.8.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- festival/armel (1:2.5.0-11 to 1:2.5.0-11)
- Migration status for festival/armel (1:2.5.0-11 to 1:2.5.0-11): Will attempt migration (Any information below is purely informational)
- fftw3/armel (3.3.10-2 to 3.3.10-2)
- Migration status for fftw3/armel (3.3.10-2 to 3.3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ffuf/armel (2.1.0-1 to 2.1.0-1)
- Migration status for ffuf/armel (2.1.0-1 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- figlet/armel (2.2.5-3 to 2.2.5-3)
- Migration status for figlet/armel (2.2.5-3 to 2.2.5-3): Will attempt migration (Any information below is purely informational)
- file/armel (1:5.46-5 to 1:5.46-5)
- Migration status for file/armel (1:5.46-5 to 1:5.46-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- findlib/armel (1.9.8-1 to 1.9.8-1)
- Migration status for findlib/armel (1.9.8-1 to 1.9.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fio/armel (3.39-1 to 3.39-1)
- Migration status for fio/armel (3.39-1 to 3.39-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: fio/armel zfs-linux (not considered)
- Invalidated by implicit-dependency
- flac/armel (1.5.0+ds-2 to 1.5.0+ds-2)
- Migration status for flac/armel (1.5.0+ds-2 to 1.5.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- flameshot/armel (12.1.0+ds-2 to 12.1.0+ds-2)
- Migration status for flameshot/armel (12.1.0+ds-2 to 12.1.0+ds-2): Will attempt migration (Any information below is purely informational)
- flashrom/armel (1.6.0-2 to 1.6.0-2)
- Migration status for flashrom/armel (1.6.0-2 to 1.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- flatpak/armel (1.16.1-2 to 1.16.1-2)
- Migration status for flatpak/armel (1.16.1-2 to 1.16.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- flex/armel (2.6.4-8.2 to 2.6.4-8.2)
- Migration status for flex/armel (2.6.4-8.2 to 2.6.4-8.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fmtlib/armel (10.1.1+ds1-4 to 10.1.1+ds1-4)
- Migration status for fmtlib/armel (10.1.1+ds1-4 to 10.1.1+ds1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fontconfig/armel (2.15.0-2.3 to 2.15.0-2.3)
- Migration status for fontconfig/armel (2.15.0-2.3 to 2.15.0-2.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fonttools/armel (4.57.0-1 to 4.57.0-1)
- Migration status for fonttools/armel (4.57.0-1 to 4.57.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- foremost/armel (1.5.7-11 to 1.5.7-11)
- Migration status for foremost/armel (1.5.7-11 to 1.5.7-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- forensics-colorize/armel (1.1-7 to 1.1-7)
- Migration status for forensics-colorize/armel (1.1-7 to 1.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fortune-mod/armel (1:1.99.1-9 to 1:1.99.1-9)
- Migration status for fortune-mod/armel (1:1.99.1-9 to 1:1.99.1-9): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: fortune-mod/armel stardict (not considered)
- Invalidated by implicit-dependency
- fping/armel (5.1-1 to 5.1-1)
- Migration status for fping/armel (5.1-1 to 5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- freetype/armel (2.13.3+dfsg-1 to 2.13.3+dfsg-1)
- Migration status for freetype/armel (2.13.3+dfsg-1 to 2.13.3+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- freexl/armel (2.0.0-1 to 2.0.0-1)
- Migration status for freexl/armel (2.0.0-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fribidi/armel (1.0.16-1 to 1.0.16-1)
- Migration status for fribidi/armel (1.0.16-1 to 1.0.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- frozenlist/armel (1.7.0-1 to 1.7.0-1)
- Migration status for frozenlist/armel (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fuse3/armel (3.17.4-1 to 3.17.4-1)
- Migration status for fuse3/armel (3.17.4-1 to 3.17.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fwbuilder/armel (5.3.7-8 to 5.3.7-8)
- Migration status for fwbuilder/armel (5.3.7-8 to 5.3.7-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fxload/armel (0.0.20081013-3 to 0.0.20081013-3)
- Migration status for fxload/armel (0.0.20081013-3 to 0.0.20081013-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- fyba/armel (4.1.1-11 to 4.1.1-11)
- Migration status for fyba/armel (4.1.1-11 to 4.1.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- galleta/armel (1.0+20040505-12 to 1.0+20040505-12)
- Migration status for galleta/armel (1.0+20040505-12 to 1.0+20040505-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gawk/armel (1:5.3.2-1 to 1:5.3.2-1)
- Migration status for gawk/armel (1:5.3.2-1 to 1:5.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gcc-12/armel (12.5.0-1 to 12.5.0-1)
- Migration status for gcc-12/armel (12.5.0-1 to 12.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gcc-14/armel (14.3.0-5 to 14.3.0-5)
- Migration status for gcc-14/armel (14.3.0-5 to 14.3.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gcc-arm-none-eabi/armel (15:14.2.rel1-1 to 15:14.2.rel1-1)
- Migration status for gcc-arm-none-eabi/armel (15:14.2.rel1-1 to 15:14.2.rel1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gcc-defaults/armel (1.220 to 1.220)
- Migration status for gcc-defaults/armel (1.220 to 1.220): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gcc-mingw-w64/armel (27 to 27)
- Migration status for gcc-mingw-w64/armel (27 to 27): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gcr/armel (3.41.2-3 to 3.41.2-3)
- Migration status for gcr/armel (3.41.2-3 to 3.41.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gcr4/armel (4.4.0.1-6 to 4.4.0.1-6)
- Migration status for gcr4/armel (4.4.0.1-6 to 4.4.0.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gdal/armel (3.11.3+dfsg-1 to 3.11.3+dfsg-1)
- Migration status for gdal/armel (3.11.3+dfsg-1 to 3.11.3+dfsg-1): Will attempt migration (Any information below is purely informational)
- gdisk/armel (1.0.10-2 to 1.0.10-2)
- Migration status for gdisk/armel (1.0.10-2 to 1.0.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gdk-pixbuf/armel (2.42.12+dfsg-5 to 2.42.12+dfsg-5)
- Migration status for gdk-pixbuf/armel (2.42.12+dfsg-5 to 2.42.12+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- geany/armel (2.1-1 to 2.1-1)
- Migration status for geany/armel (2.1-1 to 2.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: geany/armel geany-plugins (not considered)
- Invalidated by implicit-dependency
- geoclue-2.0/armel (2.7.2-2 to 2.7.2-2)
- Migration status for geoclue-2.0/armel (2.7.2-2 to 2.7.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- geos/armel (3.14.0-1 to 3.14.0-1)
- Migration status for geos/armel (3.14.0-1 to 3.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gettext/armel (0.23.1-2 to 0.23.1-2)
- Migration status for gettext/armel (0.23.1-2 to 0.23.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gfs2-utils/armel (3.6.1-1 to 3.6.1-1)
- Migration status for gfs2-utils/armel (3.6.1-1 to 3.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ghc/armel (9.6.6-4 to 9.6.6-4)
- Migration status for ghc/armel (9.6.6-4 to 9.6.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- giflib/armel (5.2.2-1 to 5.2.2-1)
- Migration status for giflib/armel (5.2.2-1 to 5.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- girara/armel (0.4.5-1 to 0.4.5-1)
- Migration status for girara/armel (0.4.5-1 to 0.4.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- git/armel (1:2.50.1-0.1 to 1:2.50.1-0.1)
- Migration status for git/armel (1:2.50.1-0.1 to 1:2.50.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gitleaks/armel (8.16.0-1 to 8.16.0-1)
- Migration status for gitleaks/armel (8.16.0-1 to 8.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gkrellm/armel (2.3.11-2 to 2.3.11-2)
- Migration status for gkrellm/armel (2.3.11-2 to 2.3.11-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: gkrellm/armel gkrellm-volume (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: gkrellm/armel gkrellm-reminder
- glib2.0/armel (2.84.4-3 to 2.84.4-3)
- Migration status for glib2.0/armel (2.84.4-3 to 2.84.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- glibc/armel (2.41-12 to 2.41-12)
- Migration status for glibc/armel (2.41-12 to 2.41-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-callout/armel (4.3-3 to 4.3-3)
- Migration status for globus-callout/armel (4.3-3 to 4.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-common/armel (18.14-3 to 18.14-3)
- Migration status for globus-common/armel (18.14-3 to 18.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-gsi-callback/armel (6.2-3 to 6.2-3)
- Migration status for globus-gsi-callback/armel (6.2-3 to 6.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-gsi-cert-utils/armel (10.11-2 to 10.11-2)
- Migration status for globus-gsi-cert-utils/armel (10.11-2 to 10.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-gsi-credential/armel (8.4-3 to 8.4-3)
- Migration status for globus-gsi-credential/armel (8.4-3 to 8.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-gsi-openssl-error/armel (4.4-3 to 4.4-3)
- Migration status for globus-gsi-openssl-error/armel (4.4-3 to 4.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-gsi-proxy-core/armel (9.8-3 to 9.8-3)
- Migration status for globus-gsi-proxy-core/armel (9.8-3 to 9.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-gsi-proxy-ssl/armel (6.5-4 to 6.5-4)
- Migration status for globus-gsi-proxy-ssl/armel (6.5-4 to 6.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-gsi-sysconfig/armel (9.6-2 to 9.6-2)
- Migration status for globus-gsi-sysconfig/armel (9.6-2 to 9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-gss-assist/armel (12.7-3 to 12.7-3)
- Migration status for globus-gss-assist/armel (12.7-3 to 12.7-3): Will attempt migration (Any information below is purely informational)
- globus-gssapi-gsi/armel (14.20-3 to 14.20-3)
- Migration status for globus-gssapi-gsi/armel (14.20-3 to 14.20-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- globus-openssl-module/armel (5.2-3 to 5.2-3)
- Migration status for globus-openssl-module/armel (5.2-3 to 5.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- glycin/armel (1.2.1+ds-3 to 1.2.1+ds-3)
- Migration status for glycin/armel (1.2.1+ds-3 to 1.2.1+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing glycin-loaders/1.2.1+ds-3/armel from kali-rolling makes loupe/48.1-3/armel uninstallable
- gmobile/armel (0.4.0-2 to 0.4.0-2)
- Migration status for gmobile/armel (0.4.0-2 to 0.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gmp/armel (2:6.3.0+dfsg-4 to 2:6.3.0+dfsg-4)
- Migration status for gmp/armel (2:6.3.0+dfsg-4 to 2:6.3.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-bluetooth3/armel (47.1-1 to 47.1-1)
- Migration status for gnome-bluetooth3/armel (47.1-1 to 47.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-calculator/armel (1:48.1-2 to 1:48.1-2)
- Migration status for gnome-calculator/armel (1:48.1-2 to 1:48.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-calendar/armel (48.1-2 to 48.1-2)
- Migration status for gnome-calendar/armel (48.1-2 to 48.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-console/armel (48.0.1-2 to 48.0.1-2)
- Migration status for gnome-console/armel (48.0.1-2 to 48.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-control-center/armel (1:48.4-1 to 1:48.4-1)
- Migration status for gnome-control-center/armel (1:48.4-1 to 1:48.4-1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
- Issues preventing migration:
- Not touching package due to block request by kali (please contact kali-release if update is needed)
- gnome-desktop-testing/armel (2021.1-4 to 2021.1-4)
- Migration status for gnome-desktop-testing/armel (2021.1-4 to 2021.1-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gnome-desktop-testing/armel fwupd (not considered)
- Invalidated by implicit-dependency
- gnome-desktop/armel (44.3-4 to 44.3-4)
- Migration status for gnome-desktop/armel (44.3-4 to 44.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-keyring/armel (48.0-3 to 48.0-3)
- Migration status for gnome-keyring/armel (48.0-3 to 48.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-online-accounts/armel (3.54.5-1 to 3.54.5-1)
- Migration status for gnome-online-accounts/armel (3.54.5-1 to 3.54.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-session/armel (48.0-1 to 48.0-1)
- Migration status for gnome-session/armel (48.0-1 to 48.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-settings-daemon/armel (48.1-2 to 48.1-2)
- Migration status for gnome-settings-daemon/armel (48.1-2 to 48.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-snapshot/armel (48.0.1-1 to 48.0.1-1)
- Migration status for gnome-snapshot/armel (48.0.1-1 to 48.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-software/armel (48.4-1 to 48.4-1)
- Migration status for gnome-software/armel (48.4-1 to 48.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-text-editor/armel (48.3-3 to 48.3-3)
- Migration status for gnome-text-editor/armel (48.3-3 to 48.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnome-usage/armel (48~rc-1 to 48~rc-1)
- Migration status for gnome-usage/armel (48~rc-1 to 48~rc-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnupg2/armel (2.4.8-3 to 2.4.8-3)
- Migration status for gnupg2/armel (2.4.8-3 to 2.4.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnuplot/armel (6.0.3+dfsg1-1 to 6.0.3+dfsg1-1)
- Migration status for gnuplot/armel (6.0.3+dfsg1-1 to 6.0.3+dfsg1-1): Will attempt migration (Any information below is purely informational)
- gnuradio/armel (3.10.12.0-1 to 3.10.12.0-1)
- Migration status for gnuradio/armel (3.10.12.0-1 to 3.10.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnustep-base/armel (1.31.1-3 to 1.31.1-3)
- Migration status for gnustep-base/armel (1.31.1-3 to 1.31.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnustep-make/armel (2.9.3-6 to 2.9.3-6)
- Migration status for gnustep-make/armel (2.9.3-6 to 2.9.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gnutls28/armel (3.8.9-3 to 3.8.9-3)
- Migration status for gnutls28/armel (3.8.9-3 to 3.8.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gobject-introspection/armel (1.84.0-1 to 1.84.0-1)
- Migration status for gobject-introspection/armel (1.84.0-1 to 1.84.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gobuster/armel (3.8.0-2 to 3.8.0-2)
- Migration status for gobuster/armel (3.8.0-2 to 3.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- golang-1.24/armel (1.24.4-1 to 1.24.4-1)
- Migration status for golang-1.24/armel (1.24.4-1 to 1.24.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- golang-defaults/armel (2:1.24~2 to 2:1.24~2)
- Migration status for golang-defaults/armel (2:1.24~2 to 2:1.24~2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- googletest/armel (1.16.0-1 to 1.16.0-1)
- Migration status for googletest/armel (1.16.0-1 to 1.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gparted/armel (1.6.0-2 to 1.6.0-2)
- Migration status for gparted/armel (1.6.0-2 to 1.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gpgme1.0/armel (1.24.2-3 to 1.24.2-3)
- Migration status for gpgme1.0/armel (1.24.2-3 to 1.24.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gpicview/armel (0.3.1-1 to 0.3.1-1)
- Migration status for gpicview/armel (0.3.1-1 to 0.3.1-1): Will attempt migration (Any information below is purely informational)
- gpsd/armel (3.25-5 to 3.25-5)
- Migration status for gpsd/armel (3.25-5 to 3.25-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gqrx-sdr/armel (2.17.6-2 to 2.17.6-2)
- Migration status for gqrx-sdr/armel (2.17.6-2 to 2.17.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gr-air-modes/armel (0.0.20210211-3.1 to 0.0.20210211-3.1)
- Migration status for gr-air-modes/armel (0.0.20210211-3.1 to 0.0.20210211-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gr-iqbal/armel (0.38.2-2 to 0.38.2-2)
- Migration status for gr-iqbal/armel (0.38.2-2 to 0.38.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gr-osmosdr/armel (0.2.6-4 to 0.2.6-4)
- Migration status for gr-osmosdr/armel (0.2.6-4 to 0.2.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- graphene/armel (1.10.8-5 to 1.10.8-5)
- Migration status for graphene/armel (1.10.8-5 to 1.10.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- graphite2/armel (1.3.14-3 to 1.3.14-3)
- Migration status for graphite2/armel (1.3.14-3 to 1.3.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- graphviz/armel (2.42.4-3 to 2.42.4-3)
- Migration status for graphviz/armel (2.42.4-3 to 2.42.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- greetd/armel (0.10.3-4 to 0.10.3-4)
- Migration status for greetd/armel (0.10.3-4 to 0.10.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- groff/armel (1.23.0-9 to 1.23.0-9)
- Migration status for groff/armel (1.23.0-9 to 1.23.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gsettings-desktop-schemas/armel (49~beta-1 to 49~beta-1)
- Migration status for gsettings-desktop-schemas/armel (49~beta-1 to 49~beta-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gsocket/armel (1.4.43-4 to 1.4.43-4)
- Migration status for gsocket/armel (1.4.43-4 to 1.4.43-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gst-plugins-base1.0/armel (1.26.5-2 to 1.26.5-2)
- Migration status for gst-plugins-base1.0/armel (1.26.5-2 to 1.26.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gst-python1.0/armel (1.26.5-2 to 1.26.5-2)
- Migration status for gst-python1.0/armel (1.26.5-2 to 1.26.5-2): Will attempt migration (Any information below is purely informational)
- gstreamer1.0/armel (1.26.5-2 to 1.26.5-2)
- Migration status for gstreamer1.0/armel (1.26.5-2 to 1.26.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gtk+2.0/armel (2.24.33-8 to 2.24.33-8)
- Migration status for gtk+2.0/armel (2.24.33-8 to 2.24.33-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gtk2-engines-murrine/armel (0.98.2-4 to 0.98.2-4)
- Migration status for gtk2-engines-murrine/armel (0.98.2-4 to 0.98.2-4): Will attempt migration (Any information below is purely informational)
- gtk4/armel (4.18.6+ds-2 to 4.18.6+ds-2)
- Migration status for gtk4/armel (4.18.6+ds-2 to 4.18.6+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gtkhash/armel (1.5-3 to 1.5-3)
- Migration status for gtkhash/armel (1.5-3 to 1.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gtklp/armel (1.3.4-3 to 1.3.4-3)
- Migration status for gtklp/armel (1.3.4-3 to 1.3.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: gtklp/armel mtpaint (not considered)
- Invalidated by implicit-dependency
- gtksourceview4/armel (4.8.4-7 to 4.8.4-7)
- Migration status for gtksourceview4/armel (4.8.4-7 to 4.8.4-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gtksourceview5/armel (5.16.0-1 to 5.16.0-1)
- Migration status for gtksourceview5/armel (5.16.0-1 to 5.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- guestfs-tools/armel (1.52.3-1 to 1.52.3-1)
- Migration status for guestfs-tools/armel (1.52.3-1 to 1.52.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- guile-3.0/armel (3.0.10+really3.0.10-4 to 3.0.10+really3.0.10-4)
- Migration status for guile-3.0/armel (3.0.10+really3.0.10-4 to 3.0.10+really3.0.10-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gvfs/armel (1.57.2-3 to 1.57.2-3)
- Migration status for gvfs/armel (1.57.2-3 to 1.57.2-3): Will attempt migration (Any information below is purely informational)
- gvmd/armel (26.2.1-1 to 26.2.1-1)
- Migration status for gvmd/armel (26.2.1-1 to 26.2.1-1): Will attempt migration (Any information below is purely informational)
- gwenview/armel (4:25.04.3-1 to 4:25.04.3-1)
- Migration status for gwenview/armel (4:25.04.3-1 to 4:25.04.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- gzip/armel (1.13-1 to 1.13-1)
- Migration status for gzip/armel (1.13-1 to 1.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- harfbuzz/armel (10.2.0-1 to 10.2.0-1)
- Migration status for harfbuzz/armel (10.2.0-1 to 10.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hashdeep/armel (4.4+git20170824+ds-1 to 4.4+git20170824+ds-1)
- Migration status for hashdeep/armel (4.4+git20170824+ds-1 to 4.4+git20170824+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hashrat/armel (1.25+ds-1 to 1.25+ds-1)
- Migration status for hashrat/armel (1.25+ds-1 to 1.25+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-adjunctions/armel (4.4.2-3 to 4.4.2-3)
- Migration status for haskell-adjunctions/armel (4.4.2-3 to 4.4.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-aeson/armel (2.1.2.1-6 to 2.1.2.1-6)
- Migration status for haskell-aeson/armel (2.1.2.1-6 to 2.1.2.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-ansi-terminal-types/armel (0.11.5-3 to 0.11.5-3)
- Migration status for haskell-ansi-terminal-types/armel (0.11.5-3 to 0.11.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-ansi-terminal/armel (1.0.2-1 to 1.0.2-1)
- Migration status for haskell-ansi-terminal/armel (1.0.2-1 to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-appar/armel (0.1.8-5 to 0.1.8-5)
- Migration status for haskell-appar/armel (0.1.8-5 to 0.1.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-asn1-encoding/armel (0.9.6-4 to 0.9.6-4)
- Migration status for haskell-asn1-encoding/armel (0.9.6-4 to 0.9.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-asn1-parse/armel (0.9.5-5 to 0.9.5-5)
- Migration status for haskell-asn1-parse/armel (0.9.5-5 to 0.9.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-asn1-types/armel (0.3.4-4 to 0.3.4-4)
- Migration status for haskell-asn1-types/armel (0.3.4-4 to 0.3.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-assoc/armel (1.1.1-1 to 1.1.1-1)
- Migration status for haskell-assoc/armel (1.1.1-1 to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-async/armel (2.2.5-1 to 2.2.5-1)
- Migration status for haskell-async/armel (2.2.5-1 to 2.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-attoparsec/armel (0.14.4-4 to 0.14.4-4)
- Migration status for haskell-attoparsec/armel (0.14.4-4 to 0.14.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-auto-update/armel (0.1.6-4 to 0.1.6-4)
- Migration status for haskell-auto-update/armel (0.1.6-4 to 0.1.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-base-compat-batteries/armel (0.13.1-1 to 0.13.1-1)
- Migration status for haskell-base-compat-batteries/armel (0.13.1-1 to 0.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-base-compat/armel (0.13.1-1 to 0.13.1-1)
- Migration status for haskell-base-compat/armel (0.13.1-1 to 0.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-base-orphans/armel (0.9.2-1 to 0.9.2-1)
- Migration status for haskell-base-orphans/armel (0.9.2-1 to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-base16-bytestring/armel (1.0.2.0-3 to 1.0.2.0-3)
- Migration status for haskell-base16-bytestring/armel (1.0.2.0-3 to 1.0.2.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-base16-bytestring/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-basement/armel (0.0.16-3 to 0.0.16-3)
- Migration status for haskell-basement/armel (0.0.16-3 to 0.0.16-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-bifunctors/armel (5.6.2-1 to 5.6.2-1)
- Migration status for haskell-bifunctors/armel (5.6.2-1 to 5.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-bitvec/armel (1.1.5.0-4 to 1.1.5.0-4)
- Migration status for haskell-bitvec/armel (1.1.5.0-4 to 1.1.5.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-blaze-builder/armel (0.4.2.3-2 to 0.4.2.3-2)
- Migration status for haskell-blaze-builder/armel (0.4.2.3-2 to 0.4.2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-blaze-html/armel (0.9.2.0-1 to 0.9.2.0-1)
- Migration status for haskell-blaze-html/armel (0.9.2.0-1 to 0.9.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-blaze-markup/armel (0.8.3.0-2 to 0.8.3.0-2)
- Migration status for haskell-blaze-markup/armel (0.8.3.0-2 to 0.8.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-bmp/armel (1.2.6.4-1 to 1.2.6.4-1)
- Migration status for haskell-bmp/armel (1.2.6.4-1 to 1.2.6.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-bmp/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-boring/armel (0.2.2-1 to 0.2.2-1)
- Migration status for haskell-boring/armel (0.2.2-1 to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-bsb-http-chunked/armel (0.0.0.4-6 to 0.0.0.4-6)
- Migration status for haskell-bsb-http-chunked/armel (0.0.0.4-6 to 0.0.0.4-6): Will attempt migration (Any information below is purely informational)
- haskell-byteorder/armel (1.0.4-13 to 1.0.4-13)
- Migration status for haskell-byteorder/armel (1.0.4-13 to 1.0.4-13): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-bytestring-to-vector/armel (0.3.0.1-6 to 0.3.0.1-6)
- Migration status for haskell-bytestring-to-vector/armel (0.3.0.1-6 to 0.3.0.1-6): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-bytestring-to-vector/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: haskell-bytestring-to-vector/armel haskell-futhark-data (not considered)
- haskell-call-stack/armel (0.4.0-3 to 0.4.0-3)
- Migration status for haskell-call-stack/armel (0.4.0-3 to 0.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-case-insensitive/armel (1.2.1.0-5 to 1.2.1.0-5)
- Migration status for haskell-case-insensitive/armel (1.2.1.0-5 to 1.2.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-cereal/armel (0.5.8.3-3 to 0.5.8.3-3)
- Migration status for haskell-cereal/armel (0.5.8.3-3 to 0.5.8.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-cmark-gfm/armel (0.2.6+ds1-1 to 0.2.6+ds1-1)
- Migration status for haskell-cmark-gfm/armel (0.2.6+ds1-1 to 0.2.6+ds1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-cmark-gfm/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-colour/armel (2.3.6-3 to 2.3.6-3)
- Migration status for haskell-colour/armel (2.3.6-3 to 2.3.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-comonad/armel (5.0.8-3 to 5.0.8-3)
- Migration status for haskell-comonad/armel (5.0.8-3 to 5.0.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- (1.3.6-3 to 1.3.6-3)
- Migration status for haskell-conduit-extra/armel (1.3.6-3 to 1.3.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-conduit/armel (1.3.6-1 to 1.3.6-1)
- Migration status for haskell-conduit/armel (1.3.6-1 to 1.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-constraints/armel (0.14.2-1 to 0.14.2-1)
- Migration status for haskell-constraints/armel (0.14.2-1 to 0.14.2-1): Will attempt migration (Any information below is purely informational)
- haskell-contravariant/armel (1.5.5-3 to 1.5.5-3)
- Migration status for haskell-contravariant/armel (1.5.5-3 to 1.5.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-crypto-api/armel (0.13.3-6 to 0.13.3-6)
- Migration status for haskell-crypto-api/armel (0.13.3-6 to 0.13.3-6): Will attempt migration (Any information below is purely informational)
- haskell-cryptohash-md5/armel (0.11.101.0-3 to 0.11.101.0-3)
- Migration status for haskell-cryptohash-md5/armel (0.11.101.0-3 to 0.11.101.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-cryptohash-md5/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-crypton-x509-store/armel (1.6.9-3 to 1.6.9-3)
- Migration status for haskell-crypton-x509-store/armel (1.6.9-3 to 1.6.9-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-crypton-x509-validation/armel (1.6.12-3 to 1.6.12-3)
- Migration status for haskell-crypton-x509-validation/armel (1.6.12-3 to 1.6.12-3): Will attempt migration (Any information below is purely informational)
- haskell-crypton-x509/armel (1.7.7-1 to 1.7.7-1)
- Migration status for haskell-crypton-x509/armel (1.7.7-1 to 1.7.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-crypton/armel (0.34-1 to 0.34-1)
- Migration status for haskell-crypton/armel (0.34-1 to 0.34-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-data-default-class/armel (0.1.2.2-1 to 0.1.2.2-1)
- Migration status for haskell-data-default-class/armel (0.1.2.2-1 to 0.1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-data-default-instances-containers/armel (0.0.1-14 to 0.0.1-14)
- Migration status for haskell-data-default-instances-containers/armel (0.0.1-14 to 0.0.1-14): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-data-default-instances-dlist/armel (0.0.1.2-1 to 0.0.1.2-1)
- Migration status for haskell-data-default-instances-dlist/armel (0.0.1.2-1 to 0.0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-data-default-instances-old-locale/armel (0.0.1.2-1 to 0.0.1.2-1)
- Migration status for haskell-data-default-instances-old-locale/armel (0.0.1.2-1 to 0.0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-data-default/armel (0.7.1.2-1 to 0.7.1.2-1)
- Migration status for haskell-data-default/armel (0.7.1.2-1 to 0.7.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-data-fix/armel (0.3.4-1 to 0.3.4-1)
- Migration status for haskell-data-fix/armel (0.3.4-1 to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-dense-linear-algebra/armel (0.1.0.0-6 to 0.1.0.0-6)
- Migration status for haskell-dense-linear-algebra/armel (0.1.0.0-6 to 0.1.0.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-directory-tree/armel (0.12.1-9 to 0.12.1-9)
- Migration status for haskell-directory-tree/armel (0.12.1-9 to 0.12.1-9): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-directory-tree/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-distributive/armel (0.6.2.1-3 to 0.6.2.1-3)
- Migration status for haskell-distributive/armel (0.6.2.1-3 to 0.6.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-dlist/armel (1.0-4 to 1.0-4)
- Migration status for haskell-dlist/armel (1.0-4 to 1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-dotgen/armel (0.4.3-4 to 0.4.3-4)
- Migration status for haskell-dotgen/armel (0.4.3-4 to 0.4.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-easy-file/armel (0.2.5-2 to 0.2.5-2)
- Migration status for haskell-easy-file/armel (0.2.5-2 to 0.2.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-entropy/armel (0.4.1.10-3 to 0.4.1.10-3)
- Migration status for haskell-entropy/armel (0.4.1.10-3 to 0.4.1.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-exception-mtl/armel (0.4.0.2-2 to 0.4.0.2-2)
- Migration status for haskell-exception-mtl/armel (0.4.0.2-2 to 0.4.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-exception-transformers/armel (0.4.0.12-2 to 0.4.0.12-2)
- Migration status for haskell-exception-transformers/armel (0.4.0.12-2 to 0.4.0.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-fast-logger/armel (3.2.4-1 to 3.2.4-1)
- Migration status for haskell-fast-logger/armel (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
- haskell-fgl-visualize/armel (0.1.0.1-2 to 0.1.0.1-2)
- Migration status for haskell-fgl-visualize/armel (0.1.0.1-2 to 0.1.0.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-fgl-visualize/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-fgl/armel (5.8.3.0-1 to 5.8.3.0-1)
- Migration status for haskell-fgl/armel (5.8.3.0-1 to 5.8.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-file-embed/armel (0.0.16.0-1 to 0.0.16.0-1)
- Migration status for haskell-file-embed/armel (0.0.16.0-1 to 0.0.16.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-file-embed/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-fmlist/armel (0.9.4-3 to 0.9.4-3)
- Migration status for haskell-fmlist/armel (0.9.4-3 to 0.9.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-free/armel (5.2-1 to 5.2-1)
- Migration status for haskell-free/armel (5.2-1 to 5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-futhark-manifest/armel (1.5.0.0-1 to 1.5.0.0-1)
- Migration status for haskell-futhark-manifest/armel (1.5.0.0-1 to 1.5.0.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-futhark-manifest/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-futhark-server/amd64 (1.2.3.0-1 to 1.2.3.0-1)
- Migration status for haskell-futhark-server/amd64 (1.2.3.0-1 to 1.2.3.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-futhark-server/amd64 haskell-futhark (not considered)
- Invalidated by implicit-dependency
- Depends: haskell-futhark-server/amd64 haskell-futhark-data (not considered)
- haskell-futhark-server/arm64 (1.2.3.0-1 to 1.2.3.0-1)
- Migration status for haskell-futhark-server/arm64 (1.2.3.0-1 to 1.2.3.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-futhark-server/arm64 haskell-futhark (not considered)
- Invalidated by implicit-dependency
- Depends: haskell-futhark-server/arm64 haskell-futhark-data (not considered)
- haskell-futhark-server/armel (1.2.3.0-1 to 1.2.3.0-1)
- Migration status for haskell-futhark-server/armel (1.2.3.0-1 to 1.2.3.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-futhark-server/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-futhark-server/armhf (1.2.3.0-1 to 1.2.3.0-1)
- Migration status for haskell-futhark-server/armhf (1.2.3.0-1 to 1.2.3.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-futhark-server/armhf haskell-futhark (not considered)
- Invalidated by implicit-dependency
- Depends: haskell-futhark-server/armhf haskell-futhark-data (not considered)
- haskell-futhark-server/i386 (1.2.3.0-1 to 1.2.3.0-1)
- Migration status for haskell-futhark-server/i386 (1.2.3.0-1 to 1.2.3.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-futhark-server/i386 haskell-futhark (not considered)
- Invalidated by implicit-dependency
- Depends: haskell-futhark-server/i386 haskell-futhark-data (not considered)
- haskell-generic-deriving/armel (1.14.5-2 to 1.14.5-2)
- Migration status for haskell-generic-deriving/armel (1.14.5-2 to 1.14.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-githash/armel (0.1.7.0-2 to 0.1.7.0-2)
- Migration status for haskell-githash/armel (0.1.7.0-2 to 0.1.7.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-githash/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-gitrev/armel (1.3.1-7 to 1.3.1-7)
- Migration status for haskell-gitrev/armel (1.3.1-7 to 1.3.1-7): Will attempt migration (Any information below is purely informational)
- haskell-half/armel (0.3.1-3 to 0.3.1-3)
- Migration status for haskell-half/armel (0.3.1-3 to 0.3.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-half/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: haskell-half/armel haskell-futhark-data (not considered)
- haskell-hashable/armel (1.4.4.0-1 to 1.4.4.0-1)
- Migration status for haskell-hashable/armel (1.4.4.0-1 to 1.4.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-hashtables/armel (1.3.1-2 to 1.3.1-2)
- Migration status for haskell-hashtables/armel (1.3.1-2 to 1.3.1-2): Will attempt migration (Any information below is purely informational)
- haskell-haskell-gi-base/armel (0.26.8-1 to 0.26.8-1)
- Migration status for haskell-haskell-gi-base/armel (0.26.8-1 to 0.26.8-1): Will attempt migration (Any information below is purely informational)
- haskell-hourglass/armel (0.2.12-7 to 0.2.12-7)
- Migration status for haskell-hourglass/armel (0.2.12-7 to 0.2.12-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-hslua-core/armel (2.3.2-1 to 2.3.2-1)
- Migration status for haskell-hslua-core/armel (2.3.2-1 to 2.3.2-1): Will attempt migration (Any information below is purely informational)
- haskell-http-date/armel (0.0.11-3 to 0.0.11-3)
- Migration status for haskell-http-date/armel (0.0.11-3 to 0.0.11-3): Will attempt migration (Any information below is purely informational)
- haskell-http-types/armel (0.12.4-1 to 0.12.4-1)
- Migration status for haskell-http-types/armel (0.12.4-1 to 0.12.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-http2/armel (5.0.1-1 to 5.0.1-1)
- Migration status for haskell-http2/armel (5.0.1-1 to 5.0.1-1): Will attempt migration (Any information below is purely informational)
- haskell-indexed-traversable-instances/armel (0.1.2-1 to 0.1.2-1)
- Migration status for haskell-indexed-traversable-instances/armel (0.1.2-1 to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-indexed-traversable/armel (0.1.4-1 to 0.1.4-1)
- Migration status for haskell-indexed-traversable/armel (0.1.4-1 to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-integer-conversion/armel (0.1.0.1-2 to 0.1.0.1-2)
- Migration status for haskell-integer-conversion/armel (0.1.0.1-2 to 0.1.0.1-2): Will attempt migration (Any information below is purely informational)
- haskell-integer-logarithms/armel (1.0.3.1-4 to 1.0.3.1-4)
- Migration status for haskell-integer-logarithms/armel (1.0.3.1-4 to 1.0.3.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-invariant/armel (0.6.3-1 to 0.6.3-1)
- Migration status for haskell-invariant/armel (0.6.3-1 to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-iproute/armel (1.7.14-1 to 1.7.14-1)
- Migration status for haskell-iproute/armel (1.7.14-1 to 1.7.14-1): Will attempt migration (Any information below is purely informational)
- haskell-kan-extensions/armel (5.2.6-1 to 5.2.6-1)
- Migration status for haskell-kan-extensions/armel (5.2.6-1 to 5.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-language-c-quote/armel (0.13.0.2-1 to 0.13.0.2-1)
- Migration status for haskell-language-c-quote/armel (0.13.0.2-1 to 0.13.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-language-c-quote/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-lens/armel (5.2.3-2 to 5.2.3-2)
- Migration status for haskell-lens/armel (5.2.3-2 to 5.2.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-lens/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-lexer/armel (1.1.1-2 to 1.1.1-2)
- Migration status for haskell-lexer/armel (1.1.1-2 to 1.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-listlike/armel (4.7.8.2-2 to 4.7.8.2-2)
- Migration status for haskell-listlike/armel (4.7.8.2-2 to 4.7.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-lua/armel (2.3.3+ds1-1 to 2.3.3+ds1-1)
- Migration status for haskell-lua/armel (2.3.3+ds1-1 to 2.3.3+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-mainland-pretty/armel (0.7.1.1-1 to 0.7.1.1-1)
- Migration status for haskell-mainland-pretty/armel (0.7.1.1-1 to 0.7.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-math-functions/armel (0.3.4.4-1 to 0.3.4.4-1)
- Migration status for haskell-math-functions/armel (0.3.4.4-1 to 0.3.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-megaparsec/armel (9.5.0-1 to 9.5.0-1)
- Migration status for haskell-megaparsec/armel (9.5.0-1 to 9.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-memory/armel (0.18.0-4 to 0.18.0-4)
- Migration status for haskell-memory/armel (0.18.0-4 to 0.18.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-monad-control/armel (1.0.3.1-3 to 1.0.3.1-3)
- Migration status for haskell-monad-control/armel (1.0.3.1-3 to 1.0.3.1-3): Will attempt migration (Any information below is purely informational)
- haskell-mono-traversable/armel (1.0.20.0-1 to 1.0.20.0-1)
- Migration status for haskell-mono-traversable/armel (1.0.20.0-1 to 1.0.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-mwc-random/armel (0.15.1.0-1 to 0.15.1.0-1)
- Migration status for haskell-mwc-random/armel (0.15.1.0-1 to 0.15.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-neat-interpolation/armel (0.5.1.4-2 to 0.5.1.4-2)
- Migration status for haskell-neat-interpolation/armel (0.5.1.4-2 to 0.5.1.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-neat-interpolation/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-network-byte-order/armel (0.1.7-2 to 0.1.7-2)
- Migration status for haskell-network-byte-order/armel (0.1.7-2 to 0.1.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-network-control/armel (0.0.2-3 to 0.0.2-3)
- Migration status for haskell-network-control/armel (0.0.2-3 to 0.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-network/armel (3.1.4.0-2 to 3.1.4.0-2)
- Migration status for haskell-network/armel (3.1.4.0-2 to 3.1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-old-locale/armel (1.0.0.7-12 to 1.0.0.7-12)
- Migration status for haskell-old-locale/armel (1.0.0.7-12 to 1.0.0.7-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-old-time/armel (1.1.0.4-1 to 1.1.0.4-1)
- Migration status for haskell-old-time/armel (1.1.0.4-1 to 1.1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-onetuple/armel (0.4.2-1 to 0.4.2-1)
- Migration status for haskell-onetuple/armel (0.4.2-1 to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-os-string/armel (2.0.6-2 to 2.0.6-2)
- Migration status for haskell-os-string/armel (2.0.6-2 to 2.0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-parallel/armel (3.2.2.0-6 to 3.2.2.0-6)
- Migration status for haskell-parallel/armel (3.2.2.0-6 to 3.2.2.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-parser-combinators/armel (1.3.0-3 to 1.3.0-3)
- Migration status for haskell-parser-combinators/armel (1.3.0-3 to 1.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-pem/armel (0.2.4-6 to 0.2.4-6)
- Migration status for haskell-pem/armel (0.2.4-6 to 0.2.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-pretty-show/armel (1.10-4 to 1.10-4)
- Migration status for haskell-pretty-show/armel (1.10-4 to 1.10-4): Will attempt migration (Any information below is purely informational)
- haskell-prettyprinter-ansi-terminal/armel (1.1.3-3 to 1.1.3-3)
- Migration status for haskell-prettyprinter-ansi-terminal/armel (1.1.3-3 to 1.1.3-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-prettyprinter-ansi-terminal/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-prettyprinter/armel (1.7.1-3 to 1.7.1-3)
- Migration status for haskell-prettyprinter/armel (1.7.1-3 to 1.7.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-primitive/armel (0.8.0.0-2 to 0.8.0.0-2)
- Migration status for haskell-primitive/armel (0.8.0.0-2 to 0.8.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- (0.7.4-7 to 0.7.4-7)
- Migration status for haskell-process-extras/armel (0.7.4-7 to 0.7.4-7): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-process-extras/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-profunctors/armel (5.6.2-3 to 5.6.2-3)
- Migration status for haskell-profunctors/armel (5.6.2-3 to 5.6.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-psqueues/armel (0.2.8.0-1 to 0.2.8.0-1)
- Migration status for haskell-psqueues/armel (0.2.8.0-1 to 0.2.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-quickcheck/armel (2.14.3-2 to 2.14.3-2)
- Migration status for haskell-quickcheck/armel (2.14.3-2 to 2.14.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-random/armel (1.2.1.2-1 to 1.2.1.2-1)
- Migration status for haskell-random/armel (1.2.1.2-1 to 1.2.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-recv/armel (0.1.0-2 to 0.1.0-2)
- Migration status for haskell-recv/armel (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
- haskell-reflection/armel (2.1.8-2 to 2.1.8-2)
- Migration status for haskell-reflection/armel (2.1.8-2 to 2.1.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-regex-base/armel (0.94.0.2-3 to 0.94.0.2-3)
- Migration status for haskell-regex-base/armel (0.94.0.2-3 to 0.94.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-regex-tdfa/armel (1.3.2.2-2 to 1.3.2.2-2)
- Migration status for haskell-regex-tdfa/armel (1.3.2.2-2 to 1.3.2.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-regex-tdfa/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-resourcet/armel (1.3.0-1 to 1.3.0-1)
- Migration status for haskell-resourcet/armel (1.3.0-1 to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-safe-exceptions/armel (0.1.7.4-2 to 0.1.7.4-2)
- Migration status for haskell-safe-exceptions/armel (0.1.7.4-2 to 0.1.7.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-safe/armel (0.3.21-1 to 0.3.21-1)
- Migration status for haskell-safe/armel (0.3.21-1 to 0.3.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-scientific/armel (0.3.7.0-3 to 0.3.7.0-3)
- Migration status for haskell-scientific/armel (0.3.7.0-3 to 0.3.7.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-semialign/armel (1.3.1-1 to 1.3.1-1)
- Migration status for haskell-semialign/armel (1.3.1-1 to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-semigroupoids/armel (6.0.1-1 to 6.0.1-1)
- Migration status for haskell-semigroupoids/armel (6.0.1-1 to 6.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-semigroups/armel (0.20-3 to 0.20-3)
- Migration status for haskell-semigroups/armel (0.20-3 to 0.20-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-simple-sendfile/armel (0.2.32-3 to 0.2.32-3)
- Migration status for haskell-simple-sendfile/armel (0.2.32-3 to 0.2.32-3): Will attempt migration (Any information below is purely informational)
- haskell-split/armel (0.2.5-1 to 0.2.5-1)
- Migration status for haskell-split/armel (0.2.5-1 to 0.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-splitmix/armel (0.1.0.5-2 to 0.1.0.5-2)
- Migration status for haskell-splitmix/armel (0.1.0.5-2 to 0.1.0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-src-exts/armel (1.23.1-5 to 1.23.1-5)
- Migration status for haskell-src-exts/armel (1.23.1-5 to 1.23.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-src-meta/armel (0.8.14-1 to 0.8.14-1)
- Migration status for haskell-src-meta/armel (0.8.14-1 to 0.8.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-srcloc/armel (0.6.0.1-2 to 0.6.0.1-2)
- Migration status for haskell-srcloc/armel (0.6.0.1-2 to 0.6.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-statevar/armel (1.2.2-3 to 1.2.2-3)
- Migration status for haskell-statevar/armel (1.2.2-3 to 1.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-statistics/armel (0.16.2.1-2 to 0.16.2.1-2)
- Migration status for haskell-statistics/armel (0.16.2.1-2 to 0.16.2.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-statistics/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-streaming-commons/armel (0.2.2.6-2 to 0.2.2.6-2)
- Migration status for haskell-streaming-commons/armel (0.2.2.6-2 to 0.2.2.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-strict/armel (0.5-2 to 0.5-2)
- Migration status for haskell-strict/armel (0.5-2 to 0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-syb/armel (0.7.2.4-2 to 0.7.2.4-2)
- Migration status for haskell-syb/armel (0.7.2.4-2 to 0.7.2.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-tagged/armel (0.8.8-1 to 0.8.8-1)
- Migration status for haskell-tagged/armel (0.8.8-1 to 0.8.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-temporary/armel (1.3-5 to 1.3-5)
- Migration status for haskell-temporary/armel (1.3-5 to 1.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-terminal-size/armel (0.3.4-2 to 0.3.4-2)
- Migration status for haskell-terminal-size/armel (0.3.4-2 to 0.3.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-terminal-size/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-text-short/armel (0.1.6-1 to 0.1.6-1)
- Migration status for haskell-text-short/armel (0.1.6-1 to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-th-abstraction/armel (0.5.0.0-1 to 0.5.0.0-1)
- Migration status for haskell-th-abstraction/armel (0.5.0.0-1 to 0.5.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-th-compat/armel (0.1.5-1 to 0.1.5-1)
- Migration status for haskell-th-compat/armel (0.1.5-1 to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-th-expand-syns/armel (0.4.11.0-2 to 0.4.11.0-2)
- Migration status for haskell-th-expand-syns/armel (0.4.11.0-2 to 0.4.11.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-th-lift/armel (0.8.4-2 to 0.8.4-2)
- Migration status for haskell-th-lift/armel (0.8.4-2 to 0.8.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-th-orphans/armel (0.13.14-3 to 0.13.14-3)
- Migration status for haskell-th-orphans/armel (0.13.14-3 to 0.13.14-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-th-reify-many/armel (0.1.10-3 to 0.1.10-3)
- Migration status for haskell-th-reify-many/armel (0.1.10-3 to 0.1.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-these/armel (1.2.1-1 to 1.2.1-1)
- Migration status for haskell-these/armel (1.2.1-1 to 1.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-time-compat/armel (1.9.6.1-3 to 1.9.6.1-3)
- Migration status for haskell-time-compat/armel (1.9.6.1-3 to 1.9.6.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-time-manager/armel (0.0.1-2 to 0.0.1-2)
- Migration status for haskell-time-manager/armel (0.0.1-2 to 0.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-transformers-base/armel (0.4.6-3 to 0.4.6-3)
- Migration status for haskell-transformers-base/armel (0.4.6-3 to 0.4.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-transformers-compat/armel (0.7.2-2 to 0.7.2-2)
- Migration status for haskell-transformers-compat/armel (0.7.2-2 to 0.7.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-typed-process/armel (0.2.12.0-1 to 0.2.12.0-1)
- Migration status for haskell-typed-process/armel (0.2.12.0-1 to 0.2.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-unix-compat/armel (0.7.3-1 to 0.7.3-1)
- Migration status for haskell-unix-compat/armel (0.7.3-1 to 0.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-unix-time/armel (0.4.15-1 to 0.4.15-1)
- Migration status for haskell-unix-time/armel (0.4.15-1 to 0.4.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-unliftio-core/armel (0.2.1.0-2 to 0.2.1.0-2)
- Migration status for haskell-unliftio-core/armel (0.2.1.0-2 to 0.2.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-unliftio/armel (0.2.25.0-2 to 0.2.25.0-2)
- Migration status for haskell-unliftio/armel (0.2.25.0-2 to 0.2.25.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-unordered-containers/armel (0.2.20-3 to 0.2.20-3)
- Migration status for haskell-unordered-containers/armel (0.2.20-3 to 0.2.20-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-utf8-string/armel (1.0.2-3 to 1.0.2-3)
- Migration status for haskell-utf8-string/armel (1.0.2-3 to 1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-uuid-types/armel (1.0.5.1-2 to 1.0.5.1-2)
- Migration status for haskell-uuid-types/armel (1.0.5.1-2 to 1.0.5.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-vault/armel (0.3.1.5-4 to 0.3.1.5-4)
- Migration status for haskell-vault/armel (0.3.1.5-4 to 0.3.1.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-vector-algorithms/armel (0.9.0.2-1 to 0.9.0.2-1)
- Migration status for haskell-vector-algorithms/armel (0.9.0.2-1 to 0.9.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-vector-binary-instances/armel (0.2.5.2-3 to 0.2.5.2-3)
- Migration status for haskell-vector-binary-instances/armel (0.2.5.2-3 to 0.2.5.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-vector-stream/armel (0.1.0.1-1 to 0.1.0.1-1)
- Migration status for haskell-vector-stream/armel (0.1.0.1-1 to 0.1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-vector-th-unbox/armel (0.2.2-3 to 0.2.2-3)
- Migration status for haskell-vector-th-unbox/armel (0.2.2-3 to 0.2.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-vector/armel (0.13.1.0-2 to 0.13.1.0-2)
- Migration status for haskell-vector/armel (0.13.1.0-2 to 0.13.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-versions/armel (6.0.7-2 to 6.0.7-2)
- Migration status for haskell-versions/armel (6.0.7-2 to 6.0.7-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: haskell-versions/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-void/armel (0.7.3-5 to 0.7.3-5)
- Migration status for haskell-void/armel (0.7.3-5 to 0.7.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-wai/armel (3.2.4-1 to 3.2.4-1)
- Migration status for haskell-wai/armel (3.2.4-1 to 3.2.4-1): Will attempt migration (Any information below is purely informational)
- haskell-witherable/armel (0.4.2-4 to 0.4.2-4)
- Migration status for haskell-witherable/armel (0.4.2-4 to 0.4.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-word8/armel (0.1.3-7 to 0.1.3-7)
- Migration status for haskell-word8/armel (0.1.3-7 to 0.1.3-7): Will attempt migration (Any information below is purely informational)
- haskell-xdg-basedir/armel (0.2.2-14 to 0.2.2-14)
- Migration status for haskell-xdg-basedir/armel (0.2.2-14 to 0.2.2-14): Will attempt migration (Any information below is purely informational)
- haskell-xml-conduit/armel (1.9.1.3-2 to 1.9.1.3-2)
- Migration status for haskell-xml-conduit/armel (1.9.1.3-2 to 1.9.1.3-2): Will attempt migration (Any information below is purely informational)
- haskell-xml-types/armel (0.3.8-4 to 0.3.8-4)
- Migration status for haskell-xml-types/armel (0.3.8-4 to 0.3.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haskell-zlib/armel (0.6.3.0-3 to 0.6.3.0-3)
- Migration status for haskell-zlib/armel (0.6.3.0-3 to 0.6.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- haveged/armel (1.9.19-12 to 1.9.19-12)
- Migration status for haveged/armel (1.9.19-12 to 1.9.19-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hcxdumptool/armel (7.0.0-1 to 7.0.0-1)
- Migration status for hcxdumptool/armel (7.0.0-1 to 7.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hcxtools/armel (6.3.5-1 to 6.3.5-1)
- Migration status for hcxtools/armel (6.3.5-1 to 6.3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hdf-eos4/armel (3.0-2 to 3.0-2)
- Migration status for hdf-eos4/armel (3.0-2 to 3.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: hdf-eos4/armel ncl (not considered)
- Invalidated by implicit-dependency
- hdf-eos5/armel (2:2.0-4 to 2:2.0-4)
- Migration status for hdf-eos5/armel (2:2.0-4 to 2:2.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: hdf-eos5/armel ncl (not considered)
- Invalidated by implicit-dependency
- hdf5/armel (1.14.5+repack-3 to 1.14.5+repack-3)
- Migration status for hdf5/armel (1.14.5+repack-3 to 1.14.5+repack-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hexwalk/armel (1.7.1-1 to 1.7.1-1)
- Migration status for hexwalk/armel (1.7.1-1 to 1.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hfsplus/armel (1.0.4-19 to 1.0.4-19)
- Migration status for hfsplus/armel (1.0.4-19 to 1.0.4-19): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- highway/armel (1.2.0-2 to 1.2.0-2)
- Migration status for highway/armel (1.2.0-2 to 1.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hiredis/armel (1.2.0-6 to 1.2.0-6)
- Migration status for hiredis/armel (1.2.0-6 to 1.2.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hivex/armel (1.3.24-1 to 1.3.24-1)
- Migration status for hivex/armel (1.3.24-1 to 1.3.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- horst/armel (5.1-3 to 5.1-3)
- Migration status for horst/armel (5.1-3 to 5.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- htop/armel (3.4.1-5 to 3.4.1-5)
- Migration status for htop/armel (3.4.1-5 to 3.4.1-5): Will attempt migration (Any information below is purely informational)
- http-parser/armel (2.9.4-6 to 2.9.4-6)
- Migration status for http-parser/armel (2.9.4-6 to 2.9.4-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- httptunnel/armel (3.3+dfsg-5 to 3.3+dfsg-5)
- Migration status for httptunnel/armel (3.3+dfsg-5 to 3.3+dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- httrack/armel (3.49.6-1 to 3.49.6-1)
- Migration status for httrack/armel (3.49.6-1 to 3.49.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hunspell/armel (1.7.2+really1.7.2-11 to 1.7.2+really1.7.2-11)
- Migration status for hunspell/armel (1.7.2+really1.7.2-11 to 1.7.2+really1.7.2-11): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: hunspell/armel link-grammar (not considered)
- Invalidated by implicit-dependency
- hw-detect/armel (1.171 to 1.171)
- Migration status for hw-detect/armel (1.171 to 1.171): Will attempt migration (Any information below is purely informational)
- hwloc/armel (2.12.0-4 to 2.12.0-4)
- Migration status for hwloc/armel (2.12.0-4 to 2.12.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- hydra/armel (9.5-3 to 9.5-3)
- Migration status for hydra/armel (9.5-3 to 9.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- i2c-tools/armel (4.4-2 to 4.4-2)
- Migration status for i2c-tools/armel (4.4-2 to 4.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- i3-wm/armel (4.24-1 to 4.24-1)
- Migration status for i3-wm/armel (4.24-1 to 4.24-1): Will attempt migration (Any information below is purely informational)
- i3status/armel (2.15-2 to 2.15-2)
- Migration status for i3status/armel (2.15-2 to 2.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ibus/armel (1.5.32-2 to 1.5.32-2)
- Migration status for ibus/armel (1.5.32-2 to 1.5.32-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: ibus/armel ibus-chewing (not considered)
- Invalidated by implicit-dependency
- icoutils/armel (0.32.3-6 to 0.32.3-6)
- Migration status for icoutils/armel (0.32.3-6 to 0.32.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- icu/armel (76.1-4 to 76.1-4)
- Migration status for icu/armel (76.1-4 to 76.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ike-scan/armel (1.9.5-2 to 1.9.5-2)
- Migration status for ike-scan/armel (1.9.5-2 to 1.9.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- imath/armel (3.1.12-1 to 3.1.12-1)
- Migration status for imath/armel (3.1.12-1 to 3.1.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- imlib2/armel (1.12.4-2 to 1.12.4-2)
- Migration status for imlib2/armel (1.12.4-2 to 1.12.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- inetutils/armel (2:2.6-4 to 2:2.6-4)
- Migration status for inetutils/armel (2:2.6-4 to 2:2.6-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- initramfs-tools/armel (0.148.3 to 0.148.3)
- Migration status for initramfs-tools/armel (0.148.3 to 0.148.3): Will attempt migration (Any information below is purely informational)
- inotify-tools/armel (4.23.9.0-2 to 4.23.9.0-2)
- Migration status for inotify-tools/armel (4.23.9.0-2 to 4.23.9.0-2): Will attempt migration (Any information below is purely informational)
- inspectrum/armel (0.3.1-1 to 0.3.1-1)
- Migration status for inspectrum/armel (0.3.1-1 to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- insserv/armel (1.26.0-1 to 1.26.0-1)
- Migration status for insserv/armel (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
- intelrdfpmath/armel (2.0u3-1 to 2.0u3-1)
- Migration status for intelrdfpmath/armel (2.0u3-1 to 2.0u3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- iodine/armel (0.7.0-11 to 0.7.0-11)
- Migration status for iodine/armel (0.7.0-11 to 0.7.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- iproute2/armel (6.16.0-1 to 6.16.0-1)
- Migration status for iproute2/armel (6.16.0-1 to 6.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- iptables/armel (1.8.11-2 to 1.8.11-2)
- Migration status for iptables/armel (1.8.11-2 to 1.8.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- iputils/armel (3:20250605-1 to 3:20250605-1)
- Migration status for iputils/armel (3:20250605-1 to 3:20250605-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- irpas/armel (0.10-10 to 0.10-10)
- Migration status for irpas/armel (0.10-10 to 0.10-10): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- isc-dhcp/armel (4.4.3-P1-8 to 4.4.3-P1-8)
- Migration status for isc-dhcp/armel (4.4.3-P1-8 to 4.4.3-P1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- iw/armel (6.9-1 to 6.9-1)
- Migration status for iw/armel (6.9-1 to 6.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- jackd2/armel (1.9.22~dfsg-5 to 1.9.22~dfsg-5)
- Migration status for jackd2/armel (1.9.22~dfsg-5 to 1.9.22~dfsg-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- janest-base/armel (0.17.3-1 to 0.17.3-1)
- Migration status for janest-base/armel (0.17.3-1 to 0.17.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: janest-base/armel ocaml-time-now (not considered)
- Invalidated by implicit-dependency
- janest-ocaml-compiler-libs/armel (0.17.0-1 to 0.17.0-1)
- Migration status for janest-ocaml-compiler-libs/armel (0.17.0-1 to 0.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- jansson/armel (2.14-2 to 2.14-2)
- Migration status for jansson/armel (2.14-2 to 2.14-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- java-atk-wrapper/armel (0.42.1-1 to 0.42.1-1)
- Migration status for java-atk-wrapper/armel (0.42.1-1 to 0.42.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- java-common/armel (0.76 to 0.76)
- Migration status for java-common/armel (0.76 to 0.76): Will attempt migration (Any information below is purely informational)
- jbigkit/armel (2.1-6.1 to 2.1-6.1)
- Migration status for jbigkit/armel (2.1-6.1 to 2.1-6.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- jfsutils/armel (1.1.15-7 to 1.1.15-7)
- Migration status for jfsutils/armel (1.1.15-7 to 1.1.15-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- jpeg-xl/armel (0.11.1-4 to 0.11.1-4)
- Migration status for jpeg-xl/armel (0.11.1-4 to 0.11.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- jq/armel (1.8.1-3 to 1.8.1-3)
- Migration status for jq/armel (1.8.1-3 to 1.8.1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: jq/armel ostree (not considered)
- Invalidated by implicit-dependency
- js-of-ocaml/armel (5.9.1-1 to 5.9.1-1)
- Migration status for js-of-ocaml/armel (5.9.1-1 to 5.9.1-1): Will attempt migration (Any information below is purely informational)
- json-c/armel (0.18+ds-1 to 0.18+ds-1)
- Migration status for json-c/armel (0.18+ds-1 to 0.18+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- json-glib/armel (1.10.6+ds-3 to 1.10.6+ds-3)
- Migration status for json-glib/armel (1.10.6+ds-3 to 1.10.6+ds-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kactivitymanagerd/armel (6.3.4-1 to 6.3.4-1)
- Migration status for kactivitymanagerd/armel (6.3.4-1 to 6.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- karchive/armel (5.116.0-1 to 5.116.0-1)
- Migration status for karchive/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kate/armel (4:25.04.3-2 to 4:25.04.3-2)
- Migration status for kate/armel (4:25.04.3-2 to 4:25.04.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kauth/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kauth/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kbd/armel (2.7.1-2 to 2.7.1-2)
- Migration status for kbd/armel (2.7.1-2 to 2.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kbookmarks/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kbookmarks/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kcalc/armel (4:25.04.0-1 to 4:25.04.0-1)
- Migration status for kcalc/armel (4:25.04.0-1 to 4:25.04.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kcodecs/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kcodecs/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kcompletion/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kcompletion/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kconfig/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kconfig/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kconfigwidgets/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kconfigwidgets/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kcoreaddons/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kcoreaddons/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kcrash/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kcrash/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kdbusaddons/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kdbusaddons/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kde-cli-tools/armel (4:6.3.4-1 to 4:6.3.4-1)
- Migration status for kde-cli-tools/armel (4:6.3.4-1 to 4:6.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kde-spectacle/armel (4:6.3.5-2 to 4:6.3.5-2)
- Migration status for kde-spectacle/armel (4:6.3.5-2 to 4:6.3.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kdeclarative/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kdeclarative/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kdeconnect/armel (25.04.2-1 to 25.04.2-1)
- Migration status for kdeconnect/armel (25.04.2-1 to 25.04.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kded/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kded/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kdesignerplugin/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kdesignerplugin/armel (5.116.0-1 to 5.116.0-1): Will attempt migration (Any information below is purely informational)
- kdoctools/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kdoctools/armel (5.116.0-1 to 5.116.0-1): Will attempt migration (Any information below is purely informational)
- kemoticons/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kemoticons/armel (5.116.0-1 to 5.116.0-1): Will attempt migration (Any information below is purely informational)
- kernsmooth/armel (2.23-26-1 to 2.23-26-1)
- Migration status for kernsmooth/armel (2.23-26-1 to 2.23-26-1): Will attempt migration (Any information below is purely informational)
- keyutils/armel (1.6.3-6 to 1.6.3-6)
- Migration status for keyutils/armel (1.6.3-6 to 1.6.3-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-baloo/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-baloo/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-karchive/armel (6.13.0-2 to 6.13.0-2)
- Migration status for kf6-karchive/armel (6.13.0-2 to 6.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kbookmarks/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kbookmarks/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kcodecs/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kcodecs/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kcolorscheme/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kcolorscheme/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kcompletion/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kcompletion/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kconfig/armel (6.13.0-2 to 6.13.0-2)
- Migration status for kf6-kconfig/armel (6.13.0-2 to 6.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kconfigwidgets/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kconfigwidgets/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kcoreaddons/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kcoreaddons/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kcrash/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kcrash/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kdbusaddons/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kdbusaddons/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kdoctools/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kdoctools/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kfilemetadata/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kfilemetadata/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kglobalaccel/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kglobalaccel/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kguiaddons/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kguiaddons/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-ki18n/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-ki18n/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kidletime/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kidletime/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kimageformats/armel (6.13.0-2 to 6.13.0-2)
- Migration status for kf6-kimageformats/armel (6.13.0-2 to 6.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kio/armel (6.13.0-6 to 6.13.0-6)
- Migration status for kf6-kio/armel (6.13.0-6 to 6.13.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kitemmodels/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kitemmodels/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kitemviews/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kitemviews/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kjobwidgets/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kjobwidgets/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-knotifications/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-knotifications/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kpackage/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kpackage/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kservice/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kservice/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kwidgetsaddons/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kwidgetsaddons/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kwindowsystem/armel (6.13.0-2 to 6.13.0-2)
- Migration status for kf6-kwindowsystem/armel (6.13.0-2 to 6.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-kxmlgui/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-kxmlgui/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-qqc2-desktop-style/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-qqc2-desktop-style/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kf6-solid/armel (6.13.0-1 to 6.13.0-1)
- Migration status for kf6-solid/armel (6.13.0-1 to 6.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kglobalaccel/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kglobalaccel/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kglobalacceld/armel (6.3.6-1 to 6.3.6-1)
- Migration status for kglobalacceld/armel (6.3.6-1 to 6.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kguiaddons/armel (5.116.0-2 to 5.116.0-2)
- Migration status for kguiaddons/armel (5.116.0-2 to 5.116.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ki18n/armel (5.116.0-1 to 5.116.0-1)
- Migration status for ki18n/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kiconthemes/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kiconthemes/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kinit/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kinit/armel (5.116.0-1 to 5.116.0-1): Will attempt migration (Any information below is purely informational)
- kio/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kio/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kirigami2/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kirigami2/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kitemmodels/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kitemmodels/armel (5.116.0-1 to 5.116.0-1): Will attempt migration (Any information below is purely informational)
- kitemviews/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kitemviews/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kitty/armel (0.41.1-2 to 0.41.1-2)
- Migration status for kitty/armel (0.41.1-2 to 0.41.1-2): Will attempt migration (Any information below is purely informational)
- kiwisolver/armel (1.4.7-3 to 1.4.7-3)
- Migration status for kiwisolver/armel (1.4.7-3 to 1.4.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kjobwidgets/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kjobwidgets/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- knotifications/armel (5.116.0-1 to 5.116.0-1)
- Migration status for knotifications/armel (5.116.0-1 to 5.116.0-1): Will attempt migration (Any information below is purely informational)
- konsole/armel (4:25.04.2-1 to 4:25.04.2-1)
- Migration status for konsole/armel (4:25.04.2-1 to 4:25.04.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kpackage/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kpackage/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kparts/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kparts/armel (5.116.0-1 to 5.116.0-1): Will attempt migration (Any information below is purely informational)
- kpublictransport/armel (25.04.3-1 to 25.04.3-1)
- Migration status for kpublictransport/armel (25.04.3-1 to 25.04.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing qml6-module-org-kde-kpublictransport/25.04.3-1/armel from kali-rolling makes ktrip/25.04.0-1+b1/armel uninstallable
- krb5/armel (1.21.3-5 to 1.21.3-5)
- Migration status for krb5/armel (1.21.3-5 to 1.21.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kservice/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kservice/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ksh93u+m/armel (1.0.10-2 to 1.0.10-2)
- Migration status for ksh93u+m/armel (1.0.10-2 to 1.0.10-2): Will attempt migration (Any information below is purely informational)
- ksystemstats/armel (6.3.4-1 to 6.3.4-1)
- Migration status for ksystemstats/armel (6.3.4-1 to 6.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ktextwidgets/armel (5.116.0-1 to 5.116.0-1)
- Migration status for ktextwidgets/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ktrip/armel (25.04.0-1 to 25.04.0-1)
- Migration status for ktrip/armel (25.04.0-1 to 25.04.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kunitconversion/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kunitconversion/armel (5.116.0-1 to 5.116.0-1): Will attempt migration (Any information below is purely informational)
- kustomize/armel (5.6.0+ds-1 to 5.6.0+ds-1)
- Migration status for kustomize/armel (5.6.0+ds-1 to 5.6.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kwidgetsaddons/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kwidgetsaddons/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kwin/armel (4:6.3.6-1 to 4:6.3.6-1)
- Migration status for kwin/armel (4:6.3.6-1 to 4:6.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kwindowsystem/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kwindowsystem/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- kxmlgui/armel (5.116.0-1 to 5.116.0-1)
- Migration status for kxmlgui/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ladspa-sdk/armel (1.17-1 to 1.17-1)
- Migration status for ladspa-sdk/armel (1.17-1 to 1.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lame/armel (3.100-6 to 3.100-6)
- Migration status for lame/armel (3.100-6 to 3.100-6): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: lame/armel ocaml-lame (not considered)
- Invalidated by implicit-dependency
- lapack/armel (3.12.1-6 to 3.12.1-6)
- Migration status for lapack/armel (3.12.1-6 to 3.12.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lattice/armel (0.22-7-1 to 0.22-7-1)
- Migration status for lattice/armel (0.22-7-1 to 0.22-7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- layer-shell-qt/armel (6.3.4-1 to 6.3.4-1)
- Migration status for layer-shell-qt/armel (6.3.4-1 to 6.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lcms2/armel (2.16-2 to 2.16-2)
- Migration status for lcms2/armel (2.16-2 to 2.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lerc/armel (4.0.0+ds-5 to 4.0.0+ds-5)
- Migration status for lerc/armel (4.0.0+ds-5 to 4.0.0+ds-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- less/armel (668-1 to 668-1)
- Migration status for less/armel (668-1 to 668-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libaec/armel (1.1.4-2 to 1.1.4-2)
- Migration status for libaec/armel (1.1.4-2 to 1.1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libao/armel (1.2.2+20180113-1.2 to 1.2.2+20180113-1.2)
- Migration status for libao/armel (1.2.2+20180113-1.2 to 1.2.2+20180113-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libarchive/armel (3.7.4-4 to 3.7.4-4)
- Migration status for libarchive/armel (3.7.4-4 to 3.7.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libassuan/armel (3.0.2-2 to 3.0.2-2)
- Migration status for libassuan/armel (3.0.2-2 to 3.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libavif/armel (1.3.0-1 to 1.3.0-1)
- Migration status for libavif/armel (1.3.0-1 to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libb-hooks-op-check-perl/armel (0.22-3 to 0.22-3)
- Migration status for libb-hooks-op-check-perl/armel (0.22-3 to 0.22-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libbde/armel (20240502-1 to 20240502-1)
- Migration status for libbde/armel (20240502-1 to 20240502-1): Will attempt migration (Any information below is purely informational)
- libbfio/armel (20170123-6 to 20170123-6)
- Migration status for libbfio/armel (20170123-6 to 20170123-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libbsd/armel (0.12.2-2 to 0.12.2-2)
- Migration status for libbsd/armel (0.12.2-2 to 0.12.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libbtbb/armel (2018.12.R1-1 to 2018.12.R1-1)
- Migration status for libbtbb/armel (2018.12.R1-1 to 2018.12.R1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libcairo-gobject-perl/armel (1.005-4 to 1.005-4)
- Migration status for libcairo-gobject-perl/armel (1.005-4 to 1.005-4): Will attempt migration (Any information below is purely informational)
- libcairo-perl/armel (1.109-5 to 1.109-5)
- Migration status for libcairo-perl/armel (1.109-5 to 1.109-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libcap2/armel (1:2.75-10 to 1:2.75-10)
- Migration status for libcap2/armel (1:2.75-10 to 1:2.75-10): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libclass-load-xs-perl/armel (0.10-2 to 0.10-2)
- Migration status for libclass-load-xs-perl/armel (0.10-2 to 0.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libclass-xsaccessor-perl/armel (1.19-4 to 1.19-4)
- Migration status for libclass-xsaccessor-perl/armel (1.19-4 to 1.19-4): Will attempt migration (Any information below is purely informational)
- libclone-perl/armel (0.47-1 to 0.47-1)
- Migration status for libclone-perl/armel (0.47-1 to 0.47-1): Will attempt migration (Any information below is purely informational)
- libcloudproviders/armel (0.3.6-2 to 0.3.6-2)
- Migration status for libcloudproviders/armel (0.3.6-2 to 0.3.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libcloudproviders/armel gtk+3.0 (not considered)
- Invalidated by implicit-dependency
- libcreg/armel (20240419-1 to 20240419-1)
- Migration status for libcreg/armel (20240419-1 to 20240419-1): Will attempt migration (Any information below is purely informational)
- libcrypt-ssleay-perl/armel (0.73.06-2 to 0.73.06-2)
- Migration status for libcrypt-ssleay-perl/armel (0.73.06-2 to 0.73.06-2): Will attempt migration (Any information below is purely informational)
- libdatetime-perl/armel (2:1.65-1 to 2:1.65-1)
- Migration status for libdatetime-perl/armel (2:1.65-1 to 2:1.65-1): Will attempt migration (Any information below is purely informational)
- libdatrie/armel (0.2.13-4 to 0.2.13-4)
- Migration status for libdatrie/armel (0.2.13-4 to 0.2.13-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libdbd-sqlite3-perl/armel (1.76-1 to 1.76-1)
- Migration status for libdbd-sqlite3-perl/armel (1.76-1 to 1.76-1): Will attempt migration (Any information below is purely informational)
- libdbi-perl/armel (1.647-1 to 1.647-1)
- Migration status for libdbi-perl/armel (1.647-1 to 1.647-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libdebian-installer/armel (0.125 to 0.125)
- Migration status for libdebian-installer/armel (0.125 to 0.125): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libdeflate/armel (1.23-2 to 1.23-2)
- Migration status for libdeflate/armel (1.23-2 to 1.23-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libdevel-callchecker-perl/armel (0.009-2 to 0.009-2)
- Migration status for libdevel-callchecker-perl/armel (0.009-2 to 0.009-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libdex/armel (0.10.1-1 to 0.10.1-1)
- Migration status for libdex/armel (0.10.1-1 to 0.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libdigest-crc-perl/armel (0.24-1 to 0.24-1)
- Migration status for libdigest-crc-perl/armel (0.24-1 to 0.24-1): Will attempt migration (Any information below is purely informational)
- libdigest-md4-perl/armel (1.9+dfsg-3 to 1.9+dfsg-3)
- Migration status for libdigest-md4-perl/armel (1.9+dfsg-3 to 1.9+dfsg-3): Will attempt migration (Any information below is purely informational)
- libdrm/armel (2.4.125-2 to 2.4.125-2)
- Migration status for libdrm/armel (2.4.125-2 to 2.4.125-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libdumbnet/armel (1.18.0-2 to 1.18.0-2)
- Migration status for libdumbnet/armel (1.18.0-2 to 1.18.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libepoxy/armel (1.5.10-2 to 1.5.10-2)
- Migration status for libepoxy/armel (1.5.10-2 to 1.5.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libesedb/armel (20240420-1 to 20240420-1)
- Migration status for libesedb/armel (20240420-1 to 20240420-1): Will attempt migration (Any information below is purely informational)
- libev/armel (1:4.33-2.1 to 1:4.33-2.1)
- Migration status for libev/armel (1:4.33-2.1 to 1:4.33-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libevdev/armel (1.13.4+dfsg-1 to 1.13.4+dfsg-1)
- Migration status for libevdev/armel (1.13.4+dfsg-1 to 1.13.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libevt/armel (20200926-2 to 20200926-2)
- Migration status for libevt/armel (20200926-2 to 20200926-2): Will attempt migration (Any information below is purely informational)
- libevtx/armel (20240504-1 to 20240504-1)
- Migration status for libevtx/armel (20240504-1 to 20240504-1): Will attempt migration (Any information below is purely informational)
- libewf/armel (20140816-1 to 20140816-1)
- Migration status for libewf/armel (20140816-1 to 20140816-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libexif/armel (0.6.25-1 to 0.6.25-1)
- Migration status for libexif/armel (0.6.25-1 to 0.6.25-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: libexif/armel imagemagick (not considered)
- Invalidated by implicit-dependency
- libffi/armel (3.4.8-2 to 3.4.8-2)
- Migration status for libffi/armel (3.4.8-2 to 3.4.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libfile-fcntllock-perl/armel (0.22-4 to 0.22-4)
- Migration status for libfile-fcntllock-perl/armel (0.22-4 to 0.22-4): Will attempt migration (Any information below is purely informational)
- libfm/armel (1.4.0-2 to 1.4.0-2)
- Migration status for libfm/armel (1.4.0-2 to 1.4.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libfontenc/armel (1:1.1.8-1 to 1:1.1.8-1)
- Migration status for libfontenc/armel (1:1.1.8-1 to 1:1.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libfreefare/armel (0.4.0-2.3 to 0.4.0-2.3)
- Migration status for libfreefare/armel (0.4.0-2.3 to 0.4.0-2.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libfsapfs/armel (20240429-1 to 20240429-1)
- Migration status for libfsapfs/armel (20240429-1 to 20240429-1): Will attempt migration (Any information below is purely informational)
- libfsext/armel (20240501-1 to 20240501-1)
- Migration status for libfsext/armel (20240501-1 to 20240501-1): Will attempt migration (Any information below is purely informational)
- libfshfs/armel (20240501-1 to 20240501-1)
- Migration status for libfshfs/armel (20240501-1 to 20240501-1): Will attempt migration (Any information below is purely informational)
- libfsntfs/armel (20240501-1 to 20240501-1)
- Migration status for libfsntfs/armel (20240501-1 to 20240501-1): Will attempt migration (Any information below is purely informational)
- libfsxfs/armel (20240501-1 to 20240501-1)
- Migration status for libfsxfs/armel (20240501-1 to 20240501-1): Will attempt migration (Any information below is purely informational)
- libfvde/armel (20240502-1 to 20240502-1)
- Migration status for libfvde/armel (20240502-1 to 20240502-1): Will attempt migration (Any information below is purely informational)
- libfwnt/armel (20240415-1 to 20240415-1)
- Migration status for libfwnt/armel (20240415-1 to 20240415-1): Will attempt migration (Any information below is purely informational)
- libfwsi/armel (20240423-1 to 20240423-1)
- Migration status for libfwsi/armel (20240423-1 to 20240423-1): Will attempt migration (Any information below is purely informational)
- libgc/armel (1:8.2.8-1 to 1:8.2.8-1)
- Migration status for libgc/armel (1:8.2.8-1 to 1:8.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libgcrypt20/armel (1.11.2-2 to 1.11.2-2)
- Migration status for libgcrypt20/armel (1.11.2-2 to 1.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libgctp/armel (2.0.0-11 to 2.0.0-11)
- Migration status for libgctp/armel (2.0.0-11 to 2.0.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libgd2/armel (2.3.3-13 to 2.3.3-13)
- Migration status for libgd2/armel (2.3.3-13 to 2.3.3-13): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: libgd2/armel gd4o (not considered)
- Invalidated by implicit-dependency
- libgeotiff/armel (1.7.4-1 to 1.7.4-1)
- Migration status for libgeotiff/armel (1.7.4-1 to 1.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libgit2/armel (1.9.1+ds-1 to 1.9.1+ds-1)
- Migration status for libgit2/armel (1.9.1+ds-1 to 1.9.1+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libglib-object-introspection-perl/armel (0.051-2 to 0.051-2)
- Migration status for libglib-object-introspection-perl/armel (0.051-2 to 0.051-2): Will attempt migration (Any information below is purely informational)
- libglib-perl/armel (3:1.329.3-3 to 3:1.329.3-3)
- Migration status for libglib-perl/armel (3:1.329.3-3 to 3:1.329.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libglvnd/armel (1.7.0-1 to 1.7.0-1)
- Migration status for libglvnd/armel (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libgpg-error/armel (1.55-2 to 1.55-2)
- Migration status for libgpg-error/armel (1.55-2 to 1.55-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libgsm/armel (1.0.22-1 to 1.0.22-1)
- Migration status for libgsm/armel (1.0.22-1 to 1.0.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libgudev/armel (238-6 to 238-6)
- Migration status for libgudev/armel (238-6 to 238-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libguestfs/armel (1:1.54.1-2 to 1:1.54.1-2)
- Migration status for libguestfs/armel (1:1.54.1-2 to 1:1.54.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libgusb/armel (0.4.9-1 to 0.4.9-1)
- Migration status for libgusb/armel (0.4.9-1 to 0.4.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libhandy-1/armel (1.8.3-3 to 1.8.3-3)
- Migration status for libhandy-1/armel (1.8.3-3 to 1.8.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libheif/armel (1.20.2-2 to 1.20.2-2)
- Migration status for libheif/armel (1.20.2-2 to 1.20.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libhtml-parser-perl/armel (3.83-1 to 3.83-1)
- Migration status for libhtml-parser-perl/armel (3.83-1 to 3.83-1): Will attempt migration (Any information below is purely informational)
- libical3/armel (3.0.20-1 to 3.0.20-1)
- Migration status for libical3/armel (3.0.20-1 to 3.0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libice/armel (2:1.1.1-1 to 2:1.1.1-1)
- Migration status for libice/armel (2:1.1.1-1 to 2:1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libid3tag/armel (0.16.3-1 to 0.16.3-1)
- Migration status for libid3tag/armel (0.16.3-1 to 0.16.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libidn2/armel (2.3.8-4 to 2.3.8-4)
- Migration status for libidn2/armel (2.3.8-4 to 2.3.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libinih/armel (61-1 to 61-1)
- Migration status for libinih/armel (61-1 to 61-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libinput/armel (1.28.1-1 to 1.28.1-1)
- Migration status for libinput/armel (1.28.1-1 to 1.28.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libio-pty-perl/armel (1:1.20-1 to 1:1.20-1)
- Migration status for libio-pty-perl/armel (1:1.20-1 to 1:1.20-1): Will attempt migration (Any information below is purely informational)
- libjcat/armel (0.2.3-1 to 0.2.3-1)
- Migration status for libjcat/armel (0.2.3-1 to 0.2.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libjcat/armel fwupd (not considered)
- Invalidated by implicit-dependency
- libjpeg-turbo/armel (1:2.1.5-4 to 1:2.1.5-4)
- Migration status for libjpeg-turbo/armel (1:2.1.5-4 to 1:2.1.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libkml/armel (1.3.0-12 to 1.3.0-12)
- Migration status for libkml/armel (1.3.0-12 to 1.3.0-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libksba/armel (1.6.7-2 to 1.6.7-2)
- Migration status for libksba/armel (1.6.7-2 to 1.6.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libldm/armel (0.2.5-1.1 to 0.2.5-1.1)
- Migration status for libldm/armel (0.2.5-1.1 to 0.2.5-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- liblnk/armel (20240423-1 to 20240423-1)
- Migration status for liblnk/armel (20240423-1 to 20240423-1): Will attempt migration (Any information below is purely informational)
- liblo/armel (0.32-3 to 0.32-3)
- Migration status for liblo/armel (0.32-3 to 0.32-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: liblo/armel ocaml-lo (not considered)
- Invalidated by implicit-dependency
- liblocale-gettext-perl/armel (1.07-7 to 1.07-7)
- Migration status for liblocale-gettext-perl/armel (1.07-7 to 1.07-7): Will attempt migration (Any information below is purely informational)
- liblockfile/armel (1.17-2 to 1.17-2)
- Migration status for liblockfile/armel (1.17-2 to 1.17-2): Will attempt migration (Any information below is purely informational)
- liblqr/armel (0.4.2-2.1 to 0.4.2-2.1)
- Migration status for liblqr/armel (0.4.2-2.1 to 0.4.2-2.1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: liblqr/armel imagemagick (not considered)
- Invalidated by implicit-dependency
- libluksde/armel (20240503-1 to 20240503-1)
- Migration status for libluksde/armel (20240503-1 to 20240503-1): Will attempt migration (Any information below is purely informational)
- libmad/armel (0.15.1b-11 to 0.15.1b-11)
- Migration status for libmad/armel (0.15.1b-11 to 0.15.1b-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libmbim/armel (1.32.0-1 to 1.32.0-1)
- Migration status for libmbim/armel (1.32.0-1 to 1.32.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libmd/armel (1.1.0-2 to 1.1.0-2)
- Migration status for libmd/armel (1.1.0-2 to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libmongocrypt/armel (1.13.2-1 to 1.13.2-1)
- Migration status for libmongocrypt/armel (1.13.2-1 to 1.13.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libmoose-perl/armel (2.2207-1 to 2.2207-1)
- Migration status for libmoose-perl/armel (2.2207-1 to 2.2207-1): Will attempt migration (Any information below is purely informational)
- libmsiecf/armel (20181227-3 to 20181227-3)
- Migration status for libmsiecf/armel (20181227-3 to 20181227-3): Will attempt migration (Any information below is purely informational)
- libnet-pcap-perl/armel (0.21-2 to 0.21-2)
- Migration status for libnet-pcap-perl/armel (0.21-2 to 0.21-2): Will attempt migration (Any information below is purely informational)
- libnet-rawip-perl/armel (0.25-4 to 0.25-4)
- Migration status for libnet-rawip-perl/armel (0.25-4 to 0.25-4): Will attempt migration (Any information below is purely informational)
- libnet-ssh2-perl/armel (0.74-1 to 0.74-1)
- Migration status for libnet-ssh2-perl/armel (0.74-1 to 0.74-1): Will attempt migration (Any information below is purely informational)
- libnet-ssleay-perl/armel (1.94-3 to 1.94-3)
- Migration status for libnet-ssleay-perl/armel (1.94-3 to 1.94-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libnetfilter-queue/armel (1.0.5-4 to 1.0.5-4)
- Migration status for libnetfilter-queue/armel (1.0.5-4 to 1.0.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libnfc/armel (1.8.0-3.1 to 1.8.0-3.1)
- Migration status for libnfc/armel (1.8.0-3.1 to 1.8.0-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libnfnetlink/armel (1.0.2-3 to 1.0.2-3)
- Migration status for libnfnetlink/armel (1.0.2-3 to 1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libnginx-mod-http-auth-pam/amd64 (1:1.5.5-3 to 1:1.5.5-3)
- Migration status for libnginx-mod-http-auth-pam/amd64 (1:1.5.5-3 to 1:1.5.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-auth-pam/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-auth-pam/arm64 (1:1.5.5-3 to 1:1.5.5-3)
- Migration status for libnginx-mod-http-auth-pam/arm64 (1:1.5.5-3 to 1:1.5.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-auth-pam/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-auth-pam/armel (1:1.5.5-3 to 1:1.5.5-3)
- Migration status for libnginx-mod-http-auth-pam/armel (1:1.5.5-3 to 1:1.5.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-auth-pam/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-auth-pam/armhf (1:1.5.5-3 to 1:1.5.5-3)
- Migration status for libnginx-mod-http-auth-pam/armhf (1:1.5.5-3 to 1:1.5.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-auth-pam/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-auth-pam/i386 (1:1.5.5-3 to 1:1.5.5-3)
- Migration status for libnginx-mod-http-auth-pam/i386 (1:1.5.5-3 to 1:1.5.5-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-auth-pam/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-auth-spnego/amd64 (1.1.3-1 to 1.1.3-1)
- Migration status for libnginx-mod-http-auth-spnego/amd64 (1.1.3-1 to 1.1.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-auth-spnego/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-auth-spnego/arm64 (1.1.3-1 to 1.1.3-1)
- Migration status for libnginx-mod-http-auth-spnego/arm64 (1.1.3-1 to 1.1.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-auth-spnego/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-auth-spnego/armhf (1.1.3-1 to 1.1.3-1)
- Migration status for libnginx-mod-http-auth-spnego/armhf (1.1.3-1 to 1.1.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-auth-spnego/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-auth-spnego/i386 (1.1.3-1 to 1.1.3-1)
- Migration status for libnginx-mod-http-auth-spnego/i386 (1.1.3-1 to 1.1.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-auth-spnego/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-brotli/amd64 (1.0.0~rc-6 to 1.0.0~rc-6)
- Migration status for libnginx-mod-http-brotli/amd64 (1.0.0~rc-6 to 1.0.0~rc-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-brotli/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-brotli/arm64 (1.0.0~rc-6 to 1.0.0~rc-6)
- Migration status for libnginx-mod-http-brotli/arm64 (1.0.0~rc-6 to 1.0.0~rc-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-brotli/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-brotli/armhf (1.0.0~rc-6 to 1.0.0~rc-6)
- Migration status for libnginx-mod-http-brotli/armhf (1.0.0~rc-6 to 1.0.0~rc-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-brotli/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-brotli/i386 (1.0.0~rc-6 to 1.0.0~rc-6)
- Migration status for libnginx-mod-http-brotli/i386 (1.0.0~rc-6 to 1.0.0~rc-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-brotli/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-cache-purge/amd64 (1:2.5.3-3 to 1:2.5.3-3)
- Migration status for libnginx-mod-http-cache-purge/amd64 (1:2.5.3-3 to 1:2.5.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-cache-purge/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-cache-purge/arm64 (1:2.5.3-3 to 1:2.5.3-3)
- Migration status for libnginx-mod-http-cache-purge/arm64 (1:2.5.3-3 to 1:2.5.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-cache-purge/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-cache-purge/armel (1:2.5.3-3 to 1:2.5.3-3)
- Migration status for libnginx-mod-http-cache-purge/armel (1:2.5.3-3 to 1:2.5.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-cache-purge/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-cache-purge/armhf (1:2.5.3-3 to 1:2.5.3-3)
- Migration status for libnginx-mod-http-cache-purge/armhf (1:2.5.3-3 to 1:2.5.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-cache-purge/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-cache-purge/i386 (1:2.5.3-3 to 1:2.5.3-3)
- Migration status for libnginx-mod-http-cache-purge/i386 (1:2.5.3-3 to 1:2.5.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-cache-purge/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-dav-ext/amd64 (1:3.0.0-6 to 1:3.0.0-6)
- Migration status for libnginx-mod-http-dav-ext/amd64 (1:3.0.0-6 to 1:3.0.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-dav-ext/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-dav-ext/arm64 (1:3.0.0-6 to 1:3.0.0-6)
- Migration status for libnginx-mod-http-dav-ext/arm64 (1:3.0.0-6 to 1:3.0.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-dav-ext/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-dav-ext/armel (1:3.0.0-6 to 1:3.0.0-6)
- Migration status for libnginx-mod-http-dav-ext/armel (1:3.0.0-6 to 1:3.0.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-dav-ext/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-dav-ext/armhf (1:3.0.0-6 to 1:3.0.0-6)
- Migration status for libnginx-mod-http-dav-ext/armhf (1:3.0.0-6 to 1:3.0.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-dav-ext/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-dav-ext/i386 (1:3.0.0-6 to 1:3.0.0-6)
- Migration status for libnginx-mod-http-dav-ext/i386 (1:3.0.0-6 to 1:3.0.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-dav-ext/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-echo/amd64 (1:0.63-7 to 1:0.63-7)
- Migration status for libnginx-mod-http-echo/amd64 (1:0.63-7 to 1:0.63-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-echo/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-echo/arm64 (1:0.63-7 to 1:0.63-7)
- Migration status for libnginx-mod-http-echo/arm64 (1:0.63-7 to 1:0.63-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-echo/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-echo/armel (1:0.63-7 to 1:0.63-7)
- Migration status for libnginx-mod-http-echo/armel (1:0.63-7 to 1:0.63-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-echo/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-echo/armhf (1:0.63-7 to 1:0.63-7)
- Migration status for libnginx-mod-http-echo/armhf (1:0.63-7 to 1:0.63-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-echo/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-echo/i386 (1:0.63-7 to 1:0.63-7)
- Migration status for libnginx-mod-http-echo/i386 (1:0.63-7 to 1:0.63-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-echo/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-fancyindex/amd64 (1:0.5.2-6 to 1:0.5.2-6)
- Migration status for libnginx-mod-http-fancyindex/amd64 (1:0.5.2-6 to 1:0.5.2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-fancyindex/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-fancyindex/arm64 (1:0.5.2-6 to 1:0.5.2-6)
- Migration status for libnginx-mod-http-fancyindex/arm64 (1:0.5.2-6 to 1:0.5.2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-fancyindex/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-fancyindex/armel (1:0.5.2-6 to 1:0.5.2-6)
- Migration status for libnginx-mod-http-fancyindex/armel (1:0.5.2-6 to 1:0.5.2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-fancyindex/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-fancyindex/armhf (1:0.5.2-6 to 1:0.5.2-6)
- Migration status for libnginx-mod-http-fancyindex/armhf (1:0.5.2-6 to 1:0.5.2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-fancyindex/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-fancyindex/i386 (1:0.5.2-6 to 1:0.5.2-6)
- Migration status for libnginx-mod-http-fancyindex/i386 (1:0.5.2-6 to 1:0.5.2-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-fancyindex/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-geoip2/amd64 (1:3.4-6 to 1:3.4-6)
- Migration status for libnginx-mod-http-geoip2/amd64 (1:3.4-6 to 1:3.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-geoip2/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-geoip2/arm64 (1:3.4-6 to 1:3.4-6)
- Migration status for libnginx-mod-http-geoip2/arm64 (1:3.4-6 to 1:3.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-geoip2/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-geoip2/armel (1:3.4-6 to 1:3.4-6)
- Migration status for libnginx-mod-http-geoip2/armel (1:3.4-6 to 1:3.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-geoip2/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-geoip2/armhf (1:3.4-6 to 1:3.4-6)
- Migration status for libnginx-mod-http-geoip2/armhf (1:3.4-6 to 1:3.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-geoip2/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-geoip2/i386 (1:3.4-6 to 1:3.4-6)
- Migration status for libnginx-mod-http-geoip2/i386 (1:3.4-6 to 1:3.4-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-geoip2/i386 nginx (not considered)
- Invalidated by dependency
- (1:0.39-1 to 1:0.39-1)
- Migration status for libnginx-mod-http-headers-more-filter/amd64 (1:0.39-1 to 1:0.39-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-headers-more-filter/amd64 nginx (not considered)
- Invalidated by dependency
- (1:0.39-1 to 1:0.39-1)
- Migration status for libnginx-mod-http-headers-more-filter/arm64 (1:0.39-1 to 1:0.39-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-headers-more-filter/arm64 nginx (not considered)
- Invalidated by dependency
- (1:0.39-1 to 1:0.39-1)
- Migration status for libnginx-mod-http-headers-more-filter/armel (1:0.39-1 to 1:0.39-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-headers-more-filter/armel nginx (not considered)
- Invalidated by implicit-dependency
- (1:0.39-1 to 1:0.39-1)
- Migration status for libnginx-mod-http-headers-more-filter/armhf (1:0.39-1 to 1:0.39-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-headers-more-filter/armhf nginx (not considered)
- Invalidated by dependency
- (1:0.39-1 to 1:0.39-1)
- Migration status for libnginx-mod-http-headers-more-filter/i386 (1:0.39-1 to 1:0.39-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-headers-more-filter/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-memc/amd64 (0.20-2 to 0.20-2)
- Migration status for libnginx-mod-http-memc/amd64 (0.20-2 to 0.20-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-memc/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-memc/arm64 (0.20-2 to 0.20-2)
- Migration status for libnginx-mod-http-memc/arm64 (0.20-2 to 0.20-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-memc/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-memc/armhf (0.20-2 to 0.20-2)
- Migration status for libnginx-mod-http-memc/armhf (0.20-2 to 0.20-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-memc/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-memc/i386 (0.20-2 to 0.20-2)
- Migration status for libnginx-mod-http-memc/i386 (0.20-2 to 0.20-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-memc/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-modsecurity/amd64 (1.0.3-2 to 1.0.3-2)
- Migration status for libnginx-mod-http-modsecurity/amd64 (1.0.3-2 to 1.0.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-modsecurity/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-modsecurity/arm64 (1.0.3-2 to 1.0.3-2)
- Migration status for libnginx-mod-http-modsecurity/arm64 (1.0.3-2 to 1.0.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-modsecurity/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-modsecurity/armhf (1.0.3-2 to 1.0.3-2)
- Migration status for libnginx-mod-http-modsecurity/armhf (1.0.3-2 to 1.0.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-modsecurity/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-modsecurity/i386 (1.0.3-2 to 1.0.3-2)
- Migration status for libnginx-mod-http-modsecurity/i386 (1.0.3-2 to 1.0.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-modsecurity/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-ndk/amd64 (1:0.3.4-2 to 1:0.3.4-2)
- Migration status for libnginx-mod-http-ndk/amd64 (1:0.3.4-2 to 1:0.3.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-ndk/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-ndk/arm64 (1:0.3.4-2 to 1:0.3.4-2)
- Migration status for libnginx-mod-http-ndk/arm64 (1:0.3.4-2 to 1:0.3.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-ndk/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-ndk/armel (1:0.3.4-2 to 1:0.3.4-2)
- Migration status for libnginx-mod-http-ndk/armel (1:0.3.4-2 to 1:0.3.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-ndk/armel libnginx-mod-http-lua (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-ndk/armhf (1:0.3.4-2 to 1:0.3.4-2)
- Migration status for libnginx-mod-http-ndk/armhf (1:0.3.4-2 to 1:0.3.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-ndk/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-ndk/i386 (1:0.3.4-2 to 1:0.3.4-2)
- Migration status for libnginx-mod-http-ndk/i386 (1:0.3.4-2 to 1:0.3.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-ndk/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-push-stream/amd64 (0.6.0+dfsg-4 to 0.6.0+dfsg-4)
- Migration status for libnginx-mod-http-push-stream/amd64 (0.6.0+dfsg-4 to 0.6.0+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-push-stream/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-push-stream/arm64 (0.6.0+dfsg-4 to 0.6.0+dfsg-4)
- Migration status for libnginx-mod-http-push-stream/arm64 (0.6.0+dfsg-4 to 0.6.0+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-push-stream/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-push-stream/armhf (0.6.0+dfsg-4 to 0.6.0+dfsg-4)
- Migration status for libnginx-mod-http-push-stream/armhf (0.6.0+dfsg-4 to 0.6.0+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-push-stream/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-push-stream/i386 (0.6.0+dfsg-4 to 0.6.0+dfsg-4)
- Migration status for libnginx-mod-http-push-stream/i386 (0.6.0+dfsg-4 to 0.6.0+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-push-stream/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-set-misc/amd64 (0.33-6 to 0.33-6)
- Migration status for libnginx-mod-http-set-misc/amd64 (0.33-6 to 0.33-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-set-misc/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-set-misc/arm64 (0.33-6 to 0.33-6)
- Migration status for libnginx-mod-http-set-misc/arm64 (0.33-6 to 0.33-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-set-misc/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-set-misc/armhf (0.33-6 to 0.33-6)
- Migration status for libnginx-mod-http-set-misc/armhf (0.33-6 to 0.33-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-set-misc/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-set-misc/i386 (0.33-6 to 0.33-6)
- Migration status for libnginx-mod-http-set-misc/i386 (0.33-6 to 0.33-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-set-misc/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-srcache-filter/amd64 (0.33-4 to 0.33-4)
- Migration status for libnginx-mod-http-srcache-filter/amd64 (0.33-4 to 0.33-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-srcache-filter/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-srcache-filter/arm64 (0.33-4 to 0.33-4)
- Migration status for libnginx-mod-http-srcache-filter/arm64 (0.33-4 to 0.33-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-srcache-filter/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-srcache-filter/armhf (0.33-4 to 0.33-4)
- Migration status for libnginx-mod-http-srcache-filter/armhf (0.33-4 to 0.33-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-srcache-filter/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-srcache-filter/i386 (0.33-4 to 0.33-4)
- Migration status for libnginx-mod-http-srcache-filter/i386 (0.33-4 to 0.33-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-srcache-filter/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-subs-filter/amd64 (1:0.6.4-7 to 1:0.6.4-7)
- Migration status for libnginx-mod-http-subs-filter/amd64 (1:0.6.4-7 to 1:0.6.4-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-subs-filter/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-subs-filter/arm64 (1:0.6.4-7 to 1:0.6.4-7)
- Migration status for libnginx-mod-http-subs-filter/arm64 (1:0.6.4-7 to 1:0.6.4-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-subs-filter/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-subs-filter/armel (1:0.6.4-7 to 1:0.6.4-7)
- Migration status for libnginx-mod-http-subs-filter/armel (1:0.6.4-7 to 1:0.6.4-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-subs-filter/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-subs-filter/armhf (1:0.6.4-7 to 1:0.6.4-7)
- Migration status for libnginx-mod-http-subs-filter/armhf (1:0.6.4-7 to 1:0.6.4-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-subs-filter/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-subs-filter/i386 (1:0.6.4-7 to 1:0.6.4-7)
- Migration status for libnginx-mod-http-subs-filter/i386 (1:0.6.4-7 to 1:0.6.4-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-subs-filter/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-uploadprogress/amd64 (1:0.9.4-2 to 1:0.9.4-2)
- Migration status for libnginx-mod-http-uploadprogress/amd64 (1:0.9.4-2 to 1:0.9.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-uploadprogress/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-uploadprogress/arm64 (1:0.9.4-2 to 1:0.9.4-2)
- Migration status for libnginx-mod-http-uploadprogress/arm64 (1:0.9.4-2 to 1:0.9.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-uploadprogress/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-uploadprogress/armel (1:0.9.4-2 to 1:0.9.4-2)
- Migration status for libnginx-mod-http-uploadprogress/armel (1:0.9.4-2 to 1:0.9.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-uploadprogress/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-uploadprogress/armhf (1:0.9.4-2 to 1:0.9.4-2)
- Migration status for libnginx-mod-http-uploadprogress/armhf (1:0.9.4-2 to 1:0.9.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-uploadprogress/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-uploadprogress/i386 (1:0.9.4-2 to 1:0.9.4-2)
- Migration status for libnginx-mod-http-uploadprogress/i386 (1:0.9.4-2 to 1:0.9.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-uploadprogress/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-upstream-fair/amd64 (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6)
- Migration status for libnginx-mod-http-upstream-fair/amd64 (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-upstream-fair/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-upstream-fair/arm64 (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6)
- Migration status for libnginx-mod-http-upstream-fair/arm64 (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-upstream-fair/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-upstream-fair/armel (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6)
- Migration status for libnginx-mod-http-upstream-fair/armel (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-http-upstream-fair/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-http-upstream-fair/armhf (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6)
- Migration status for libnginx-mod-http-upstream-fair/armhf (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-upstream-fair/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-http-upstream-fair/i386 (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6)
- Migration status for libnginx-mod-http-upstream-fair/i386 (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-upstream-fair/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-js/amd64 (0.8.9-1 to 0.8.9-1)
- Migration status for libnginx-mod-js/amd64 (0.8.9-1 to 0.8.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-js/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-js/arm64 (0.8.9-1 to 0.8.9-1)
- Migration status for libnginx-mod-js/arm64 (0.8.9-1 to 0.8.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-js/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-js/armhf (0.8.9-1 to 0.8.9-1)
- Migration status for libnginx-mod-js/armhf (0.8.9-1 to 0.8.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-js/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-js/i386 (0.8.9-1 to 0.8.9-1)
- Migration status for libnginx-mod-js/i386 (0.8.9-1 to 0.8.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-js/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-nchan/amd64 (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2)
- Migration status for libnginx-mod-nchan/amd64 (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-nchan/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-nchan/arm64 (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2)
- Migration status for libnginx-mod-nchan/arm64 (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-nchan/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-nchan/armel (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2)
- Migration status for libnginx-mod-nchan/armel (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libnginx-mod-nchan/armel nginx (not considered)
- Invalidated by implicit-dependency
- libnginx-mod-nchan/armhf (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2)
- Migration status for libnginx-mod-nchan/armhf (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-nchan/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-nchan/i386 (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2)
- Migration status for libnginx-mod-nchan/i386 (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-nchan/i386 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-rtmp/amd64 (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-6)
- Migration status for libnginx-mod-rtmp/amd64 (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-rtmp/amd64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-rtmp/arm64 (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-6)
- Migration status for libnginx-mod-rtmp/arm64 (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-rtmp/arm64 nginx (not considered)
- Invalidated by dependency
- libnginx-mod-rtmp/armhf (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-6)
- Migration status for libnginx-mod-rtmp/armhf (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-rtmp/armhf nginx (not considered)
- Invalidated by dependency
- libnginx-mod-rtmp/i386 (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-6)
- Migration status for libnginx-mod-rtmp/i386 (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-rtmp/i386 nginx (not considered)
- Invalidated by dependency
- libnl3/armel (3.7.0-2 to 3.7.0-2)
- Migration status for libnl3/armel (3.7.0-2 to 3.7.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libogg/armel (1.3.6-1 to 1.3.6-1)
- Migration status for libogg/armel (1.3.6-1 to 1.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libpackage-stash-xs-perl/armel (0.30-1 to 0.30-1)
- Migration status for libpackage-stash-xs-perl/armel (0.30-1 to 0.30-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libpaper/armel (2.2.5-0.3 to 2.2.5-0.3)
- Migration status for libpaper/armel (2.2.5-0.3 to 2.2.5-0.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libparams-classify-perl/armel (0.015-2 to 0.015-2)
- Migration status for libparams-classify-perl/armel (0.015-2 to 0.015-2): Will attempt migration (Any information below is purely informational)
- libparams-util-perl/armel (1.102-3 to 1.102-3)
- Migration status for libparams-util-perl/armel (1.102-3 to 1.102-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libparams-validate-perl/armel (1.31-2 to 1.31-2)
- Migration status for libparams-validate-perl/armel (1.31-2 to 1.31-2): Will attempt migration (Any information below is purely informational)
- libpcap/armel (1.10.5-2 to 1.10.5-2)
- Migration status for libpcap/armel (1.10.5-2 to 1.10.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libpciaccess/armel (0.17-3 to 0.17-3)
- Migration status for libpciaccess/armel (0.17-3 to 0.17-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libpeas/armel (1.36.0-4 to 1.36.0-4)
- Migration status for libpeas/armel (1.36.0-4 to 1.36.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libplasma/armel (6.3.5-1 to 6.3.5-1)
- Migration status for libplasma/armel (6.3.5-1 to 6.3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libpng1.6/armel (1.6.50-1 to 1.6.50-1)
- Migration status for libpng1.6/armel (1.6.50-1 to 1.6.50-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libpsl/armel (0.21.2-1.1 to 0.21.2-1.1)
- Migration status for libpsl/armel (0.21.2-1.1 to 0.21.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libpst/armel (0.6.76-1.2 to 0.6.76-1.2)
- Migration status for libpst/armel (0.6.76-1.2 to 0.6.76-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libqcow/armel (20240308-1 to 20240308-1)
- Migration status for libqcow/armel (20240308-1 to 20240308-1): Will attempt migration (Any information below is purely informational)
- libqmi/armel (1.36.0-1 to 1.36.0-1)
- Migration status for libqmi/armel (1.36.0-1 to 1.36.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libqrtr-glib/armel (1.2.2-1 to 1.2.2-1)
- Migration status for libqrtr-glib/armel (1.2.2-1 to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- librabbitmq/armel (0.15.0-1 to 0.15.0-1)
- Migration status for librabbitmq/armel (0.15.0-1 to 0.15.0-1): Will attempt migration (Any information below is purely informational)
- libraw/armel (0.21.4-2 to 0.21.4-2)
- Migration status for libraw/armel (0.21.4-2 to 0.21.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libregf/armel (20240421-1 to 20240421-1)
- Migration status for libregf/armel (20240421-1 to 20240421-1): Will attempt migration (Any information below is purely informational)
- librsvg/armel (2.60.0+dfsg-1 to 2.60.0+dfsg-1)
- Migration status for librsvg/armel (2.60.0+dfsg-1 to 2.60.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- librttopo/armel (1.1.0-4 to 1.1.0-4)
- Migration status for librttopo/armel (1.1.0-4 to 1.1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libscca/armel (20200717-2 to 20200717-2)
- Migration status for libscca/armel (20200717-2 to 20200717-2): Will attempt migration (Any information below is purely informational)
- libseccomp/armel (2.6.0-2 to 2.6.0-2)
- Migration status for libseccomp/armel (2.6.0-2 to 2.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libsecret/armel (0.21.7-1 to 0.21.7-1)
- Migration status for libsecret/armel (0.21.7-1 to 0.21.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libselinux/armel (3.8.1-1 to 3.8.1-1)
- Migration status for libselinux/armel (3.8.1-1 to 3.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libsepol/armel (3.8.1-1 to 3.8.1-1)
- Migration status for libsepol/armel (3.8.1-1 to 3.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libsigscan/armel (20240505-1 to 20240505-1)
- Migration status for libsigscan/armel (20240505-1 to 20240505-1): Will attempt migration (Any information below is purely informational)
- libsm/armel (2:1.2.6-1 to 2:1.2.6-1)
- Migration status for libsm/armel (2:1.2.6-1 to 2:1.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libsmdev/armel (20190315-3 to 20190315-3)
- Migration status for libsmdev/armel (20190315-3 to 20190315-3): Will attempt migration (Any information below is purely informational)
- libsmraw/armel (20240506-1 to 20240506-1)
- Migration status for libsmraw/armel (20240506-1 to 20240506-1): Will attempt migration (Any information below is purely informational)
- libsndfile/armel (1.2.2-2 to 1.2.2-2)
- Migration status for libsndfile/armel (1.2.2-2 to 1.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libsocket6-perl/armel (0.29-3 to 0.29-3)
- Migration status for libsocket6-perl/armel (0.29-3 to 0.29-3): Will attempt migration (Any information below is purely informational)
- libspectre/armel (0.2.12-1 to 0.2.12-1)
- Migration status for libspectre/armel (0.2.12-1 to 0.2.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libspelling/armel (0.4.8-1 to 0.4.8-1)
- Migration status for libspelling/armel (0.4.8-1 to 0.4.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: libspelling/armel dialect (not considered)
- Invalidated by implicit-dependency
- libssh/armel (0.11.2-1 to 0.11.2-1)
- Migration status for libssh/armel (0.11.2-1 to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libssh2/armel (1.11.1-1 to 1.11.1-1)
- Migration status for libssh2/armel (1.11.1-1 to 1.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libstring-crc32-perl/armel (2.100-2 to 2.100-2)
- Migration status for libstring-crc32-perl/armel (2.100-2 to 2.100-2): Will attempt migration (Any information below is purely informational)
- libsub-identify-perl/armel (0.14-3 to 0.14-3)
- Migration status for libsub-identify-perl/armel (0.14-3 to 0.14-3): Will attempt migration (Any information below is purely informational)
- libsub-name-perl/armel (0.28-1 to 0.28-1)
- Migration status for libsub-name-perl/armel (0.28-1 to 0.28-1): Will attempt migration (Any information below is purely informational)
- libsys-virt-perl/armel (11.1.0-1 to 11.1.0-1)
- Migration status for libsys-virt-perl/armel (11.1.0-1 to 11.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libtasn1-6/armel (4.20.0-2 to 4.20.0-2)
- Migration status for libtasn1-6/armel (4.20.0-2 to 4.20.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libterm-readline-gnu-perl/armel (1.47-1 to 1.47-1)
- Migration status for libterm-readline-gnu-perl/armel (1.47-1 to 1.47-1): Will attempt migration (Any information below is purely informational)
- libtext-charwidth-perl/armel (0.04-11 to 0.04-11)
- Migration status for libtext-charwidth-perl/armel (0.04-11 to 0.04-11): Will attempt migration (Any information below is purely informational)
- libtext-iconv-perl/armel (1.7-8 to 1.7-8)
- Migration status for libtext-iconv-perl/armel (1.7-8 to 1.7-8): Will attempt migration (Any information below is purely informational)
- libtextwrap/armel (0.1-17 to 0.1-17)
- Migration status for libtextwrap/armel (0.1-17 to 0.1-17): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libthai/armel (0.1.29-2 to 0.1.29-2)
- Migration status for libthai/armel (0.1.29-2 to 0.1.29-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libtheora/armel (1.2.0~alpha1+dfsg-6 to 1.2.0~alpha1+dfsg-6)
- Migration status for libtheora/armel (1.2.0~alpha1+dfsg-6 to 1.2.0~alpha1+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libtirpc/armel (1.3.6+ds-1 to 1.3.6+ds-1)
- Migration status for libtirpc/armel (1.3.6+ds-1 to 1.3.6+ds-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: libtirpc/armel zfs-linux (not considered)
- Invalidated by implicit-dependency
- libtool/armel (2.5.4-4 to 2.5.4-4)
- Migration status for libtool/armel (2.5.4-4 to 2.5.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libunibreak/armel (6.1-3 to 6.1-3)
- Migration status for libunibreak/armel (6.1-3 to 6.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libunwind/armel (1.8.1-0.1 to 1.8.1-0.1)
- Migration status for libunwind/armel (1.8.1-0.1 to 1.8.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- liburcu/armel (0.15.3-1 to 0.15.3-1)
- Migration status for liburcu/armel (0.15.3-1 to 0.15.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- liburing/armel (2.11-1 to 2.11-1)
- Migration status for liburing/armel (2.11-1 to 2.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libusb-1.0/armel (2:1.0.29-2 to 2:1.0.29-2)
- Migration status for libusb-1.0/armel (2:1.0.29-2 to 2:1.0.29-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libusb/armel (2:0.1.12-35 to 2:0.1.12-35)
- Migration status for libusb/armel (2:0.1.12-35 to 2:0.1.12-35): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libuuid-perl/armel (0.37-1 to 0.37-1)
- Migration status for libuuid-perl/armel (0.37-1 to 0.37-1): Will attempt migration (Any information below is purely informational)
- libvariable-magic-perl/armel (0.64-1 to 0.64-1)
- Migration status for libvariable-magic-perl/armel (0.64-1 to 0.64-1): Will attempt migration (Any information below is purely informational)
- libverto/armel (0.3.1-1.2 to 0.3.1-1.2)
- Migration status for libverto/armel (0.3.1-1.2 to 0.3.1-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libvhdi/armel (20240509-2 to 20240509-2)
- Migration status for libvhdi/armel (20240509-2 to 20240509-2): Will attempt migration (Any information below is purely informational)
- libvmdk/armel (20240510-1 to 20240510-1)
- Migration status for libvmdk/armel (20240510-1 to 20240510-1): Will attempt migration (Any information below is purely informational)
- libvorbis/armel (1.3.7-3 to 1.3.7-3)
- Migration status for libvorbis/armel (1.3.7-3 to 1.3.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libvpx/armel (1.15.2-2 to 1.15.2-2)
- Migration status for libvpx/armel (1.15.2-2 to 1.15.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libvshadow/armel (20240504-1 to 20240504-1)
- Migration status for libvshadow/armel (20240504-1 to 20240504-1): Will attempt migration (Any information below is purely informational)
- libvslvm/armel (20240504-1 to 20240504-1)
- Migration status for libvslvm/armel (20240504-1 to 20240504-1): Will attempt migration (Any information below is purely informational)
- libwacom/armel (2.16.1-1 to 2.16.1-1)
- Migration status for libwacom/armel (2.16.1-1 to 2.16.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libwebp/armel (1.5.0-0.1 to 1.5.0-0.1)
- Migration status for libwebp/armel (1.5.0-0.1 to 1.5.0-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libwmf/armel (0.2.13-1.1 to 0.2.13-1.1)
- Migration status for libwmf/armel (0.2.13-1.1 to 0.2.13-1.1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: libwmf/armel imagemagick (not considered)
- Invalidated by implicit-dependency
- libx11/armel (2:1.8.12-1 to 2:1.8.12-1)
- Migration status for libx11/armel (2:1.8.12-1 to 2:1.8.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxau/armel (1:1.0.11-1 to 1:1.0.11-1)
- Migration status for libxau/armel (1:1.0.11-1 to 1:1.0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxcb/armel (1.17.0-2 to 1.17.0-2)
- Migration status for libxcb/armel (1.17.0-2 to 1.17.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxcomposite/armel (1:0.4.6-1 to 1:0.4.6-1)
- Migration status for libxcomposite/armel (1:0.4.6-1 to 1:0.4.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxcrypt/armel (1:4.4.38-1 to 1:4.4.38-1)
- Migration status for libxcrypt/armel (1:4.4.38-1 to 1:4.4.38-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxcursor/armel (1:1.2.3-1 to 1:1.2.3-1)
- Migration status for libxcursor/armel (1:1.2.3-1 to 1:1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxcvt/armel (0.1.3-1 to 0.1.3-1)
- Migration status for libxcvt/armel (0.1.3-1 to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxdamage/armel (1:1.1.6-1 to 1:1.1.6-1)
- Migration status for libxdamage/armel (1:1.1.6-1 to 1:1.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxdmcp/armel (1:1.1.5-1 to 1:1.1.5-1)
- Migration status for libxdmcp/armel (1:1.1.5-1 to 1:1.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxext/armel (2:1.3.4-1 to 2:1.3.4-1)
- Migration status for libxext/armel (2:1.3.4-1 to 2:1.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxfce4ui/armel (4.20.1-1 to 4.20.1-1)
- Migration status for libxfce4ui/armel (4.20.1-1 to 4.20.1-1): Will attempt migration (Any information below is purely informational)
- libxfce4util/armel (4.20.1-1 to 4.20.1-1)
- Migration status for libxfce4util/armel (4.20.1-1 to 4.20.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxfixes/armel (1:6.0.0-2 to 1:6.0.0-2)
- Migration status for libxfixes/armel (1:6.0.0-2 to 1:6.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxfont/armel (1:2.0.6-1 to 1:2.0.6-1)
- Migration status for libxfont/armel (1:2.0.6-1 to 1:2.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxi/armel (2:1.8.2-1 to 2:1.8.2-1)
- Migration status for libxi/armel (2:1.8.2-1 to 2:1.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxinerama/armel (2:1.1.4-3 to 2:1.1.4-3)
- Migration status for libxinerama/armel (2:1.1.4-3 to 2:1.1.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxkbcommon/armel (1.7.0-2.1 to 1.7.0-2.1)
- Migration status for libxkbcommon/armel (1.7.0-2.1 to 1.7.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxkbfile/armel (1:1.1.0-1 to 1:1.1.0-1)
- Migration status for libxkbfile/armel (1:1.1.0-1 to 1:1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxklavier/armel (5.4-5 to 5.4-5)
- Migration status for libxklavier/armel (5.4-5 to 5.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxml-parser-perl/armel (2.47-1 to 2.47-1)
- Migration status for libxml-parser-perl/armel (2.47-1 to 2.47-1): Will attempt migration (Any information below is purely informational)
- libxml2/armel (2.14.5+dfsg-0.2 to 2.14.5+dfsg-0.2)
- Migration status for libxml2/armel (2.14.5+dfsg-0.2 to 2.14.5+dfsg-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxmlb/armel (0.3.23-1 to 0.3.23-1)
- Migration status for libxmlb/armel (0.3.23-1 to 0.3.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxmu/armel (2:1.1.3-3 to 2:1.1.3-3)
- Migration status for libxmu/armel (2:1.1.3-3 to 2:1.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxpm/armel (1:3.5.17-1 to 1:3.5.17-1)
- Migration status for libxpm/armel (1:3.5.17-1 to 1:3.5.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxrandr/armel (2:1.5.4-1 to 2:1.5.4-1)
- Migration status for libxrandr/armel (2:1.5.4-1 to 2:1.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxrender/armel (1:0.9.12-1 to 1:0.9.12-1)
- Migration status for libxrender/armel (1:0.9.12-1 to 1:0.9.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxshmfence/armel (1.3.3-1 to 1.3.3-1)
- Migration status for libxshmfence/armel (1.3.3-1 to 1.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxslt/armel (1.1.43-0.2 to 1.1.43-0.2)
- Migration status for libxslt/armel (1.1.43-0.2 to 1.1.43-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxss/armel (1:1.2.3-1 to 1:1.2.3-1)
- Migration status for libxss/armel (1:1.2.3-1 to 1:1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxstring-perl/armel (0.005-2 to 0.005-2)
- Migration status for libxstring-perl/armel (0.005-2 to 0.005-2): Will attempt migration (Any information below is purely informational)
- libxt/armel (1:1.2.1-1.2 to 1:1.2.1-1.2)
- Migration status for libxt/armel (1:1.2.1-1.2 to 1:1.2.1-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxtst/armel (2:1.2.5-1 to 2:1.2.5-1)
- Migration status for libxtst/armel (2:1.2.5-1 to 2:1.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libxxf86vm/armel (1:1.1.4-1 to 1:1.1.4-1)
- Migration status for libxxf86vm/armel (1:1.1.4-1 to 1:1.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libxxf86vm/armel rust-x11 (not considered)
- Invalidated by implicit-dependency
- libzip/armel (1.11.4-1 to 1.11.4-1)
- Migration status for libzip/armel (1.11.4-1 to 1.11.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- libzstd/armel (1.5.7+dfsg-1 to 1.5.7+dfsg-1)
- Migration status for libzstd/armel (1.5.7+dfsg-1 to 1.5.7+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lightdm/armel (1.32.0-6 to 1.32.0-6)
- Migration status for lightdm/armel (1.32.0-6 to 1.32.0-6): Will attempt migration (Any information below is purely informational)
- lighttpd/amd64 (1.4.79-2 to 1.4.79-2)
- Migration status for lighttpd/amd64 (1.4.79-2 to 1.4.79-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: lighttpd/amd64 wolfssl (not considered)
- Invalidated by dependency
- lighttpd/arm64 (1.4.79-2 to 1.4.79-2)
- Migration status for lighttpd/arm64 (1.4.79-2 to 1.4.79-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: lighttpd/arm64 wolfssl (not considered)
- Invalidated by dependency
- lighttpd/armhf (1.4.79-2 to 1.4.79-2)
- Migration status for lighttpd/armhf (1.4.79-2 to 1.4.79-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: lighttpd/armhf wolfssl (not considered)
- Invalidated by dependency
- lighttpd/i386 (1.4.79-2 to 1.4.79-2)
- Migration status for lighttpd/i386 (1.4.79-2 to 1.4.79-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: lighttpd/i386 wolfssl (not considered)
- Invalidated by dependency
- limesuite/armel (23.11.0+dfsg-3 to 23.11.0+dfsg-3)
- Migration status for limesuite/armel (23.11.0+dfsg-3 to 23.11.0+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- littler/armel (0.3.21-1 to 0.3.21-1)
- Migration status for littler/armel (0.3.21-1 to 0.3.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lksctp-tools/armel (1.0.21+dfsg-1 to 1.0.21+dfsg-1)
- Migration status for lksctp-tools/armel (1.0.21+dfsg-1 to 1.0.21+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- llvm-defaults/armel (0.63 to 0.63)
- Migration status for llvm-defaults/armel (0.63 to 0.63): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- llvm-toolchain-18/armel (1:18.1.8-18 to 1:18.1.8-18)
- Migration status for llvm-toolchain-18/armel (1:18.1.8-18 to 1:18.1.8-18): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing llvm-18/1:18.1.8-18+b2/armel from kali-rolling makes ghc/9.6.6-4/armel uninstallable
- llvm-toolchain-19/armel (1:19.1.7-3 to 1:19.1.7-3)
- Migration status for llvm-toolchain-19/armel (1:19.1.7-3 to 1:19.1.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lm-sensors/armel (1:3.6.2-2 to 1:3.6.2-2)
- Migration status for lm-sensors/armel (1:3.6.2-2 to 1:3.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- log4cxx/armel (1.4.0-1 to 1.4.0-1)
- Migration status for log4cxx/armel (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
- logrotate/armel (3.22.0-1 to 3.22.0-1)
- Migration status for logrotate/armel (3.22.0-1 to 3.22.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lomiri-app-launch/armel (0.1.12-1 to 0.1.12-1)
- Migration status for lomiri-app-launch/armel (0.1.12-1 to 0.1.12-1): Will attempt migration (Any information below is purely informational)
- loupe/armel (48.1-3 to 48.1-3)
- Migration status for loupe/armel (48.1-3 to 48.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lsof/armel (4.99.4+dfsg-2 to 4.99.4+dfsg-2)
- Migration status for lsof/armel (4.99.4+dfsg-2 to 4.99.4+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lsscsi/armel (0.32-2 to 0.32-2)
- Migration status for lsscsi/armel (0.32-2 to 0.32-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lua-filesystem/armel (1.8.0-3 to 1.8.0-3)
- Migration status for lua-filesystem/armel (1.8.0-3 to 1.8.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: lua-filesystem/armel corsix-th (not considered)
- Invalidated by implicit-dependency
- lua-lpeg/armel (1.1.0-2 to 1.1.0-2)
- Migration status for lua-lpeg/armel (1.1.0-2 to 1.1.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: lua-lpeg/armel corsix-th (not considered)
- Invalidated by implicit-dependency
- lua5.1/armel (5.1.5-11 to 5.1.5-11)
- Migration status for lua5.1/armel (5.1.5-11 to 5.1.5-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lua5.4/armel (5.4.8-1 to 5.4.8-1)
- Migration status for lua5.4/armel (5.4.8-1 to 5.4.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lvm2/armel (2.03.31-2 to 2.03.31-2)
- Migration status for lvm2/armel (2.03.31-2 to 2.03.31-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lwt-log/armel (1.1.2-4 to 1.1.2-4)
- Migration status for lwt-log/armel (1.1.2-4 to 1.1.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lwt/armel (5.9.1-1 to 5.9.1-1)
- Migration status for lwt/armel (5.9.1-1 to 5.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lxappearance-obconf/armel (0.2.4-1 to 0.2.4-1)
- Migration status for lxappearance-obconf/armel (0.2.4-1 to 0.2.4-1): Will attempt migration (Any information below is purely informational)
- lxappearance/armel (0.6.4-1 to 0.6.4-1)
- Migration status for lxappearance/armel (0.6.4-1 to 0.6.4-1): Will attempt migration (Any information below is purely informational)
- lxcfs/armel (6.0.5-1 to 6.0.5-1)
- Migration status for lxcfs/armel (6.0.5-1 to 6.0.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: lxcfs/armel incus (not considered)
- Invalidated by implicit-dependency
- lxhotkey/armel (0.1.2-1 to 0.1.2-1)
- Migration status for lxhotkey/armel (0.1.2-1 to 0.1.2-1): Will attempt migration (Any information below is purely informational)
- lxinput/armel (0.3.6-1 to 0.3.6-1)
- Migration status for lxinput/armel (0.3.6-1 to 0.3.6-1): Will attempt migration (Any information below is purely informational)
- lxml/armel (5.4.0-1 to 5.4.0-1)
- Migration status for lxml/armel (5.4.0-1 to 5.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lxpanel/armel (0.11.1-1 to 0.11.1-1)
- Migration status for lxpanel/armel (0.11.1-1 to 0.11.1-1): Will attempt migration (Any information below is purely informational)
- lxrandr/armel (0.3.3-1 to 0.3.3-1)
- Migration status for lxrandr/armel (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
- lxsession/armel (0.5.6-2 to 0.5.6-2)
- Migration status for lxsession/armel (0.5.6-2 to 0.5.6-2): Will attempt migration (Any information below is purely informational)
- lxterminal/armel (0.4.1-1 to 0.4.1-1)
- Migration status for lxterminal/armel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
- lz4/armel (1.10.0-4 to 1.10.0-4)
- Migration status for lz4/armel (1.10.0-4 to 1.10.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lzo2/armel (2.10-3 to 2.10-3)
- Migration status for lzo2/armel (2.10-3 to 2.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- lzop/armel (1.04-2 to 1.04-2)
- Migration status for lzop/armel (1.04-2 to 1.04-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- m2crypto/armel (0.42.0-3 to 0.42.0-3)
- Migration status for m2crypto/armel (0.42.0-3 to 0.42.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- m4/armel (1.4.19-8 to 1.4.19-8)
- Migration status for m4/armel (1.4.19-8 to 1.4.19-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mac-robber/armel (1.02-13 to 1.02-13)
- Migration status for mac-robber/armel (1.02-13 to 1.02-13): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- macchanger/armel (1.7.0-6 to 1.7.0-6)
- Migration status for macchanger/armel (1.7.0-6 to 1.7.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- magicrescue/armel (1.1.10+dfsg-2 to 1.1.10+dfsg-2)
- Migration status for magicrescue/armel (1.1.10+dfsg-2 to 1.1.10+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- make-dfsg/armel (4.4.1-2 to 4.4.1-2)
- Migration status for make-dfsg/armel (4.4.1-2 to 4.4.1-2): Will attempt migration (Any information below is purely informational)
- malcontent/armel (0.13.0-2 to 0.13.0-2)
- Migration status for malcontent/armel (0.13.0-2 to 0.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- man-db/armel (2.13.1-1 to 2.13.1-1)
- Migration status for man-db/armel (2.13.1-1 to 2.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- marco/armel (1.26.2-4.1 to 1.26.2-4.1)
- Migration status for marco/armel (1.26.2-4.1 to 1.26.2-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mariadb/armel (1:11.8.3-1 to 1:11.8.3-1)
- Migration status for mariadb/armel (1:11.8.3-1 to 1:11.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- markupsafe/armel (2.1.5-1 to 2.1.5-1)
- Migration status for markupsafe/armel (2.1.5-1 to 2.1.5-1): Will attempt migration (Any information below is purely informational)
- maskprocessor/armel (0.73+git20170609.1708898-4 to 0.73+git20170609.1708898-4)
- Migration status for maskprocessor/armel (0.73+git20170609.1708898-4 to 0.73+git20170609.1708898-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- masscan/armel (2:1.3.2+ds1-2 to 2:1.3.2+ds1-2)
- Migration status for masscan/armel (2:1.3.2+ds1-2 to 2:1.3.2+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mate-calc/armel (1.26.0-1 to 1.26.0-1)
- Migration status for mate-calc/armel (1.26.0-1 to 1.26.0-1): Will attempt migration (Any information below is purely informational)
- mate-control-center/armel (1.26.1-1.1 to 1.26.1-1.1)
- Migration status for mate-control-center/armel (1.26.1-1.1 to 1.26.1-1.1): Will attempt migration (Any information below is purely informational)
- mate-desktop/armel (1.26.2-1.2 to 1.26.2-1.2)
- Migration status for mate-desktop/armel (1.26.2-1.2 to 1.26.2-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- (1.26.1-1 to 1.26.1-1)
- Migration status for mate-menus/armel (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
- mate-panel/armel (1.27.1-4.1 to 1.27.1-4.1)
- Migration status for mate-panel/armel (1.27.1-4.1 to 1.27.1-4.1): Will attempt migration (Any information below is purely informational)
- mate-polkit/armel (1.26.1-4 to 1.26.1-4)
- Migration status for mate-polkit/armel (1.26.1-4 to 1.26.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mate-session-manager/armel (1.26.1-2 to 1.26.1-2)
- Migration status for mate-session-manager/armel (1.26.1-2 to 1.26.1-2): Will attempt migration (Any information below is purely informational)
- mate-settings-daemon/armel (1.26.1-1.2 to 1.26.1-1.2)
- Migration status for mate-settings-daemon/armel (1.26.1-1.2 to 1.26.1-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mate-system-monitor/armel (1.26.3-1 to 1.26.3-1)
- Migration status for mate-system-monitor/armel (1.26.3-1 to 1.26.3-1): Will attempt migration (Any information below is purely informational)
- mate-terminal/armel (1.26.1-1 to 1.26.1-1)
- Migration status for mate-terminal/armel (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
- mate-utils/armel (1.26.1-1 to 1.26.1-1)
- Migration status for mate-utils/armel (1.26.1-1 to 1.26.1-1): Will attempt migration (Any information below is purely informational)
- matplotlib/armel (3.10.1+dfsg1-4 to 3.10.1+dfsg1-4)
- Migration status for matplotlib/armel (3.10.1+dfsg1-4 to 3.10.1+dfsg1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mawk/armel (1.3.4.20250131-1 to 1.3.4.20250131-1)
- Migration status for mawk/armel (1.3.4.20250131-1 to 1.3.4.20250131-1): Will attempt migration (Any information below is purely informational)
- mbedtls/armel (3.6.4-2 to 3.6.4-2)
- Migration status for mbedtls/armel (3.6.4-2 to 3.6.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mc/armel (3:4.8.33-1 to 3:4.8.33-1)
- Migration status for mc/armel (3:4.8.33-1 to 3:4.8.33-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mdadm/armel (4.4-11 to 4.4-11)
- Migration status for mdadm/armel (4.4-11 to 4.4-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mdbtools/armel (1.0.1-0.1 to 1.0.1-0.1)
- Migration status for mdbtools/armel (1.0.1-0.1 to 1.0.1-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mdk3/armel (6.0-9 to 6.0-9)
- Migration status for mdk3/armel (6.0-9 to 6.0-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mdk4/armel (4.2-5 to 4.2-5)
- Migration status for mdk4/armel (4.2-5 to 4.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mecab/armel (0.996-15.1 to 0.996-15.1)
- Migration status for mecab/armel (0.996-15.1 to 0.996-15.1): Will attempt migration (Any information below is purely informational)
- medusa/armel (2.3-2 to 2.3-2)
- Migration status for medusa/armel (2.3-2 to 2.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- megapixels/armel (1.8.3-1 to 1.8.3-1)
- Migration status for megapixels/armel (1.8.3-1 to 1.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- memdump/armel (1.01-9 to 1.01-9)
- Migration status for memdump/armel (1.01-9 to 1.01-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- menhir/armel (20240715+ds-1 to 20240715+ds-1)
- Migration status for menhir/armel (20240715+ds-1 to 20240715+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mercurial/armel (7.0.1-2 to 7.0.1-2)
- Migration status for mercurial/armel (7.0.1-2 to 7.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mesa-demos/armel (9.0.0-2 to 9.0.0-2)
- Migration status for mesa-demos/armel (9.0.0-2 to 9.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mesa/armel (25.0.7-2 to 25.0.7-2)
- Migration status for mesa/armel (25.0.7-2 to 25.0.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- metacam/armel (1.2-14 to 1.2-14)
- Migration status for metacam/armel (1.2-14 to 1.2-14): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mfcuk/armel (0.3.8+git20180720-2 to 0.3.8+git20180720-2)
- Migration status for mfcuk/armel (0.3.8+git20180720-2 to 0.3.8+git20180720-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mfoc/armel (0.10.7+git20180724-2 to 0.10.7+git20180724-2)
- Migration status for mfoc/armel (0.10.7+git20180724-2 to 0.10.7+git20180724-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- milou/armel (4:6.3.5-1 to 4:6.3.5-1)
- Migration status for milou/armel (4:6.3.5-1 to 4:6.3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mingw-w64/armel (12.0.0-5 to 12.0.0-5)
- Migration status for mingw-w64/armel (12.0.0-5 to 12.0.0-5): Will attempt migration (Any information below is purely informational)
- minicom/armel (2.10-1 to 2.10-1)
- Migration status for minicom/armel (2.10-1 to 2.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- minisat2/armel (1:2.2.1-8 to 1:2.2.1-8)
- Migration status for minisat2/armel (1:2.2.1-8 to 1:2.2.1-8): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: minisat2/armel link-grammar (not considered)
- Invalidated by implicit-dependency
- miredo/armel (1.2.6-7.2 to 1.2.6-7.2)
- Migration status for miredo/armel (1.2.6-7.2 to 1.2.6-7.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- missidentify/armel (1.0-11 to 1.0-11)
- Migration status for missidentify/armel (1.0-11 to 1.0-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- modemmanager/armel (1.24.2-1 to 1.24.2-1)
- Migration status for modemmanager/armel (1.24.2-1 to 1.24.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mongo-c-driver/armel (2.1.0-1 to 2.1.0-1)
- Migration status for mongo-c-driver/armel (2.1.0-1 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mono/armel (6.14.1+ds-6 to 6.14.1+ds-6)
- Migration status for mono/armel (6.14.1+ds-6 to 6.14.1+ds-6): Will attempt migration (Any information below is purely informational)
- moreutils/armel (0.69-1 to 0.69-1)
- Migration status for moreutils/armel (0.69-1 to 0.69-1): Will attempt migration (Any information below is purely informational)
- mousepad/armel (0.6.3-1 to 0.6.3-1)
- Migration status for mousepad/armel (0.6.3-1 to 0.6.3-1): Will attempt migration (Any information below is purely informational)
- mpclib3/armel (1.3.1-1 to 1.3.1-1)
- Migration status for mpclib3/armel (1.3.1-1 to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mpfr4/armel (4.2.2-1 to 4.2.2-1)
- Migration status for mpfr4/armel (4.2.2-1 to 4.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mpg123/armel (1.33.2-1 to 1.33.2-1)
- Migration status for mpg123/armel (1.33.2-1 to 1.33.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mpi-defaults/armel (1.18 to 1.18)
- Migration status for mpi-defaults/armel (1.18 to 1.18): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mpich/armel (4.3.0+really4.2.1-1 to 4.3.0+really4.2.1-1)
- Migration status for mpich/armel (4.3.0+really4.2.1-1 to 4.3.0+really4.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- msitools/armel (0.106+repack-2 to 0.106+repack-2)
- Migration status for msitools/armel (0.106+repack-2 to 0.106+repack-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mtdev/armel (1.1.7-1 to 1.1.7-1)
- Migration status for mtdev/armel (1.1.7-1 to 1.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mtools/armel (4.0.49-1 to 4.0.49-1)
- Migration status for mtools/armel (4.0.49-1 to 4.0.49-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- multimon-ng/armel (1.3.1+dfsg-1 to 1.3.1+dfsg-1)
- Migration status for multimon-ng/armel (1.3.1+dfsg-1 to 1.3.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- muparser/armel (2.3.4-1 to 2.3.4-1)
- Migration status for muparser/armel (2.3.4-1 to 2.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- myrescue/armel (0.9.8-3 to 0.9.8-3)
- Migration status for myrescue/armel (0.9.8-3 to 0.9.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- mysql-defaults/armel (1.1.1 to 1.1.1)
- Migration status for mysql-defaults/armel (1.1.1 to 1.1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nano/armel (8.6-1 to 8.6-1)
- Migration status for nano/armel (8.6-1 to 8.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nasm/armel (2.16.03-1 to 2.16.03-1)
- Migration status for nasm/armel (2.16.03-1 to 2.16.03-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nasty/armel (0.6+git20220929.9830b7a-2 to 0.6+git20220929.9830b7a-2)
- Migration status for nasty/armel (0.6+git20220929.9830b7a-2 to 0.6+git20220929.9830b7a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nbtscan/armel (1.7.2-3 to 1.7.2-3)
- Migration status for nbtscan/armel (1.7.2-3 to 1.7.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ncrack/armel (0.7+debian-6 to 0.7+debian-6)
- Migration status for ncrack/armel (0.7+debian-6 to 0.7+debian-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ncurses-hexedit/armel (0.9.7+orig-7.3 to 0.9.7+orig-7.3)
- Migration status for ncurses-hexedit/armel (0.9.7+orig-7.3 to 0.9.7+orig-7.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ncurses/armel (6.5+20250216-2 to 6.5+20250216-2)
- Migration status for ncurses/armel (6.5+20250216-2 to 6.5+20250216-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- net-snmp/armel (5.9.4+dfsg-2 to 5.9.4+dfsg-2)
- Migration status for net-snmp/armel (5.9.4+dfsg-2 to 5.9.4+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- net-tools/armel (2.10-1.3 to 2.10-1.3)
- Migration status for net-tools/armel (2.10-1.3 to 2.10-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- netcat/armel (1.10-50 to 1.10-50)
- Migration status for netcat/armel (1.10-50 to 1.10-50): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- netcdf/armel (1:4.9.3-1 to 1:4.9.3-1)
- Migration status for netcdf/armel (1:4.9.3-1 to 1:4.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- netdiscover/armel (0.21-1 to 0.21-1)
- Migration status for netdiscover/armel (0.21-1 to 0.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- netifaces/armel (0.11.0-2 to 0.11.0-2)
- Migration status for netifaces/armel (0.11.0-2 to 0.11.0-2): Will attempt migration (Any information below is purely informational)
- netkit-ftp-ssl/armel (0.17.34+really0.17-2 to 0.17.34+really0.17-2)
- Migration status for netkit-ftp-ssl/armel (0.17.34+really0.17-2 to 0.17.34+really0.17-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- netmask/armel (2.5.0-1 to 2.5.0-1)
- Migration status for netmask/armel (2.5.0-1 to 2.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- netpbm-free/armel (2:11.11.00-2 to 2:11.11.00-2)
- Migration status for netpbm-free/armel (2:11.11.00-2 to 2:11.11.00-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- netsed/armel (1.4-1 to 1.4-1)
- Migration status for netsed/armel (1.4-1 to 1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nettle/armel (3.10.1-1 to 3.10.1-1)
- Migration status for nettle/armel (3.10.1-1 to 3.10.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- netw-ib-ox-ag/armel (5.39.0+dfsg-0.1 to 5.39.0+dfsg-0.1)
- Migration status for netw-ib-ox-ag/armel (5.39.0+dfsg-0.1 to 5.39.0+dfsg-0.1): Will attempt migration (Any information below is purely informational)
- network-manager-applet/armel (1.36.0-4 to 1.36.0-4)
- Migration status for network-manager-applet/armel (1.36.0-4 to 1.36.0-4): Will attempt migration (Any information below is purely informational)
- network-manager/armel (1.54.0-4 to 1.54.0-4)
- Migration status for network-manager/armel (1.54.0-4 to 1.54.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- newt/armel (0.52.25-1 to 0.52.25-1)
- Migration status for newt/armel (0.52.25-1 to 0.52.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nfs-utils/armel (1:2.8.3-1 to 1:2.8.3-1)
- Migration status for nfs-utils/armel (1:2.8.3-1 to 1:2.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nftables/armel (1.1.3-1 to 1.1.3-1)
- Migration status for nftables/armel (1.1.3-1 to 1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nghttp2/armel (1.64.0-1.1 to 1.64.0-1.1)
- Migration status for nghttp2/armel (1.64.0-1.1 to 1.64.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nghttp3/armel (1.8.0-1 to 1.8.0-1)
- Migration status for nghttp3/armel (1.8.0-1 to 1.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ngrep/armel (1.47+ds1-6 to 1.47+ds1-6)
- Migration status for ngrep/armel (1.47+ds1-6 to 1.47+ds1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ngtcp2/armel (1.11.0-1 to 1.11.0-1)
- Migration status for ngtcp2/armel (1.11.0-1 to 1.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nickle/armel (2.103 to 2.103)
- Migration status for nickle/armel (2.103 to 2.103): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: nickle/armel altos (not considered)
- Invalidated by implicit-dependency
- nilfs-tools/armel (2.2.11-2 to 2.2.11-2)
- Migration status for nilfs-tools/armel (2.2.11-2 to 2.2.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nitrogen/armel (1.6.1-2 to 1.6.1-2)
- Migration status for nitrogen/armel (1.6.1-2 to 1.6.1-2): Will attempt migration (Any information below is purely informational)
- nspr/armel (2:4.36-1 to 2:4.36-1)
- Migration status for nspr/armel (2:4.36-1 to 2:4.36-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- nss/armel (2:3.114-1 to 2:3.114-1)
- Migration status for nss/armel (2:3.114-1 to 2:3.114-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ntfs-3g/armel (1:2022.10.3-5 to 1:2022.10.3-5)
- Migration status for ntfs-3g/armel (1:2022.10.3-5 to 1:2022.10.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ntpsec/armel (1.2.3+dfsg1-8 to 1.2.3+dfsg1-8)
- Migration status for ntpsec/armel (1.2.3+dfsg1-8 to 1.2.3+dfsg1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- numactl/armel (2.0.19-1 to 2.0.19-1)
- Migration status for numactl/armel (2.0.19-1 to 2.0.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- numcodecs/armel (0.16.2+ds-2 to 0.16.2+ds-2)
- Migration status for numcodecs/armel (0.16.2+ds-2 to 0.16.2+ds-2): Will attempt migration (Any information below is purely informational)
- numlockx/armel (1.2-10 to 1.2-10)
- Migration status for numlockx/armel (1.2-10 to 1.2-10): Will attempt migration (Any information below is purely informational)
- numpy/armel (1:2.2.4+ds-1 to 1:2.2.4+ds-1)
- Migration status for numpy/armel (1:2.2.4+ds-1 to 1:2.2.4+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-alsa/armel (0.3.0-4 to 0.3.0-4)
- Migration status for ocaml-alsa/armel (0.3.0-4 to 0.3.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: ocaml-alsa/armel ocaml-mm (not considered)
- Invalidated by implicit-dependency
- ocaml-angstrom/armel (0.16.1-1 to 0.16.1-1)
- Migration status for ocaml-angstrom/armel (0.16.1-1 to 0.16.1-1): Will attempt migration (Any information below is purely informational)
- ocaml-ao/armel (0.2.4-3 to 0.2.4-3)
- Migration status for ocaml-ao/armel (0.2.4-3 to 0.2.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: ocaml-ao/armel ocaml-mm (not considered)
- Invalidated by implicit-dependency
- ocaml-bigstringaf/armel (0.10.0-1 to 0.10.0-1)
- Migration status for ocaml-bigstringaf/armel (0.10.0-1 to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-cstruct/armel (6.2.0-3 to 6.2.0-3)
- Migration status for ocaml-cstruct/armel (6.2.0-3 to 6.2.0-3): Will attempt migration (Any information below is purely informational)
- ocaml-domain-name/armel (0.4.1-1 to 0.4.1-1)
- Migration status for ocaml-domain-name/armel (0.4.1-1 to 0.4.1-1): Will attempt migration (Any information below is purely informational)
- ocaml-fmt/armel (0.11.0-1 to 0.11.0-1)
- Migration status for ocaml-fmt/armel (0.11.0-1 to 0.11.0-1): Will attempt migration (Any information below is purely informational)
- ocaml-gen/armel (1.1-1 to 1.1-1)
- Migration status for ocaml-gen/armel (1.1-1 to 1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-graphics/armel (5.2.0-2 to 5.2.0-2)
- Migration status for ocaml-graphics/armel (5.2.0-2 to 5.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-intrinsics-kernel/armel (0.17.1-1 to 0.17.1-1)
- Migration status for ocaml-intrinsics-kernel/armel (0.17.1-1 to 0.17.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-mad/armel (0.5.3-1 to 0.5.3-1)
- Migration status for ocaml-mad/armel (0.5.3-1 to 0.5.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: ocaml-mad/armel ocaml-mm (not considered)
- Invalidated by implicit-dependency
- ocaml-num/armel (1.6-1 to 1.6-1)
- Migration status for ocaml-num/armel (1.6-1 to 1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-parsexp/armel (0.17.0-1 to 0.17.0-1)
- Migration status for ocaml-parsexp/armel (0.17.0-1 to 0.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-pulseaudio/armel (0.1.5-3 to 0.1.5-3)
- Migration status for ocaml-pulseaudio/armel (0.1.5-3 to 0.1.5-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: ocaml-pulseaudio/armel ocaml-mm (not considered)
- Invalidated by implicit-dependency
- ocaml-re/armel (1.12.0+really1.11.0-1 to 1.12.0+really1.11.0-1)
- Migration status for ocaml-re/armel (1.12.0+really1.11.0-1 to 1.12.0+really1.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-sedlex/armel (3.6-1 to 3.6-1)
- Migration status for ocaml-sedlex/armel (3.6-1 to 3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-sexplib0/armel (0.17.0-1 to 0.17.0-1)
- Migration status for ocaml-sexplib0/armel (0.17.0-1 to 0.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocaml-ssl/armel (0.7.0-1 to 0.7.0-1)
- Migration status for ocaml-ssl/armel (0.7.0-1 to 0.7.0-1): Will attempt migration (Any information below is purely informational)
- ocaml-stringext/armel (1.6.0-3 to 1.6.0-3)
- Migration status for ocaml-stringext/armel (1.6.0-3 to 1.6.0-3): Will attempt migration (Any information below is purely informational)
- ocaml-xiph/armel (1.0.0-1 to 1.0.0-1)
- Migration status for ocaml-xiph/armel (1.0.0-1 to 1.0.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: ocaml-xiph/armel ocaml-mm (not considered)
- Invalidated by implicit-dependency
- ocaml/armel (5.3.0-3 to 5.3.0-3)
- Migration status for ocaml/armel (5.3.0-3 to 5.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ocplib-endian/armel (1.2-4 to 1.2-4)
- Migration status for ocplib-endian/armel (1.2-4 to 1.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- okular/armel (4:25.04.2-1 to 4:25.04.2-1)
- Migration status for okular/armel (4:25.04.2-1 to 4:25.04.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- omniorb-dfsg/armel (4.3.3+ds1-1 to 4.3.3+ds1-1)
- Migration status for omniorb-dfsg/armel (4.3.3+ds1-1 to 4.3.3+ds1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- onboard/armel (1.4.1-10 to 1.4.1-10)
- Migration status for onboard/armel (1.4.1-10 to 1.4.1-10): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- onesixtyone/armel (0.3.4-1 to 0.3.4-1)
- Migration status for onesixtyone/armel (0.3.4-1 to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- openbox/armel (3.6.1-12 to 3.6.1-12)
- Migration status for openbox/armel (3.6.1-12 to 3.6.1-12): Will attempt migration (Any information below is purely informational)
- openexr/armel (3.1.13-2 to 3.1.13-2)
- Migration status for openexr/armel (3.1.13-2 to 3.1.13-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: openexr/armel imagemagick (not considered)
- Invalidated by implicit-dependency
- openjdk-21/armel (21.0.8+9-1 to 21.0.8+9-1)
- Migration status for openjdk-21/armel (21.0.8+9-1 to 21.0.8+9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- openjpeg2/armel (2.5.3-2.1 to 2.5.3-2.1)
- Migration status for openjpeg2/armel (2.5.3-2.1 to 2.5.3-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- openldap/armel (2.6.10+dfsg-1 to 2.6.10+dfsg-1)
- Migration status for openldap/armel (2.6.10+dfsg-1 to 2.6.10+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- openocd/armel (0.12.0-3 to 0.12.0-3)
- Migration status for openocd/armel (0.12.0-3 to 0.12.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- opensmtpd/armel (7.7.0p0-1 to 7.7.0p0-1)
- Migration status for opensmtpd/armel (7.7.0p0-1 to 7.7.0p0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- openssh-ssh1/armel (1:7.5p1-17 to 1:7.5p1-17)
- Migration status for openssh-ssh1/armel (1:7.5p1-17 to 1:7.5p1-17): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- openssh/armel (1:10.0p1-8 to 1:10.0p1-8)
- Migration status for openssh/armel (1:10.0p1-8 to 1:10.0p1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- openssl/armel (3.5.2-1 to 3.5.2-1)
- Migration status for openssl/armel (3.5.2-1 to 3.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- openvpn/armel (2.6.14-1 to 2.6.14-1)
- Migration status for openvpn/armel (2.6.14-1 to 2.6.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ophcrack/armel (3.8.0-4 to 3.8.0-4)
- Migration status for ophcrack/armel (3.8.0-4 to 3.8.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- opus/armel (1.5.2-2 to 1.5.2-2)
- Migration status for opus/armel (1.5.2-2 to 1.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- orc/armel (1:0.4.41-1 to 1:0.4.41-1)
- Migration status for orc/armel (1:0.4.41-1 to 1:0.4.41-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- orcania/armel (2.3.3-1 to 2.3.3-1)
- Migration status for orcania/armel (2.3.3-1 to 2.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- os-prober/armel (1.83 to 1.83)
- Migration status for os-prober/armel (1.83 to 1.83): Will attempt migration (Any information below is purely informational)
- outguess/armel (1:0.4-2 to 1:0.4-2)
- Migration status for outguess/armel (1:0.4-2 to 1:0.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- p0f/armel (3.09b-4 to 3.09b-4)
- Migration status for p0f/armel (3.09b-4 to 3.09b-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- p11-kit/armel (0.25.5-3 to 0.25.5-3)
- Migration status for p11-kit/armel (0.25.5-3 to 0.25.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- packagekit/armel (1.3.1-1 to 1.3.1-1)
- Migration status for packagekit/armel (1.3.1-1 to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pam/armel (1.7.0-5 to 1.7.0-5)
- Migration status for pam/armel (1.7.0-5 to 1.7.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pandas/armel (2.2.3+dfsg-9 to 2.2.3+dfsg-9)
- Migration status for pandas/armel (2.2.3+dfsg-9 to 2.2.3+dfsg-9): Will attempt migration (Any information below is purely informational)
- pango1.0/armel (1.56.3-1 to 1.56.3-1)
- Migration status for pango1.0/armel (1.56.3-1 to 1.56.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- parted/armel (3.6-5 to 3.6-5)
- Migration status for parted/armel (3.6-5 to 3.6-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pasco/armel (20040505-4 to 20040505-4)
- Migration status for pasco/armel (20040505-4 to 20040505-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- patch/armel (2.8-2 to 2.8-2)
- Migration status for patch/armel (2.8-2 to 2.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- patchutils/armel (0.4.2-1 to 0.4.2-1)
- Migration status for patchutils/armel (0.4.2-1 to 0.4.2-1): Will attempt migration (Any information below is purely informational)
- pavucontrol/armel (6.1-1 to 6.1-1)
- Migration status for pavucontrol/armel (6.1-1 to 6.1-1): Will attempt migration (Any information below is purely informational)
- pcapy/armel (0.11.5-5 to 0.11.5-5)
- Migration status for pcapy/armel (0.11.5-5 to 0.11.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pciutils/armel (1:3.14.0-1 to 1:3.14.0-1)
- Migration status for pciutils/armel (1:3.14.0-1 to 1:3.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pcmanfm/armel (1.4.0-1 to 1.4.0-1)
- Migration status for pcmanfm/armel (1.4.0-1 to 1.4.0-1): Will attempt migration (Any information below is purely informational)
- pcsc-lite/armel (2.3.3-1 to 2.3.3-1)
- Migration status for pcsc-lite/armel (2.3.3-1 to 2.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pdfcrack/armel (0.20-1 to 0.20-1)
- Migration status for pdfcrack/armel (0.20-1 to 0.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- perl-openssl-defaults/armel (7 to 7)
- Migration status for perl-openssl-defaults/armel (7 to 7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- perl-tk/armel (1:804.036+dfsg1-5 to 1:804.036+dfsg1-5)
- Migration status for perl-tk/armel (1:804.036+dfsg1-5 to 1:804.036+dfsg1-5): Will attempt migration (Any information below is purely informational)
- perl/armel (5.40.1-6 to 5.40.1-6)
- Migration status for perl/armel (5.40.1-6 to 5.40.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- phoc/armel (0.46.0-1 to 0.46.0-1)
- Migration status for phoc/armel (0.46.0-1 to 0.46.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- phonon/armel (4:4.12.0-5 to 4:4.12.0-5)
- Migration status for phonon/armel (4:4.12.0-5 to 4:4.12.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- phosh-mobile-settings/armel (0.49.0-1 to 0.49.0-1)
- Migration status for phosh-mobile-settings/armel (0.49.0-1 to 0.49.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- phosh-osk-stevia/armel (0.49.0-2 to 0.49.0-2)
- Migration status for phosh-osk-stevia/armel (0.49.0-2 to 0.49.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- phosh-tour/armel (0.46.0-1 to 0.46.0-1)
- Migration status for phosh-tour/armel (0.46.0-1 to 0.46.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- phosh/armel (0.49.0-1 to 0.49.0-1)
- Migration status for phosh/armel (0.49.0-1 to 0.49.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- php8.4/armel (8.4.11-1 to 8.4.11-1)
- Migration status for php8.4/armel (8.4.11-1 to 8.4.11-1): Will attempt migration (Any information below is purely informational)
- phrog/armel (0.46.0-2 to 0.46.0-2)
- Migration status for phrog/armel (0.46.0-2 to 0.46.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- picom/armel (12.5-1 to 12.5-1)
- Migration status for picom/armel (12.5-1 to 12.5-1): Will attempt migration (Any information below is purely informational)
- pigpio/armel (1.78-1.1 to 1.78-1.1)
- Migration status for pigpio/armel (1.78-1.1 to 1.78-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pillow/armel (11.1.0-5 to 11.1.0-5)
- Migration status for pillow/armel (11.1.0-5 to 11.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pinentry/armel (1.3.2-3 to 1.3.2-3)
- Migration status for pinentry/armel (1.3.2-3 to 1.3.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pipewire/armel (1.4.7-3 to 1.4.7-3)
- Migration status for pipewire/armel (1.4.7-3 to 1.4.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pixiewps/armel (1.4.2-5 to 1.4.2-5)
- Migration status for pixiewps/armel (1.4.2-5 to 1.4.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pixman/armel (0.44.0-3 to 0.44.0-3)
- Migration status for pixman/armel (0.44.0-3 to 0.44.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pkgconf/armel (1.8.1-4 to 1.8.1-4)
- Migration status for pkgconf/armel (1.8.1-4 to 1.8.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- plasma-desktop/armel (4:6.3.6-1 to 4:6.3.6-1)
- Migration status for plasma-desktop/armel (4:6.3.6-1 to 4:6.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- plasma-integration/armel (6.3.6-1 to 6.3.6-1)
- Migration status for plasma-integration/armel (6.3.6-1 to 6.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- plasma-nm/armel (4:6.3.4-2 to 4:6.3.4-2)
- Migration status for plasma-nm/armel (4:6.3.4-2 to 4:6.3.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- plasma-systemmonitor/armel (6.3.6-1 to 6.3.6-1)
- Migration status for plasma-systemmonitor/armel (6.3.6-1 to 6.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- plasma-workspace/armel (4:6.3.6-2 to 4:6.3.6-2)
- Migration status for plasma-workspace/armel (4:6.3.6-2 to 4:6.3.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- plocate/armel (1.1.23-1 to 1.1.23-1)
- Migration status for plocate/armel (1.1.23-1 to 1.1.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pluma/armel (1.26.1-2.1 to 1.26.1-2.1)
- Migration status for pluma/armel (1.26.1-2.1 to 1.26.1-2.1): Will attempt migration (Any information below is purely informational)
- plymouth/armel (24.004.60-5 to 24.004.60-5)
- Migration status for plymouth/armel (24.004.60-5 to 24.004.60-5): Will attempt migration (Any information below is purely informational)
- pnscan/armel (1.14.1-2 to 1.14.1-2)
- Migration status for pnscan/armel (1.14.1-2 to 1.14.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- polkit-kde-agent-1/armel (4:6.3.6-1 to 4:6.3.6-1)
- Migration status for polkit-kde-agent-1/armel (4:6.3.6-1 to 4:6.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- polybar/armel (3.7.2-1 to 3.7.2-1)
- Migration status for polybar/armel (3.7.2-1 to 3.7.2-1): Will attempt migration (Any information below is purely informational)
- popt/armel (1.19+dfsg-2 to 1.19+dfsg-2)
- Migration status for popt/armel (1.19+dfsg-2 to 1.19+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- portaudio19/armel (19.6.0-1.2 to 19.6.0-1.2)
- Migration status for portaudio19/armel (19.6.0-1.2 to 19.6.0-1.2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: portaudio19/armel ocaml-portaudio (not considered)
- Invalidated by implicit-dependency
- ppx-derivers/armel (1.2.1-4 to 1.2.1-4)
- Migration status for ppx-derivers/armel (1.2.1-4 to 1.2.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ppxlib/armel (0.35.0-1 to 0.35.0-1)
- Migration status for ppxlib/armel (0.35.0-1 to 0.35.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- procps/armel (2:4.0.4-9 to 2:4.0.4-9)
- Migration status for procps/armel (2:4.0.4-9 to 2:4.0.4-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- proftpd-mod-autohost/amd64 (0.6-2 to 0.6-2)
- Migration status for proftpd-mod-autohost/amd64 (0.6-2 to 0.6-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-autohost/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-autohost/arm64 (0.6-2 to 0.6-2)
- Migration status for proftpd-mod-autohost/arm64 (0.6-2 to 0.6-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-autohost/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-autohost/armhf (0.6-2 to 0.6-2)
- Migration status for proftpd-mod-autohost/armhf (0.6-2 to 0.6-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-autohost/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-autohost/i386 (0.6-2 to 0.6-2)
- Migration status for proftpd-mod-autohost/i386 (0.6-2 to 0.6-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-autohost/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-case/amd64 (0.9.1-1 to 0.9.1-1)
- Migration status for proftpd-mod-case/amd64 (0.9.1-1 to 0.9.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-case/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-case/arm64 (0.9.1-1 to 0.9.1-1)
- Migration status for proftpd-mod-case/arm64 (0.9.1-1 to 0.9.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-case/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-case/armhf (0.9.1-1 to 0.9.1-1)
- Migration status for proftpd-mod-case/armhf (0.9.1-1 to 0.9.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-case/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-case/i386 (0.9.1-1 to 0.9.1-1)
- Migration status for proftpd-mod-case/i386 (0.9.1-1 to 0.9.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-case/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-clamav/amd64 (0.14~rc2-5 to 0.14~rc2-5)
- Migration status for proftpd-mod-clamav/amd64 (0.14~rc2-5 to 0.14~rc2-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-clamav/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-clamav/arm64 (0.14~rc2-5 to 0.14~rc2-5)
- Migration status for proftpd-mod-clamav/arm64 (0.14~rc2-5 to 0.14~rc2-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-clamav/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-clamav/armhf (0.14~rc2-5 to 0.14~rc2-5)
- Migration status for proftpd-mod-clamav/armhf (0.14~rc2-5 to 0.14~rc2-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-clamav/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-clamav/i386 (0.14~rc2-5 to 0.14~rc2-5)
- Migration status for proftpd-mod-clamav/i386 (0.14~rc2-5 to 0.14~rc2-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-clamav/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-counter/amd64 (0.6.2-2 to 0.6.2-2)
- Migration status for proftpd-mod-counter/amd64 (0.6.2-2 to 0.6.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-counter/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-counter/arm64 (0.6.2-2 to 0.6.2-2)
- Migration status for proftpd-mod-counter/arm64 (0.6.2-2 to 0.6.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-counter/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-counter/armhf (0.6.2-2 to 0.6.2-2)
- Migration status for proftpd-mod-counter/armhf (0.6.2-2 to 0.6.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-counter/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-counter/i386 (0.6.2-2 to 0.6.2-2)
- Migration status for proftpd-mod-counter/i386 (0.6.2-2 to 0.6.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-counter/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-fsync/amd64 (0.3-4 to 0.3-4)
- Migration status for proftpd-mod-fsync/amd64 (0.3-4 to 0.3-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-fsync/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-fsync/arm64 (0.3-4 to 0.3-4)
- Migration status for proftpd-mod-fsync/arm64 (0.3-4 to 0.3-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-fsync/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-fsync/armhf (0.3-4 to 0.3-4)
- Migration status for proftpd-mod-fsync/armhf (0.3-4 to 0.3-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-fsync/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-fsync/i386 (0.3-4 to 0.3-4)
- Migration status for proftpd-mod-fsync/i386 (0.3-4 to 0.3-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-fsync/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-geoip2/amd64 (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-geoip2/amd64 (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-geoip2/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-geoip2/arm64 (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-geoip2/arm64 (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-geoip2/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-geoip2/armhf (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-geoip2/armhf (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-geoip2/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-geoip2/i386 (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-geoip2/i386 (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-geoip2/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-kafka/amd64 (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-kafka/amd64 (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-kafka/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-kafka/arm64 (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-kafka/arm64 (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-kafka/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-kafka/armhf (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-kafka/armhf (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-kafka/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-kafka/i386 (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-kafka/i386 (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-kafka/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-msg/amd64 (0.5.1-1 to 0.5.1-1)
- Migration status for proftpd-mod-msg/amd64 (0.5.1-1 to 0.5.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-msg/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-msg/arm64 (0.5.1-1 to 0.5.1-1)
- Migration status for proftpd-mod-msg/arm64 (0.5.1-1 to 0.5.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-msg/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-msg/armhf (0.5.1-1 to 0.5.1-1)
- Migration status for proftpd-mod-msg/armhf (0.5.1-1 to 0.5.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-msg/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-msg/i386 (0.5.1-1 to 0.5.1-1)
- Migration status for proftpd-mod-msg/i386 (0.5.1-1 to 0.5.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-msg/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-prometheus/amd64 (0.2-1 to 0.2-1)
- Migration status for proftpd-mod-prometheus/amd64 (0.2-1 to 0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-prometheus/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-prometheus/arm64 (0.2-1 to 0.2-1)
- Migration status for proftpd-mod-prometheus/arm64 (0.2-1 to 0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-prometheus/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-prometheus/armhf (0.2-1 to 0.2-1)
- Migration status for proftpd-mod-prometheus/armhf (0.2-1 to 0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-prometheus/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-prometheus/i386 (0.2-1 to 0.2-1)
- Migration status for proftpd-mod-prometheus/i386 (0.2-1 to 0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-prometheus/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-proxy-protocol/amd64 (0.6-1 to 0.6-1)
- Migration status for proftpd-mod-proxy-protocol/amd64 (0.6-1 to 0.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-proxy-protocol/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-proxy-protocol/arm64 (0.6-1 to 0.6-1)
- Migration status for proftpd-mod-proxy-protocol/arm64 (0.6-1 to 0.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-proxy-protocol/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-proxy-protocol/armhf (0.6-1 to 0.6-1)
- Migration status for proftpd-mod-proxy-protocol/armhf (0.6-1 to 0.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-proxy-protocol/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-proxy-protocol/i386 (0.6-1 to 0.6-1)
- Migration status for proftpd-mod-proxy-protocol/i386 (0.6-1 to 0.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-proxy-protocol/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-proxy/amd64 (0.9.5-1 to 0.9.5-1)
- Migration status for proftpd-mod-proxy/amd64 (0.9.5-1 to 0.9.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-proxy/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-proxy/arm64 (0.9.5-1 to 0.9.5-1)
- Migration status for proftpd-mod-proxy/arm64 (0.9.5-1 to 0.9.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-proxy/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-proxy/armhf (0.9.5-1 to 0.9.5-1)
- Migration status for proftpd-mod-proxy/armhf (0.9.5-1 to 0.9.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-proxy/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-proxy/i386 (0.9.5-1 to 0.9.5-1)
- Migration status for proftpd-mod-proxy/i386 (0.9.5-1 to 0.9.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-proxy/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-statsd/amd64 (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-statsd/amd64 (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-statsd/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-statsd/arm64 (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-statsd/arm64 (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-statsd/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-statsd/armhf (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-statsd/armhf (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-statsd/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-statsd/i386 (0.1-1 to 0.1-1)
- Migration status for proftpd-mod-statsd/i386 (0.1-1 to 0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-statsd/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-tar/amd64 (0.4-3 to 0.4-3)
- Migration status for proftpd-mod-tar/amd64 (0.4-3 to 0.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-tar/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-tar/arm64 (0.4-3 to 0.4-3)
- Migration status for proftpd-mod-tar/arm64 (0.4-3 to 0.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-tar/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-tar/armhf (0.4-3 to 0.4-3)
- Migration status for proftpd-mod-tar/armhf (0.4-3 to 0.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-tar/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-tar/i386 (0.4-3 to 0.4-3)
- Migration status for proftpd-mod-tar/i386 (0.4-3 to 0.4-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-tar/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-vroot/amd64 (0.9.12-1 to 0.9.12-1)
- Migration status for proftpd-mod-vroot/amd64 (0.9.12-1 to 0.9.12-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-vroot/amd64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-vroot/arm64 (0.9.12-1 to 0.9.12-1)
- Migration status for proftpd-mod-vroot/arm64 (0.9.12-1 to 0.9.12-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-vroot/arm64 proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-vroot/armhf (0.9.12-1 to 0.9.12-1)
- Migration status for proftpd-mod-vroot/armhf (0.9.12-1 to 0.9.12-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-vroot/armhf proftpd-dfsg (not considered)
- Invalidated by dependency
- proftpd-mod-vroot/i386 (0.9.12-1 to 0.9.12-1)
- Migration status for proftpd-mod-vroot/i386 (0.9.12-1 to 0.9.12-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: proftpd-mod-vroot/i386 proftpd-dfsg (not considered)
- Invalidated by dependency
- proj/armel (9.6.2-1 to 9.6.2-1)
- Migration status for proj/armel (9.6.2-1 to 9.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- properties-cpp/armel (0.0.3-2 to 0.0.3-2)
- Migration status for properties-cpp/armel (0.0.3-2 to 0.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- protobuf/armel (3.21.12-11 to 3.21.12-11)
- Migration status for protobuf/armel (3.21.12-11 to 3.21.12-11): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- proxychains-ng/armel (4.17-3 to 4.17-3)
- Migration status for proxychains-ng/armel (4.17-3 to 4.17-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- proxytunnel/armel (1.12.3-1 to 1.12.3-1)
- Migration status for proxytunnel/armel (1.12.3-1 to 1.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- psmisc/armel (23.7-2 to 23.7-2)
- Migration status for psmisc/armel (23.7-2 to 23.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- psycopg2/armel (2.9.10-1 to 2.9.10-1)
- Migration status for psycopg2/armel (2.9.10-1 to 2.9.10-1): Will attempt migration (Any information below is purely informational)
- ptunnel/armel (0.72-3 to 0.72-3)
- Migration status for ptunnel/armel (0.72-3 to 0.72-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pulseaudio/armel (17.0+dfsg1-2 to 17.0+dfsg1-2)
- Migration status for pulseaudio/armel (17.0+dfsg1-2 to 17.0+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pure-ftpd/armel (1.0.50-2.2 to 1.0.50-2.2)
- Migration status for pure-ftpd/armel (1.0.50-2.2 to 1.0.50-2.2): Will attempt migration (Any information below is purely informational)
- putty/armel (0.83-3 to 0.83-3)
- Migration status for putty/armel (0.83-3 to 0.83-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- py-ubjson/armel (0.16.1-4 to 0.16.1-4)
- Migration status for py-ubjson/armel (0.16.1-4 to 0.16.1-4): Will attempt migration (Any information below is purely informational)
- pybluez/armel (0.23-5.1 to 0.23-5.1)
- Migration status for pybluez/armel (0.23-5.1 to 0.23-5.1): Will attempt migration (Any information below is purely informational)
- pycairo/armel (1.27.0-2 to 1.27.0-2)
- Migration status for pycairo/armel (1.27.0-2 to 1.27.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pycares/armel (4.4.0-2 to 4.4.0-2)
- Migration status for pycares/armel (4.4.0-2 to 4.4.0-2): Will attempt migration (Any information below is purely informational)
- pycryptodome/armel (3.20.0+dfsg-3 to 3.20.0+dfsg-3)
- Migration status for pycryptodome/armel (3.20.0+dfsg-3 to 3.20.0+dfsg-3): Will attempt migration (Any information below is purely informational)
- pycurl/armel (7.45.6-1 to 7.45.6-1)
- Migration status for pycurl/armel (7.45.6-1 to 7.45.6-1): Will attempt migration (Any information below is purely informational)
- pydantic-core/armel (2.27.2-3 to 2.27.2-3)
- Migration status for pydantic-core/armel (2.27.2-3 to 2.27.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pydantic/armel (2.10.6-2 to 2.10.6-2)
- Migration status for pydantic/armel (2.10.6-2 to 2.10.6-2): Will attempt migration (Any information below is purely informational)
- pyephem/armel (4.2-1 to 4.2-1)
- Migration status for pyephem/armel (4.2-1 to 4.2-1): Will attempt migration (Any information below is purely informational)
- pyerfa/armel (2.0.1.5+ds-1 to 2.0.1.5+ds-1)
- Migration status for pyerfa/armel (2.0.1.5+ds-1 to 2.0.1.5+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pygattlib/armel (0~20210616-1.1 to 0~20210616-1.1)
- Migration status for pygattlib/armel (0~20210616-1.1 to 0~20210616-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pygobject/armel (3.50.0-4 to 3.50.0-4)
- Migration status for pygobject/armel (3.50.0-4 to 3.50.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pylsqpack/armel (0.3.22-1 to 0.3.22-1)
- Migration status for pylsqpack/armel (0.3.22-1 to 0.3.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pyodbc/armel (5.2.0-1 to 5.2.0-1)
- Migration status for pyodbc/armel (5.2.0-1 to 5.2.0-1): Will attempt migration (Any information below is purely informational)
- pyqt5-sip/armel (12.17.0-1 to 12.17.0-1)
- Migration status for pyqt5-sip/armel (12.17.0-1 to 12.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pyqt5/armel (5.15.11+dfsg-2 to 5.15.11+dfsg-2)
- Migration status for pyqt5/armel (5.15.11+dfsg-2 to 5.15.11+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pyqt5chart/armel (5.15.7+dfsg-1 to 5.15.7+dfsg-1)
- Migration status for pyqt5chart/armel (5.15.7+dfsg-1 to 5.15.7+dfsg-1): Will attempt migration (Any information below is purely informational)
- pyqt6-sip/armel (13.10.0-1 to 13.10.0-1)
- Migration status for pyqt6-sip/armel (13.10.0-1 to 13.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pyqt6/armel (6.9.0-2 to 6.9.0-2)
- Migration status for pyqt6/armel (6.9.0-2 to 6.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pyscard/armel (2.3.0-1 to 2.3.0-1)
- Migration status for pyscard/armel (2.3.0-1 to 2.3.0-1): Will attempt migration (Any information below is purely informational)
- pyside2/armel (5.15.16-3.1 to 5.15.16-3.1)
- Migration status for pyside2/armel (5.15.16-3.1 to 5.15.16-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-aiohttp/armel (3.11.16-1 to 3.11.16-1)
- Migration status for python-aiohttp/armel (3.11.16-1 to 3.11.16-1): Will attempt migration (Any information below is purely informational)
- python-bcrypt/armel (4.2.0-2.1 to 4.2.0-2.1)
- Migration status for python-bcrypt/armel (4.2.0-2.1 to 4.2.0-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-cbor/armel (1.0.0-1.2 to 1.0.0-1.2)
- Migration status for python-cbor/armel (1.0.0-1.2 to 1.0.0-1.2): Will attempt migration (Any information below is purely informational)
- python-cffi/armel (2.0.0~b1-1 to 2.0.0~b1-1)
- Migration status for python-cffi/armel (2.0.0~b1-1 to 2.0.0~b1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-charset-normalizer/armel (3.4.3-1 to 3.4.3-1)
- Migration status for python-charset-normalizer/armel (3.4.3-1 to 3.4.3-1): Will attempt migration (Any information below is purely informational)
- python-coverage/armel (7.8.2+dfsg1-1 to 7.8.2+dfsg1-1)
- Migration status for python-coverage/armel (7.8.2+dfsg1-1 to 7.8.2+dfsg1-1): Will attempt migration (Any information below is purely informational)
- python-crc32c/armel (2.7.1-1 to 2.7.1-1)
- Migration status for python-crc32c/armel (2.7.1-1 to 2.7.1-1): Will attempt migration (Any information below is purely informational)
- python-cryptography/armel (43.0.0-3 to 43.0.0-3)
- Migration status for python-cryptography/armel (43.0.0-3 to 43.0.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-geoip/armel (1.3.2-6 to 1.3.2-6)
- Migration status for python-geoip/armel (1.3.2-6 to 1.3.2-6): Will attempt migration (Any information below is purely informational)
- python-gevent/armel (24.11.1-1 to 24.11.1-1)
- Migration status for python-gevent/armel (24.11.1-1 to 24.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-greenlet/armel (3.1.0-1 to 3.1.0-1)
- Migration status for python-greenlet/armel (3.1.0-1 to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-gssapi/armel (1.9.0-1 to 1.9.0-1)
- Migration status for python-gssapi/armel (1.9.0-1 to 1.9.0-1): Will attempt migration (Any information below is purely informational)
- python-jq/armel (1.10.0+dfsg-1 to 1.10.0+dfsg-1)
- Migration status for python-jq/armel (1.10.0+dfsg-1 to 1.10.0+dfsg-1): Will attempt migration (Any information below is purely informational)
- python-ldap/armel (3.4.4-1 to 3.4.4-1)
- Migration status for python-ldap/armel (3.4.4-1 to 3.4.4-1): Will attempt migration (Any information below is purely informational)
- python-levenshtein/armel (0.27.1-2 to 0.27.1-2)
- Migration status for python-levenshtein/armel (0.27.1-2 to 0.27.1-2): Will attempt migration (Any information below is purely informational)
- python-lz4/armel (4.4.4+dfsg-1 to 4.4.4+dfsg-1)
- Migration status for python-lz4/armel (4.4.4+dfsg-1 to 4.4.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-maxminddb/armel (2.8.2-1 to 2.8.2-1)
- Migration status for python-maxminddb/armel (2.8.2-1 to 2.8.2-1): Will attempt migration (Any information below is purely informational)
- python-msgpack/armel (1.0.3-3 to 1.0.3-3)
- Migration status for python-msgpack/armel (1.0.3-3 to 1.0.3-3): Will attempt migration (Any information below is purely informational)
- python-multidict/armel (6.4.3-1 to 6.4.3-1)
- Migration status for python-multidict/armel (6.4.3-1 to 6.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-mysqldb/armel (1.4.6-2 to 1.4.6-2)
- Migration status for python-mysqldb/armel (1.4.6-2 to 1.4.6-2): Will attempt migration (Any information below is purely informational)
- python-nacl/armel (1.5.0-7 to 1.5.0-7)
- Migration status for python-nacl/armel (1.5.0-7 to 1.5.0-7): Will attempt migration (Any information below is purely informational)
- python-propcache/armel (0.3.1-1 to 0.3.1-1)
- Migration status for python-propcache/armel (0.3.1-1 to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-psutil/armel (7.0.0-2 to 7.0.0-2)
- Migration status for python-psutil/armel (7.0.0-2 to 7.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-rjsmin/armel (1.2.0+dfsg1-2 to 1.2.0+dfsg1-2)
- Migration status for python-rjsmin/armel (1.2.0+dfsg1-2 to 1.2.0+dfsg1-2): Will attempt migration (Any information below is purely informational)
- python-setproctitle/armel (1.3.6-2 to 1.3.6-2)
- Migration status for python-setproctitle/armel (1.3.6-2 to 1.3.6-2): Will attempt migration (Any information below is purely informational)
- python-snappy/armel (0.5.3-1.2 to 0.5.3-1.2)
- Migration status for python-snappy/armel (0.5.3-1.2 to 0.5.3-1.2): Will attempt migration (Any information below is purely informational)
- python-tornado/armel (6.4.2-3 to 6.4.2-3)
- Migration status for python-tornado/armel (6.4.2-3 to 6.4.2-3): Will attempt migration (Any information below is purely informational)
- python-websockets/armel (15.0.1-1 to 15.0.1-1)
- Migration status for python-websockets/armel (15.0.1-1 to 15.0.1-1): Will attempt migration (Any information below is purely informational)
- python-wordcloud/armel (1.9.3+dfsg-2 to 1.9.3+dfsg-2)
- Migration status for python-wordcloud/armel (1.9.3+dfsg-2 to 1.9.3+dfsg-2): Will attempt migration (Any information below is purely informational)
- python-wrapt/armel (1.15.0-4 to 1.15.0-4)
- Migration status for python-wrapt/armel (1.15.0-4 to 1.15.0-4): Will attempt migration (Any information below is purely informational)
- python-wsaccel/armel (0.6.3-5 to 0.6.3-5)
- Migration status for python-wsaccel/armel (0.6.3-5 to 0.6.3-5): Will attempt migration (Any information below is purely informational)
- python-xattr/armel (0.10.1-1 to 0.10.1-1)
- Migration status for python-xattr/armel (0.10.1-1 to 0.10.1-1): Will attempt migration (Any information below is purely informational)
- python-zopfli/armel (0.2.3.post1-1 to 0.2.3.post1-1)
- Migration status for python-zopfli/armel (0.2.3.post1-1 to 0.2.3.post1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-zstd/armel (1.5.5.1-1 to 1.5.5.1-1)
- Migration status for python-zstd/armel (1.5.5.1-1 to 1.5.5.1-1): Will attempt migration (Any information below is purely informational)
- python3-defaults/armel (3.13.5-1 to 3.13.5-1)
- Migration status for python3-defaults/armel (3.13.5-1 to 3.13.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python3-stdlib-extensions/armel (3.13.5-1 to 3.13.5-1)
- Migration status for python3-stdlib-extensions/armel (3.13.5-1 to 3.13.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python3.13/armel (3.13.7-1 to 3.13.7-1)
- Migration status for python3.13/armel (3.13.7-1 to 3.13.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pytsk/armel (20231007-1 to 20231007-1)
- Migration status for pytsk/armel (20231007-1 to 20231007-1): Will attempt migration (Any information below is purely informational)
- pyyaml/armel (6.0.2-2 to 6.0.2-2)
- Migration status for pyyaml/armel (6.0.2-2 to 6.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- pyzmq/armel (26.4.0-1 to 26.4.0-1)
- Migration status for pyzmq/armel (26.4.0-1 to 26.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qhull/armel (2020.2-6 to 2020.2-6)
- Migration status for qhull/armel (2020.2-6 to 2020.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qmlkonsole/armel (25.08.0-1 to 25.08.0-1)
- Migration status for qmlkonsole/armel (25.08.0-1 to 25.08.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qqc2-breeze-style/armel (6.3.5-1 to 6.3.5-1)
- Migration status for qqc2-breeze-style/armel (6.3.5-1 to 6.3.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qqc2-desktop-style/armel (5.116.1-1 to 5.116.1-1)
- Migration status for qqc2-desktop-style/armel (5.116.1-1 to 5.116.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qscintilla2/armel (2.14.1+dfsg-1 to 2.14.1+dfsg-1)
- Migration status for qscintilla2/armel (2.14.1+dfsg-1 to 2.14.1+dfsg-1): Will attempt migration (Any information below is purely informational)
- qt5ct/armel (1.9-1 to 1.9-1)
- Migration status for qt5ct/armel (1.9-1 to 1.9-1): Will attempt migration (Any information below is purely informational)
- qt6-base/armel (6.8.2+dfsg-10 to 6.8.2+dfsg-10)
- Migration status for qt6-base/armel (6.8.2+dfsg-10 to 6.8.2+dfsg-10): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qt6-connectivity/armel (6.8.2-3 to 6.8.2-3)
- Migration status for qt6-connectivity/armel (6.8.2-3 to 6.8.2-3): Will attempt migration (Any information below is purely informational)
- qt6-declarative/armel (6.8.2+dfsg-7 to 6.8.2+dfsg-7)
- Migration status for qt6-declarative/armel (6.8.2+dfsg-7 to 6.8.2+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qt6-tools/armel (6.8.2-5 to 6.8.2-5)
- Migration status for qt6-tools/armel (6.8.2-5 to 6.8.2-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qt6-wayland/armel (6.8.2-4 to 6.8.2-4)
- Migration status for qt6-wayland/armel (6.8.2-4 to 6.8.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qt6ct/armel (0.10-2 to 0.10-2)
- Migration status for qt6ct/armel (0.10-2 to 0.10-2): Will attempt migration (Any information below is purely informational)
- qtbase-opensource-src/armel (5.15.15+dfsg-6 to 5.15.15+dfsg-6)
- Migration status for qtbase-opensource-src/armel (5.15.15+dfsg-6 to 5.15.15+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qtchooser/armel (66-2 to 66-2)
- Migration status for qtchooser/armel (66-2 to 66-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qtdeclarative-opensource-src/armel (5.15.15+dfsg-3 to 5.15.15+dfsg-3)
- Migration status for qtdeclarative-opensource-src/armel (5.15.15+dfsg-3 to 5.15.15+dfsg-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qterminal/armel (2.2.1-1 to 2.2.1-1)
- Migration status for qterminal/armel (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
- qtscript-opensource-src/armel (5.15.15+dfsg-2 to 5.15.15+dfsg-2)
- Migration status for qtscript-opensource-src/armel (5.15.15+dfsg-2 to 5.15.15+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qtsvg-opensource-src/armel (5.15.15-2 to 5.15.15-2)
- Migration status for qtsvg-opensource-src/armel (5.15.15-2 to 5.15.15-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- qttools-opensource-src/armel (5.15.15-6 to 5.15.15-6)
- Migration status for qttools-opensource-src/armel (5.15.15-6 to 5.15.15-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- (5.15.15-2 to 5.15.15-2)
- Migration status for qtx11extras-opensource-src/armel (5.15.15-2 to 5.15.15-2): Will attempt migration (Any information below is purely informational)
- r-base/armel (4.5.1-1 to 4.5.1-1)
- Migration status for r-base/armel (4.5.1-1 to 4.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- r-cran-class/armel (7.3-23-1 to 7.3-23-1)
- Migration status for r-cran-class/armel (7.3-23-1 to 7.3-23-1): Will attempt migration (Any information below is purely informational)
- r-cran-cli/armel (3.6.4-1 to 3.6.4-1)
- Migration status for r-cran-cli/armel (3.6.4-1 to 3.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- r-cran-data.table/armel (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
- Migration status for r-cran-data.table/armel (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
- r-cran-fansi/armel (1.0.6-2 to 1.0.6-2)
- Migration status for r-cran-fansi/armel (1.0.6-2 to 1.0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- r-cran-glue/armel (1.8.0-1 to 1.8.0-1)
- Migration status for r-cran-glue/armel (1.8.0-1 to 1.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- r-cran-magrittr/armel (2.0.3-1 to 2.0.3-1)
- Migration status for r-cran-magrittr/armel (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- r-cran-mass/armel (7.3-65-1 to 7.3-65-1)
- Migration status for r-cran-mass/armel (7.3-65-1 to 7.3-65-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- r-cran-plyr/armel (1.8.9-1 to 1.8.9-1)
- Migration status for r-cran-plyr/armel (1.8.9-1 to 1.8.9-1): Will attempt migration (Any information below is purely informational)
- r-cran-proxy/armel (0.4-27-1 to 0.4-27-1)
- Migration status for r-cran-proxy/armel (0.4-27-1 to 0.4-27-1): Will attempt migration (Any information below is purely informational)
- r-cran-rlang/armel (1.1.5-3 to 1.1.5-3)
- Migration status for r-cran-rlang/armel (1.1.5-3 to 1.1.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- r-cran-spatstat.utils/armel (3.1-3-1 to 3.1-3-1)
- Migration status for r-cran-spatstat.utils/armel (3.1-3-1 to 3.1-3-1): Will attempt migration (Any information below is purely informational)
- r-cran-tibble/armel (3.2.1+dfsg-3 to 3.2.1+dfsg-3)
- Migration status for r-cran-tibble/armel (3.2.1+dfsg-3 to 3.2.1+dfsg-3): Will attempt migration (Any information below is purely informational)
- r-cran-tidyselect/armel (1.2.1+dfsg-1 to 1.2.1+dfsg-1)
- Migration status for r-cran-tidyselect/armel (1.2.1+dfsg-1 to 1.2.1+dfsg-1): Will attempt migration (Any information below is purely informational)
- r-cran-utf8/armel (1.2.4-1 to 1.2.4-1)
- Migration status for r-cran-utf8/armel (1.2.4-1 to 1.2.4-1): Will attempt migration (Any information below is purely informational)
- r-cran-vctrs/armel (0.6.5-1 to 0.6.5-1)
- Migration status for r-cran-vctrs/armel (0.6.5-1 to 0.6.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rapidfuzz/armel (3.12.2+ds-1 to 3.12.2+ds-1)
- Migration status for rapidfuzz/armel (3.12.2+ds-1 to 3.12.2+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rcpp/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rcpp/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rdesktop/armel (1.9.0-2 to 1.9.0-2)
- Migration status for rdesktop/armel (1.9.0-2 to 1.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- react/armel (1.2.2-1 to 1.2.2-1)
- Migration status for react/armel (1.2.2-1 to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- reactivedata/armel (0.3-4 to 0.3-4)
- Migration status for reactivedata/armel (0.3-4 to 0.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- reaver/armel (1.6.6-2 to 1.6.6-2)
- Migration status for reaver/armel (1.6.6-2 to 1.6.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- recode/armel (3.7.15-1 to 3.7.15-1)
- Migration status for recode/armel (3.7.15-1 to 3.7.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- recordmydesktop/armel (0.4.0-1 to 0.4.0-1)
- Migration status for recordmydesktop/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- recoverdm/armel (0.20-9 to 0.20-9)
- Migration status for recoverdm/armel (0.20-9 to 0.20-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- recoverjpeg/armel (2.6.3-5 to 2.6.3-5)
- Migration status for recoverjpeg/armel (2.6.3-5 to 2.6.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- redis/armel (5:8.0.2-3 to 5:8.0.2-3)
- Migration status for redis/armel (5:8.0.2-3 to 5:8.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- redsocks/armel (0.5-2 to 0.5-2)
- Migration status for redsocks/armel (0.5-2 to 0.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- reglookup/armel (1.0.1+svn296-1 to 1.0.1+svn296-1)
- Migration status for reglookup/armel (1.0.1+svn296-1 to 1.0.1+svn296-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- reiserfsprogs/armel (1:3.6.27-9 to 1:3.6.27-9)
- Migration status for reiserfsprogs/armel (1:3.6.27-9 to 1:3.6.27-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rephrase/armel (0.2-4 to 0.2-4)
- Migration status for rephrase/armel (0.2-4 to 0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- retry/armel (1.0.6-1 to 1.0.6-1)
- Migration status for retry/armel (1.0.6-1 to 1.0.6-1): Will attempt migration (Any information below is purely informational)
- rfdump/armel (1.6-9.1 to 1.6-9.1)
- Migration status for rfdump/armel (1.6-9.1 to 1.6-9.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rhash/armel (1.4.6-1 to 1.4.6-1)
- Migration status for rhash/armel (1.4.6-1 to 1.4.6-1): Will attempt migration (Any information below is purely informational)
- rifiuti/armel (20040505-4 to 20040505-4)
- Migration status for rifiuti/armel (20040505-4 to 20040505-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rifiuti2/armel (0.8.2-1 to 0.8.2-1)
- Migration status for rifiuti2/armel (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rinetd/armel (0.73-2 to 0.73-2)
- Migration status for rinetd/armel (0.73-2 to 0.73-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ristretto/armel (0.13.3-1 to 0.13.3-1)
- Migration status for ristretto/armel (0.13.3-1 to 0.13.3-1): Will attempt migration (Any information below is purely informational)
- rkflashtool/armel (0~20160324-2 to 0~20160324-2)
- Migration status for rkflashtool/armel (0~20160324-2 to 0~20160324-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rmatrix/armel (1.7-3-1 to 1.7-3-1)
- Migration status for rmatrix/armel (1.7-3-1 to 1.7-3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rofi/armel (1.7.5-0.1 to 1.7.5-0.1)
- Migration status for rofi/armel (1.7.5-0.1 to 1.7.5-0.1): Will attempt migration (Any information below is purely informational)
- rootskel/armel (1.138 to 1.138)
- Migration status for rootskel/armel (1.138 to 1.138): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ros-class-loader/armel (2.9.0-1 to 2.9.0-1)
- Migration status for ros-class-loader/armel (2.9.0-1 to 2.9.0-1): Will attempt migration (Any information below is purely informational)
- ros-message-runtime/armel (0.4.13-6 to 0.4.13-6)
- Migration status for ros-message-runtime/armel (0.4.13-6 to 0.4.13-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ros-ros/armel (1.15.10-1 to 1.15.10-1)
- Migration status for ros-ros/armel (1.15.10-1 to 1.15.10-1): Will attempt migration (Any information below is purely informational)
- ros-roscpp-core/armel (0.7.3-3 to 0.7.3-3)
- Migration status for ros-roscpp-core/armel (0.7.3-3 to 0.7.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ros-rospack/armel (2.6.4-1 to 2.6.4-1)
- Migration status for ros-rospack/armel (2.6.4-1 to 2.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ros-std-msgs/armel (0.5.14-1 to 0.5.14-1)
- Migration status for ros-std-msgs/armel (0.5.14-1 to 0.5.14-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: ros-std-msgs/armel ros-common-msgs (not considered)
- Invalidated by implicit-dependency
- ros2-ament-index/armel (1.10.1-1 to 1.10.1-1)
- Migration status for ros2-ament-index/armel (1.10.1-1 to 1.10.1-1): Will attempt migration (Any information below is purely informational)
- ros2-rcpputils/armel (2.13.2-1 to 2.13.2-1)
- Migration status for ros2-rcpputils/armel (2.13.2-1 to 2.13.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ros2-rcutils/armel (6.9.4-1 to 6.9.4-1)
- Migration status for ros2-rcutils/armel (6.9.4-1 to 6.9.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rpcbind/armel (1.2.7-1 to 1.2.7-1)
- Migration status for rpcbind/armel (1.2.7-1 to 1.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rpds-py/armel (0.21.0-2 to 0.21.0-2)
- Migration status for rpds-py/armel (0.21.0-2 to 0.21.0-2): Will attempt migration (Any information below is purely informational)
- rpi.gpio/armel (0.7.1~a4-1.2 to 0.7.1~a4-1.2)
- Migration status for rpi.gpio/armel (0.7.1~a4-1.2 to 0.7.1~a4-1.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rsakeyfind/armel (1:1.0-8 to 1:1.0-8)
- Migration status for rsakeyfind/armel (1:1.0-8 to 1:1.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rtmpdump/armel (2.4+20151223.gitfa8646d.1-3 to 2.4+20151223.gitfa8646d.1-3)
- Migration status for rtmpdump/armel (2.4+20151223.gitfa8646d.1-3 to 2.4+20151223.gitfa8646d.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ruamel.yaml.clib/armel (0.2.12+ds-1 to 0.2.12+ds-1)
- Migration status for ruamel.yaml.clib/armel (0.2.12+ds-1 to 0.2.12+ds-1): Will attempt migration (Any information below is purely informational)
- ruby-atomic/armel (1.1.101-1 to 1.1.101-1)
- Migration status for ruby-atomic/armel (1.1.101-1 to 1.1.101-1): Will attempt migration (Any information below is purely informational)
- ruby-defaults/armel (1:3.3 to 1:3.3)
- Migration status for ruby-defaults/armel (1:3.3 to 1:3.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ruby-ffi/armel (1.17.0+dfsg-1 to 1.17.0+dfsg-1)
- Migration status for ruby-ffi/armel (1.17.0+dfsg-1 to 1.17.0+dfsg-1): Will attempt migration (Any information below is purely informational)
- ruby-hitimes/armel (1.3.1-1 to 1.3.1-1)
- Migration status for ruby-hitimes/armel (1.3.1-1 to 1.3.1-1): Will attempt migration (Any information below is purely informational)
- ruby-http-parser.rb/armel (0.6.0-6 to 0.6.0-6)
- Migration status for ruby-http-parser.rb/armel (0.6.0-6 to 0.6.0-6): Will attempt migration (Any information below is purely informational)
- ruby-http-parser/armel (1.2.3-1 to 1.2.3-1)
- Migration status for ruby-http-parser/armel (1.2.3-1 to 1.2.3-1): Will attempt migration (Any information below is purely informational)
- ruby-json/armel (2.9.1+dfsg-1 to 2.9.1+dfsg-1)
- Migration status for ruby-json/armel (2.9.1+dfsg-1 to 2.9.1+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ruby-levenshtein/armel (0.2.2-3 to 0.2.2-3)
- Migration status for ruby-levenshtein/armel (0.2.2-3 to 0.2.2-3): Will attempt migration (Any information below is purely informational)
- ruby-nio4r/armel (2.7.3-1 to 2.7.3-1)
- Migration status for ruby-nio4r/armel (2.7.3-1 to 2.7.3-1): Will attempt migration (Any information below is purely informational)
- ruby-nokogiri/armel (1.18.2+dfsg-1 to 1.18.2+dfsg-1)
- Migration status for ruby-nokogiri/armel (1.18.2+dfsg-1 to 1.18.2+dfsg-1): Will attempt migration (Any information below is purely informational)
- ruby-pg/armel (1.5.6-1 to 1.5.6-1)
- Migration status for ruby-pg/armel (1.5.6-1 to 1.5.6-1): Will attempt migration (Any information below is purely informational)
- ruby-rbtree/armel (0.4.6-1 to 0.4.6-1)
- Migration status for ruby-rbtree/armel (0.4.6-1 to 0.4.6-1): Will attempt migration (Any information below is purely informational)
- ruby-sqlite3/armel (1.7.3-2 to 1.7.3-2)
- Migration status for ruby-sqlite3/armel (1.7.3-2 to 1.7.3-2): Will attempt migration (Any information below is purely informational)
- ruby-unf-ext/armel (0.0.7.7-1 to 0.0.7.7-1)
- Migration status for ruby-unf-ext/armel (0.0.7.7-1 to 0.0.7.7-1): Will attempt migration (Any information below is purely informational)
- ruby-yajl/armel (1.4.3-1 to 1.4.3-1)
- Migration status for ruby-yajl/armel (1.4.3-1 to 1.4.3-1): Will attempt migration (Any information below is purely informational)
- ruby3.3/armel (3.3.8-2 to 3.3.8-2)
- Migration status for ruby3.3/armel (3.3.8-2 to 3.3.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- runc/armel (1.1.15+ds1-2 to 1.1.15+ds1-2)
- Migration status for runc/armel (1.1.15+ds1-2 to 1.1.15+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ab-glyph-rasterizer/armel (0.1.7-1 to 0.1.7-1)
- Migration status for rust-ab-glyph-rasterizer/armel (0.1.7-1 to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ab-glyph/armel (0.2.29-1 to 0.2.29-1)
- Migration status for rust-ab-glyph/armel (0.2.29-1 to 0.2.29-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-codec/armel (0.5.2-1 to 0.5.2-1)
- Migration status for rust-actix-codec/armel (0.5.2-1 to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-http/armel (3.9.0-3 to 3.9.0-3)
- Migration status for rust-actix-http/armel (3.9.0-3 to 3.9.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-macros/armel (0.2.3-1 to 0.2.3-1)
- Migration status for rust-actix-macros/armel (0.2.3-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-router/armel (0.5.3-3 to 0.5.3-3)
- Migration status for rust-actix-router/armel (0.5.3-3 to 0.5.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-rt/armel (2.10.0-1 to 2.10.0-1)
- Migration status for rust-actix-rt/armel (2.10.0-1 to 2.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-server/armel (2.6.0-1 to 2.6.0-1)
- Migration status for rust-actix-server/armel (2.6.0-1 to 2.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-service/armel (2.0.2-1 to 2.0.2-1)
- Migration status for rust-actix-service/armel (2.0.2-1 to 2.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-utils/armel (3.0.1-1 to 3.0.1-1)
- Migration status for rust-actix-utils/armel (3.0.1-1 to 3.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-web-codegen/armel (4.3.0-1 to 4.3.0-1)
- Migration status for rust-actix-web-codegen/armel (4.3.0-1 to 4.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-actix-web/armel (4.9.0-2 to 4.9.0-2)
- Migration status for rust-actix-web/armel (4.9.0-2 to 4.9.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-actix-web/armel rust-rebuilderd (not considered)
- Invalidated by implicit-dependency
- rust-addchain/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-addchain/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-addr2line/armel (0.24.2-2 to 0.24.2-2)
- Migration status for rust-addr2line/armel (0.24.2-2 to 0.24.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-adler/armel (1.0.2-2 to 1.0.2-2)
- Migration status for rust-adler/armel (1.0.2-2 to 1.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-aead/armel (0.5.2-2 to 0.5.2-2)
- Migration status for rust-aead/armel (0.5.2-2 to 0.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-aes-gcm/armel (0.10.3-2 to 0.10.3-2)
- Migration status for rust-aes-gcm/armel (0.10.3-2 to 0.10.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-aes/armel (0.8.4-1 to 0.8.4-1)
- Migration status for rust-aes/armel (0.8.4-1 to 0.8.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-aho-corasick/armel (1.1.3-1 to 1.1.3-1)
- Migration status for rust-aho-corasick/armel (1.1.3-1 to 1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-alloc-no-stdlib/armel (2.0.4-1 to 2.0.4-1)
- Migration status for rust-alloc-no-stdlib/armel (2.0.4-1 to 2.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-alloc-stdlib/armel (0.2.2-1 to 0.2.2-1)
- Migration status for rust-alloc-stdlib/armel (0.2.2-1 to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-allocator-api2/armel (0.2.16-2 to 0.2.16-2)
- Migration status for rust-allocator-api2/armel (0.2.16-2 to 0.2.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-anes/armel (0.1.6-1 to 0.1.6-1)
- Migration status for rust-anes/armel (0.1.6-1 to 0.1.6-1): Will attempt migration (Any information below is purely informational)
- rust-annotate-snippets/armel (0.11.4-1 to 0.11.4-1)
- Migration status for rust-annotate-snippets/armel (0.11.4-1 to 0.11.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ansi-colours/armel (1.2.3-1 to 1.2.3-1)
- Migration status for rust-ansi-colours/armel (1.2.3-1 to 1.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ansi-term/armel (0.12.1-1 to 0.12.1-1)
- Migration status for rust-ansi-term/armel (0.12.1-1 to 0.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ansiterm/armel (0.12.2-1 to 0.12.2-1)
- Migration status for rust-ansiterm/armel (0.12.2-1 to 0.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-anstream/armel (0.6.15-1 to 0.6.15-1)
- Migration status for rust-anstream/armel (0.6.15-1 to 0.6.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-anstyle-parse/armel (0.2.1-1 to 0.2.1-1)
- Migration status for rust-anstyle-parse/armel (0.2.1-1 to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-anstyle-query/armel (1.0.0-1 to 1.0.0-1)
- Migration status for rust-anstyle-query/armel (1.0.0-1 to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-anstyle/armel (1.0.8-1 to 1.0.8-1)
- Migration status for rust-anstyle/armel (1.0.8-1 to 1.0.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-anyhow/armel (1.0.95-1 to 1.0.95-1)
- Migration status for rust-anyhow/armel (1.0.95-1 to 1.0.95-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-aom-sys/armel (0.3.3-5 to 0.3.3-5)
- Migration status for rust-aom-sys/armel (0.3.3-5 to 0.3.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-approx/armel (0.5.1-1 to 0.5.1-1)
- Migration status for rust-approx/armel (0.5.1-1 to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-arbitrary/armel (1.4.1-1 to 1.4.1-1)
- Migration status for rust-arbitrary/armel (1.4.1-1 to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-arboard/armel (3.5.0-1 to 3.5.0-1)
- Migration status for rust-arboard/armel (3.5.0-1 to 3.5.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-arboard/armel rust-bacon (not considered)
- Invalidated by implicit-dependency
- rust-arc-swap/armel (1.7.1-1 to 1.7.1-1)
- Migration status for rust-arc-swap/armel (1.7.1-1 to 1.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-arg-enum-proc-macro/armel (0.3.4-1 to 0.3.4-1)
- Migration status for rust-arg-enum-proc-macro/armel (0.3.4-1 to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-argon2/armel (0.5.3-1 to 0.5.3-1)
- Migration status for rust-argon2/armel (0.5.3-1 to 0.5.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-array-init/armel (2.0.1-1 to 2.0.1-1)
- Migration status for rust-array-init/armel (2.0.1-1 to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-arraydeque/armel (0.5.1-1 to 0.5.1-1)
- Migration status for rust-arraydeque/armel (0.5.1-1 to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-arrayref/armel (0.3.9-1 to 0.3.9-1)
- Migration status for rust-arrayref/armel (0.3.9-1 to 0.3.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-arrayvec/armel (0.7.6-1 to 0.7.6-1)
- Migration status for rust-arrayvec/armel (0.7.6-1 to 0.7.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-as-raw-xcb-connection/armel (1.0.1-1 to 1.0.1-1)
- Migration status for rust-as-raw-xcb-connection/armel (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ascii-canvas/armel (3.0.0-1 to 3.0.0-1)
- Migration status for rust-ascii-canvas/armel (3.0.0-1 to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-async-compression/armel (0.4.13-1 to 0.4.13-1)
- Migration status for rust-async-compression/armel (0.4.13-1 to 0.4.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-async-global-executor/armel (2.4.1-5 to 2.4.1-5)
- Migration status for rust-async-global-executor/armel (2.4.1-5 to 2.4.1-5): Will attempt migration (Any information below is purely informational)
- rust-async-io/armel (2.3.3-4 to 2.3.3-4)
- Migration status for rust-async-io/armel (2.3.3-4 to 2.3.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-async-signal/armel (0.2.10-1 to 0.2.10-1)
- Migration status for rust-async-signal/armel (0.2.10-1 to 0.2.10-1): Will attempt migration (Any information below is purely informational)
- rust-async-trait/armel (0.1.83-1 to 0.1.83-1)
- Migration status for rust-async-trait/armel (0.1.83-1 to 0.1.83-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-atoi/armel (2.0.0-1 to 2.0.0-1)
- Migration status for rust-atoi/armel (2.0.0-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-atomic-refcell/armel (0.1.13-1 to 0.1.13-1)
- Migration status for rust-atomic-refcell/armel (0.1.13-1 to 0.1.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-atomic-waker/armel (1.1.2-1 to 1.1.2-1)
- Migration status for rust-atomic-waker/armel (1.1.2-1 to 1.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-atomic/armel (0.6.0-1 to 0.6.0-1)
- Migration status for rust-atomic/armel (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-autocfg/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-autocfg/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-av-metrics/armel (0.9.1-3 to 0.9.1-3)
- Migration status for rust-av-metrics/armel (0.9.1-3 to 0.9.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-av1-grain/armel (0.2.4-1 to 0.2.4-1)
- Migration status for rust-av1-grain/armel (0.2.4-1 to 0.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-backtrace/armel (0.3.74-3 to 0.3.74-3)
- Migration status for rust-backtrace/armel (0.3.74-3 to 0.3.74-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-base16ct/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-base16ct/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-base64/armel (0.22.1-1 to 0.22.1-1)
- Migration status for rust-base64/armel (0.22.1-1 to 0.22.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-base64ct/armel (1.6.0-1 to 1.6.0-1)
- Migration status for rust-base64ct/armel (1.6.0-1 to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bet/armel (1.0.4-1 to 1.0.4-1)
- Migration status for rust-bet/armel (1.0.4-1 to 1.0.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-bet/armel rust-dysk-cli (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-bet/armel rust-broot
- rust-bigdecimal/armel (0.4.7-1 to 0.4.7-1)
- Migration status for rust-bigdecimal/armel (0.4.7-1 to 0.4.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bincode/armel (1.3.3-1 to 1.3.3-1)
- Migration status for rust-bincode/armel (1.3.3-1 to 1.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bindgen/armel (0.71.1-4 to 0.71.1-4)
- Migration status for rust-bindgen/armel (0.71.1-4 to 0.71.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bit-field/armel (0.10.2-1 to 0.10.2-1)
- Migration status for rust-bit-field/armel (0.10.2-1 to 0.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bit-set/armel (0.8.0-1 to 0.8.0-1)
- Migration status for rust-bit-set/armel (0.8.0-1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bit-vec/armel (0.8.0-1 to 0.8.0-1)
- Migration status for rust-bit-vec/armel (0.8.0-1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bitflags-1/armel (1.3.2-7 to 1.3.2-7)
- Migration status for rust-bitflags-1/armel (1.3.2-7 to 1.3.2-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bitflags/armel (2.9.1-2 to 2.9.1-2)
- Migration status for rust-bitflags/armel (2.9.1-2 to 2.9.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bitstream-io/armel (2.6.0-1 to 2.6.0-1)
- Migration status for rust-bitstream-io/armel (2.6.0-1 to 2.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bitvec/armel (1.0.1-1 to 1.0.1-1)
- Migration status for rust-bitvec/armel (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-blake2/armel (0.10.6-3 to 0.10.6-3)
- Migration status for rust-blake2/armel (0.10.6-3 to 0.10.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-blobby/armel (0.3.1-1 to 0.3.1-1)
- Migration status for rust-blobby/armel (0.3.1-1 to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-block-buffer/armel (0.10.4-1 to 0.10.4-1)
- Migration status for rust-block-buffer/armel (0.10.4-1 to 0.10.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-block-padding/armel (0.3.3-1 to 0.3.3-1)
- Migration status for rust-block-padding/armel (0.3.3-1 to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-blowfish/armel (0.9.1-1 to 0.9.1-1)
- Migration status for rust-blowfish/armel (0.9.1-1 to 0.9.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-botan-sys/armel (0.10.5-1 to 0.10.5-1)
- Migration status for rust-botan-sys/armel (0.10.5-1 to 0.10.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-botan/armel (0.10.7-1 to 0.10.7-1)
- Migration status for rust-botan/armel (0.10.7-1 to 0.10.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-brotli-decompressor/armel (4.0.1-1 to 4.0.1-1)
- Migration status for rust-brotli-decompressor/armel (4.0.1-1 to 4.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-brotli/armel (6.0.0-1 to 6.0.0-1)
- Migration status for rust-brotli/armel (6.0.0-1 to 6.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bstr/armel (1.12.0-1 to 1.12.0-1)
- Migration status for rust-bstr/armel (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-buffered-reader/armel (1.3.1-2 to 1.3.1-2)
- Migration status for rust-buffered-reader/armel (1.3.1-2 to 1.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bumpalo/armel (3.16.0-1 to 3.16.0-1)
- Migration status for rust-bumpalo/armel (3.16.0-1 to 3.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-by-address/armel (1.2.1-1 to 1.2.1-1)
- Migration status for rust-by-address/armel (1.2.1-1 to 1.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bytecheck-derive/armel (0.8.0-1 to 0.8.0-1)
- Migration status for rust-bytecheck-derive/armel (0.8.0-1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bytecheck/armel (0.8.0-1 to 0.8.0-1)
- Migration status for rust-bytecheck/armel (0.8.0-1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bytemuck-derive/armel (1.5.0-2 to 1.5.0-2)
- Migration status for rust-bytemuck-derive/armel (1.5.0-2 to 1.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bytemuck/armel (1.21.0-1 to 1.21.0-1)
- Migration status for rust-bytemuck/armel (1.21.0-1 to 1.21.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-byteorder/armel (1.5.0-1 to 1.5.0-1)
- Migration status for rust-byteorder/armel (1.5.0-1 to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bytes/armel (1.9.0-1 to 1.9.0-1)
- Migration status for rust-bytes/armel (1.9.0-1 to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bytesize/armel (1.3.0-2 to 1.3.0-2)
- Migration status for rust-bytesize/armel (1.3.0-2 to 1.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bytestring/armel (1.4.0-1 to 1.4.0-1)
- Migration status for rust-bytestring/armel (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bzip2-sys/armel (0.1.11-1 to 0.1.11-1)
- Migration status for rust-bzip2-sys/armel (0.1.11-1 to 0.1.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-bzip2/armel (0.4.4-1 to 0.4.4-1)
- Migration status for rust-bzip2/armel (0.4.4-1 to 0.4.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cairo-rs/armel (0.20.7-2 to 0.20.7-2)
- Migration status for rust-cairo-rs/armel (0.20.7-2 to 0.20.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cairo-sys-rs/armel (0.20.7-1 to 0.20.7-1)
- Migration status for rust-cairo-sys-rs/armel (0.20.7-1 to 0.20.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-camellia/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-camellia/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cargo-metadata/armel (0.19.2-1 to 0.19.2-1)
- Migration status for rust-cargo-metadata/armel (0.19.2-1 to 0.19.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-cargo-metadata/armel rust-bacon (not considered)
- Invalidated by implicit-dependency
- rust-cargo-platform/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-cargo-platform/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cassowary/armel (0.3.0-2 to 0.3.0-2)
- Migration status for rust-cassowary/armel (0.3.0-2 to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cast/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-cast/armel (0.3.0-1 to 0.3.0-1): Will attempt migration (Any information below is purely informational)
- rust-cast5/armel (0.11.1-1 to 0.11.1-1)
- Migration status for rust-cast5/armel (0.11.1-1 to 0.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-castaway/armel (0.2.4-1 to 0.2.4-1)
- Migration status for rust-castaway/armel (0.2.4-1 to 0.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cbc/armel (0.1.2-1 to 0.1.2-1)
- Migration status for rust-cbc/armel (0.1.2-1 to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cc/armel (1.2.19-1 to 1.2.19-1)
- Migration status for rust-cc/armel (1.2.19-1 to 1.2.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cexpr/armel (0.6.0-2 to 0.6.0-2)
- Migration status for rust-cexpr/armel (0.6.0-2 to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cfb-mode/armel (0.8.2-1 to 0.8.2-1)
- Migration status for rust-cfb-mode/armel (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cfg-aliases/armel (0.2.1-1 to 0.2.1-1)
- Migration status for rust-cfg-aliases/armel (0.2.1-1 to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cfg-expr/armel (0.15.8-1 to 0.15.8-1)
- Migration status for rust-cfg-expr/armel (0.15.8-1 to 0.15.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cfg-if-0.1/armel (0.1.10-3 to 0.1.10-3)
- Migration status for rust-cfg-if-0.1/armel (0.1.10-3 to 0.1.10-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cfg-if/armel (1.0.0-1 to 1.0.0-1)
- Migration status for rust-cfg-if/armel (1.0.0-1 to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-char-reader/armel (0.1.1-2 to 0.1.1-2)
- Migration status for rust-char-reader/armel (0.1.1-2 to 0.1.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-char-reader/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-chrono-tz-build/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-chrono-tz-build/armel (0.4.0-1 to 0.4.0-1): Will attempt migration (Any information below is purely informational)
- rust-chrono/armel (0.4.39-2 to 0.4.39-2)
- Migration status for rust-chrono/armel (0.4.39-2 to 0.4.39-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ciborium-io/armel (0.2.2-1 to 0.2.2-1)
- Migration status for rust-ciborium-io/armel (0.2.2-1 to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ciborium-ll/armel (0.2.2-2 to 0.2.2-2)
- Migration status for rust-ciborium-ll/armel (0.2.2-2 to 0.2.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ciborium/armel (0.2.2-2 to 0.2.2-2)
- Migration status for rust-ciborium/armel (0.2.2-2 to 0.2.2-2): Will attempt migration (Any information below is purely informational)
- rust-cipher/armel (0.4.4-3 to 0.4.4-3)
- Migration status for rust-cipher/armel (0.4.4-3 to 0.4.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-clang-sys/armel (1.8.1-3 to 1.8.1-3)
- Migration status for rust-clang-sys/armel (1.8.1-3 to 1.8.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-clap-builder/armel (4.5.23-1 to 4.5.23-1)
- Migration status for rust-clap-builder/armel (4.5.23-1 to 4.5.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-clap-complete/armel (4.5.40-1 to 4.5.40-1)
- Migration status for rust-clap-complete/armel (4.5.40-1 to 4.5.40-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-clap-derive/armel (4.5.18-1 to 4.5.18-1)
- Migration status for rust-clap-derive/armel (4.5.18-1 to 4.5.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-clap-help/armel (1.4.0-3 to 1.4.0-3)
- Migration status for rust-clap-help/armel (1.4.0-3 to 1.4.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-clap-help/armel rust-dysk-cli (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-clap-help/armel rust-bacon
- Implicit dependency: rust-clap-help/armel rust-broot
- rust-clap-lex/armel (0.7.4-1 to 0.7.4-1)
- Migration status for rust-clap-lex/armel (0.7.4-1 to 0.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-clap-mangen/armel (0.2.20-1 to 0.2.20-1)
- Migration status for rust-clap-mangen/armel (0.2.20-1 to 0.2.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-clap/armel (4.5.23-1 to 4.5.23-1)
- Migration status for rust-clap/armel (4.5.23-1 to 4.5.23-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cli-log/armel (2.0.0-1 to 2.0.0-1)
- Migration status for rust-cli-log/armel (2.0.0-1 to 2.0.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-cli-log/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-cli-log/armel rust-bacon
- rust-clru/armel (0.6.2-1 to 0.6.2-1)
- Migration status for rust-clru/armel (0.6.2-1 to 0.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cmac/armel (0.7.2-1 to 0.7.2-1)
- Migration status for rust-cmac/armel (0.7.2-1 to 0.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-color-quant/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-color-quant/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-colorchoice/armel (1.0.0-1 to 1.0.0-1)
- Migration status for rust-colorchoice/armel (1.0.0-1 to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-colored/armel (2.2.0-1 to 2.2.0-1)
- Migration status for rust-colored/armel (2.2.0-1 to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-compact-str/armel (0.8.1-1 to 0.8.1-1)
- Migration status for rust-compact-str/armel (0.8.1-1 to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-compiler-builtins/armel (0.1.139-1 to 0.1.139-1)
- Migration status for rust-compiler-builtins/armel (0.1.139-1 to 0.1.139-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-concurrent-queue/armel (2.5.0-4 to 2.5.0-4)
- Migration status for rust-concurrent-queue/armel (2.5.0-4 to 2.5.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-console/armel (0.15.10-1 to 0.15.10-1)
- Migration status for rust-console/armel (0.15.10-1 to 0.15.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-const-oid/armel (0.9.6-1 to 0.9.6-1)
- Migration status for rust-const-oid/armel (0.9.6-1 to 0.9.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-const-random-macro/armel (0.1.16-2 to 0.1.16-2)
- Migration status for rust-const-random-macro/armel (0.1.16-2 to 0.1.16-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-const-random/armel (0.1.17-2 to 0.1.17-2)
- Migration status for rust-const-random/armel (0.1.17-2 to 0.1.17-2): Will attempt migration (Any information below is purely informational)
- rust-constant-time-eq/armel (0.3.1-1 to 0.3.1-1)
- Migration status for rust-constant-time-eq/armel (0.3.1-1 to 0.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-convert-case/armel (0.6.0-2 to 0.6.0-2)
- Migration status for rust-convert-case/armel (0.6.0-2 to 0.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cookie-store/armel (0.21.1-1 to 0.21.1-1)
- Migration status for rust-cookie-store/armel (0.21.1-1 to 0.21.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cookie/armel (0.18.1-2 to 0.18.1-2)
- Migration status for rust-cookie/armel (0.18.1-2 to 0.18.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-coolor/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-coolor/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-core-maths/armel (0.1.1-1 to 0.1.1-1)
- Migration status for rust-core-maths/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-core2/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-core2/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cpp-demangle/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-cpp-demangle/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cpufeatures/armel (0.2.16-1 to 0.2.16-1)
- Migration status for rust-cpufeatures/armel (0.2.16-1 to 0.2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crc-catalog/armel (2.4.0-1 to 2.4.0-1)
- Migration status for rust-crc-catalog/armel (2.4.0-1 to 2.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crc/armel (3.2.1-1 to 3.2.1-1)
- Migration status for rust-crc/armel (3.2.1-1 to 3.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crc32fast/armel (1.4.2-1 to 1.4.2-1)
- Migration status for rust-crc32fast/armel (1.4.2-1 to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-critical-section/armel (1.2.0-1 to 1.2.0-1)
- Migration status for rust-critical-section/armel (1.2.0-1 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crokey-proc-macros/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-crokey-proc-macros/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crokey/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-crokey/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-crokey/armel rust-termimad (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-crokey/armel rust-bacon
- Implicit dependency: rust-crokey/armel rust-broot
- rust-crossbeam-channel/armel (0.5.15-1 to 0.5.15-1)
- Migration status for rust-crossbeam-channel/armel (0.5.15-1 to 0.5.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crossbeam-deque/armel (0.8.5-1 to 0.8.5-1)
- Migration status for rust-crossbeam-deque/armel (0.8.5-1 to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crossbeam-epoch/armel (0.9.18-1 to 0.9.18-1)
- Migration status for rust-crossbeam-epoch/armel (0.9.18-1 to 0.9.18-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crossbeam-queue/armel (0.3.11-1 to 0.3.11-1)
- Migration status for rust-crossbeam-queue/armel (0.3.11-1 to 0.3.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crossbeam-utils/armel (0.8.19-1 to 0.8.19-1)
- Migration status for rust-crossbeam-utils/armel (0.8.19-1 to 0.8.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crossbeam/armel (0.8.4-1 to 0.8.4-1)
- Migration status for rust-crossbeam/armel (0.8.4-1 to 0.8.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crossterm/armel (0.27.0-5 to 0.27.0-5)
- Migration status for rust-crossterm/armel (0.27.0-5 to 0.27.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crosstermion/armel (0.14.0-3 to 0.14.0-3)
- Migration status for rust-crosstermion/armel (0.14.0-3 to 0.14.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crunchy/armel (0.2.2-1 to 0.2.2-1)
- Migration status for rust-crunchy/armel (0.2.2-1 to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crypto-bigint/armel (0.5.2-1 to 0.5.2-1)
- Migration status for rust-crypto-bigint/armel (0.5.2-1 to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-crypto-common/armel (0.1.6-1 to 0.1.6-1)
- Migration status for rust-crypto-common/armel (0.1.6-1 to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cstr/armel (0.2.12-1 to 0.2.12-1)
- Migration status for rust-cstr/armel (0.2.12-1 to 0.2.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-csv-core/armel (0.1.11-1 to 0.1.11-1)
- Migration status for rust-csv-core/armel (0.1.11-1 to 0.1.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-csv/armel (1.3.0-1 to 1.3.0-1)
- Migration status for rust-csv/armel (1.3.0-1 to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ctor/armel (0.1.26-1 to 0.1.26-1)
- Migration status for rust-ctor/armel (0.1.26-1 to 0.1.26-1): Will attempt migration (Any information below is purely informational)
- rust-ctr/armel (0.9.2-1 to 0.9.2-1)
- Migration status for rust-ctr/armel (0.9.2-1 to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ctrlc/armel (3.4.5-3 to 3.4.5-3)
- Migration status for rust-ctrlc/armel (3.4.5-3 to 3.4.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-curl-sys/armel (0.4.67-3 to 0.4.67-3)
- Migration status for rust-curl-sys/armel (0.4.67-3 to 0.4.67-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-curl/armel (0.4.44-5 to 0.4.44-5)
- Migration status for rust-curl/armel (0.4.44-5 to 0.4.44-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-cursor-icon/armel (1.1.0-2 to 1.1.0-2)
- Migration status for rust-cursor-icon/armel (1.1.0-2 to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-custom-error/armel (1.9.2-2 to 1.9.2-2)
- Migration status for rust-custom-error/armel (1.9.2-2 to 1.9.2-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-custom-error/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-darling-core/armel (0.20.10-1 to 0.20.10-1)
- Migration status for rust-darling-core/armel (0.20.10-1 to 0.20.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-darling-macro/armel (0.20.10-1 to 0.20.10-1)
- Migration status for rust-darling-macro/armel (0.20.10-1 to 0.20.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-darling/armel (0.20.10-1 to 0.20.10-1)
- Migration status for rust-darling/armel (0.20.10-1 to 0.20.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dashmap/armel (6.1.0-1 to 6.1.0-1)
- Migration status for rust-dashmap/armel (6.1.0-1 to 6.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-data-encoding/armel (2.6.0-1 to 2.6.0-1)
- Migration status for rust-data-encoding/armel (2.6.0-1 to 2.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-data-url/armel (0.3.1-2 to 0.3.1-2)
- Migration status for rust-data-url/armel (0.3.1-2 to 0.3.1-2): Will attempt migration (Any information below is purely informational)
- rust-dav1d-sys/armel (0.7.1-3 to 0.7.1-3)
- Migration status for rust-dav1d-sys/armel (0.7.1-3 to 0.7.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dbl/armel (0.3.2-1 to 0.3.2-1)
- Migration status for rust-dbl/armel (0.3.2-1 to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dbus/armel (0.9.7-1 to 0.9.7-1)
- Migration status for rust-dbus/armel (0.9.7-1 to 0.9.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-deflate64/armel (0.1.8-1 to 0.1.8-1)
- Migration status for rust-deflate64/armel (0.1.8-1 to 0.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-defmt-macros/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-defmt-macros/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-defmt-parser/armel (0.4.1-1 to 0.4.1-1)
- Migration status for rust-defmt-parser/armel (0.4.1-1 to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-defmt/armel (0.3.10-2 to 0.3.10-2)
- Migration status for rust-defmt/armel (0.3.10-2 to 0.3.10-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-der-derive/armel (0.7.1-1 to 0.7.1-1)
- Migration status for rust-der-derive/armel (0.7.1-1 to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-der/armel (0.7.7-1 to 0.7.7-1)
- Migration status for rust-der/armel (0.7.7-1 to 0.7.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-deranged/armel (0.3.11-1 to 0.3.11-1)
- Migration status for rust-deranged/armel (0.3.11-1 to 0.3.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-derive-arbitrary/armel (1.4.1-1 to 1.4.1-1)
- Migration status for rust-derive-arbitrary/armel (1.4.1-1 to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-derive-builder-core/armel (0.20.1-1 to 0.20.1-1)
- Migration status for rust-derive-builder-core/armel (0.20.1-1 to 0.20.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-derive-builder-macro/armel (0.20.1-1 to 0.20.1-1)
- Migration status for rust-derive-builder-macro/armel (0.20.1-1 to 0.20.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-derive-builder/armel (0.20.1-2 to 0.20.1-2)
- Migration status for rust-derive-builder/armel (0.20.1-2 to 0.20.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-derive-more-0.99/armel (0.99.18-2 to 0.99.18-2)
- Migration status for rust-derive-more-0.99/armel (0.99.18-2 to 0.99.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-des/armel (0.8.1-1 to 0.8.1-1)
- Migration status for rust-des/armel (0.8.1-1 to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-deser-hjson/armel (2.2.4-2 to 2.2.4-2)
- Migration status for rust-deser-hjson/armel (2.2.4-2 to 2.2.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-deser-hjson/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-diesel-derives/armel (2.2.3-1 to 2.2.3-1)
- Migration status for rust-diesel-derives/armel (2.2.3-1 to 2.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-diesel-migrations/armel (2.2.0-1 to 2.2.0-1)
- Migration status for rust-diesel-migrations/armel (2.2.0-1 to 2.2.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-diesel-migrations/armel rust-rebuilderd (not considered)
- Invalidated by implicit-dependency
- rust-diesel-table-macro-syntax/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-diesel-table-macro-syntax/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-diesel/armel (2.2.7-2 to 2.2.7-2)
- Migration status for rust-diesel/armel (2.2.7-2 to 2.2.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-digest/armel (0.10.7-2 to 0.10.7-2)
- Migration status for rust-digest/armel (0.10.7-2 to 0.10.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-directories-next/armel (2.0.0-1 to 2.0.0-1)
- Migration status for rust-directories-next/armel (2.0.0-1 to 2.0.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-directories-next/armel rust-bacon (not considered)
- Invalidated by implicit-dependency
- rust-directories/armel (5.0.1-1 to 5.0.1-1)
- Migration status for rust-directories/armel (5.0.1-1 to 5.0.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-directories/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-dirs-next/armel (2.0.0-1 to 2.0.0-1)
- Migration status for rust-dirs-next/armel (2.0.0-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dirs-sys-next/armel (0.1.1-1 to 0.1.1-1)
- Migration status for rust-dirs-sys-next/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dirs-sys/armel (0.4.1-1 to 0.4.1-1)
- Migration status for rust-dirs-sys/armel (0.4.1-1 to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dirs/armel (5.0.1-1 to 5.0.1-1)
- Migration status for rust-dirs/armel (5.0.1-1 to 5.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dlib/armel (0.5.2-2 to 0.5.2-2)
- Migration status for rust-dlib/armel (0.5.2-2 to 0.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- (0.3.3-1 to 0.3.3-1)
- Migration status for rust-doc-comment/armel (0.3.3-1 to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-document-features/armel (0.2.7-3 to 0.2.7-3)
- Migration status for rust-document-features/armel (0.2.7-3 to 0.2.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dogged/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-dogged/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dotenvy/armel (0.15.7-1 to 0.15.7-1)
- Migration status for rust-dotenvy/armel (0.15.7-1 to 0.15.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-downcast-rs/armel (1.2.0-1 to 1.2.0-1)
- Migration status for rust-downcast-rs/armel (1.2.0-1 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dsa/armel (0.6.3-1 to 0.6.3-1)
- Migration status for rust-dsa/armel (0.6.3-1 to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dsl-auto-type/armel (0.1.3-1 to 0.1.3-1)
- Migration status for rust-dsl-auto-type/armel (0.1.3-1 to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dunce/armel (1.0.5-1 to 1.0.5-1)
- Migration status for rust-dunce/armel (1.0.5-1 to 1.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-dyn-clone/armel (1.0.16-1 to 1.0.16-1)
- Migration status for rust-dyn-clone/armel (1.0.16-1 to 1.0.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-eax/armel (0.5.0-1 to 0.5.0-1)
- Migration status for rust-eax/armel (0.5.0-1 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ecb/armel (0.1.1-1 to 0.1.1-1)
- Migration status for rust-ecb/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ecdsa/armel (0.16.9-1 to 0.16.9-1)
- Migration status for rust-ecdsa/armel (0.16.9-1 to 0.16.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-either/armel (1.13.0-1 to 1.13.0-1)
- Migration status for rust-either/armel (1.13.0-1 to 1.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-elliptic-curve/armel (0.13.8-1 to 0.13.8-1)
- Migration status for rust-elliptic-curve/armel (0.13.8-1 to 0.13.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-embedded-io/armel (0.6.1-1 to 0.6.1-1)
- Migration status for rust-embedded-io/armel (0.6.1-1 to 0.6.1-1): Will attempt migration (Any information below is purely informational)
- rust-ena/armel (0.14.0-2 to 0.14.0-2)
- Migration status for rust-ena/armel (0.14.0-2 to 0.14.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-encoding-index-japanese/armel (1.20141219.5-1 to 1.20141219.5-1)
- Migration status for rust-encoding-index-japanese/armel (1.20141219.5-1 to 1.20141219.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-encoding-index-korean/armel (1.20141219.5-1 to 1.20141219.5-1)
- Migration status for rust-encoding-index-korean/armel (1.20141219.5-1 to 1.20141219.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-encoding-index-simpchinese/armel (1.20141219.5-1 to 1.20141219.5-1)
- Migration status for rust-encoding-index-simpchinese/armel (1.20141219.5-1 to 1.20141219.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-encoding-index-singlebyte/armel (1.20141219.5-1 to 1.20141219.5-1)
- Migration status for rust-encoding-index-singlebyte/armel (1.20141219.5-1 to 1.20141219.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-encoding-index-tests/armel (0.1.4-2 to 0.1.4-2)
- Migration status for rust-encoding-index-tests/armel (0.1.4-2 to 0.1.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-encoding-index-tradchinese/armel (1.20141219.5-1 to 1.20141219.5-1)
- Migration status for rust-encoding-index-tradchinese/armel (1.20141219.5-1 to 1.20141219.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-encoding-rs/armel (0.8.35-1 to 0.8.35-1)
- Migration status for rust-encoding-rs/armel (0.8.35-1 to 0.8.35-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-encoding/armel (0.2.33-1 to 0.2.33-1)
- Migration status for rust-encoding/armel (0.2.33-1 to 0.2.33-1): Will attempt migration (Any information below is purely informational)
- rust-endi/armel (1.1.0-2 to 1.1.0-2)
- Migration status for rust-endi/armel (1.1.0-2 to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-endian-type/armel (0.1.2-2 to 0.1.2-2)
- Migration status for rust-endian-type/armel (0.1.2-2 to 0.1.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-enum-as-inner/armel (0.6.0-1 to 0.6.0-1)
- Migration status for rust-enum-as-inner/armel (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-enumflags2-derive/armel (0.7.10-1 to 0.7.10-1)
- Migration status for rust-enumflags2-derive/armel (0.7.10-1 to 0.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-enumflags2/armel (0.7.10-1 to 0.7.10-1)
- Migration status for rust-enumflags2/armel (0.7.10-1 to 0.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-enumset-derive/armel (0.10.0-1 to 0.10.0-1)
- Migration status for rust-enumset-derive/armel (0.10.0-1 to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-enumset/armel (1.1.5-1 to 1.1.5-1)
- Migration status for rust-enumset/armel (1.1.5-1 to 1.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-env-filter/armel (0.1.3-1 to 0.1.3-1)
- Migration status for rust-env-filter/armel (0.1.3-1 to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-env-logger/armel (0.11.6-1 to 0.11.6-1)
- Migration status for rust-env-logger/armel (0.11.6-1 to 0.11.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-equivalent/armel (1.0.1-1 to 1.0.1-1)
- Migration status for rust-equivalent/armel (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-erased-serde/armel (0.3.31-1 to 0.3.31-1)
- Migration status for rust-erased-serde/armel (0.3.31-1 to 0.3.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-errno/armel (0.3.8-1 to 0.3.8-1)
- Migration status for rust-errno/armel (0.3.8-1 to 0.3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-error-chain/armel (0.12.4-1 to 0.12.4-1)
- Migration status for rust-error-chain/armel (0.12.4-1 to 0.12.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-etcetera/armel (0.8.0-1 to 0.8.0-1)
- Migration status for rust-etcetera/armel (0.8.0-1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-eui48/armel (1.1.0-2 to 1.1.0-2)
- Migration status for rust-eui48/armel (1.1.0-2 to 1.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-event-listener-strategy/armel (0.5.3-1 to 0.5.3-1)
- Migration status for rust-event-listener-strategy/armel (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
- rust-exr/armel (1.73.0-2 to 1.73.0-2)
- Migration status for rust-exr/armel (1.73.0-2 to 1.73.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fallible-iterator/armel (0.3.0-2 to 0.3.0-2)
- Migration status for rust-fallible-iterator/armel (0.3.0-2 to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fallible-streaming-iterator/armel (0.1.9-1 to 0.1.9-1)
- Migration status for rust-fallible-streaming-iterator/armel (0.1.9-1 to 0.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fancy-regex/armel (0.11.0-3 to 0.11.0-3)
- Migration status for rust-fancy-regex/armel (0.11.0-3 to 0.11.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-faster-hex/armel (0.9.0-1 to 0.9.0-1)
- Migration status for rust-faster-hex/armel (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fastrand/armel (2.1.1-4 to 2.1.1-4)
- Migration status for rust-fastrand/armel (2.1.1-4 to 2.1.1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fd-lock/armel (3.0.13-1 to 3.0.13-1)
- Migration status for rust-fd-lock/armel (3.0.13-1 to 3.0.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fern/armel (0.6.2-1 to 0.6.2-1)
- Migration status for rust-fern/armel (0.6.2-1 to 0.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ff-derive/armel (0.13.0-1 to 0.13.0-1)
- Migration status for rust-ff-derive/armel (0.13.0-1 to 0.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ff/armel (0.13.0-1 to 0.13.0-1)
- Migration status for rust-ff/armel (0.13.0-1 to 0.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-field-offset/armel (0.3.6-1 to 0.3.6-1)
- Migration status for rust-field-offset/armel (0.3.6-1 to 0.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-file-size/armel (1.0.3-1 to 1.0.3-1)
- Migration status for rust-file-size/armel (1.0.3-1 to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-filedescriptor/armel (0.8.2-1 to 0.8.2-1)
- Migration status for rust-filedescriptor/armel (0.8.2-1 to 0.8.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-find-crate/armel (0.6.3-1 to 0.6.3-1)
- Migration status for rust-find-crate/armel (0.6.3-1 to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fixedbitset/armel (0.4.2-1 to 0.4.2-1)
- Migration status for rust-fixedbitset/armel (0.4.2-1 to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-flagset/armel (0.4.3-1 to 0.4.3-1)
- Migration status for rust-flagset/armel (0.4.3-1 to 0.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-flate2/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-flate2/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-flex-grow/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-flex-grow/armel (0.1.0-1 to 0.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-flex-grow/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-float-cmp/armel (0.9.0-1 to 0.9.0-1)
- Migration status for rust-float-cmp/armel (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-float-ord/armel (0.3.2-1 to 0.3.2-1)
- Migration status for rust-float-ord/armel (0.3.2-1 to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fnv/armel (1.0.7-1 to 1.0.7-1)
- Migration status for rust-fnv/armel (1.0.7-1 to 1.0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-font-kit/armel (0.14.2-2 to 0.14.2-2)
- Migration status for rust-font-kit/armel (0.14.2-2 to 0.14.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fontconfig-parser/armel (0.5.8-1 to 0.5.8-1)
- Migration status for rust-fontconfig-parser/armel (0.5.8-1 to 0.5.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fontdb/armel (0.22.0-3 to 0.22.0-3)
- Migration status for rust-fontdb/armel (0.22.0-3 to 0.22.0-3): Will attempt migration (Any information below is purely informational)
- rust-foreign-types-0.3/armel (0.3.2-2 to 0.3.2-2)
- Migration status for rust-foreign-types-0.3/armel (0.3.2-2 to 0.3.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-foreign-types-0.3/armel rust-openssl (not considered)
- Invalidated by implicit-dependency
- rust-foreign-types-macros/armel (0.2.1-1 to 0.2.1-1)
- Migration status for rust-foreign-types-macros/armel (0.2.1-1 to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-foreign-types-shared-0.1/armel (0.1.1-2 to 0.1.1-2)
- Migration status for rust-foreign-types-shared-0.1/armel (0.1.1-2 to 0.1.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-foreign-types-shared/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-foreign-types-shared/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-foreign-types/armel (0.5.0-1 to 0.5.0-1)
- Migration status for rust-foreign-types/armel (0.5.0-1 to 0.5.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-foreign-types/armel rust-lcms2 (not considered)
- Invalidated by implicit-dependency
- rust-form-urlencoded/armel (1.2.1-1 to 1.2.1-1)
- Migration status for rust-form-urlencoded/armel (1.2.1-1 to 1.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-freetype-rs/armel (0.36.0-2 to 0.36.0-2)
- Migration status for rust-freetype-rs/armel (0.36.0-2 to 0.36.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-freetype-sys/armel (0.20.1-1 to 0.20.1-1)
- Migration status for rust-freetype-sys/armel (0.20.1-1 to 0.20.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-freetype/armel (0.7.2-2 to 0.7.2-2)
- Migration status for rust-freetype/armel (0.7.2-2 to 0.7.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fuchsia-zircon-sys/armel (0.3.3-2 to 0.3.3-2)
- Migration status for rust-fuchsia-zircon-sys/armel (0.3.3-2 to 0.3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-fuchsia-zircon/armel (0.3.3-2 to 0.3.3-2)
- Migration status for rust-fuchsia-zircon/armel (0.3.3-2 to 0.3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-funty/armel (2.0.0-1 to 2.0.0-1)
- Migration status for rust-funty/armel (2.0.0-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futf/armel (0.1.5-1 to 0.1.5-1)
- Migration status for rust-futf/armel (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
- rust-futures-channel/armel (0.3.31-1 to 0.3.31-1)
- Migration status for rust-futures-channel/armel (0.3.31-1 to 0.3.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures-core/armel (0.3.31-1 to 0.3.31-1)
- Migration status for rust-futures-core/armel (0.3.31-1 to 0.3.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures-executor/armel (0.3.31-1 to 0.3.31-1)
- Migration status for rust-futures-executor/armel (0.3.31-1 to 0.3.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures-intrusive/armel (0.5.0-1 to 0.5.0-1)
- Migration status for rust-futures-intrusive/armel (0.5.0-1 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures-io/armel (0.3.31-1 to 0.3.31-1)
- Migration status for rust-futures-io/armel (0.3.31-1 to 0.3.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures-lite/armel (2.3.0-2 to 2.3.0-2)
- Migration status for rust-futures-lite/armel (2.3.0-2 to 2.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures-macro/armel (0.3.31-1 to 0.3.31-1)
- Migration status for rust-futures-macro/armel (0.3.31-1 to 0.3.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures-sink/armel (0.3.31-1 to 0.3.31-1)
- Migration status for rust-futures-sink/armel (0.3.31-1 to 0.3.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures-task/armel (0.3.31-3 to 0.3.31-3)
- Migration status for rust-futures-task/armel (0.3.31-3 to 0.3.31-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures-util/armel (0.3.31-1 to 0.3.31-1)
- Migration status for rust-futures-util/armel (0.3.31-1 to 0.3.31-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-futures/armel (0.3.31-2 to 0.3.31-2)
- Migration status for rust-futures/armel (0.3.31-2 to 0.3.31-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gdk-pixbuf-sys/armel (0.20.7-1 to 0.20.7-1)
- Migration status for rust-gdk-pixbuf-sys/armel (0.20.7-1 to 0.20.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gdk-pixbuf/armel (0.20.9-1 to 0.20.9-1)
- Migration status for rust-gdk-pixbuf/armel (0.20.9-1 to 0.20.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gdk4-sys/armel (0.9.6-1 to 0.9.6-1)
- Migration status for rust-gdk4-sys/armel (0.9.6-1 to 0.9.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gdk4-wayland-sys/armel (0.9.6-2 to 0.9.6-2)
- Migration status for rust-gdk4-wayland-sys/armel (0.9.6-2 to 0.9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gdk4-wayland/armel (0.9.6-1 to 0.9.6-1)
- Migration status for rust-gdk4-wayland/armel (0.9.6-1 to 0.9.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gdk4-x11-sys/armel (0.9.6-1 to 0.9.6-1)
- Migration status for rust-gdk4-x11-sys/armel (0.9.6-1 to 0.9.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gdk4-x11/armel (0.9.6-1 to 0.9.6-1)
- Migration status for rust-gdk4-x11/armel (0.9.6-1 to 0.9.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gdk4/armel (0.9.6-2 to 0.9.6-2)
- Migration status for rust-gdk4/armel (0.9.6-2 to 0.9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-generic-array/armel (0.14.7-1 to 0.14.7-1)
- Migration status for rust-generic-array/armel (0.14.7-1 to 0.14.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-geo-types/armel (0.7.11-2 to 0.7.11-2)
- Migration status for rust-geo-types/armel (0.7.11-2 to 0.7.11-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gethostname/armel (0.4.3-1 to 0.4.3-1)
- Migration status for rust-gethostname/armel (0.4.3-1 to 0.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-getopts/armel (0.2.21-4 to 0.2.21-4)
- Migration status for rust-getopts/armel (0.2.21-4 to 0.2.21-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-getopts/armel rust-ripcalc (not considered)
- Invalidated by implicit-dependency
- rust-getrandom/armel (0.2.15-3 to 0.2.15-3)
- Migration status for rust-getrandom/armel (0.2.15-3 to 0.2.15-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ghash/armel (0.5.0-1 to 0.5.0-1)
- Migration status for rust-ghash/armel (0.5.0-1 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ghost/armel (0.1.5-1 to 0.1.5-1)
- Migration status for rust-ghost/armel (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
- rust-gif/armel (0.13.1-1 to 0.13.1-1)
- Migration status for rust-gif/armel (0.13.1-1 to 0.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gimli/armel (0.31.1-2 to 0.31.1-2)
- Migration status for rust-gimli/armel (0.31.1-2 to 0.31.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gio-sys/armel (0.20.9-1 to 0.20.9-1)
- Migration status for rust-gio-sys/armel (0.20.9-1 to 0.20.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gio/armel (0.20.9-1 to 0.20.9-1)
- Migration status for rust-gio/armel (0.20.9-1 to 0.20.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-git2/armel (0.20.1-1 to 0.20.1-1)
- Migration status for rust-git2/armel (0.20.1-1 to 0.20.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-git2/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-gix-actor/armel (0.33.1-1 to 0.33.1-1)
- Migration status for rust-gix-actor/armel (0.33.1-1 to 0.33.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-archive/armel (0.18.0-2 to 0.18.0-2)
- Migration status for rust-gix-archive/armel (0.18.0-2 to 0.18.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-attributes/armel (0.23.1-1 to 0.23.1-1)
- Migration status for rust-gix-attributes/armel (0.23.1-1 to 0.23.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-bitmap/armel (0.2.13-1 to 0.2.13-1)
- Migration status for rust-gix-bitmap/armel (0.2.13-1 to 0.2.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-chunk/armel (0.4.10-1 to 0.4.10-1)
- Migration status for rust-gix-chunk/armel (0.4.10-1 to 0.4.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-command/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-gix-command/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-commitgraph/armel (0.25.1-1 to 0.25.1-1)
- Migration status for rust-gix-commitgraph/armel (0.25.1-1 to 0.25.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-config-value/armel (0.14.10-1 to 0.14.10-1)
- Migration status for rust-gix-config-value/armel (0.14.10-1 to 0.14.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-config/armel (0.42.0-1 to 0.42.0-1)
- Migration status for rust-gix-config/armel (0.42.0-1 to 0.42.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-credentials/armel (0.26.0-1 to 0.26.0-1)
- Migration status for rust-gix-credentials/armel (0.26.0-1 to 0.26.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-date/armel (0.9.3-1 to 0.9.3-1)
- Migration status for rust-gix-date/armel (0.9.3-1 to 0.9.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-diff/armel (0.49.0-1 to 0.49.0-1)
- Migration status for rust-gix-diff/armel (0.49.0-1 to 0.49.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-dir/armel (0.11.0-1 to 0.11.0-1)
- Migration status for rust-gix-dir/armel (0.11.0-1 to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-discover/armel (0.37.0-1 to 0.37.0-1)
- Migration status for rust-gix-discover/armel (0.37.0-1 to 0.37.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-features/armel (0.39.1-2 to 0.39.1-2)
- Migration status for rust-gix-features/armel (0.39.1-2 to 0.39.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-filter/armel (0.16.0-1 to 0.16.0-1)
- Migration status for rust-gix-filter/armel (0.16.0-1 to 0.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-fs/armel (0.12.1-1 to 0.12.1-1)
- Migration status for rust-gix-fs/armel (0.12.1-1 to 0.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-glob/armel (0.17.1-1 to 0.17.1-1)
- Migration status for rust-gix-glob/armel (0.17.1-1 to 0.17.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-hash/armel (0.15.1-2 to 0.15.1-2)
- Migration status for rust-gix-hash/armel (0.15.1-2 to 0.15.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-hashtable/armel (0.6.0-1 to 0.6.0-1)
- Migration status for rust-gix-hashtable/armel (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-ignore/armel (0.12.1-1 to 0.12.1-1)
- Migration status for rust-gix-ignore/armel (0.12.1-1 to 0.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-index/armel (0.37.0-1 to 0.37.0-1)
- Migration status for rust-gix-index/armel (0.37.0-1 to 0.37.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-lock/armel (15.0.1-1 to 15.0.1-1)
- Migration status for rust-gix-lock/armel (15.0.1-1 to 15.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-mailmap/armel (0.25.1-1 to 0.25.1-1)
- Migration status for rust-gix-mailmap/armel (0.25.1-1 to 0.25.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-merge/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-gix-merge/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-negotiate/armel (0.17.0-1 to 0.17.0-1)
- Migration status for rust-gix-negotiate/armel (0.17.0-1 to 0.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-object/armel (0.46.1-1 to 0.46.1-1)
- Migration status for rust-gix-object/armel (0.46.1-1 to 0.46.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-odb/armel (0.66.0-1 to 0.66.0-1)
- Migration status for rust-gix-odb/armel (0.66.0-1 to 0.66.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-pack/armel (0.56.0-1 to 0.56.0-1)
- Migration status for rust-gix-pack/armel (0.56.0-1 to 0.56.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-packetline-blocking/armel (0.18.1-1 to 0.18.1-1)
- Migration status for rust-gix-packetline-blocking/armel (0.18.1-1 to 0.18.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-packetline/armel (0.18.2-1 to 0.18.2-1)
- Migration status for rust-gix-packetline/armel (0.18.2-1 to 0.18.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-path/armel (0.10.13-1 to 0.10.13-1)
- Migration status for rust-gix-path/armel (0.10.13-1 to 0.10.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-pathspec/armel (0.8.1-1 to 0.8.1-1)
- Migration status for rust-gix-pathspec/armel (0.8.1-1 to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-prompt/armel (0.9.0-1 to 0.9.0-1)
- Migration status for rust-gix-prompt/armel (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-protocol/armel (0.47.0-1 to 0.47.0-1)
- Migration status for rust-gix-protocol/armel (0.47.0-1 to 0.47.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-quote/armel (0.4.14-1 to 0.4.14-1)
- Migration status for rust-gix-quote/armel (0.4.14-1 to 0.4.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-ref/armel (0.49.1-1 to 0.49.1-1)
- Migration status for rust-gix-ref/armel (0.49.1-1 to 0.49.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-refspec/armel (0.27.0-1 to 0.27.0-1)
- Migration status for rust-gix-refspec/armel (0.27.0-1 to 0.27.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-revision/armel (0.31.1-1 to 0.31.1-1)
- Migration status for rust-gix-revision/armel (0.31.1-1 to 0.31.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-revwalk/armel (0.17.0-1 to 0.17.0-1)
- Migration status for rust-gix-revwalk/armel (0.17.0-1 to 0.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-sec/armel (0.10.10-1 to 0.10.10-1)
- Migration status for rust-gix-sec/armel (0.10.10-1 to 0.10.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-shallow/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-gix-shallow/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-status/armel (0.16.0-1 to 0.16.0-1)
- Migration status for rust-gix-status/armel (0.16.0-1 to 0.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-submodule/armel (0.16.0-1 to 0.16.0-1)
- Migration status for rust-gix-submodule/armel (0.16.0-1 to 0.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-tempfile/armel (15.0.0-1 to 15.0.0-1)
- Migration status for rust-gix-tempfile/armel (15.0.0-1 to 15.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-trace/armel (0.1.11-1 to 0.1.11-1)
- Migration status for rust-gix-trace/armel (0.1.11-1 to 0.1.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-transport/armel (0.44.0-1 to 0.44.0-1)
- Migration status for rust-gix-transport/armel (0.44.0-1 to 0.44.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-traverse/armel (0.43.1-1 to 0.43.1-1)
- Migration status for rust-gix-traverse/armel (0.43.1-1 to 0.43.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-url/armel (0.28.2-1 to 0.28.2-1)
- Migration status for rust-gix-url/armel (0.28.2-1 to 0.28.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-utils/armel (0.1.13-1 to 0.1.13-1)
- Migration status for rust-gix-utils/armel (0.1.13-1 to 0.1.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-validate/armel (0.9.2-1 to 0.9.2-1)
- Migration status for rust-gix-validate/armel (0.9.2-1 to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-worktree-state/armel (0.16.0-1 to 0.16.0-1)
- Migration status for rust-gix-worktree-state/armel (0.16.0-1 to 0.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-worktree-stream/armel (0.18.0-1 to 0.18.0-1)
- Migration status for rust-gix-worktree-stream/armel (0.18.0-1 to 0.18.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix-worktree/armel (0.38.0-1 to 0.38.0-1)
- Migration status for rust-gix-worktree/armel (0.38.0-1 to 0.38.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gix/armel (0.69.1-1 to 0.69.1-1)
- Migration status for rust-gix/armel (0.69.1-1 to 0.69.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-gix/armel rust-bacon (not considered)
- Invalidated by implicit-dependency
- rust-gl-generator/armel (0.14.0-1 to 0.14.0-1)
- Migration status for rust-gl-generator/armel (0.14.0-1 to 0.14.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gl/armel (0.14.0-2 to 0.14.0-2)
- Migration status for rust-gl/armel (0.14.0-2 to 0.14.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-glib-macros/armel (0.20.7-1 to 0.20.7-1)
- Migration status for rust-glib-macros/armel (0.20.7-1 to 0.20.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-glib-sys-0.18/armel (0.18.1-2 to 0.18.1-2)
- Migration status for rust-glib-sys-0.18/armel (0.18.1-2 to 0.18.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-glib-sys/armel (0.20.9-1 to 0.20.9-1)
- Migration status for rust-glib-sys/armel (0.20.9-1 to 0.20.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-glib/armel (0.20.9-1 to 0.20.9-1)
- Migration status for rust-glib/armel (0.20.9-1 to 0.20.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-glob/armel (0.3.2-1 to 0.3.2-1)
- Migration status for rust-glob/armel (0.3.2-1 to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gobject-sys-0.18/armel (0.18.0-2 to 0.18.0-2)
- Migration status for rust-gobject-sys-0.18/armel (0.18.0-2 to 0.18.0-2): Will attempt migration (Any information below is purely informational)
- rust-gobject-sys/armel (0.20.9-1 to 0.20.9-1)
- Migration status for rust-gobject-sys/armel (0.20.9-1 to 0.20.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-graphene-rs/armel (0.20.9-1 to 0.20.9-1)
- Migration status for rust-graphene-rs/armel (0.20.9-1 to 0.20.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-graphene-sys/armel (0.20.7-2 to 0.20.7-2)
- Migration status for rust-graphene-sys/armel (0.20.7-2 to 0.20.7-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-group/armel (0.13.0-1 to 0.13.0-1)
- Migration status for rust-group/armel (0.13.0-1 to 0.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gsk4-sys/armel (0.9.6-1 to 0.9.6-1)
- Migration status for rust-gsk4-sys/armel (0.9.6-1 to 0.9.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gsk4/armel (0.9.6-1 to 0.9.6-1)
- Migration status for rust-gsk4/armel (0.9.6-1 to 0.9.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gst-plugin-gtk4/armel (0.13.5-1 to 0.13.5-1)
- Migration status for rust-gst-plugin-gtk4/armel (0.13.5-1 to 0.13.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gst-plugin-version-helper/armel (0.8.2-2 to 0.8.2-2)
- Migration status for rust-gst-plugin-version-helper/armel (0.8.2-2 to 0.8.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-allocators-sys/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-allocators-sys/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-allocators/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-allocators/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-base-sys/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-base-sys/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-base/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-base/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-gl-egl-sys/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-gl-egl-sys/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-gl-egl/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-gl-egl/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-gl-sys/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-gl-sys/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-gl-wayland-sys/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-gl-wayland-sys/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-gl-wayland/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-gl-wayland/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-gl-x11-sys/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-gl-x11-sys/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-gl-x11/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-gl-x11/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-gl/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-gl/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-sys/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-sys/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-video-sys/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-video-sys/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer-video/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer-video/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gstreamer/armel (0.23.5-2 to 0.23.5-2)
- Migration status for rust-gstreamer/armel (0.23.5-2 to 0.23.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gtk4-macros/armel (0.9.5-1 to 0.9.5-1)
- Migration status for rust-gtk4-macros/armel (0.9.5-1 to 0.9.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gtk4-sys/armel (0.9.6-2 to 0.9.6-2)
- Migration status for rust-gtk4-sys/armel (0.9.6-2 to 0.9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-gtk4/armel (0.9.6-2 to 0.9.6-2)
- Migration status for rust-gtk4/armel (0.9.6-2 to 0.9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-h2/armel (0.4.7-3 to 0.4.7-3)
- Migration status for rust-h2/armel (0.4.7-3 to 0.4.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-h3-quinn/armel (0.0.7-1 to 0.0.7-1)
- Migration status for rust-h3-quinn/armel (0.0.7-1 to 0.0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-h3/armel (0.0.6-2 to 0.0.6-2)
- Migration status for rust-h3/armel (0.0.6-2 to 0.0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-half/armel (2.4.1-2 to 2.4.1-2)
- Migration status for rust-half/armel (2.4.1-2 to 2.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hash32/armel (0.3.1-2 to 0.3.1-2)
- Migration status for rust-hash32/armel (0.3.1-2 to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hashbrown/armel (0.14.5-5 to 0.14.5-5)
- Migration status for rust-hashbrown/armel (0.14.5-5 to 0.14.5-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hashlink/armel (0.8.4-1 to 0.8.4-1)
- Migration status for rust-hashlink/armel (0.8.4-1 to 0.8.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-heapless/armel (0.8.0-2 to 0.8.0-2)
- Migration status for rust-heapless/armel (0.8.0-2 to 0.8.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-heapsize/armel (0.4.2-1 to 0.4.2-1)
- Migration status for rust-heapsize/armel (0.4.2-1 to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-heck/armel (0.5.0-1+really0.4.1-2 to 0.5.0-1+really0.4.1-2)
- Migration status for rust-heck/armel (0.5.0-1+really0.4.1-2 to 0.5.0-1+really0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hex-literal/armel (0.4.1-1 to 0.4.1-1)
- Migration status for rust-hex-literal/armel (0.4.1-1 to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hex/armel (0.4.3-2 to 0.4.3-2)
- Migration status for rust-hex/armel (0.4.3-2 to 0.4.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hickory-client/armel (0.24.4-1 to 0.24.4-1)
- Migration status for rust-hickory-client/armel (0.24.4-1 to 0.24.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hickory-proto/armel (0.24.4-4.1 to 0.24.4-4.1)
- Migration status for rust-hickory-proto/armel (0.24.4-4.1 to 0.24.4-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hickory-resolver/armel (0.24.4-1 to 0.24.4-1)
- Migration status for rust-hickory-resolver/armel (0.24.4-1 to 0.24.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hkdf/armel (0.12.4-1 to 0.12.4-1)
- Migration status for rust-hkdf/armel (0.12.4-1 to 0.12.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hmac/armel (0.12.1-1 to 0.12.1-1)
- Migration status for rust-hmac/armel (0.12.1-1 to 0.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-home/armel (0.5.9-1 to 0.5.9-1)
- Migration status for rust-home/armel (0.5.9-1 to 0.5.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hostname/armel (0.3.1-2 to 0.3.1-2)
- Migration status for rust-hostname/armel (0.3.1-2 to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-http-0.2/armel (0.2.11-1 to 0.2.11-1)
- Migration status for rust-http-0.2/armel (0.2.11-1 to 0.2.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-http-body-util/armel (0.1.2-1 to 0.1.2-1)
- Migration status for rust-http-body-util/armel (0.1.2-1 to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-http-body/armel (1.0.1-1 to 1.0.1-1)
- Migration status for rust-http-body/armel (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-http/armel (1.2.0-1 to 1.2.0-1)
- Migration status for rust-http/armel (1.2.0-1 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-httparse/armel (1.8.0-1 to 1.8.0-1)
- Migration status for rust-httparse/armel (1.8.0-1 to 1.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-httpdate/armel (1.0.2-1 to 1.0.2-1)
- Migration status for rust-httpdate/armel (1.0.2-1 to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-human-format/armel (1.0.3-1 to 1.0.3-1)
- Migration status for rust-human-format/armel (1.0.3-1 to 1.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-humantime/armel (2.1.0-2 to 2.1.0-2)
- Migration status for rust-humantime/armel (2.1.0-2 to 2.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hyper-tls/armel (0.6.0-1 to 0.6.0-1)
- Migration status for rust-hyper-tls/armel (0.6.0-1 to 0.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hyper-util/armel (0.1.10-1 to 0.1.10-1)
- Migration status for rust-hyper-util/armel (0.1.10-1 to 0.1.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-hyper/armel (1.5.2-1 to 1.5.2-1)
- Migration status for rust-hyper/armel (1.5.2-1 to 1.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-iana-time-zone/armel (0.1.63-1 to 0.1.63-1)
- Migration status for rust-iana-time-zone/armel (0.1.63-1 to 0.1.63-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-idea/armel (0.5.1-1 to 0.5.1-1)
- Migration status for rust-idea/armel (0.5.1-1 to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ident-case/armel (1.0.1-1 to 1.0.1-1)
- Migration status for rust-ident-case/armel (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-idna-adapter/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-idna-adapter/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-idna-mapping/armel (1.0.0-1 to 1.0.0-1)
- Migration status for rust-idna-mapping/armel (1.0.0-1 to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-idna/armel (1.0.3-2 to 1.0.3-2)
- Migration status for rust-idna/armel (1.0.3-2 to 1.0.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-image-webp/armel (0.2.0-2 to 0.2.0-2)
- Migration status for rust-image-webp/armel (0.2.0-2 to 0.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-image/armel (0.25.5-3 to 0.25.5-3)
- Migration status for rust-image/armel (0.25.5-3 to 0.25.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-imagesize/armel (0.13.0-1 to 0.13.0-1)
- Migration status for rust-imagesize/armel (0.13.0-1 to 0.13.0-1): Will attempt migration (Any information below is purely informational)
- rust-imara-diff/armel (0.1.7-1 to 0.1.7-1)
- Migration status for rust-imara-diff/armel (0.1.7-1 to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-impl-more/armel (0.1.9-1 to 0.1.9-1)
- Migration status for rust-impl-more/armel (0.1.9-1 to 0.1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-include-dir-macros/armel (0.7.3-1 to 0.7.3-1)
- Migration status for rust-include-dir-macros/armel (0.7.3-1 to 0.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-include-dir/armel (0.7.3-1 to 0.7.3-1)
- Migration status for rust-include-dir/armel (0.7.3-1 to 0.7.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-include-dir/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-indenter/armel (0.3.3-1 to 0.3.3-1)
- Migration status for rust-indenter/armel (0.3.3-1 to 0.3.3-1): Will attempt migration (Any information below is purely informational)
- rust-indexmap/armel (2.7.0-1 to 2.7.0-1)
- Migration status for rust-indexmap/armel (2.7.0-1 to 2.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-inotify-sys/armel (0.1.5-1 to 0.1.5-1)
- Migration status for rust-inotify-sys/armel (0.1.5-1 to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-inotify/armel (0.9.6-1 to 0.9.6-1)
- Migration status for rust-inotify/armel (0.9.6-1 to 0.9.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-inout/armel (0.1.3-3 to 0.1.3-3)
- Migration status for rust-inout/armel (0.1.3-3 to 0.1.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-io-close/armel (0.3.7-1 to 0.3.7-1)
- Migration status for rust-io-close/armel (0.3.7-1 to 0.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-iovec/armel (0.1.2-1 to 0.1.2-1)
- Migration status for rust-iovec/armel (0.1.2-1 to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ipnet/armel (2.11.0-1 to 2.11.0-1)
- Migration status for rust-ipnet/armel (2.11.0-1 to 2.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ipnetwork/armel (0.17.0-1 to 0.17.0-1)
- Migration status for rust-ipnetwork/armel (0.17.0-1 to 0.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-iq/armel (0.2.2-1 to 0.2.2-1)
- Migration status for rust-iq/armel (0.2.2-1 to 0.2.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-iq/armel rust-bacon (not considered)
- Invalidated by implicit-dependency
- rust-is-executable/armel (1.0.1-3 to 1.0.1-3)
- Migration status for rust-is-executable/armel (1.0.1-3 to 1.0.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-is-terminal/armel (0.4.13-1 to 0.4.13-1)
- Migration status for rust-is-terminal/armel (0.4.13-1 to 0.4.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-itertools/armel (0.13.0-3 to 0.13.0-3)
- Migration status for rust-itertools/armel (0.13.0-3 to 0.13.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-itoa/armel (1.0.14-1 to 1.0.14-1)
- Migration status for rust-itoa/armel (1.0.14-1 to 1.0.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ivf/armel (0.1.3-1 to 0.1.3-1)
- Migration status for rust-ivf/armel (0.1.3-1 to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-jiff-tzdb/armel (0.1.2-1 to 0.1.2-1)
- Migration status for rust-jiff-tzdb/armel (0.1.2-1 to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-jiff/armel (0.1.28-1 to 0.1.28-1)
- Migration status for rust-jiff/armel (0.1.28-1 to 0.1.28-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-jobserver/armel (0.1.32-1 to 0.1.32-1)
- Migration status for rust-jobserver/armel (0.1.32-1 to 0.1.32-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-jpeg-decoder/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-jpeg-decoder/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-js-sys/armel (0.3.77-1 to 0.3.77-1)
- Migration status for rust-js-sys/armel (0.3.77-1 to 0.3.77-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-jwalk/armel (0.8.1-1 to 0.8.1-1)
- Migration status for rust-jwalk/armel (0.8.1-1 to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-keccak/armel (0.1.5-1 to 0.1.5-1)
- Migration status for rust-keccak/armel (0.1.5-1 to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-khronos-api/armel (3.1.0-1 to 3.1.0-1)
- Migration status for rust-khronos-api/armel (3.1.0-1 to 3.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-khronos-egl/armel (4.1.0-5 to 4.1.0-5)
- Migration status for rust-khronos-egl/armel (4.1.0-5 to 4.1.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-kstring/armel (2.0.0-1 to 2.0.0-1)
- Migration status for rust-kstring/armel (2.0.0-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-kurbo/armel (0.11.1-1 to 0.11.1-1)
- Migration status for rust-kurbo/armel (0.11.1-1 to 0.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lab/armel (0.11.0-1 to 0.11.0-1)
- Migration status for rust-lab/armel (0.11.0-1 to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lalrpop-util/armel (0.20.0-1 to 0.20.0-1)
- Migration status for rust-lalrpop-util/armel (0.20.0-1 to 0.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lalrpop/armel (0.20.2-2 to 0.20.2-2)
- Migration status for rust-lalrpop/armel (0.20.2-2 to 0.20.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-language-tags/armel (0.3.2-1 to 0.3.2-1)
- Migration status for rust-language-tags/armel (0.3.2-1 to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lazy-static/armel (1.5.0-1 to 1.5.0-1)
- Migration status for rust-lazy-static/armel (1.5.0-1 to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lebe/armel (0.5.2-1 to 0.5.2-1)
- Migration status for rust-lebe/armel (0.5.2-1 to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-libc/armel (0.2.175-1 to 0.2.175-1)
- Migration status for rust-libc/armel (0.2.175-1 to 0.2.175-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-libdbus-sys/armel (0.2.5-1 to 0.2.5-1)
- Migration status for rust-libdbus-sys/armel (0.2.5-1 to 0.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-libgit2-sys/armel (0.18.1-1 to 0.18.1-1)
- Migration status for rust-libgit2-sys/armel (0.18.1-1 to 0.18.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-libloading/armel (0.8.5-1 to 0.8.5-1)
- Migration status for rust-libloading/armel (0.8.5-1 to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-libm/armel (0.2.8-1 to 0.2.8-1)
- Migration status for rust-libm/armel (0.2.8-1 to 0.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-libnghttp2-sys/armel (0.1.3-1 to 0.1.3-1)
- Migration status for rust-libnghttp2-sys/armel (0.1.3-1 to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-libsqlite3-sys/armel (0.26.0-1 to 0.26.0-1)
- Migration status for rust-libsqlite3-sys/armel (0.26.0-1 to 0.26.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-libssh2-sys/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-libssh2-sys/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-libz-sys/armel (1.1.20-1 to 1.1.20-1)
- Migration status for rust-libz-sys/armel (1.1.20-1 to 1.1.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-linked-hash-map/armel (0.5.6-1 to 0.5.6-1)
- Migration status for rust-linked-hash-map/armel (0.5.6-1 to 0.5.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-linux-raw-sys/armel (0.4.14-1 to 0.4.14-1)
- Migration status for rust-linux-raw-sys/armel (0.4.14-1 to 0.4.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-litrs/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-litrs/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-local-channel/armel (0.1.5-1 to 0.1.5-1)
- Migration status for rust-local-channel/armel (0.1.5-1 to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-local-waker/armel (0.1.4-1 to 0.1.4-1)
- Migration status for rust-local-waker/armel (0.1.4-1 to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lock-api/armel (0.4.12-1 to 0.4.12-1)
- Migration status for rust-lock-api/armel (0.4.12-1 to 0.4.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lockfree-object-pool/armel (0.1.6-1 to 0.1.6-1)
- Migration status for rust-lockfree-object-pool/armel (0.1.6-1 to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-log/armel (0.4.26-1 to 0.4.26-1)
- Migration status for rust-log/armel (0.4.26-1 to 0.4.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lru-cache/armel (0.1.2-1 to 0.1.2-1)
- Migration status for rust-lru-cache/armel (0.1.2-1 to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lru/armel (0.12.3-2 to 0.12.3-2)
- Migration status for rust-lru/armel (0.12.3-2 to 0.12.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lzma-rs/armel (0.3.0-3 to 0.3.0-3)
- Migration status for rust-lzma-rs/armel (0.3.0-3 to 0.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-lzma-sys/armel (0.1.20-1 to 0.1.20-1)
- Migration status for rust-lzma-sys/armel (0.1.20-1 to 0.1.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-mac-address/armel (1.1.5-2 to 1.1.5-2)
- Migration status for rust-mac-address/armel (1.1.5-2 to 1.1.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-mac/armel (0.1.1-1 to 0.1.1-1)
- Migration status for rust-mac/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-markup-proc-macro/armel (0.13.1-1 to 0.13.1-1)
- Migration status for rust-markup-proc-macro/armel (0.13.1-1 to 0.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-markup/armel (0.13.1-1 to 0.13.1-1)
- Migration status for rust-markup/armel (0.13.1-1 to 0.13.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-match-cfg/armel (0.1.0-4 to 0.1.0-4)
- Migration status for rust-match-cfg/armel (0.1.0-4 to 0.1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-maybe-async/armel (0.2.7-1 to 0.2.7-1)
- Migration status for rust-maybe-async/armel (0.2.7-1 to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-md-5/armel (0.10.6-1 to 0.10.6-1)
- Migration status for rust-md-5/armel (0.10.6-1 to 0.10.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-md5-asm/armel (0.5.0-2 to 0.5.0-2)
- Migration status for rust-md5-asm/armel (0.5.0-2 to 0.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-memchr/armel (2.7.4-1 to 2.7.4-1)
- Migration status for rust-memchr/armel (2.7.4-1 to 2.7.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-memmap2/armel (0.9.5-1 to 0.9.5-1)
- Migration status for rust-memmap2/armel (0.9.5-1 to 0.9.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-memoffset/armel (0.8.0-1 to 0.8.0-1)
- Migration status for rust-memoffset/armel (0.8.0-1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-memsec/armel (0.7.0-1 to 0.7.0-1)
- Migration status for rust-memsec/armel (0.7.0-1 to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-memuse/armel (0.2.2-1 to 0.2.2-1)
- Migration status for rust-memuse/armel (0.2.2-1 to 0.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-migrations-internals/armel (2.2.0-1 to 2.2.0-1)
- Migration status for rust-migrations-internals/armel (2.2.0-1 to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-migrations-macros/armel (2.2.0-1 to 2.2.0-1)
- Migration status for rust-migrations-macros/armel (2.2.0-1 to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-mime-guess/armel (2.0.5-1 to 2.0.5-1)
- Migration status for rust-mime-guess/armel (2.0.5-1 to 2.0.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-mime/armel (0.3.17-1 to 0.3.17-1)
- Migration status for rust-mime/armel (0.3.17-1 to 0.3.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-minimad/armel (0.13.0-1 to 0.13.0-1)
- Migration status for rust-minimad/armel (0.13.0-1 to 0.13.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-minimad/armel rust-termimad (not considered)
- Invalidated by implicit-dependency
- rust-minimal-lexical/armel (0.2.1-2 to 0.2.1-2)
- Migration status for rust-minimal-lexical/armel (0.2.1-2 to 0.2.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-miniz-oxide/armel (0.7.1-2 to 0.7.1-2)
- Migration status for rust-miniz-oxide/armel (0.7.1-2 to 0.7.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-mint/armel (0.5.9-1 to 0.5.9-1)
- Migration status for rust-mint/armel (0.5.9-1 to 0.5.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-mio-0.6/armel (0.6.23-5 to 0.6.23-5)
- Migration status for rust-mio-0.6/armel (0.6.23-5 to 0.6.23-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-mio-uds/armel (0.6.7-1 to 0.6.7-1)
- Migration status for rust-mio-uds/armel (0.6.7-1 to 0.6.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-mio/armel (1.0.2-3 to 1.0.2-3)
- Migration status for rust-mio/armel (1.0.2-3 to 1.0.2-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-miow/armel (0.3.7-1 to 0.3.7-1)
- Migration status for rust-miow/armel (0.3.7-1 to 0.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-muldiv/armel (1.0.1-2 to 1.0.1-2)
- Migration status for rust-muldiv/armel (1.0.1-2 to 1.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-munge-macro/armel (0.4.1-1 to 0.4.1-1)
- Migration status for rust-munge-macro/armel (0.4.1-1 to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-munge/armel (0.4.1-1 to 0.4.1-1)
- Migration status for rust-munge/armel (0.4.1-1 to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-mysqlclient-sys/armel (0.2.5-2 to 0.2.5-2)
- Migration status for rust-mysqlclient-sys/armel (0.2.5-2 to 0.2.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-nasm-rs/armel (0.2.5-1 to 0.2.5-1)
- Migration status for rust-nasm-rs/armel (0.2.5-1 to 0.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-native-tls/armel (0.2.13-1 to 0.2.13-1)
- Migration status for rust-native-tls/armel (0.2.13-1 to 0.2.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-net2/armel (0.2.39-1 to 0.2.39-1)
- Migration status for rust-net2/armel (0.2.39-1 to 0.2.39-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-nettle-sys/armel (2.3.1-1 to 2.3.1-1)
- Migration status for rust-nettle-sys/armel (2.3.1-1 to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-nettle/armel (7.3.0-1 to 7.3.0-1)
- Migration status for rust-nettle/armel (7.3.0-1 to 7.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-new-debug-unreachable/armel (1.0.4-1 to 1.0.4-1)
- Migration status for rust-new-debug-unreachable/armel (1.0.4-1 to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-nibble-vec/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-nibble-vec/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-nix/armel (0.29.0-2 to 0.29.0-2)
- Migration status for rust-nix/armel (0.29.0-2 to 0.29.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-no-panic/armel (0.1.32-1 to 0.1.32-1)
- Migration status for rust-no-panic/armel (0.1.32-1 to 0.1.32-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-nom/armel (7.1.3-1 to 7.1.3-1)
- Migration status for rust-nom/armel (7.1.3-1 to 7.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-nonempty/armel (0.11.0-1 to 0.11.0-1)
- Migration status for rust-nonempty/armel (0.11.0-1 to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-noop-proc-macro/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-noop-proc-macro/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-normpath/armel (1.1.1-1 to 1.1.1-1)
- Migration status for rust-normpath/armel (1.1.1-1 to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-notify/armel (6.1.1-3 to 6.1.1-3)
- Migration status for rust-notify/armel (6.1.1-3 to 6.1.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-notify/armel rust-bacon (not considered)
- Invalidated by implicit-dependency
- rust-num-bigint-dig/armel (0.8.4-1 to 0.8.4-1)
- Migration status for rust-num-bigint-dig/armel (0.8.4-1 to 0.8.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-bigint/armel (0.4.6-1 to 0.4.6-1)
- Migration status for rust-num-bigint/armel (0.4.6-1 to 0.4.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-complex/armel (0.4.6-3 to 0.4.6-3)
- Migration status for rust-num-complex/armel (0.4.6-3 to 0.4.6-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-conv/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-num-conv/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-cpus/armel (1.16.0-1 to 1.16.0-1)
- Migration status for rust-num-cpus/armel (1.16.0-1 to 1.16.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-derive/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-num-derive/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-integer/armel (0.1.46-1 to 0.1.46-1)
- Migration status for rust-num-integer/armel (0.1.46-1 to 0.1.46-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-iter/armel (0.1.45-1 to 0.1.45-1)
- Migration status for rust-num-iter/armel (0.1.45-1 to 0.1.45-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-rational/armel (0.4.2-1 to 0.4.2-1)
- Migration status for rust-num-rational/armel (0.4.2-1 to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-threads/armel (0.1.7-1 to 0.1.7-1)
- Migration status for rust-num-threads/armel (0.1.7-1 to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-num-traits/armel (0.2.19-2 to 0.2.19-2)
- Migration status for rust-num-traits/armel (0.2.19-2 to 0.2.19-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-numtoa/armel (0.2.4-1 to 0.2.4-1)
- Migration status for rust-numtoa/armel (0.2.4-1 to 0.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-object/armel (0.36.5-2 to 0.36.5-2)
- Migration status for rust-object/armel (0.36.5-2 to 0.36.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ocb3/armel (0.1.0-2 to 0.1.0-2)
- Migration status for rust-ocb3/armel (0.1.0-2 to 0.1.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-oid/armel (0.2.1-2 to 0.2.1-2)
- Migration status for rust-oid/armel (0.2.1-2 to 0.2.1-2): Will attempt migration (Any information below is purely informational)
- rust-once-cell/armel (1.20.2-1 to 1.20.2-1)
- Migration status for rust-once-cell/armel (1.20.2-1 to 1.20.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-oorandom/armel (11.1.3-1 to 11.1.3-1)
- Migration status for rust-oorandom/armel (11.1.3-1 to 11.1.3-1): Will attempt migration (Any information below is purely informational)
- rust-opaque-debug/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-opaque-debug/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-opener/armel (0.6.1-2 to 0.6.1-2)
- Migration status for rust-opener/armel (0.6.1-2 to 0.6.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-opener/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-openpgp-cert-d/armel (0.3.4-1 to 0.3.4-1)
- Migration status for rust-openpgp-cert-d/armel (0.3.4-1 to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-openssl-macros/armel (0.1.1-1 to 0.1.1-1)
- Migration status for rust-openssl-macros/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-openssl-macros/armel rust-openssl (not considered)
- Invalidated by implicit-dependency
- rust-openssl-probe/armel (0.1.2-1 to 0.1.2-1)
- Migration status for rust-openssl-probe/armel (0.1.2-1 to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-openssl-sys/armel (0.9.109-1 to 0.9.109-1)
- Migration status for rust-openssl-sys/armel (0.9.109-1 to 0.9.109-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-option-ext/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-option-ext/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-option-operations/armel (0.5.0-2 to 0.5.0-2)
- Migration status for rust-option-operations/armel (0.5.0-2 to 0.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-os-pipe/armel (1.2.1-1 to 1.2.1-1)
- Migration status for rust-os-pipe/armel (1.2.1-1 to 1.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-owned-ttf-parser/armel (0.25.0-2 to 0.25.0-2)
- Migration status for rust-owned-ttf-parser/armel (0.25.0-2 to 0.25.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-owning-ref/armel (0.4.1-1 to 0.4.1-1)
- Migration status for rust-owning-ref/armel (0.4.1-1 to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-p256/armel (0.13.2-1 to 0.13.2-1)
- Migration status for rust-p256/armel (0.13.2-1 to 0.13.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-p384/armel (0.13.0-1 to 0.13.0-1)
- Migration status for rust-p384/armel (0.13.0-1 to 0.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-palette-derive/armel (0.7.6-1 to 0.7.6-1)
- Migration status for rust-palette-derive/armel (0.7.6-1 to 0.7.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-palette/armel (0.7.6-1 to 0.7.6-1)
- Migration status for rust-palette/armel (0.7.6-1 to 0.7.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pango-sys/armel (0.20.9-2 to 0.20.9-2)
- Migration status for rust-pango-sys/armel (0.20.9-2 to 0.20.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pango/armel (0.20.9-4 to 0.20.9-4)
- Migration status for rust-pango/armel (0.20.9-4 to 0.20.9-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-parking-lot-core/armel (0.9.10-1 to 0.9.10-1)
- Migration status for rust-parking-lot-core/armel (0.9.10-1 to 0.9.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-parking-lot/armel (0.12.3-1 to 0.12.3-1)
- Migration status for rust-parking-lot/armel (0.12.3-1 to 0.12.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-parking/armel (2.2.0-1 to 2.2.0-1)
- Migration status for rust-parking/armel (2.2.0-1 to 2.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-parse-zoneinfo/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-parse-zoneinfo/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-password-hash/armel (0.5.0-1 to 0.5.0-1)
- Migration status for rust-password-hash/armel (0.5.0-1 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-paste/armel (1.0.15-1 to 1.0.15-1)
- Migration status for rust-paste/armel (1.0.15-1 to 1.0.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pathdiff/armel (0.2.3-1 to 0.2.3-1)
- Migration status for rust-pathdiff/armel (0.2.3-1 to 0.2.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-pathdiff/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-pathfinder-geometry/armel (0.5.1-1 to 0.5.1-1)
- Migration status for rust-pathfinder-geometry/armel (0.5.1-1 to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pathfinder-simd/armel (0.5.2-1 to 0.5.2-1)
- Migration status for rust-pathfinder-simd/armel (0.5.2-1 to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pbkdf2/armel (0.12.2-1 to 0.12.2-1)
- Migration status for rust-pbkdf2/armel (0.12.2-1 to 0.12.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pem-rfc7468/armel (0.7.0-1 to 0.7.0-1)
- Migration status for rust-pem-rfc7468/armel (0.7.0-1 to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-percent-encoding/armel (2.3.1-1 to 2.3.1-1)
- Migration status for rust-percent-encoding/armel (2.3.1-1 to 2.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-petgraph/armel (0.6.4-1 to 0.6.4-1)
- Migration status for rust-petgraph/armel (0.6.4-1 to 0.6.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-phf-codegen/armel (0.11.2-1 to 0.11.2-1)
- Migration status for rust-phf-codegen/armel (0.11.2-1 to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-phf-generator/armel (0.11.2-2 to 0.11.2-2)
- Migration status for rust-phf-generator/armel (0.11.2-2 to 0.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-phf-macros/armel (0.11.2-1 to 0.11.2-1)
- Migration status for rust-phf-macros/armel (0.11.2-1 to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-phf-shared/armel (0.11.2-2 to 0.11.2-2)
- Migration status for rust-phf-shared/armel (0.11.2-2 to 0.11.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-phf/armel (0.11.2-1 to 0.11.2-1)
- Migration status for rust-phf/armel (0.11.2-1 to 0.11.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pico-args/armel (0.5.0-1 to 0.5.0-1)
- Migration status for rust-pico-args/armel (0.5.0-1 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pin-project-internal/armel (1.1.3-1 to 1.1.3-1)
- Migration status for rust-pin-project-internal/armel (1.1.3-1 to 1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pin-project-lite/armel (0.2.13-1 to 0.2.13-1)
- Migration status for rust-pin-project-lite/armel (0.2.13-1 to 0.2.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pin-project/armel (1.1.3-1 to 1.1.3-1)
- Migration status for rust-pin-project/armel (1.1.3-1 to 1.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pin-utils/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-pin-utils/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pkcs1/armel (0.7.5-1 to 0.7.5-1)
- Migration status for rust-pkcs1/armel (0.7.5-1 to 0.7.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pkcs5/armel (0.7.1-1 to 0.7.1-1)
- Migration status for rust-pkcs5/armel (0.7.1-1 to 0.7.1-1): Will attempt migration (Any information below is purely informational)
- rust-pkg-config/armel (0.3.32-3 to 0.3.32-3)
- Migration status for rust-pkg-config/armel (0.3.32-3 to 0.3.32-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-plist/armel (1.7.0-1 to 1.7.0-1)
- Migration status for rust-plist/armel (1.7.0-1 to 1.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-plotters-backend/armel (0.3.7-1 to 0.3.7-1)
- Migration status for rust-plotters-backend/armel (0.3.7-1 to 0.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-plotters-bitmap/armel (0.3.7-3 to 0.3.7-3)
- Migration status for rust-plotters-bitmap/armel (0.3.7-3 to 0.3.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-plotters-svg/armel (0.3.7-1 to 0.3.7-1)
- Migration status for rust-plotters-svg/armel (0.3.7-1 to 0.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-plotters/armel (0.3.7-3 to 0.3.7-3)
- Migration status for rust-plotters/armel (0.3.7-3 to 0.3.7-3): Will attempt migration (Any information below is purely informational)
- rust-png/armel (0.17.7-4 to 0.17.7-4)
- Migration status for rust-png/armel (0.17.7-4 to 0.17.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-polling/armel (3.4.0-1 to 3.4.0-1)
- Migration status for rust-polling/armel (3.4.0-1 to 3.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-polyval/armel (0.6.1-1 to 0.6.1-1)
- Migration status for rust-polyval/armel (0.6.1-1 to 0.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-portable-atomic/armel (1.10.0-3 to 1.10.0-3)
- Migration status for rust-portable-atomic/armel (1.10.0-3 to 1.10.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-postgres-derive/armel (0.4.6-1 to 0.4.6-1)
- Migration status for rust-postgres-derive/armel (0.4.6-1 to 0.4.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-postgres-protocol/armel (0.6.7-1 to 0.6.7-1)
- Migration status for rust-postgres-protocol/armel (0.6.7-1 to 0.6.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-postgres-types/armel (0.2.8-1 to 0.2.8-1)
- Migration status for rust-postgres-types/armel (0.2.8-1 to 0.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-powerfmt-macros/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-powerfmt-macros/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-powerfmt/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-powerfmt/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pq-sys/armel (0.4.8-2 to 0.4.8-2)
- Migration status for rust-pq-sys/armel (0.4.8-2 to 0.4.8-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-precomputed-hash/armel (0.1.1-1 to 0.1.1-1)
- Migration status for rust-precomputed-hash/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-primal-check/armel (0.3.4-1 to 0.3.4-1)
- Migration status for rust-primal-check/armel (0.3.4-1 to 0.3.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-primeorder/armel (0.13.6-1 to 0.13.6-1)
- Migration status for rust-primeorder/armel (0.13.6-1 to 0.13.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-proc-macro-crate-1/armel (1.3.1-4 to 1.3.1-4)
- Migration status for rust-proc-macro-crate-1/armel (1.3.1-4 to 1.3.1-4): Will attempt migration (Any information below is purely informational)
- rust-proc-macro-crate/armel (3.2.0-1 to 3.2.0-1)
- Migration status for rust-proc-macro-crate/armel (3.2.0-1 to 3.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-proc-macro-error-attr/armel (1.0.4-1 to 1.0.4-1)
- Migration status for rust-proc-macro-error-attr/armel (1.0.4-1 to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-proc-macro-error-attr2/armel (2.0.0-1 to 2.0.0-1)
- Migration status for rust-proc-macro-error-attr2/armel (2.0.0-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-proc-macro-error/armel (1.0.4-1 to 1.0.4-1)
- Migration status for rust-proc-macro-error/armel (1.0.4-1 to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-proc-macro-error2/armel (2.0.1-1 to 2.0.1-1)
- Migration status for rust-proc-macro-error2/armel (2.0.1-1 to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-proc-macro-hack/armel (0.5.19-1 to 0.5.19-1)
- Migration status for rust-proc-macro-hack/armel (0.5.19-1 to 0.5.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-proc-macro2/armel (1.0.92-1 to 1.0.92-1)
- Migration status for rust-proc-macro2/armel (1.0.92-1 to 1.0.92-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-proc-status/armel (0.1.1-1 to 0.1.1-1)
- Migration status for rust-proc-status/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-prodash/armel (28.0.0-4 to 28.0.0-4)
- Migration status for rust-prodash/armel (28.0.0-4 to 28.0.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-proptest/armel (1.6.0-1 to 1.6.0-1)
- Migration status for rust-proptest/armel (1.6.0-1 to 1.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-psl-types/armel (2.0.11-1 to 2.0.11-1)
- Migration status for rust-psl-types/armel (2.0.11-1 to 2.0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ptr-meta-derive/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-ptr-meta-derive/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ptr-meta/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-ptr-meta/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-publicsuffix/armel (2.2.3-4 to 2.2.3-4)
- Migration status for rust-publicsuffix/armel (2.2.3-4 to 2.2.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pure-rust-locales/armel (0.8.1-1 to 0.8.1-1)
- Migration status for rust-pure-rust-locales/armel (0.8.1-1 to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pyo3-build-config/armel (0.22.6-1 to 0.22.6-1)
- Migration status for rust-pyo3-build-config/armel (0.22.6-1 to 0.22.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-pyo3-macros-backend/armel (0.22.6-1 to 0.22.6-1)
- Migration status for rust-pyo3-macros-backend/armel (0.22.6-1 to 0.22.6-1): Will attempt migration (Any information below is purely informational)
- rust-python3-dll-a/armel (0.2.10-1 to 0.2.10-1)
- Migration status for rust-python3-dll-a/armel (0.2.10-1 to 0.2.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-qoi/armel (0.4.1-2 to 0.4.1-2)
- Migration status for rust-qoi/armel (0.4.1-2 to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-quick-error/armel (2.0.1-1 to 2.0.1-1)
- Migration status for rust-quick-error/armel (2.0.1-1 to 2.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-quick-xml/armel (0.36.1-2 to 0.36.1-2)
- Migration status for rust-quick-xml/armel (0.36.1-2 to 0.36.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-quickcheck/armel (1.0.3-5 to 1.0.3-5)
- Migration status for rust-quickcheck/armel (1.0.3-5 to 1.0.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-quinn-proto/armel (0.11.9-1 to 0.11.9-1)
- Migration status for rust-quinn-proto/armel (0.11.9-1 to 0.11.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-quinn-udp/armel (0.5.9-1 to 0.5.9-1)
- Migration status for rust-quinn-udp/armel (0.5.9-1 to 0.5.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-quinn/armel (0.11.6-1 to 0.11.6-1)
- Migration status for rust-quinn/armel (0.11.6-1 to 0.11.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-quote/armel (1.0.40-1 to 1.0.40-1)
- Migration status for rust-quote/armel (1.0.40-1 to 1.0.40-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-r2d2/armel (0.8.10-8 to 0.8.10-8)
- Migration status for rust-r2d2/armel (0.8.10-8 to 0.8.10-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-radium/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-radium/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-radix-trie/armel (0.2.1-1 to 0.2.1-1)
- Migration status for rust-radix-trie/armel (0.2.1-1 to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rancor/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-rancor/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rand-chacha/armel (0.3.1-2 to 0.3.1-2)
- Migration status for rust-rand-chacha/armel (0.3.1-2 to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rand-core/armel (0.6.4-2 to 0.6.4-2)
- Migration status for rust-rand-core/armel (0.6.4-2 to 0.6.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rand-distr/armel (0.4.3-1 to 0.4.3-1)
- Migration status for rust-rand-distr/armel (0.4.3-1 to 0.4.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rand-xorshift/armel (0.3.0-2 to 0.3.0-2)
- Migration status for rust-rand-xorshift/armel (0.3.0-2 to 0.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rand/armel (0.8.5-1 to 0.8.5-1)
- Migration status for rust-rand/armel (0.8.5-1 to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ratatui/armel (0.28.1-9 to 0.28.1-9)
- Migration status for rust-ratatui/armel (0.28.1-9 to 0.28.1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rav1e/armel (0.7.1-9 to 0.7.1-9)
- Migration status for rust-rav1e/armel (0.7.1-9 to 0.7.1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-raw-window-handle/armel (0.6.2-1 to 0.6.2-1)
- Migration status for rust-raw-window-handle/armel (0.6.2-1 to 0.6.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rayon-core/armel (1.12.1-1 to 1.12.1-1)
- Migration status for rust-rayon-core/armel (1.12.1-1 to 1.12.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rayon/armel (1.10.0-1 to 1.10.0-1)
- Migration status for rust-rayon/armel (1.10.0-1 to 1.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-redox-syscall/armel (0.2.16-1 to 0.2.16-1)
- Migration status for rust-redox-syscall/armel (0.2.16-1 to 0.2.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-redox-termios/armel (0.1.2-1 to 0.1.2-1)
- Migration status for rust-redox-termios/armel (0.1.2-1 to 0.1.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-regex-automata/armel (0.4.9-2 to 0.4.9-2)
- Migration status for rust-regex-automata/armel (0.4.9-2 to 0.4.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-regex-lite/armel (0.1.6-2 to 0.1.6-2)
- Migration status for rust-regex-lite/armel (0.1.6-2 to 0.1.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-regex-syntax/armel (0.8.5-1 to 0.8.5-1)
- Migration status for rust-regex-syntax/armel (0.8.5-1 to 0.8.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-regex/armel (1.11.1-2 to 1.11.1-2)
- Migration status for rust-regex/armel (1.11.1-2 to 1.11.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rend/armel (0.5.2-1 to 0.5.2-1)
- Migration status for rust-rend/armel (0.5.2-1 to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-reqwest/armel (0.12.15-1 to 0.12.15-1)
- Migration status for rust-reqwest/armel (0.12.15-1 to 0.12.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-resolv-conf/armel (0.7.0-1 to 0.7.0-1)
- Migration status for rust-resolv-conf/armel (0.7.0-1 to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rfc6979/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-rfc6979/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rgb/armel (0.8.50-1 to 0.8.50-1)
- Migration status for rust-rgb/armel (0.8.50-1 to 0.8.50-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ring/armel (0.17.14-2 to 0.17.14-2)
- Migration status for rust-ring/armel (0.17.14-2 to 0.17.14-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ripemd/armel (0.1.3-1 to 0.1.3-1)
- Migration status for rust-ripemd/armel (0.1.3-1 to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rkyv-derive/armel (0.8.9-1 to 0.8.9-1)
- Migration status for rust-rkyv-derive/armel (0.8.9-1 to 0.8.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rkyv/armel (0.8.9-2 to 0.8.9-2)
- Migration status for rust-rkyv/armel (0.8.9-2 to 0.8.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rlp-derive/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-rlp-derive/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rlp/armel (0.5.2-2 to 0.5.2-2)
- Migration status for rust-rlp/armel (0.5.2-2 to 0.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-roff/armel (0.2.1-1 to 0.2.1-1)
- Migration status for rust-roff/armel (0.2.1-1 to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ron/armel (0.7.1-6 to 0.7.1-6)
- Migration status for rust-ron/armel (0.7.1-6 to 0.7.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-roxmltree/armel (0.20.0-1 to 0.20.0-1)
- Migration status for rust-roxmltree/armel (0.20.0-1 to 0.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rsa/armel (0.9.7-1 to 0.9.7-1)
- Migration status for rust-rsa/armel (0.9.7-1 to 0.9.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rusqlite/armel (0.29.0-3 to 0.29.0-3)
- Migration status for rust-rusqlite/armel (0.29.0-3 to 0.29.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rust-decimal/armel (1.36.0-2 to 1.36.0-2)
- Migration status for rust-rust-decimal/armel (1.36.0-2 to 1.36.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustc-demangle/armel (0.1.24-1 to 0.1.24-1)
- Migration status for rust-rustc-demangle/armel (0.1.24-1 to 0.1.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustc-hash-2/armel (2.0.0-1 to 2.0.0-1)
- Migration status for rust-rustc-hash-2/armel (2.0.0-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustc-hash/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-rustc-hash/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustc-hex/armel (2.1.0-1 to 2.1.0-1)
- Migration status for rust-rustc-hex/armel (2.1.0-1 to 2.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustc-std-workspace-core/armel (1.0.1-1 to 1.0.1-1)
- Migration status for rust-rustc-std-workspace-core/armel (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustc-version/armel (0.4.1-1 to 0.4.1-1)
- Migration status for rust-rustc-version/armel (0.4.1-1 to 0.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustfft/armel (6.4.0-1 to 6.4.0-1)
- Migration status for rust-rustfft/armel (6.4.0-1 to 6.4.0-1): Will attempt migration (Any information below is purely informational)
- rust-rustix/armel (0.38.37-4 to 0.38.37-4)
- Migration status for rust-rustix/armel (0.38.37-4 to 0.38.37-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustls-pemfile/armel (2.2.0-3 to 2.2.0-3)
- Migration status for rust-rustls-pemfile/armel (2.2.0-3 to 2.2.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustversion/armel (1.0.14-1 to 1.0.14-1)
- Migration status for rust-rustversion/armel (1.0.14-1 to 1.0.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rusty-fork/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-rusty-fork/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-rustybuzz/armel (0.18.0-2 to 0.18.0-2)
- Migration status for rust-rustybuzz/armel (0.18.0-2 to 0.18.0-2): Will attempt migration (Any information below is purely informational)
- rust-ruzstd/armel (0.7.3-2 to 0.7.3-2)
- Migration status for rust-ruzstd/armel (0.7.3-2 to 0.7.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ryu/armel (1.0.19-1 to 1.0.19-1)
- Migration status for rust-ryu/armel (1.0.19-1 to 1.0.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-salsa20/armel (0.10.2-1 to 0.10.2-1)
- Migration status for rust-salsa20/armel (0.10.2-1 to 0.10.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-same-file/armel (1.0.6-1 to 1.0.6-1)
- Migration status for rust-same-file/armel (1.0.6-1 to 1.0.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-scan-fmt/armel (0.2.6-1 to 0.2.6-1)
- Migration status for rust-scan-fmt/armel (0.2.6-1 to 0.2.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-schannel/armel (0.1.19-1 to 0.1.19-1)
- Migration status for rust-schannel/armel (0.1.19-1 to 0.1.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-scheduled-thread-pool/armel (0.2.7-1 to 0.2.7-1)
- Migration status for rust-scheduled-thread-pool/armel (0.2.7-1 to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-schemars-derive/armel (0.8.21-1 to 0.8.21-1)
- Migration status for rust-schemars-derive/armel (0.8.21-1 to 0.8.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-schemars/armel (0.8.21-1 to 0.8.21-1)
- Migration status for rust-schemars/armel (0.8.21-1 to 0.8.21-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-scoped-tls/armel (1.0.1-1 to 1.0.1-1)
- Migration status for rust-scoped-tls/armel (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-scopeguard/armel (1.2.0-1 to 1.2.0-1)
- Migration status for rust-scopeguard/armel (1.2.0-1 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-scrypt/armel (0.11.0-1 to 0.11.0-1)
- Migration status for rust-scrypt/armel (0.11.0-1 to 0.11.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sec1/armel (0.7.2-1 to 0.7.2-1)
- Migration status for rust-sec1/armel (0.7.2-1 to 0.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-secular/armel (1.0.1-2 to 1.0.1-2)
- Migration status for rust-secular/armel (1.0.1-2 to 1.0.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-secular/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-sequoia-cert-store/armel (0.7.0-1 to 0.7.0-1)
- Migration status for rust-sequoia-cert-store/armel (0.7.0-1 to 0.7.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-sequoia-cert-store/armel rust-sequoia-wot (not considered)
- Invalidated by implicit-dependency
- rust-sequoia-net/armel (0.30.0-1 to 0.30.0-1)
- Migration status for rust-sequoia-net/armel (0.30.0-1 to 0.30.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sequoia-openpgp/armel (2.0.0-2 to 2.0.0-2)
- Migration status for rust-sequoia-openpgp/armel (2.0.0-2 to 2.0.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sequoia-policy-config/armel (0.8.0-1 to 0.8.0-1)
- Migration status for rust-sequoia-policy-config/armel (0.8.0-1 to 0.8.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-sequoia-policy-config/armel rust-sequoia-sop (not considered)
- Invalidated by implicit-dependency
- rust-sequoia-sqv/armel (1.3.0-3 to 1.3.0-3)
- Migration status for rust-sequoia-sqv/armel (1.3.0-3 to 1.3.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serde-big-array/armel (0.5.1-1 to 0.5.1-1)
- Migration status for rust-serde-big-array/armel (0.5.1-1 to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serde-bytes/armel (0.11.12-1 to 0.11.12-1)
- Migration status for rust-serde-bytes/armel (0.11.12-1 to 0.11.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serde-derive-internals/armel (0.29.1-1 to 0.29.1-1)
- Migration status for rust-serde-derive-internals/armel (0.29.1-1 to 0.29.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serde-derive/armel (1.0.219-1 to 1.0.219-1)
- Migration status for rust-serde-derive/armel (1.0.219-1 to 1.0.219-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serde-json/armel (1.0.143-1 to 1.0.143-1)
- Migration status for rust-serde-json/armel (1.0.143-1 to 1.0.143-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serde-spanned/armel (0.6.7-1 to 0.6.7-1)
- Migration status for rust-serde-spanned/armel (0.6.7-1 to 0.6.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serde-test/armel (1.0.171-1 to 1.0.171-1)
- Migration status for rust-serde-test/armel (1.0.171-1 to 1.0.171-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serde-urlencoded/armel (0.7.1-1 to 0.7.1-1)
- Migration status for rust-serde-urlencoded/armel (0.7.1-1 to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serde/armel (1.0.219-1 to 1.0.219-1)
- Migration status for rust-serde/armel (1.0.219-1 to 1.0.219-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-serdect/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-serdect/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sha1-asm/armel (0.5.1-2 to 0.5.1-2)
- Migration status for rust-sha1-asm/armel (0.5.1-2 to 0.5.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sha1-checked/armel (0.10.0-1 to 0.10.0-1)
- Migration status for rust-sha1-checked/armel (0.10.0-1 to 0.10.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sha1/armel (0.10.6-1 to 0.10.6-1)
- Migration status for rust-sha1/armel (0.10.6-1 to 0.10.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sha1collisiondetection/armel (0.3.2-1 to 0.3.2-1)
- Migration status for rust-sha1collisiondetection/armel (0.3.2-1 to 0.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sha2-asm/armel (0.6.2-2 to 0.6.2-2)
- Migration status for rust-sha2-asm/armel (0.6.2-2 to 0.6.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sha2/armel (0.10.8-1 to 0.10.8-1)
- Migration status for rust-sha2/armel (0.10.8-1 to 0.10.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sha3/armel (0.10.8-1 to 0.10.8-1)
- Migration status for rust-sha3/armel (0.10.8-1 to 0.10.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-shell-words/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-shell-words/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-shlex/armel (1.3.0-1 to 1.3.0-1)
- Migration status for rust-shlex/armel (1.3.0-1 to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-signal-hook-mio/armel (0.2.4-2 to 0.2.4-2)
- Migration status for rust-signal-hook-mio/armel (0.2.4-2 to 0.2.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-signal-hook-registry/armel (1.4.0-1 to 1.4.0-1)
- Migration status for rust-signal-hook-registry/armel (1.4.0-1 to 1.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-signal-hook/armel (0.3.17-1 to 0.3.17-1)
- Migration status for rust-signal-hook/armel (0.3.17-1 to 0.3.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-simd-adler32/armel (0.3.7-1 to 0.3.7-1)
- Migration status for rust-simd-adler32/armel (0.3.7-1 to 0.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-simd-helpers/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-simd-helpers/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-simdutf8/armel (0.1.4-4 to 0.1.4-4)
- Migration status for rust-simdutf8/armel (0.1.4-4 to 0.1.4-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-simplecss/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-simplecss/armel (0.2.0-1 to 0.2.0-1): Will attempt migration (Any information below is purely informational)
- rust-siphasher/armel (1.0.1-1 to 1.0.1-1)
- Migration status for rust-siphasher/armel (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-slab/armel (0.4.9-1 to 0.4.9-1)
- Migration status for rust-slab/armel (0.4.9-1 to 0.4.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-slog/armel (2.7.0-1 to 2.7.0-1)
- Migration status for rust-slog/armel (2.7.0-1 to 2.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-slotmap/armel (1.0.7-1 to 1.0.7-1)
- Migration status for rust-slotmap/armel (1.0.7-1 to 1.0.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-smallvec/armel (1.13.2-1 to 1.13.2-1)
- Migration status for rust-smallvec/armel (1.13.2-1 to 1.13.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-smol-str/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-smol-str/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-snafu-derive/armel (0.7.1-1 to 0.7.1-1)
- Migration status for rust-snafu-derive/armel (0.7.1-1 to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-snafu/armel (0.7.1-1 to 0.7.1-1)
- Migration status for rust-snafu/armel (0.7.1-1 to 0.7.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-snafu/armel rust-lfs-core (not considered)
- Invalidated by implicit-dependency
- rust-socket2/armel (0.5.8-1 to 0.5.8-1)
- Migration status for rust-socket2/armel (0.5.8-1 to 0.5.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sop/armel (0.8.2-1 to 0.8.2-1)
- Migration status for rust-sop/armel (0.8.2-1 to 0.8.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-sop/armel rust-sequoia-sop (not considered)
- Invalidated by implicit-dependency
- rust-spin/armel (0.9.8-4 to 0.9.8-4)
- Migration status for rust-spin/armel (0.9.8-4 to 0.9.8-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-spki/armel (0.7.3-1 to 0.7.3-1)
- Migration status for rust-spki/armel (0.7.3-1 to 0.7.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-splitty/armel (1.0.2-1 to 1.0.2-1)
- Migration status for rust-splitty/armel (1.0.2-1 to 1.0.2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-splitty/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-sqlx-core/armel (0.8.3-2 to 0.8.3-2)
- Migration status for rust-sqlx-core/armel (0.8.3-2 to 0.8.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sqlx-macros-core/armel (0.8.3-3 to 0.8.3-3)
- Migration status for rust-sqlx-macros-core/armel (0.8.3-3 to 0.8.3-3): Will attempt migration (Any information below is purely informational)
- rust-sqlx-mysql/armel (0.8.3-1 to 0.8.3-1)
- Migration status for rust-sqlx-mysql/armel (0.8.3-1 to 0.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sqlx-postgres/armel (0.8.3-1 to 0.8.3-1)
- Migration status for rust-sqlx-postgres/armel (0.8.3-1 to 0.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sqlx-sqlite/armel (0.8.3-1 to 0.8.3-1)
- Migration status for rust-sqlx-sqlite/armel (0.8.3-1 to 0.8.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-stable-deref-trait/armel (1.2.0-1 to 1.2.0-1)
- Migration status for rust-stable-deref-trait/armel (1.2.0-1 to 1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-static-assertions/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-static-assertions/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-strength-reduce/armel (0.2.4-1 to 0.2.4-1)
- Migration status for rust-strength-reduce/armel (0.2.4-1 to 0.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-strict-num/armel (0.1.1-1 to 0.1.1-1)
- Migration status for rust-strict-num/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-strict/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-strict/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-string-cache/armel (0.8.7-1 to 0.8.7-1)
- Migration status for rust-string-cache/armel (0.8.7-1 to 0.8.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-stringprep/armel (0.1.5-1 to 0.1.5-1)
- Migration status for rust-stringprep/armel (0.1.5-1 to 0.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-strsim/armel (0.11.1-1 to 0.11.1-1)
- Migration status for rust-strsim/armel (0.11.1-1 to 0.11.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-strum-macros/armel (0.26.4-1 to 0.26.4-1)
- Migration status for rust-strum-macros/armel (0.26.4-1 to 0.26.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-strum/armel (0.26.3-2 to 0.26.3-2)
- Migration status for rust-strum/armel (0.26.3-2 to 0.26.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-subtle/armel (2.6.1-1 to 2.6.1-1)
- Migration status for rust-subtle/armel (2.6.1-1 to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sval-buffer/armel (2.6.1-1 to 2.6.1-1)
- Migration status for rust-sval-buffer/armel (2.6.1-1 to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sval-derive/armel (2.6.1-2 to 2.6.1-2)
- Migration status for rust-sval-derive/armel (2.6.1-2 to 2.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sval-dynamic/armel (2.6.1-1 to 2.6.1-1)
- Migration status for rust-sval-dynamic/armel (2.6.1-1 to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sval-fmt/armel (2.6.1-1 to 2.6.1-1)
- Migration status for rust-sval-fmt/armel (2.6.1-1 to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sval-ref/armel (2.6.1-1 to 2.6.1-1)
- Migration status for rust-sval-ref/armel (2.6.1-1 to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sval-serde/armel (2.6.1-1 to 2.6.1-1)
- Migration status for rust-sval-serde/armel (2.6.1-1 to 2.6.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sval/armel (2.6.1-2 to 2.6.1-2)
- Migration status for rust-sval/armel (2.6.1-2 to 2.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-svgtypes/armel (0.15.2-2 to 0.15.2-2)
- Migration status for rust-svgtypes/armel (0.15.2-2 to 0.15.2-2): Will attempt migration (Any information below is purely informational)
- rust-syn-1/armel (1.0.109-3 to 1.0.109-3)
- Migration status for rust-syn-1/armel (1.0.109-3 to 1.0.109-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-syn/armel (2.0.98-1 to 2.0.98-1)
- Migration status for rust-syn/armel (2.0.98-1 to 2.0.98-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-sync-wrapper/armel (1.0.2-1 to 1.0.2-1)
- Migration status for rust-sync-wrapper/armel (1.0.2-1 to 1.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-synstructure-0.12/armel (0.12.6-1 to 0.12.6-1)
- Migration status for rust-synstructure-0.12/armel (0.12.6-1 to 0.12.6-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-synstructure-0.12/armel rust-abscissa-derive (not considered)
- Invalidated by implicit-dependency
- rust-syntect-no-panic/armel (6.0.0-2 to 6.0.0-2)
- Migration status for rust-syntect-no-panic/armel (6.0.0-2 to 6.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-syntect-no-panic/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-syslog/armel (6.0.1-2 to 6.0.1-2)
- Migration status for rust-syslog/armel (6.0.1-2 to 6.0.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-system-deps/armel (7.0.2-2 to 7.0.2-2)
- Migration status for rust-system-deps/armel (7.0.2-2 to 7.0.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tap/armel (1.0.1-1 to 1.0.1-1)
- Migration status for rust-tap/armel (1.0.1-1 to 1.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tar/armel (0.4.44-1 to 0.4.44-1)
- Migration status for rust-tar/armel (0.4.44-1 to 0.4.44-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-target-lexicon/armel (0.12.14-1 to 0.12.14-1)
- Migration status for rust-target-lexicon/armel (0.12.14-1 to 0.12.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-term/armel (0.7.0-1 to 0.7.0-1)
- Migration status for rust-term/armel (0.7.0-1 to 0.7.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-termcolor/armel (1.4.1-1 to 1.4.1-1)
- Migration status for rust-termcolor/armel (1.4.1-1 to 1.4.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-terminal-clipboard/armel (0.4.1-2 to 0.4.1-2)
- Migration status for rust-terminal-clipboard/armel (0.4.1-2 to 0.4.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-terminal-clipboard/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-terminal-light/armel (1.8.0-1 to 1.8.0-1)
- Migration status for rust-terminal-light/armel (1.8.0-1 to 1.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-terminal-size/armel (0.4.1-2 to 0.4.1-2)
- Migration status for rust-terminal-size/armel (0.4.1-2 to 0.4.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-termion/armel (1.5.6-1 to 1.5.6-1)
- Migration status for rust-termion/armel (1.5.6-1 to 1.5.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-thin-vec/armel (0.2.13-2 to 0.2.13-2)
- Migration status for rust-thin-vec/armel (0.2.13-2 to 0.2.13-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-thiserror-1/armel (1.0.69-1 to 1.0.69-1)
- Migration status for rust-thiserror-1/armel (1.0.69-1 to 1.0.69-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-thiserror-impl-1/armel (1.0.69-1 to 1.0.69-1)
- Migration status for rust-thiserror-impl-1/armel (1.0.69-1 to 1.0.69-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-thiserror-impl/armel (2.0.11-1 to 2.0.11-1)
- Migration status for rust-thiserror-impl/armel (2.0.11-1 to 2.0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-thiserror/armel (2.0.11-1 to 2.0.11-1)
- Migration status for rust-thiserror/armel (2.0.11-1 to 2.0.11-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tiff/armel (0.9.0-1 to 0.9.0-1)
- Migration status for rust-tiff/armel (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-time-core/armel (0.1.3-1 to 0.1.3-1)
- Migration status for rust-time-core/armel (0.1.3-1 to 0.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-time-macros/armel (0.2.20-1 to 0.2.20-1)
- Migration status for rust-time-macros/armel (0.2.20-1 to 0.2.20-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-time/armel (0.3.39-1 to 0.3.39-1)
- Migration status for rust-time/armel (0.3.39-1 to 0.3.39-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tiny-keccak/armel (2.0.2-1 to 2.0.2-1)
- Migration status for rust-tiny-keccak/armel (2.0.2-1 to 2.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tiny-skia-path/armel (0.11.4-1 to 0.11.4-1)
- Migration status for rust-tiny-skia-path/armel (0.11.4-1 to 0.11.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tiny-skia/armel (0.11.4-1 to 0.11.4-1)
- Migration status for rust-tiny-skia/armel (0.11.4-1 to 0.11.4-1): Will attempt migration (Any information below is purely informational)
- rust-tinystr/armel (0.3.2-2 to 0.3.2-2)
- Migration status for rust-tinystr/armel (0.3.2-2 to 0.3.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tinytemplate/armel (1.2.1-1 to 1.2.1-1)
- Migration status for rust-tinytemplate/armel (1.2.1-1 to 1.2.1-1): Will attempt migration (Any information below is purely informational)
- rust-tinyvec-macros/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-tinyvec-macros/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tinyvec/armel (1.6.0-2 to 1.6.0-2)
- Migration status for rust-tinyvec/armel (1.6.0-2 to 1.6.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tokio-macros/armel (2.5.0-1 to 2.5.0-1)
- Migration status for rust-tokio-macros/armel (2.5.0-1 to 2.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tokio-native-tls/armel (0.3.1-2 to 0.3.1-2)
- Migration status for rust-tokio-native-tls/armel (0.3.1-2 to 0.3.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tokio-openssl/armel (0.6.3-1 to 0.6.3-1)
- Migration status for rust-tokio-openssl/armel (0.6.3-1 to 0.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tokio-rustls/armel (0.26.1-2 to 0.26.1-2)
- Migration status for rust-tokio-rustls/armel (0.26.1-2 to 0.26.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tokio-stream/armel (0.1.17-1 to 0.1.17-1)
- Migration status for rust-tokio-stream/armel (0.1.17-1 to 0.1.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tokio-uring/armel (0.5.0-1 to 0.5.0-1)
- Migration status for rust-tokio-uring/armel (0.5.0-1 to 0.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tokio-util/armel (0.7.10-1 to 0.7.10-1)
- Migration status for rust-tokio-util/armel (0.7.10-1 to 0.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tokio/armel (1.47.1-2 to 1.47.1-2)
- Migration status for rust-tokio/armel (1.47.1-2 to 1.47.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-toml-0.5/armel (0.5.11-4 to 0.5.11-4)
- Migration status for rust-toml-0.5/armel (0.5.11-4 to 0.5.11-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-toml-datetime/armel (0.6.8-1 to 0.6.8-1)
- Migration status for rust-toml-datetime/armel (0.6.8-1 to 0.6.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-toml-edit/armel (0.22.22-1 to 0.22.22-1)
- Migration status for rust-toml-edit/armel (0.22.22-1 to 0.22.22-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-toml/armel (0.8.19-1 to 0.8.19-1)
- Migration status for rust-toml/armel (0.8.19-1 to 0.8.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tower-layer/armel (0.3.3-1 to 0.3.3-1)
- Migration status for rust-tower-layer/armel (0.3.3-1 to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tower-service/armel (0.3.3-1 to 0.3.3-1)
- Migration status for rust-tower-service/armel (0.3.3-1 to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tower/armel (0.5.2-2 to 0.5.2-2)
- Migration status for rust-tower/armel (0.5.2-2 to 0.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tracing-attributes/armel (0.1.27-1 to 0.1.27-1)
- Migration status for rust-tracing-attributes/armel (0.1.27-1 to 0.1.27-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tracing-core/armel (0.1.32-1 to 0.1.32-1)
- Migration status for rust-tracing-core/armel (0.1.32-1 to 0.1.32-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tracing/armel (0.1.40-1 to 0.1.40-1)
- Migration status for rust-tracing/armel (0.1.40-1 to 0.1.40-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-traitobject/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-traitobject/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-transpose/armel (0.2.3-1 to 0.2.3-1)
- Migration status for rust-transpose/armel (0.2.3-1 to 0.2.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-trash/armel (5.2.0-2 to 5.2.0-2)
- Migration status for rust-trash/armel (5.2.0-2 to 5.2.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-trash/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-tree-magic-db/armel (3.0.0-1 to 3.0.0-1)
- Migration status for rust-tree-magic-db/armel (3.0.0-1 to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tree-magic-mini/armel (3.1.6-1 to 3.1.6-1)
- Migration status for rust-tree-magic-mini/armel (3.1.6-1 to 3.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-triomphe/armel (0.1.14-1 to 0.1.14-1)
- Migration status for rust-triomphe/armel (0.1.14-1 to 0.1.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-try-lock/armel (0.2.5-1 to 0.2.5-1)
- Migration status for rust-try-lock/armel (0.2.5-1 to 0.2.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ttf-parser/armel (0.25.1-1 to 0.25.1-1)
- Migration status for rust-ttf-parser/armel (0.25.1-1 to 0.25.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-tui-react/armel (0.23.2-4 to 0.23.2-4)
- Migration status for rust-tui-react/armel (0.23.2-4 to 0.23.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-twofish/armel (0.7.1-1 to 0.7.1-1)
- Migration status for rust-twofish/armel (0.7.1-1 to 0.7.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-twox-hash/armel (1.6.3-1 to 1.6.3-1)
- Migration status for rust-twox-hash/armel (1.6.3-1 to 1.6.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-typed-arena/armel (2.0.2-1 to 2.0.2-1)
- Migration status for rust-typed-arena/armel (2.0.2-1 to 2.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-typemap/armel (0.3.3-2 to 0.3.3-2)
- Migration status for rust-typemap/armel (0.3.3-2 to 0.3.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-typenum/armel (1.17.0-3 to 1.17.0-3)
- Migration status for rust-typenum/armel (1.17.0-3 to 1.17.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-ucd-trie/armel (0.1.5-1 to 0.1.5-1)
- Migration status for rust-ucd-trie/armel (0.1.5-1 to 0.1.5-1): Will attempt migration (Any information below is purely informational)
- rust-ufmt-write/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-ufmt-write/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-uluru/armel (3.0.0-1 to 3.0.0-1)
- Migration status for rust-uluru/armel (3.0.0-1 to 3.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-umask/armel (2.1.0-1 to 2.1.0-1)
- Migration status for rust-umask/armel (2.1.0-1 to 2.1.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-umask/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-unarray/armel (0.1.4-1 to 0.1.4-1)
- Migration status for rust-unarray/armel (0.1.4-1 to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-uncased/armel (0.9.6-2 to 0.9.6-2)
- Migration status for rust-uncased/armel (0.9.6-2 to 0.9.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unic-langid-impl/armel (0.9.0-1 to 0.9.0-1)
- Migration status for rust-unic-langid-impl/armel (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unic-langid-macros-impl/armel (0.9.0-1 to 0.9.0-1)
- Migration status for rust-unic-langid-macros-impl/armel (0.9.0-1 to 0.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unic-langid-macros/armel (0.9.0-1 to 0.9.0-1)
- Migration status for rust-unic-langid-macros/armel (0.9.0-1 to 0.9.0-1): Will attempt migration (Any information below is purely informational)
- rust-unicase/armel (2.8.0-1 to 2.8.0-1)
- Migration status for rust-unicase/armel (2.8.0-1 to 2.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-bidi-mirroring/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-unicode-bidi-mirroring/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-bidi/armel (0.3.17-1 to 0.3.17-1)
- Migration status for rust-unicode-bidi/armel (0.3.17-1 to 0.3.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-bom/armel (2.0.3-1 to 2.0.3-1)
- Migration status for rust-unicode-bom/armel (2.0.3-1 to 2.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-ccc/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-unicode-ccc/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-ident/armel (1.0.13-1 to 1.0.13-1)
- Migration status for rust-unicode-ident/armel (1.0.13-1 to 1.0.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-joining-type/armel (1.0.0-1 to 1.0.0-1)
- Migration status for rust-unicode-joining-type/armel (1.0.0-1 to 1.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-normalization/armel (0.1.24-1 to 0.1.24-1)
- Migration status for rust-unicode-normalization/armel (0.1.24-1 to 0.1.24-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-properties/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-unicode-properties/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-script/armel (0.5.2-4 to 0.5.2-4)
- Migration status for rust-unicode-script/armel (0.5.2-4 to 0.5.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-segmentation/armel (1.12.0-1 to 1.12.0-1)
- Migration status for rust-unicode-segmentation/armel (1.12.0-1 to 1.12.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-truncate/armel (2.0.0-1 to 2.0.0-1)
- Migration status for rust-unicode-truncate/armel (2.0.0-1 to 2.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-vo/armel (0.1.0-2 to 0.1.0-2)
- Migration status for rust-unicode-vo/armel (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
- rust-unicode-width-0.1/armel (0.1.14-2 to 0.1.14-2)
- Migration status for rust-unicode-width-0.1/armel (0.1.14-2 to 0.1.14-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-width/armel (0.2.0-1 to 0.2.0-1)
- Migration status for rust-unicode-width/armel (0.2.0-1 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unicode-xid/armel (0.2.4-1 to 0.2.4-1)
- Migration status for rust-unicode-xid/armel (0.2.4-1 to 0.2.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-uniquote/armel (3.3.0-1 to 3.3.0-1)
- Migration status for rust-uniquote/armel (3.3.0-1 to 3.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-universal-hash/armel (0.5.1-1 to 0.5.1-1)
- Migration status for rust-universal-hash/armel (0.5.1-1 to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unsafe-any/armel (0.4.2-2 to 0.4.2-2)
- Migration status for rust-unsafe-any/armel (0.4.2-2 to 0.4.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-unsize/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-unsize/armel (1.1.0-1 to 1.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-untrusted/armel (0.9.0-2 to 0.9.0-2)
- Migration status for rust-untrusted/armel (0.9.0-2 to 0.9.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-url/armel (2.5.4-3 to 2.5.4-3)
- Migration status for rust-url/armel (2.5.4-3 to 2.5.4-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-urlencoding/armel (2.1.3-1 to 2.1.3-1)
- Migration status for rust-urlencoding/armel (2.1.3-1 to 2.1.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-utf-8/armel (0.7.6-2 to 0.7.6-2)
- Migration status for rust-utf-8/armel (0.7.6-2 to 0.7.6-2): Will attempt migration (Any information below is purely informational)
- rust-utf8-iter/armel (1.0.4-1 to 1.0.4-1)
- Migration status for rust-utf8-iter/armel (1.0.4-1 to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-utf8parse/armel (0.2.1-1 to 0.2.1-1)
- Migration status for rust-utf8parse/armel (0.2.1-1 to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-uzers/armel (0.12.1-2 to 0.12.1-2)
- Migration status for rust-uzers/armel (0.12.1-2 to 0.12.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-uzers/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-v-frame/armel (0.3.7-1 to 0.3.7-1)
- Migration status for rust-v-frame/armel (0.3.7-1 to 0.3.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-valuable-derive/armel (0.1.0-1 to 0.1.0-1)
- Migration status for rust-valuable-derive/armel (0.1.0-1 to 0.1.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-valuable/armel (0.1.0-4 to 0.1.0-4)
- Migration status for rust-valuable/armel (0.1.0-4 to 0.1.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-value-bag-serde1/armel (1.9.0-1 to 1.9.0-1)
- Migration status for rust-value-bag-serde1/armel (1.9.0-1 to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-value-bag-sval2/armel (1.9.0-1 to 1.9.0-1)
- Migration status for rust-value-bag-sval2/armel (1.9.0-1 to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-value-bag/armel (1.9.0-1 to 1.9.0-1)
- Migration status for rust-value-bag/armel (1.9.0-1 to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-vcpkg/armel (0.2.8-1 to 0.2.8-1)
- Migration status for rust-vcpkg/armel (0.2.8-1 to 0.2.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-version-check/armel (0.9.5-1 to 0.9.5-1)
- Migration status for rust-version-check/armel (0.9.5-1 to 0.9.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-version-compare/armel (0.1.1-1 to 0.1.1-1)
- Migration status for rust-version-compare/armel (0.1.1-1 to 0.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-vmm-sys-util/armel (0.12.1-2 to 0.12.1-2)
- Migration status for rust-vmm-sys-util/armel (0.12.1-2 to 0.12.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-vmm-sys-util/armel rust-kvm-bindings (not considered)
- Invalidated by implicit-dependency
- rust-vte/armel (0.15.0-1 to 0.15.0-1)
- Migration status for rust-vte/armel (0.15.0-1 to 0.15.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-vte/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-vte/armel rust-bacon
- rust-wait-timeout/armel (0.2.1-1 to 0.2.1-1)
- Migration status for rust-wait-timeout/armel (0.2.1-1 to 0.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-walkdir/armel (2.5.0-1 to 2.5.0-1)
- Migration status for rust-walkdir/armel (2.5.0-1 to 2.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-want/armel (0.3.0-1 to 0.3.0-1)
- Migration status for rust-want/armel (0.3.0-1 to 0.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wasm-bindgen-backend/armel (0.2.100-1 to 0.2.100-1)
- Migration status for rust-wasm-bindgen-backend/armel (0.2.100-1 to 0.2.100-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wasm-bindgen-macro-support/armel (0.2.100-1 to 0.2.100-1)
- Migration status for rust-wasm-bindgen-macro-support/armel (0.2.100-1 to 0.2.100-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wasm-bindgen-macro/armel (0.2.100-1 to 0.2.100-1)
- Migration status for rust-wasm-bindgen-macro/armel (0.2.100-1 to 0.2.100-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wasm-bindgen-shared/armel (0.2.100-1 to 0.2.100-1)
- Migration status for rust-wasm-bindgen-shared/armel (0.2.100-1 to 0.2.100-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wasm-bindgen/armel (0.2.100-1 to 0.2.100-1)
- Migration status for rust-wasm-bindgen/armel (0.2.100-1 to 0.2.100-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wayland-backend/armel (0.3.8-3 to 0.3.8-3)
- Migration status for rust-wayland-backend/armel (0.3.8-3 to 0.3.8-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wayland-client/armel (0.31.8-1 to 0.31.8-1)
- Migration status for rust-wayland-client/armel (0.31.8-1 to 0.31.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wayland-protocols-wlr/armel (0.3.6-1 to 0.3.6-1)
- Migration status for rust-wayland-protocols-wlr/armel (0.3.6-1 to 0.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wayland-protocols/armel (0.32.6-1 to 0.32.6-1)
- Migration status for rust-wayland-protocols/armel (0.32.6-1 to 0.32.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wayland-scanner/armel (0.31.6-1 to 0.31.6-1)
- Migration status for rust-wayland-scanner/armel (0.31.6-1 to 0.31.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wayland-server/armel (0.31.7-1 to 0.31.7-1)
- Migration status for rust-wayland-server/armel (0.31.7-1 to 0.31.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-web-time/armel (1.1.0-1 to 1.1.0-1)
- Migration status for rust-web-time/armel (1.1.0-1 to 1.1.0-1): Will attempt migration (Any information below is purely informational)
- rust-weezl/armel (0.1.8-1 to 0.1.8-1)
- Migration status for rust-weezl/armel (0.1.8-1 to 0.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-which/armel (8.0.0-2 to 8.0.0-2)
- Migration status for rust-which/armel (8.0.0-2 to 8.0.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-which/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- rust-whoami/armel (1.5.2-1 to 1.5.2-1)
- Migration status for rust-whoami/armel (1.5.2-1 to 1.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-winapi-i686-pc-windows-gnu/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-winapi-i686-pc-windows-gnu/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-winapi-util/armel (0.1.6-1 to 0.1.6-1)
- Migration status for rust-winapi-util/armel (0.1.6-1 to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-winapi-x86-64-pc-windows-gnu/armel (0.4.0-1 to 0.4.0-1)
- Migration status for rust-winapi-x86-64-pc-windows-gnu/armel (0.4.0-1 to 0.4.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-winapi/armel (0.3.9-1 to 0.3.9-1)
- Migration status for rust-winapi/armel (0.3.9-1 to 0.3.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-winnow/armel (0.6.26-1 to 0.6.26-1)
- Migration status for rust-winnow/armel (0.6.26-1 to 0.6.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wl-clipboard-rs/armel (0.9.2-1 to 0.9.2-1)
- Migration status for rust-wl-clipboard-rs/armel (0.9.2-1 to 0.9.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-wyz/armel (0.5.1-1 to 0.5.1-1)
- Migration status for rust-wyz/armel (0.5.1-1 to 0.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-x11-clipboard/armel (0.9.2-2 to 0.9.2-2)
- Migration status for rust-x11-clipboard/armel (0.9.2-2 to 0.9.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-x11rb-protocol/armel (0.13.1-2 to 0.13.1-2)
- Migration status for rust-x11rb-protocol/armel (0.13.1-2 to 0.13.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-x11rb/armel (0.13.0-2 to 0.13.0-2)
- Migration status for rust-x11rb/armel (0.13.0-2 to 0.13.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-xattr/armel (1.3.1-1 to 1.3.1-1)
- Migration status for rust-xattr/armel (1.3.1-1 to 1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-xdg-home/armel (1.3.0-1 to 1.3.0-1)
- Migration status for rust-xdg-home/armel (1.3.0-1 to 1.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-xml-rs/armel (0.8.19-1 to 0.8.19-1)
- Migration status for rust-xml-rs/armel (0.8.19-1 to 0.8.19-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-xmlwriter/armel (0.1.0-2 to 0.1.0-2)
- Migration status for rust-xmlwriter/armel (0.1.0-2 to 0.1.0-2): Will attempt migration (Any information below is purely informational)
- rust-xterm-query/armel (0.5.2-1 to 0.5.2-1)
- Migration status for rust-xterm-query/armel (0.5.2-1 to 0.5.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-xxhash-rust/armel (0.8.15-1 to 0.8.15-1)
- Migration status for rust-xxhash-rust/armel (0.8.15-1 to 0.8.15-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-xz2/armel (0.1.7-1 to 0.1.7-1)
- Migration status for rust-xz2/armel (0.1.7-1 to 0.1.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-y4m/armel (0.8.0-1 to 0.8.0-1)
- Migration status for rust-y4m/armel (0.8.0-1 to 0.8.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-yaml-rust2/armel (0.10.3-1 to 0.10.3-1)
- Migration status for rust-yaml-rust2/armel (0.10.3-1 to 0.10.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-yeslogic-fontconfig-sys/armel (5.0.0-1 to 5.0.0-1)
- Migration status for rust-yeslogic-fontconfig-sys/armel (5.0.0-1 to 5.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-z-base-32/armel (0.1.4-1 to 0.1.4-1)
- Migration status for rust-z-base-32/armel (0.1.4-1 to 0.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zeroize-derive/armel (1.4.2-1 to 1.4.2-1)
- Migration status for rust-zeroize-derive/armel (1.4.2-1 to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zeroize/armel (1.8.1-1 to 1.8.1-1)
- Migration status for rust-zeroize/armel (1.8.1-1 to 1.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zip/armel (2.5.0-1 to 2.5.0-1)
- Migration status for rust-zip/armel (2.5.0-1 to 2.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zopfli/armel (0.8.1-1 to 0.8.1-1)
- Migration status for rust-zopfli/armel (0.8.1-1 to 0.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zstd-safe/armel (7.2.1-1 to 7.2.1-1)
- Migration status for rust-zstd-safe/armel (7.2.1-1 to 7.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zstd-sys/armel (2.0.13-2 to 2.0.13-2)
- Migration status for rust-zstd-sys/armel (2.0.13-2 to 2.0.13-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zstd/armel (0.13.2-2 to 0.13.2-2)
- Migration status for rust-zstd/armel (0.13.2-2 to 0.13.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zune-core/armel (0.4.12-1 to 0.4.12-1)
- Migration status for rust-zune-core/armel (0.4.12-1 to 0.4.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zune-inflate/armel (0.2.54-1 to 0.2.54-1)
- Migration status for rust-zune-inflate/armel (0.2.54-1 to 0.2.54-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zune-jpeg/armel (0.4.18-2 to 0.4.18-2)
- Migration status for rust-zune-jpeg/armel (0.4.18-2 to 0.4.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zvariant-derive/armel (5.2.0-2 to 5.2.0-2)
- Migration status for rust-zvariant-derive/armel (5.2.0-2 to 5.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- rust-zvariant/armel (5.2.0-4 to 5.2.0-4)
- Migration status for rust-zvariant/armel (5.2.0-4 to 5.2.0-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-zvariant/armel rust-zbus-names (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-zvariant/armel rust-gvdb
- rxtx/armel (2.2.0+dfsg-3.1 to 2.2.0+dfsg-3.1)
- Migration status for rxtx/armel (2.2.0+dfsg-3.1 to 2.2.0+dfsg-3.1): Will attempt migration (Any information below is purely informational)
- safecopy/armel (1.7-7 to 1.7-7)
- Migration status for safecopy/armel (1.7-7 to 1.7-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- samba/armel (2:4.22.4+dfsg-1 to 2:4.22.4+dfsg-1)
- Migration status for samba/armel (2:4.22.4+dfsg-1 to 2:4.22.4+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- samdump2/armel (3.0.0-8 to 3.0.0-8)
- Migration status for samdump2/armel (3.0.0-8 to 3.0.0-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- scalpel/armel (1.60+git20240110.6960eb2-1 to 1.60+git20240110.6960eb2-1)
- Migration status for scalpel/armel (1.60+git20240110.6960eb2-1 to 1.60+git20240110.6960eb2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- scikit-learn/armel (1.4.2+dfsg-8 to 1.4.2+dfsg-8)
- Migration status for scikit-learn/armel (1.4.2+dfsg-8 to 1.4.2+dfsg-8): Will attempt migration (Any information below is purely informational)
- scipy/armel (1.15.3-1 to 1.15.3-1)
- Migration status for scipy/armel (1.15.3-1 to 1.15.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- screen/armel (4.9.1-3 to 4.9.1-3)
- Migration status for screen/armel (4.9.1-3 to 4.9.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- scrounge-ntfs/armel (0.9-11 to 0.9-11)
- Migration status for scrounge-ntfs/armel (0.9-11 to 0.9-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- scrub/armel (2.6.1+git20240819.9b4267e-1 to 2.6.1+git20240819.9b4267e-1)
- Migration status for scrub/armel (2.6.1+git20240819.9b4267e-1 to 2.6.1+git20240819.9b4267e-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sddm/armel (0.21.0+git20250502.4fe234b-2 to 0.21.0+git20250502.4fe234b-2)
- Migration status for sddm/armel (0.21.0+git20250502.4fe234b-2 to 0.21.0+git20250502.4fe234b-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sed/armel (4.9-2 to 4.9-2)
- Migration status for sed/armel (4.9-2 to 4.9-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sexplib310/armel (1:0.17.0-1 to 1:0.17.0-1)
- Migration status for sexplib310/armel (1:0.17.0-1 to 1:0.17.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- shared-mime-info/armel (2.4-5 to 2.4-5)
- Migration status for shared-mime-info/armel (2.4-5 to 2.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- shed/armel (1.16-1 to 1.16-1)
- Migration status for shed/armel (1.16-1 to 1.16-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- shine/armel (3.1.1-2 to 3.1.1-2)
- Migration status for shine/armel (3.1.1-2 to 3.1.1-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: shine/armel ocaml-shine (not considered)
- Invalidated by implicit-dependency
- siege/armel (4.1.6-1 to 4.1.6-1)
- Migration status for siege/armel (4.1.6-1 to 4.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- signond/armel (8.61+git20231015.c8ad982-7 to 8.61+git20231015.c8ad982-7)
- Migration status for signond/armel (8.61+git20231015.c8ad982-7 to 8.61+git20231015.c8ad982-7): Will attempt migration (Any information below is purely informational)
- simplejson/armel (3.20.1-1 to 3.20.1-1)
- Migration status for simplejson/armel (3.20.1-1 to 3.20.1-1): Will attempt migration (Any information below is purely informational)
- sip-tester/amd64 (1:3.7.3-2 to 1:3.7.3-2)
- Migration status for sip-tester/amd64 (1:3.7.3-2 to 1:3.7.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: sip-tester/amd64 wolfssl (not considered)
- Invalidated by dependency
- sip-tester/arm64 (1:3.7.3-2 to 1:3.7.3-2)
- Migration status for sip-tester/arm64 (1:3.7.3-2 to 1:3.7.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: sip-tester/arm64 wolfssl (not considered)
- Invalidated by dependency
- sip-tester/armhf (1:3.7.3-2 to 1:3.7.3-2)
- Migration status for sip-tester/armhf (1:3.7.3-2 to 1:3.7.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: sip-tester/armhf wolfssl (not considered)
- Invalidated by dependency
- sip-tester/i386 (1:3.7.3-2 to 1:3.7.3-2)
- Migration status for sip-tester/i386 (1:3.7.3-2 to 1:3.7.3-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: sip-tester/i386 wolfssl (not considered)
- Invalidated by dependency
- sipcrack/armel (0.2-4 to 0.2-4)
- Migration status for sipcrack/armel (0.2-4 to 0.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sipsak/armel (0.9.8.1-1 to 0.9.8.1-1)
- Migration status for sipsak/armel (0.9.8.1-1 to 0.9.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- slang2/armel (2.3.3-5 to 2.3.3-5)
- Migration status for slang2/armel (2.3.3-5 to 2.3.3-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- slowhttptest/armel (1.9.0-1 to 1.9.0-1)
- Migration status for slowhttptest/armel (1.9.0-1 to 1.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- snapd/armel (2.68.3-3 to 2.68.3-3)
- Migration status for snapd/armel (2.68.3-3 to 2.68.3-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- snappy-java/armel (1.1.10.8-1 to 1.1.10.8-1)
- Migration status for snappy-java/armel (1.1.10.8-1 to 1.1.10.8-1): Will attempt migration (Any information below is purely informational)
- snappy/armel (1.2.2-1 to 1.2.2-1)
- Migration status for snappy/armel (1.2.2-1 to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapyairspy/armel (0.2.0-4 to 0.2.0-4)
- Migration status for soapyairspy/armel (0.2.0-4 to 0.2.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapyaudio/armel (0.1.1-6 to 0.1.1-6)
- Migration status for soapyaudio/armel (0.1.1-6 to 0.1.1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapybladerf/armel (0.4.2-1 to 0.4.2-1)
- Migration status for soapybladerf/armel (0.4.2-1 to 0.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapyhackrf/armel (0.3.4-2 to 0.3.4-2)
- Migration status for soapyhackrf/armel (0.3.4-2 to 0.3.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapyosmo/armel (0.2.5-8 to 0.2.5-8)
- Migration status for soapyosmo/armel (0.2.5-8 to 0.2.5-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapyredpitaya/armel (0.1.1-5 to 0.1.1-5)
- Migration status for soapyredpitaya/armel (0.1.1-5 to 0.1.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapyremote/armel (0.5.2-4 to 0.5.2-4)
- Migration status for soapyremote/armel (0.5.2-4 to 0.5.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapyrtlsdr/armel (0.3.3-1 to 0.3.3-1)
- Migration status for soapyrtlsdr/armel (0.3.3-1 to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapysdr/armel (0.8.1-5 to 0.8.1-5)
- Migration status for soapysdr/armel (0.8.1-5 to 0.8.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soapyuhd/armel (0.4.1-5 to 0.4.1-5)
- Migration status for soapyuhd/armel (0.4.1-5 to 0.4.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- socat/armel (1.8.0.3-1 to 1.8.0.3-1)
- Migration status for socat/armel (1.8.0.3-1 to 1.8.0.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- solid/armel (5.116.0-1 to 5.116.0-1)
- Migration status for solid/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sonnet/armel (5.116.0-1 to 5.116.0-1)
- Migration status for sonnet/armel (5.116.0-1 to 5.116.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- soundtouch/armel (2.4.0+ds-1 to 2.4.0+ds-1)
- Migration status for soundtouch/armel (2.4.0+ds-1 to 2.4.0+ds-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: soundtouch/armel ocaml-soundtouch (not considered)
- Invalidated by implicit-dependency
- sox/armel (14.4.2+git20190427-5 to 14.4.2+git20190427-5)
- Migration status for sox/armel (14.4.2+git20190427-5 to 14.4.2+git20190427-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- spatialite/armel (5.1.0-3 to 5.1.0-3)
- Migration status for spatialite/armel (5.1.0-3 to 5.1.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- spdlog/armel (1:1.15.3+ds-1 to 1:1.15.3+ds-1)
- Migration status for spdlog/armel (1:1.15.3+ds-1 to 1:1.15.3+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- spectools/armel (201601r1-6 to 201601r1-6)
- Migration status for spectools/armel (201601r1-6 to 201601r1-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- speech-tools/armel (1:2.5.0-13 to 1:2.5.0-13)
- Migration status for speech-tools/armel (1:2.5.0-13 to 1:2.5.0-13): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- speex/armel (1.2.1-3 to 1.2.1-3)
- Migration status for speex/armel (1.2.1-3 to 1.2.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- spherepack/armel (3.3~a1-8 to 3.3~a1-8)
- Migration status for spherepack/armel (3.3~a1-8 to 3.3~a1-8): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: spherepack/armel ncl (not considered)
- Invalidated by implicit-dependency
- spice-vdagent/armel (0.22.1-4.1 to 0.22.1-4.1)
- Migration status for spice-vdagent/armel (0.22.1-4.1 to 0.22.1-4.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sqlcipher/armel (4.6.1-2 to 4.6.1-2)
- Migration status for sqlcipher/armel (4.6.1-2 to 4.6.1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sqlite3/armel (3.46.1-7 to 3.46.1-7)
- Migration status for sqlite3/armel (3.46.1-7 to 3.46.1-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sqlitebrowser/armel (3.13.0-1 to 3.13.0-1)
- Migration status for sqlitebrowser/armel (3.13.0-1 to 3.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- squashfs-tools-ng/armel (1.3.2-1 to 1.3.2-1)
- Migration status for squashfs-tools-ng/armel (1.3.2-1 to 1.3.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- squashfs-tools/armel (1:4.7.2-1 to 1:4.7.2-1)
- Migration status for squashfs-tools/armel (1:4.7.2-1 to 1:4.7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ssdeep/armel (2.14.1+git20180629.57fcfff-3 to 2.14.1+git20180629.57fcfff-3)
- Migration status for ssdeep/armel (2.14.1+git20180629.57fcfff-3 to 2.14.1+git20180629.57fcfff-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sshfs-fuse/armel (3.7.3-1.1 to 3.7.3-1.1)
- Migration status for sshfs-fuse/armel (3.7.3-1.1 to 3.7.3-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ssldump/armel (1.9-1 to 1.9-1)
- Migration status for ssldump/armel (1.9-1 to 1.9-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sslh/armel (2.1.4-1 to 2.1.4-1)
- Migration status for sslh/armel (2.1.4-1 to 2.1.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sslscan/armel (2.1.5-1 to 2.1.5-1)
- Migration status for sslscan/armel (2.1.5-1 to 2.1.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sslsniff/armel (0.8+git20111017-1 to 0.8+git20111017-1)
- Migration status for sslsniff/armel (0.8+git20111017-1 to 0.8+git20111017-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sslsplit/armel (0.5.5-2.1 to 0.5.5-2.1)
- Migration status for sslsplit/armel (0.5.5-2.1 to 0.5.5-2.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- startpar/armel (0.66-1 to 0.66-1)
- Migration status for startpar/armel (0.66-1 to 0.66-1): Will attempt migration (Any information below is purely informational)
- startup-notification/armel (0.12-8 to 0.12-8)
- Migration status for startup-notification/armel (0.12-8 to 0.12-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- statsprocessor/armel (0.11+git20160316-5 to 0.11+git20160316-5)
- Migration status for statsprocessor/armel (0.11+git20160316-5 to 0.11+git20160316-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- stegsnow/armel (20130616-8 to 20130616-8)
- Migration status for stegsnow/armel (20130616-8 to 20130616-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- strace/armel (6.16+ds-2 to 6.16+ds-2)
- Migration status for strace/armel (6.16+ds-2 to 6.16+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- stunnel4/armel (3:5.74-2 to 3:5.74-2)
- Migration status for stunnel4/armel (3:5.74-2 to 3:5.74-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- subversion/armel (1.14.5-3 to 1.14.5-3)
- Migration status for subversion/armel (1.14.5-3 to 1.14.5-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- suckless-tools/armel (48-1 to 48-1)
- Migration status for suckless-tools/armel (48-1 to 48-1): Will attempt migration (Any information below is purely informational)
- sudo/armel (1.9.17p2-1 to 1.9.17p2-1)
- Migration status for sudo/armel (1.9.17p2-1 to 1.9.17p2-1): Will attempt migration (Any information below is purely informational)
- sunxi-tools/armel (1.4.2+git20240825.4390ca-1 to 1.4.2+git20240825.4390ca-1)
- Migration status for sunxi-tools/armel (1.4.2+git20240825.4390ca-1 to 1.4.2+git20240825.4390ca-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- superlu/armel (7.0.1+dfsg1-2 to 7.0.1+dfsg1-2)
- Migration status for superlu/armel (7.0.1+dfsg1-2 to 7.0.1+dfsg1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- supermin/armel (5.2.2-6 to 5.2.2-6)
- Migration status for supermin/armel (5.2.2-6 to 5.2.2-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- survival/armel (3.8-3-1 to 3.8-3-1)
- Migration status for survival/armel (3.8-3-1 to 3.8-3-1): Will attempt migration (Any information below is purely informational)
- svt-av1/armel (2.3.0+dfsg-1 to 2.3.0+dfsg-1)
- Migration status for svt-av1/armel (2.3.0+dfsg-1 to 2.3.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- swtpm/armel (0.7.1-1.5 to 0.7.1-1.5)
- Migration status for swtpm/armel (0.7.1-1.5 to 0.7.1-1.5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: swtpm/armel incus (not considered)
- Invalidated by implicit-dependency
- sxiv/armel (26-1 to 26-1)
- Migration status for sxiv/armel (26-1 to 26-1): Will attempt migration (Any information below is purely informational)
- sysprof/armel (48.0-2 to 48.0-2)
- Migration status for sysprof/armel (48.0-2 to 48.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sysstat/armel (12.7.5-2 to 12.7.5-2)
- Migration status for sysstat/armel (12.7.5-2 to 12.7.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: sysstat/armel zfs-linux (not considered)
- Invalidated by implicit-dependency
- systemd-udeb/armel (257.4-1 to 257.4-1)
- Migration status for systemd-udeb/armel (257.4-1 to 257.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- sysvinit/armel (3.14-4 to 3.14-4)
- Migration status for sysvinit/armel (3.14-4 to 3.14-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- t1utils/armel (1.41-4 to 1.41-4)
- Migration status for t1utils/armel (1.41-4 to 1.41-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- t50/armel (5.8.7b-1 to 5.8.7b-1)
- Migration status for t50/armel (5.8.7b-1 to 5.8.7b-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tar/armel (1.35+dfsg-3.1 to 1.35+dfsg-3.1)
- Migration status for tar/armel (1.35+dfsg-3.1 to 1.35+dfsg-3.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tcl8.6/armel (8.6.17+dfsg-1 to 8.6.17+dfsg-1)
- Migration status for tcl8.6/armel (8.6.17+dfsg-1 to 8.6.17+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tcltk-defaults/armel (8.6.16 to 8.6.16)
- Migration status for tcltk-defaults/armel (8.6.16 to 8.6.16): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tcp-wrappers/armel (7.6.q-36 to 7.6.q-36)
- Migration status for tcp-wrappers/armel (7.6.q-36 to 7.6.q-36): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tcpdump/armel (4.99.5-2 to 4.99.5-2)
- Migration status for tcpdump/armel (4.99.5-2 to 4.99.5-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tcpflow/armel (1.6.1-3 to 1.6.1-3)
- Migration status for tcpflow/armel (1.6.1-3 to 1.6.1-3): Will attempt migration (Any information below is purely informational)
- tcpick/armel (0.2.1-11 to 0.2.1-11)
- Migration status for tcpick/armel (0.2.1-11 to 0.2.1-11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tcpreplay/armel (4.5.1-1 to 4.5.1-1)
- Migration status for tcpreplay/armel (4.5.1-1 to 4.5.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tcptrace/armel (6.6.7-6 to 6.6.7-6)
- Migration status for tcptrace/armel (6.6.7-6 to 6.6.7-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tcsh/armel (6.24.13-2 to 6.24.13-2)
- Migration status for tcsh/armel (6.24.13-2 to 6.24.13-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: tcsh/armel ncl (not considered)
- Invalidated by implicit-dependency
- tecla/armel (48.0.2-1 to 48.0.2-1)
- Migration status for tecla/armel (48.0.2-1 to 48.0.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- terminology/armel (1.14.0-1 to 1.14.0-1)
- Migration status for terminology/armel (1.14.0-1 to 1.14.0-1): Will attempt migration (Any information below is purely informational)
- testdisk/armel (7.2-0.1 to 7.2-0.1)
- Migration status for testdisk/armel (7.2-0.1 to 7.2-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- texinfo/armel (7.2-4 to 7.2-4)
- Migration status for texinfo/armel (7.2-4 to 7.2-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: texinfo/armel stardict (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: texinfo/armel mgetty
- texlive-bin/armel (2025.20250727.75242+ds-4 to 2025.20250727.75242+ds-4)
- Migration status for texlive-bin/armel (2025.20250727.75242+ds-4 to 2025.20250727.75242+ds-4): Will attempt migration (Any information below is purely informational)
- tftp-hpa/armel (5.2+20240610-3 to 5.2+20240610-3)
- Migration status for tftp-hpa/armel (5.2+20240610-3 to 5.2+20240610-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- thc-ipv6/armel (3.8-1 to 3.8-1)
- Migration status for thc-ipv6/armel (3.8-1 to 3.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- thrift/armel (0.19.0-4 to 0.19.0-4)
- Migration status for thrift/armel (0.19.0-4 to 0.19.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- thunar-archive-plugin/armel (0.5.3-1 to 0.5.3-1)
- Migration status for thunar-archive-plugin/armel (0.5.3-1 to 0.5.3-1): Will attempt migration (Any information below is purely informational)
- thunar/armel (4.20.4-1 to 4.20.4-1)
- Migration status for thunar/armel (4.20.4-1 to 4.20.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tiff/armel (4.7.0-4 to 4.7.0-4)
- Migration status for tiff/armel (4.7.0-4 to 4.7.0-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tiger/armel (1:3.2.4~rc1-3.4 to 1:3.2.4~rc1-3.4)
- Migration status for tiger/armel (1:3.2.4~rc1-3.4 to 1:3.2.4~rc1-3.4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tigervnc/armel (1.15.0+dfsg-2 to 1.15.0+dfsg-2)
- Migration status for tigervnc/armel (1.15.0+dfsg-2 to 1.15.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tightvnc/armel (1:1.3.10-10 to 1:1.3.10-10)
- Migration status for tightvnc/armel (1:1.3.10-10 to 1:1.3.10-10): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- time/armel (1.9-0.2 to 1.9-0.2)
- Migration status for time/armel (1.9-0.2 to 1.9-0.2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tini/armel (0.19.0-3 to 0.19.0-3)
- Migration status for tini/armel (0.19.0-3 to 0.19.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tinyproxy/armel (1.11.2-1 to 1.11.2-1)
- Migration status for tinyproxy/armel (1.11.2-1 to 1.11.2-1): Will attempt migration (Any information below is purely informational)
- tinyxml2/armel (11.0.0+dfsg-1 to 11.0.0+dfsg-1)
- Migration status for tinyxml2/armel (11.0.0+dfsg-1 to 11.0.0+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tk8.6/armel (8.6.17-1 to 8.6.17-1)
- Migration status for tk8.6/armel (8.6.17-1 to 8.6.17-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing tk8.6/8.6.17-1/armel from kali-rolling makes tk/8.6.16/armel uninstallable
- removing tk8.6-dev/8.6.17-1/armel from kali-rolling makes tk-dev/8.6.16/armel uninstallable
- tmux/armel (3.5a-3 to 3.5a-3)
- Migration status for tmux/armel (3.5a-3 to 3.5a-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tokodon/armel (25.04.3-1 to 25.04.3-1)
- Migration status for tokodon/armel (25.04.3-1 to 25.04.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- totem-pl-parser/armel (3.26.6-2 to 3.26.6-2)
- Migration status for totem-pl-parser/armel (3.26.6-2 to 3.26.6-2): Will attempt migration (Any information below is purely informational)
- tree/armel (2.2.1-1 to 2.2.1-1)
- Migration status for tree/armel (2.2.1-1 to 2.2.1-1): Will attempt migration (Any information below is purely informational)
- triggerhappy/armel (0.5.0-1.1 to 0.5.0-1.1)
- Migration status for triggerhappy/armel (0.5.0-1.1 to 0.5.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- tyxml/armel (4.6.0-1 to 4.6.0-1)
- Migration status for tyxml/armel (4.6.0-1 to 4.6.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- u-boot/armel (2025.01-3 to 2025.01-3)
- Migration status for u-boot/armel (2025.01-3 to 2025.01-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- udisks2/armel (2.10.90-3 to 2.10.90-3)
- Migration status for udisks2/armel (2.10.90-3 to 2.10.90-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- udpkg/armel (1.21 to 1.21)
- Migration status for udpkg/armel (1.21 to 1.21): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- udptunnel/armel (1.1-12 to 1.1-12)
- Migration status for udptunnel/armel (1.1-12 to 1.1-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- uhd/armel (4.8.0.0+ds1-2 to 4.8.0.0+ds1-2)
- Migration status for uhd/armel (4.8.0.0+ds1-2 to 4.8.0.0+ds1-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ujson/armel (5.10.0-1 to 5.10.0-1)
- Migration status for ujson/armel (5.10.0-1 to 5.10.0-1): Will attempt migration (Any information below is purely informational)
- umockdev/armel (0.19.3-2 to 0.19.3-2)
- Migration status for umockdev/armel (0.19.3-2 to 0.19.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- unar/armel (1.10.8+ds1-9 to 1.10.8+ds1-9)
- Migration status for unar/armel (1.10.8+ds1-9 to 1.10.8+ds1-9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- undbx/armel (0.21-4 to 0.21-4)
- Migration status for undbx/armel (0.21-4 to 0.21-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- unhide/armel (20240510-2 to 20240510-2)
- Migration status for unhide/armel (20240510-2 to 20240510-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- universal-ctags/armel (5.9.20210829.0-2 to 5.9.20210829.0-2)
- Migration status for universal-ctags/armel (5.9.20210829.0-2 to 5.9.20210829.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: universal-ctags/armel geany-plugins (not considered)
- Invalidated by implicit-dependency
- unixodbc/armel (2.3.12-2 to 2.3.12-2)
- Migration status for unixodbc/armel (2.3.12-2 to 2.3.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- unl0kr/armel (2.0.3+dfsg-2 to 2.0.3+dfsg-2)
- Migration status for unl0kr/armel (2.0.3+dfsg-2 to 2.0.3+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- unzip/armel (6.0-29 to 6.0-29)
- Migration status for unzip/armel (6.0-29 to 6.0-29): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- upower/armel (1.90.10-1 to 1.90.10-1)
- Migration status for upower/armel (1.90.10-1 to 1.90.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- upx-ucl/armel (4.2.4-1.1 to 4.2.4-1.1)
- Migration status for upx-ucl/armel (4.2.4-1.1 to 4.2.4-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- uriparser/armel (0.9.8+dfsg-2 to 0.9.8+dfsg-2)
- Migration status for uriparser/armel (0.9.8+dfsg-2 to 0.9.8+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- urwid/armel (2.6.16-1 to 2.6.16-1)
- Migration status for urwid/armel (2.6.16-1 to 2.6.16-1): Will attempt migration (Any information below is purely informational)
- usbutils/armel (1:018-2 to 1:018-2)
- Migration status for usbutils/armel (1:018-2 to 1:018-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- utf8proc/armel (2.9.0-1 to 2.9.0-1)
- Migration status for utf8proc/armel (2.9.0-1 to 2.9.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- util-linux/armel (2.41.1-1 to 2.41.1-1)
- Migration status for util-linux/armel (2.41.1-1 to 2.41.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- uutf/armel (1.0.4-1 to 1.0.4-1)
- Migration status for uutf/armel (1.0.4-1 to 1.0.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- uvloop/armel (0.21.0+ds1-3 to 0.21.0+ds1-3)
- Migration status for uvloop/armel (0.21.0+ds1-3 to 0.21.0+ds1-3): Will attempt migration (Any information below is purely informational)
- vboot-utils/armel (0~R106-15054.B+dfsg-0.1 to 0~R106-15054.B+dfsg-0.1)
- Migration status for vboot-utils/armel (0~R106-15054.B+dfsg-0.1 to 0~R106-15054.B+dfsg-0.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- vdeplug-agno/amd64 (0.1.1-1 to 0.1.1-1)
- Migration status for vdeplug-agno/amd64 (0.1.1-1 to 0.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: vdeplug-agno/amd64 wolfssl (not considered)
- Invalidated by dependency
- vdeplug-agno/arm64 (0.1.1-1 to 0.1.1-1)
- Migration status for vdeplug-agno/arm64 (0.1.1-1 to 0.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: vdeplug-agno/arm64 wolfssl (not considered)
- Invalidated by dependency
- vdeplug-agno/armhf (0.1.1-1 to 0.1.1-1)
- Migration status for vdeplug-agno/armhf (0.1.1-1 to 0.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: vdeplug-agno/armhf wolfssl (not considered)
- Invalidated by dependency
- vdeplug-agno/i386 (0.1.1-1 to 0.1.1-1)
- Migration status for vdeplug-agno/i386 (0.1.1-1 to 0.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: vdeplug-agno/i386 wolfssl (not considered)
- Invalidated by dependency
- vim/armel (2:9.1.1230-2 to 2:9.1.1230-2)
- Migration status for vim/armel (2:9.1.1230-2 to 2:9.1.1230-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- vnstat/armel (2.13-1 to 2.13-1)
- Migration status for vnstat/armel (2.13-1 to 2.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- vo-aacenc/armel (0.1.3-3 to 0.1.3-3)
- Migration status for vo-aacenc/armel (0.1.3-3 to 0.1.3-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: vo-aacenc/armel ocaml-voaacenc (not considered)
- Invalidated by implicit-dependency
- volk/armel (3.2.0-2 to 3.2.0-2)
- Migration status for volk/armel (3.2.0-2 to 3.2.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- vpnc/armel (0.5.3+git20241220-2 to 0.5.3+git20241220-2)
- Migration status for vpnc/armel (0.5.3+git20241220-2 to 0.5.3+git20241220-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- vte2.91/armel (0.80.3-2 to 0.80.3-2)
- Migration status for vte2.91/armel (0.80.3-2 to 0.80.3-2): Will attempt migration (Any information below is purely informational)
- vulkan-loader/armel (1.4.321.0-1 to 1.4.321.0-1)
- Migration status for vulkan-loader/armel (1.4.321.0-1 to 1.4.321.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- wayland/armel (1.23.1-3 to 1.23.1-3)
- Migration status for wayland/armel (1.23.1-3 to 1.23.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- webp-pixbuf-loader/armel (0.2.7-1 to 0.2.7-1)
- Migration status for webp-pixbuf-loader/armel (0.2.7-1 to 0.2.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- wget/armel (1.25.0-2 to 1.25.0-2)
- Migration status for wget/armel (1.25.0-2 to 1.25.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- whois/armel (5.6.4 to 5.6.4)
- Migration status for whois/armel (5.6.4 to 5.6.4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- winregfs/armel (0.7-5 to 0.7-5)
- Migration status for winregfs/armel (0.7-5 to 0.7-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- wipe/armel (0.24-10 to 0.24-10)
- Migration status for wipe/armel (0.24-10 to 0.24-10): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- wireless-tools/armel (30~pre9-18 to 30~pre9-18)
- Migration status for wireless-tools/armel (30~pre9-18 to 30~pre9-18): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- wireplumber/armel (0.5.10-3 to 0.5.10-3)
- Migration status for wireplumber/armel (0.5.10-3 to 0.5.10-3): Will attempt migration (Any information below is purely informational)
- wireshark/armel (4.4.7-1 to 4.4.7-1)
- Migration status for wireshark/armel (4.4.7-1 to 4.4.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- wpa/armel (2:2.10-24 to 2:2.10-24)
- Migration status for wpa/armel (2:2.10-24 to 2:2.10-24): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- wxpython4.0/armel (4.2.3+dfsg-2 to 4.2.3+dfsg-2)
- Migration status for wxpython4.0/armel (4.2.3+dfsg-2 to 4.2.3+dfsg-2): Will attempt migration (Any information below is purely informational)
- x11-apps/armel (7.7+11 to 7.7+11)
- Migration status for x11-apps/armel (7.7+11 to 7.7+11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- x11-session-utils/armel (7.7+6 to 7.7+6)
- Migration status for x11-session-utils/armel (7.7+6 to 7.7+6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing x11-session-utils/7.7+6+b1/armel from kali-rolling makes xorg/1:7.7+24/armel uninstallable
- x11-utils/armel (7.7+7 to 7.7+7)
- Migration status for x11-utils/armel (7.7+7 to 7.7+7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- x11-xkb-utils/armel (7.7+9 to 7.7+9)
- Migration status for x11-xkb-utils/armel (7.7+9 to 7.7+9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- x11-xserver-utils/armel (7.7+11 to 7.7+11)
- Migration status for x11-xserver-utils/armel (7.7+11 to 7.7+11): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xarchiver/armel (1:0.5.4.25-2 to 1:0.5.4.25-2)
- Migration status for xarchiver/armel (1:0.5.4.25-2 to 1:0.5.4.25-2): Will attempt migration (Any information below is purely informational)
- xauth/armel (1:1.1.2-1.1 to 1:1.1.2-1.1)
- Migration status for xauth/armel (1:1.1.2-1.1 to 1:1.1.2-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xaw3d/armel (1.5+F-2 to 1.5+F-2)
- Migration status for xaw3d/armel (1.5+F-2 to 1.5+F-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: xaw3d/armel emacs (not considered)
- Invalidated by implicit-dependency
- xcape/armel (1.2-3 to 1.2-3)
- Migration status for xcape/armel (1.2-3 to 1.2-3): Will attempt migration (Any information below is purely informational)
- xclip/armel (0.13-4 to 0.13-4)
- Migration status for xclip/armel (0.13-4 to 0.13-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xdg-dbus-proxy/armel (0.1.6-1 to 0.1.6-1)
- Migration status for xdg-dbus-proxy/armel (0.1.6-1 to 0.1.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xdg-desktop-portal-phosh/armel (0.46.0-2 to 0.46.0-2)
- Migration status for xdg-desktop-portal-phosh/armel (0.46.0-2 to 0.46.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xdg-desktop-portal/armel (1.20.3+ds-1 to 1.20.3+ds-1)
- Migration status for xdg-desktop-portal/armel (1.20.3+ds-1 to 1.20.3+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xdotool/armel (1:3.20160805.1-5.1 to 1:3.20160805.1-5.1)
- Migration status for xdotool/armel (1:3.20160805.1-5.1 to 1:3.20160805.1-5.1): Will attempt migration (Any information below is purely informational)
- xerces-c/armel (3.2.4+debian-1.3 to 3.2.4+debian-1.3)
- Migration status for xerces-c/armel (3.2.4+debian-1.3 to 3.2.4+debian-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xfce4-appfinder/armel (4.20.0-2 to 4.20.0-2)
- Migration status for xfce4-appfinder/armel (4.20.0-2 to 4.20.0-2): Will attempt migration (Any information below is purely informational)
- xfce4-cpugraph-plugin/armel (1.2.10-1 to 1.2.10-1)
- Migration status for xfce4-cpugraph-plugin/armel (1.2.10-1 to 1.2.10-1): Will attempt migration (Any information below is purely informational)
- xfce4-genmon-plugin/armel (4.3.0-1 to 4.3.0-1)
- Migration status for xfce4-genmon-plugin/armel (4.3.0-1 to 4.3.0-1): Will attempt migration (Any information below is purely informational)
- xfce4-panel/armel (4.20.4-1 to 4.20.4-1)
- Migration status for xfce4-panel/armel (4.20.4-1 to 4.20.4-1): Will attempt migration (Any information below is purely informational)
- xfce4-power-manager/armel (4.20.0-1 to 4.20.0-1)
- Migration status for xfce4-power-manager/armel (4.20.0-1 to 4.20.0-1): Will attempt migration (Any information below is purely informational)
- xfce4-pulseaudio-plugin/armel (0.4.9-1 to 0.4.9-1)
- Migration status for xfce4-pulseaudio-plugin/armel (0.4.9-1 to 0.4.9-1): Will attempt migration (Any information below is purely informational)
- xfce4-screensaver/armel (4.20.1-1 to 4.20.1-1)
- Migration status for xfce4-screensaver/armel (4.20.1-1 to 4.20.1-1): Will attempt migration (Any information below is purely informational)
- xfce4-screenshooter/armel (1.11.1-1 to 1.11.1-1)
- Migration status for xfce4-screenshooter/armel (1.11.1-1 to 1.11.1-1): Will attempt migration (Any information below is purely informational)
- xfce4-session/armel (4.20.3-1 to 4.20.3-1)
- Migration status for xfce4-session/armel (4.20.3-1 to 4.20.3-1): Will attempt migration (Any information below is purely informational)
- xfce4-settings/armel (4.20.2-1 to 4.20.2-1)
- Migration status for xfce4-settings/armel (4.20.2-1 to 4.20.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xfce4-taskmanager/armel (1.5.8-1 to 1.5.8-1)
- Migration status for xfce4-taskmanager/armel (1.5.8-1 to 1.5.8-1): Will attempt migration (Any information below is purely informational)
- (2.9.2-1 to 2.9.2-1)
- Migration status for xfce4-whiskermenu-plugin/armel (2.9.2-1 to 2.9.2-1): Will attempt migration (Any information below is purely informational)
- xfconf/armel (4.20.0-1 to 4.20.0-1)
- Migration status for xfconf/armel (4.20.0-1 to 4.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xfdesktop4/armel (4.20.1-1 to 4.20.1-1)
- Migration status for xfdesktop4/armel (4.20.1-1 to 4.20.1-1): Will attempt migration (Any information below is purely informational)
- xfonts-utils/armel (1:7.7+7 to 1:7.7+7)
- Migration status for xfonts-utils/armel (1:7.7+7 to 1:7.7+7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xfsprogs/armel (6.15.0-1 to 6.15.0-1)
- Migration status for xfsprogs/armel (6.15.0-1 to 6.15.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xft/armel (2.3.6-1 to 2.3.6-1)
- Migration status for xft/armel (2.3.6-1 to 2.3.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xfwm4/armel (4.20.0-1 to 4.20.0-1)
- Migration status for xfwm4/armel (4.20.0-1 to 4.20.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xinit/armel (1.4.2-1 to 1.4.2-1)
- Migration status for xinit/armel (1.4.2-1 to 1.4.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xmlm/armel (1.4.0-1 to 1.4.0-1)
- Migration status for xmlm/armel (1.4.0-1 to 1.4.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: xmlm/armel ocaml-xmlplaylist (not considered)
- Invalidated by implicit-dependency
- xmount/armel (1.2.0+ds-1 to 1.2.0+ds-1)
- Migration status for xmount/armel (1.2.0+ds-1 to 1.2.0+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xorg-server/armel (2:21.1.16-1.3 to 2:21.1.16-1.3)
- Migration status for xorg-server/armel (2:21.1.16-1.3 to 2:21.1.16-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xorg/armel (1:7.7+24 to 1:7.7+24)
- Migration status for xorg/armel (1:7.7+24 to 1:7.7+24): Will attempt migration (Any information below is purely informational)
- xrootd/armel (5.8.4-2 to 5.8.4-2)
- Migration status for xrootd/armel (5.8.4-2 to 5.8.4-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: xrootd/armel xrootd-s3-http (not considered)
- Invalidated by implicit-dependency
- xserver-xorg-input-libinput/armel (1.5.0-1 to 1.5.0-1)
- Migration status for xserver-xorg-input-libinput/armel (1.5.0-1 to 1.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xserver-xorg-video-amdgpu/armel (23.0.0-1 to 23.0.0-1)
- Migration status for xserver-xorg-video-amdgpu/armel (23.0.0-1 to 23.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xserver-xorg-video-ati/armel (1:22.0.0-1 to 1:22.0.0-1)
- Migration status for xserver-xorg-video-ati/armel (1:22.0.0-1 to 1:22.0.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xserver-xorg-video-fbdev/armel (1:0.5.0-2 to 1:0.5.0-2)
- Migration status for xserver-xorg-video-fbdev/armel (1:0.5.0-2 to 1:0.5.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xterm/armel (398-1 to 398-1)
- Migration status for xterm/armel (398-1 to 398-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xutils-dev/armel (1:7.7+7 to 1:7.7+7)
- Migration status for xutils-dev/armel (1:7.7+7 to 1:7.7+7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xxhash/armel (0.8.3-2 to 0.8.3-2)
- Migration status for xxhash/armel (0.8.3-2 to 0.8.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- xz-utils/armel (5.8.1-1 to 5.8.1-1)
- Migration status for xz-utils/armel (5.8.1-1 to 5.8.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- yaml-cpp/armel (0.8.0+dfsg-7 to 0.8.0+dfsg-7)
- Migration status for yaml-cpp/armel (0.8.0+dfsg-7 to 0.8.0+dfsg-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- yara-python/armel (4.5.4-1 to 4.5.4-1)
- Migration status for yara-python/armel (4.5.4-1 to 4.5.4-1): Will attempt migration (Any information below is purely informational)
- yara/armel (4.5.4-1 to 4.5.4-1)
- Migration status for yara/armel (4.5.4-1 to 4.5.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- yarl/armel (1.19.0-1 to 1.19.0-1)
- Migration status for yarl/armel (1.19.0-1 to 1.19.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- yder/armel (1.4.20-1.1 to 1.4.20-1.1)
- Migration status for yder/armel (1.4.20-1.1 to 1.4.20-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- yojson/armel (2.2.2-1 to 2.2.2-1)
- Migration status for yojson/armel (2.2.2-1 to 2.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- z3/armel (4.13.3-1 to 4.13.3-1)
- Migration status for z3/armel (4.13.3-1 to 4.13.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- zathura-pdf-poppler/armel (0.3.3-1 to 0.3.3-1)
- Migration status for zathura-pdf-poppler/armel (0.3.3-1 to 0.3.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- zathura/armel (0.5.12-3 to 0.5.12-3)
- Migration status for zathura/armel (0.5.12-3 to 0.5.12-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- zeitgeist/armel (1.0.4-5 to 1.0.4-5)
- Migration status for zeitgeist/armel (1.0.4-5 to 1.0.4-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- zenity/armel (4.1.99-1 to 4.1.99-1)
- Migration status for zenity/armel (4.1.99-1 to 4.1.99-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- zephyr/armel (3.1.2-1.1 to 3.1.2-1.1)
- Migration status for zephyr/armel (3.1.2-1.1 to 3.1.2-1.1): Will attempt migration (Any information below is purely informational)
- zerofree/armel (1.1.1-1 to 1.1.1-1)
- Migration status for zerofree/armel (1.1.1-1 to 1.1.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- zip/armel (3.0-15 to 3.0-15)
- Migration status for zip/armel (3.0-15 to 3.0-15): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- zlib/armel (1:1.3.dfsg+really1.3.1-1 to 1:1.3.dfsg+really1.3.1-1)
- Migration status for zlib/armel (1:1.3.dfsg+really1.3.1-1 to 1:1.3.dfsg+really1.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- zope.interface/armel (7.2-1 to 7.2-1)
- Migration status for zope.interface/armel (7.2-1 to 7.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- zsh/armel (5.9-8 to 5.9-8)
- Migration status for zsh/armel (5.9-8 to 5.9-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- android-platform-art (14.0.0+r15-4 to 14.0.0+r15-5)
- Migration status for android-platform-art (14.0.0+r15-4 to 14.0.0+r15-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- android-platform-external-boringssl (14.0.0+r45-2 to 14.0.0+r45-3)
- Migration status for android-platform-external-boringssl (14.0.0+r45-2 to 14.0.0+r45-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for android-platform-external-boringssl/14.0.0+r45-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- android-platform-frameworks-base (1:14~beta1-3 to 1:14~beta1-4)
- Migration status for android-platform-frameworks-base (1:14~beta1-3 to 1:14~beta1-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for android-platform-frameworks-base/1:14~beta1-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- asf-search (10.0.1-1 to 10.0.2-1)
- Migration status for asf-search (10.0.1-1 to 10.0.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for asf-search/10.0.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- asunder (3.0.1+ds-1 to 3.0.1+ds-2)
- Migration status for asunder (3.0.1+ds-1 to 3.0.1+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autodep8 (0.29 to 0.30)
- Migration status for autodep8 (0.29 to 0.30): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for autodep8/0.30: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- axisregistry (0.3.5-2 to 0.3.5-3)
- Migration status for axisregistry (0.3.5-2 to 0.3.5-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- binutils (2.45-4 to 2.45-5)
- Migration status for binutils (2.45-4 to 2.45-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for binutils/2.45-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- blkreplay (1.0-3.1 to 1.0-4)
- Migration status for blkreplay (1.0-3.1 to 1.0-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- bootcd (6.8.2 to 6.9)
- Migration status for bootcd (6.8.2 to 6.9): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- buildtorrent (0.9.1-1 to 0.9.1-2)
- Migration status for buildtorrent (0.9.1-1 to 0.9.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- capirca (2.0.9-0.1 to 2.0.9-0.2)
- Migration status for capirca (2.0.9-0.1 to 2.0.9-0.2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- cd-discid (1.4-2 to 1.4-3)
- Migration status for cd-discid (1.4-2 to 1.4-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- cif-tools (1.0.12-4 to 1.0.12-5)
- Migration status for cif-tools (1.0.12-4 to 1.0.12-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for cif-tools: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- cpu-x (5.3.1-0.3 to 5.4.0-0.1)
- Migration status for cpu-x (5.3.1-0.3 to 5.4.0-0.1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- cyme (2.2.4+dfsg-2 to 2.2.4+dfsg-3)
- Migration status for cyme (2.2.4+dfsg-2 to 2.2.4+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- darkstat (3.0.721-2 to 3.0.721-3)
- Migration status for darkstat (3.0.721-2 to 3.0.721-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ddcui (0.6.0-1 to 0.6.0-2)
- Migration status for ddcui (0.6.0-1 to 0.6.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ddcutil (2.2.1-1 to 2.2.1-2)
- Migration status for ddcutil (2.2.1-1 to 2.2.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- dials (- to 3.25.0+dfsg3-2)
- Migration status for dials (- to 3.25.0+dfsg3-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for dials/3.25.0+dfsg3-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- dns2tcp (0.5.2-3 to 0.5.2-4)
- Migration status for dns2tcp (0.5.2-3 to 0.5.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for dns2tcp/0.5.2-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- dssp (4.4.10-1 to 4.5.5-1)
- Migration status for dssp (4.4.10-1 to 4.5.5-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- edu-sync (0.3.0-1 to 0.3.2-3)
- Migration status for edu-sync (0.3.0-1 to 0.3.2-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- eodag (- to 3.3.1+ds-1)
- Migration status for eodag (- to 3.3.1+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for eodag/3.3.1+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- evdi (1.14.8+dfsg-1 to 1.14.10+dfsg-1)
- Migration status for evdi (1.14.8+dfsg-1 to 1.14.10+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- fabric (2.6.0-5 to 2.6.0-6)
- Migration status for fabric (2.6.0-5 to 2.6.0-6): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Depends: fabric sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- firewalk (5.0-5 to 5.0-6)
- Migration status for firewalk (5.0-5 to 5.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- fpylll (0.6.3-2 to 0.6.4-1)
- Migration status for fpylll (0.6.3-2 to 0.6.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for fpylll: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- gammapy (1.3-2 to 2.0-1)
- Migration status for gammapy (1.3-2 to 2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gammapy/2.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- gap-anupq (3.3.1-1 to 3.3.2-1)
- Migration status for gap-anupq (3.3.1-1 to 3.3.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gap-anupq: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- gap-float (1.0.7+ds-2 to 1.0.9+ds-1)
- Migration status for gap-float (1.0.7+ds-2 to 1.0.9+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gap-float/1.0.9+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- gap-io (4.9.1+ds-1 to 4.9.3+ds-1)
- Migration status for gap-io (4.9.1+ds-1 to 4.9.3+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gap-io/4.9.3+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- gdigi (0.4.0+git20200615+1c2c89f-3 to 0.4.0+git20200615+1c2c89f-4)
- Migration status for gdigi (0.4.0+git20200615+1c2c89f-3 to 0.4.0+git20200615+1c2c89f-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- git-delta (0.18.2-4 to 0.18.2-5)
- Migration status for git-delta (0.18.2-4 to 0.18.2-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- gxr (0.15.1-4.2 to 0.15.1-4.3)
- Migration status for gxr (0.15.1-4.2 to 0.15.1-4.3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- harp (1.25-2 to 1.26-1)
- Migration status for harp (1.25-2 to 1.26-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- helvum (0.5.1+20240829-4 to 0.5.1+20240829-5)
- Migration status for helvum (0.5.1+20240829-4 to 0.5.1+20240829-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- jplephem (2.23+ds-1 to 2.23+ds-2)
- Migration status for jplephem (2.23+ds-1 to 2.23+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for jplephem/2.23+ds-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- jsonpath-ng (1.7.0-1 to 1.7.0-2)
- Migration status for jsonpath-ng (1.7.0-1 to 1.7.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for jsonpath-ng/1.7.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- kamailio (6.0.2-2 to 6.0.2-3)
- Migration status for kamailio (6.0.2-2 to 6.0.2-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Depends: kamailio wolfssl
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- keyman (18.0.238-1 to 18.0.240-1)
- Migration status for keyman (18.0.238-1 to 18.0.240-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for keyman/18.0.240-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnotify (0.8.6-1 to 0.8.6-2)
- Migration status for libnotify (0.8.6-1 to 0.8.6-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- lomiri (0.5.0-5 to 0.5.0-6)
- Migration status for lomiri (0.5.0-5 to 0.5.0-6): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ltris (2.0.3-1 to 2.0.4-1)
- Migration status for ltris (2.0.3-1 to 2.0.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- lua-lpty (1.0.1-2 to 1.0.1-3)
- Migration status for lua-lpty (1.0.1-2 to 1.0.1-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- mangohud (0.8.1-2 to 0.8.1-3)
- Migration status for mangohud (0.8.1-2 to 0.8.1-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- metview (5.23.1-1 to 5.25.1-2)
- Migration status for metview (5.23.1-1 to 5.25.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Depends: metview atlas-ecmwf
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- mp3blaster (1:3.2.6-3 to 1:3.2.6-4)
- Migration status for mp3blaster (1:3.2.6-3 to 1:3.2.6-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- mpl-animators (1.2.1-1 to 1.2.4-1)
- Migration status for mpl-animators (1.2.1-1 to 1.2.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for mpl-animators/1.2.4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- nestopia (1.53.1+dfsg-2 to 1.53.2+dfsg-1)
- Migration status for nestopia (1.53.1+dfsg-2 to 1.53.2+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- nvidia-graphics-drivers (550.163.01-2 to 550.163.01-3)
- Migration status for nvidia-graphics-drivers (550.163.01-2 to 550.163.01-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- objfw (1.3-1 to 1.4.1-1)
- Migration status for objfw (1.3-1 to 1.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- odr-dabmux (5.1.0+ds-1 to 5.3.0-1)
- Migration status for odr-dabmux (5.1.0+ds-1 to 5.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ostree (2025.4-1 to 2025.5-1)
- Migration status for ostree (2025.4-1 to 2025.5-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ostree/2025.5-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- php-guzzlehttp-psr7 (2.7.1-1 to 2.8.0-1)
- Migration status for php-guzzlehttp-psr7 (2.7.1-1 to 2.8.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- php-hamcrest (2.1.1-1 to 2.1.1-2)
- Migration status for php-hamcrest (2.1.1-1 to 2.1.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for php-hamcrest/2.1.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- php-phpstan-phpdoc-parser (2.2.0-2 to 2.3.0-1)
- Migration status for php-phpstan-phpdoc-parser (2.2.0-2 to 2.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- php-proxy-manager (2.11.1+1.0.18-3 to 2.11.1+1.0.18-4)
- Migration status for php-proxy-manager (2.11.1+1.0.18-3 to 2.11.1+1.0.18-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for php-proxy-manager/2.11.1+1.0.18-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- php-slim-psr7 (1.7.0-3 to 1.7.1-1)
- Migration status for php-slim-psr7 (1.7.0-3 to 1.7.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for php-slim-psr7/1.7.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pivy (0.6.10-2 to 0.6.10-3)
- Migration status for pivy (0.6.10-2 to 0.6.10-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- pkg-rocm-tools (0.8.2 to 0.9.0)
- Migration status for pkg-rocm-tools (0.8.2 to 0.9.0): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ptpython (3.0.30-4 to 3.0.31-1)
- Migration status for ptpython (3.0.30-4 to 3.0.31-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- pycoast (1.7.1+dfsg-1 to 1.7.1+dfsg-2)
- Migration status for pycoast (1.7.1+dfsg-1 to 1.7.1+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Depends: pycoast sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pycoast/1.7.1+dfsg-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pytest-unordered (0.7.0-1 to 0.7.0-2)
- Migration status for pytest-unordered (0.7.0-1 to 0.7.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pytest-unordered/0.7.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-django-navtag (3.0-3 to 3.3.1-1)
- Migration status for python-django-navtag (3.0-3 to 3.3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-django-navtag/3.3.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-django-otp (1.5.4-1 to 1.6.1-1)
- Migration status for python-django-otp (1.5.4-1 to 1.6.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-django-otp/1.6.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-kajiki (0.9.2-2 to 1.0.2-1)
- Migration status for python-kajiki (0.9.2-2 to 1.0.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Depends: python-kajiki sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-kajiki: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- python-msrest (0.6.21-5 to 0.6.21-7)
- Migration status for python-msrest (0.6.21-5 to 0.6.21-7): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-msrest/0.6.21-7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-pbs-installer (2025.08.18-1 to 2025.08.28-1)
- Migration status for python-pbs-installer (2025.08.18-1 to 2025.08.28-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-pbs-installer/2025.08.28-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-pebble (5.1.1-1 to 5.1.3-1)
- Migration status for python-pebble (5.1.1-1 to 5.1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- python-setuptools-rust (1.9.0+dfsg-4 to 1.12.0+dfsg-1)
- Migration status for python-setuptools-rust (1.9.0+dfsg-4 to 1.12.0+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-setuptools-rust/1.12.0+dfsg-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-typing-extensions (4.14.1-1 to 4.15.0-1)
- Migration status for python-typing-extensions (4.14.1-1 to 4.15.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- rakarrack (0.6.1-9 to 0.6.1-10)
- Migration status for rakarrack (0.6.1-9 to 0.6.1-10): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- readline (8.2-6 to 8.3-2)
- Migration status for readline (8.2-6 to 8.3-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- remotezip (0.12.3-1 to 0.12.3-2)
- Migration status for remotezip (0.12.3-1 to 0.12.3-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for remotezip/0.12.3-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- ros-common-msgs (1.13.1-3 to 1.13.2-1)
- Migration status for ros-common-msgs (1.13.1-3 to 1.13.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ruby-asciidoctor-pdf (2.3.4-3 to 2.3.19-2)
- Migration status for ruby-asciidoctor-pdf (2.3.4-3 to 2.3.19-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- rust-foldhash (0.1.4-1 to 0.1.5-1)
- Migration status for rust-foldhash (0.1.4-1 to 0.1.5-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-foldhash/0.1.5-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-io-uring (0.7.8-1 to 0.7.10-1)
- Migration status for rust-io-uring (0.7.8-1 to 0.7.10-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- rust-wayland-sys (0.31.6-2 to 0.31.7-1)
- Migration status for rust-wayland-sys (0.31.6-2 to 0.31.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-wayland-sys/0.31.7-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-x11 (2.19.1-1 to 2.21.0-1)
- Migration status for rust-x11 (2.19.1-1 to 2.21.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-x11/2.21.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-yaxpeax-arm (0.3.0-1 to 0.3.1-1)
- Migration status for rust-yaxpeax-arm (0.3.0-1 to 0.3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-yaxpeax-arm/0.3.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- sctk (- to 2.4.12+dfsg-1.1)
- Migration status for sctk (- to 2.4.12+dfsg-1.1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- snowdrop (0.02b-15 to 0.02b-16)
- Migration status for snowdrop (0.02b-15 to 0.02b-16): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for snowdrop/0.02b-16: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- sphinx-sqlalchemy (- to 0.3.0-1)
- Migration status for sphinx-sqlalchemy (- to 0.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- sqlglot (27.8.0-1 to 27.9.0-1)
- Migration status for sqlglot (27.8.0-1 to 27.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- sscg (3.0.2-2 to 3.0.8-1)
- Migration status for sscg (3.0.2-2 to 3.0.8-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for sscg: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- stac-check (1.11.1-1 to 1.11.1-2)
- Migration status for stac-check (1.11.1-1 to 1.11.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Depends: stac-check sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for stac-check/1.11.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- stac-validator (3.10.1-1 to 3.10.1-2)
- Migration status for stac-validator (3.10.1-1 to 3.10.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for stac-validator/3.10.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- stravalib (2.3-1 to 2.4-1)
- Migration status for stravalib (2.3-1 to 2.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for stravalib/2.4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- subprocess-tee (0.4.2-1 to 0.4.2-1.1)
- Migration status for subprocess-tee (0.4.2-1 to 0.4.2-1.1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- tdom (0.9.6-1 to 0.9.6-2)
- Migration status for tdom (0.9.6-1 to 0.9.6-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for tdom: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- telepathy-mission-control-5 (1:5.16.5-2.2 to 1:5.16.6-2)
- Migration status for telepathy-mission-control-5 (1:5.16.5-2.2 to 1:5.16.6-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- toot (0.50.0-1 to 0.50.1-1)
- Migration status for toot (0.50.0-1 to 0.50.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- trollimage (1.26.0-1 to 1.26.0-2)
- Migration status for trollimage (1.26.0-1 to 1.26.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for trollimage/1.26.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- user-session-migration (0.4.3+nmu1 to 0.5.0)
- Migration status for user-session-migration (0.4.3+nmu1 to 0.5.0): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- wolfssl (5.7.2-0.4 to 5.8.2-1.2)
- Migration status for wolfssl (5.7.2-0.4 to 5.8.2-1.2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for wolfssl/5.8.2-1.2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- xraylarch (0.9.81+ds1-2 to 0.9.81+ds1-3)
- Migration status for xraylarch (0.9.81+ds1-2 to 0.9.81+ds1-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Depends: xraylarch sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for xraylarch/0.9.81+ds1-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- yelp (42.3-2 to 42.3-3)
- Migration status for yelp (42.3-2 to 42.3-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- yt-dlp (2025.08.11-1 to 2025.08.27-1)
- Migration status for yt-dlp (2025.08.11-1 to 2025.08.27-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for yt-dlp/2025.08.27-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- zabbix-cli (3.5.1-1 to 3.5.2-2)
- Migration status for zabbix-cli (3.5.1-1 to 3.5.2-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- a2ps (1:4.15.6-1 to 1:4.15.7-1)
- Migration status for a2ps (1:4.15.6-1 to 1:4.15.7-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- abcmidi (20250216+ds-1 to 20250627+ds-1)
- Migration status for abcmidi (20250216+ds-1 to 20250627+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for abcmidi/20250627+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- acpica-unix (20250404-1 to 20250807-1)
- Migration status for acpica-unix (20250404-1 to 20250807-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- aiopurpleair (2023.12.0-2 to 2025.08.1-1)
- Migration status for aiopurpleair (2023.12.0-2 to 2025.08.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for aiopurpleair/2025.08.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- aiosignal (1.3.2-1 to 1.4.0-1)
- Migration status for aiosignal (1.3.2-1 to 1.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for aiosignal/1.4.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- altos (1.9.21-1 to 1.9.22-1)
- Migration status for altos (1.9.21-1 to 1.9.22-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- amarok (3.2.2-1 to 3.3.1-1)
- Migration status for amarok (3.2.2-1 to 3.3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: amarok libmygpo-qt
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ansible-core (2.19.0-1 to 2.19.1-1)
- Migration status for ansible-core (2.19.0-1 to 2.19.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ansible-core/2.19.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- appstream (1.0.6-1 to 1.0.6-2)
- Migration status for appstream (1.0.6-1 to 1.0.6-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for appstream/1.0.6-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- astropy-sphinx-theme (2.0-1 to 2.0-2)
- Migration status for astropy-sphinx-theme (2.0-1 to 2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- atlas-ecmwf (0.42.0-1 to 0.43.1-1)
- Migration status for atlas-ecmwf (0.42.0-1 to 0.43.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- atop (2.11.1-3 to 2.12.0-1)
- Migration status for atop (2.11.1-3 to 2.12.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- awstats (7.9-1 to 8.0-2)
- Migration status for awstats (7.9-1 to 8.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- billiard (4.2.1-2 to 4.2.1-3)
- Migration status for billiard (4.2.1-2 to 4.2.1-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for billiard/4.2.1-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- bleak-retry-connector (4.0.0-1 to 4.4.3-1)
- Migration status for bleak-retry-connector (4.0.0-1 to 4.4.3-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for bleak-retry-connector/4.4.3-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- boinctui (2.7.1-1 to 2.7.2-1)
- Migration status for boinctui (2.7.1-1 to 2.7.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- bootstrap-html (5.3.7+dfsg-3 to 5.3.8+dfsg-1)
- Migration status for bootstrap-html (5.3.7+dfsg-3 to 5.3.8+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- brltty (6.7-3.1 to 6.8-2)
- Migration status for brltty (6.7-3.1 to 6.8-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- butteraugli (0~20170116-3 to 0~20190319-1)
- Migration status for butteraugli (0~20170116-3 to 0~20190319-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ccbuild (2.0.9-1 to 2.0.9-2)
- Migration status for ccbuild (2.0.9-1 to 2.0.9-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- checkit-tiff (1.6.0-1 to 1.6.0-2)
- Migration status for checkit-tiff (1.6.0-1 to 1.6.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- chordpro (6.080.0+ds-1 to 6.080.1+ds-1)
- Migration status for chordpro (6.080.0+ds-1 to 6.080.1+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for chordpro/6.080.1+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- chrony (4.7-3 to 4.8-1)
- Migration status for chrony (4.7-3 to 4.8-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 22 days old
- Additional info:
- cluster-glue (1.0.12-24 to 1.0.12-25)
- Migration status for cluster-glue (1.0.12-24 to 1.0.12-25): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for cluster-glue/1.0.12-25: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- cmor (3.9.0-1 to 3.11.0-2)
- Migration status for cmor (3.9.0-1 to 3.11.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- composer (2.8.11-1 to 2.8.11-2)
- Migration status for composer (2.8.11-1 to 2.8.11-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for composer/2.8.11-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- corsix-th (0.69.0-1 to 0.69.1-1)
- Migration status for corsix-th (0.69.0-1 to 0.69.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- d52 (3.4.1-1.3 to 3.4.1-1.4)
- Migration status for d52 (3.4.1-1.3 to 3.4.1-1.4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- damo (2.8.8-1 to 2.9.4-1)
- Migration status for damo (2.8.8-1 to 2.9.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for damo/2.9.4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- debian-codesearch-cli (1.0.0+nmu2 to 1.0.0+nmu3)
- Migration status for debian-codesearch-cli (1.0.0+nmu2 to 1.0.0+nmu3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- debian-reference (2.127 to 2.128)
- Migration status for debian-reference (2.127 to 2.128): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for debian-reference/2.128: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- debputy (0.1.74.1 to 0.1.75)
- Migration status for debputy (0.1.74.1 to 0.1.75): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for debputy/0.1.75: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- dialect (2.6.0+~2.6.0-3 to 2.6.0+~2.6.0-4)
- Migration status for dialect (2.6.0+~2.6.0-3 to 2.6.0+~2.6.0-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- distlib (0.3.9-1 to 0.4.0-1)
- Migration status for distlib (0.3.9-1 to 0.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for distlib/0.4.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- doublecmd (1.1.22-1 to 1.1.28-1)
- Migration status for doublecmd (1.1.22-1 to 1.1.28-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- doublecmd-help (1.1.21-1 to 1.1.26-1)
- Migration status for doublecmd-help (1.1.21-1 to 1.1.26-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- drbl (5.5.9-1 to 5.5.10-1)
- Migration status for drbl (5.5.9-1 to 5.5.10-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- eccodes (2.43.0-1 to 2.43.0-3)
- Migration status for eccodes (2.43.0-1 to 2.43.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- emacs (1:30.1+1-8 to 1:30.1+1-9)
- Migration status for emacs (1:30.1+1-8 to 1:30.1+1-9): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- enrich (1.3.0-2 to 1.3.0-2.1)
- Migration status for enrich (1.3.0-2 to 1.3.0-2.1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- esorex (- to 3.13.7+ds-2)
- Migration status for esorex (- to 3.13.7+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for esorex/3.13.7+ds-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- exploitdb (20250819-0kali1 to 20250827-0kali1)
- Migration status for exploitdb (20250819-0kali1 to 20250827-0kali1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- ezurio-qcacld-2.0-dkms (0.0~git20240408.aa96a9f+dfsg-5 to 0.0~git20240408.aa96a9f+dfsg-7)
- Migration status for ezurio-qcacld-2.0-dkms (0.0~git20240408.aa96a9f+dfsg-5 to 0.0~git20240408.aa96a9f+dfsg-7): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- feh (3.10.3-1 to 3.11.1-1)
- Migration status for feh (3.10.3-1 to 3.11.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for feh/3.11.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- firejail (0.9.74-1 to 0.9.76-1)
- Migration status for firejail (0.9.74-1 to 0.9.76-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- fluster (1.0.1+git20231211.d9106f5-1 to 1.0.1+really0.4.1-1)
- Migration status for fluster (1.0.1+git20231211.d9106f5-1 to 1.0.1+really0.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- fontparts (0.12.4-1 to 0.13.3-1)
- Migration status for fontparts (0.12.4-1 to 0.13.3-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- fonts-uniol (1.0.1-2 to 2.001-2)
- Migration status for fonts-uniol (1.0.1-2 to 2.001-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- foomatic-db (20230202-1 to 20250819-1)
- Migration status for foomatic-db (20230202-1 to 20250819-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- free42-nologo (3.2.8+ds-1 to 3.3.8+ds-1)
- Migration status for free42-nologo (3.2.8+ds-1 to 3.3.8+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- freeradius (3.2.7+dfsg-2 to 3.2.8+dfsg-1)
- Migration status for freeradius (3.2.7+dfsg-2 to 3.2.8+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for freeradius/3.2.8+dfsg-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- freespace2 (24.0.2+repack-1 to 24.2.0+repack-1)
- Migration status for freespace2 (24.0.2+repack-1 to 24.2.0+repack-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- fwupd (2.0.13-2 to 2.0.14-1)
- Migration status for fwupd (2.0.13-2 to 2.0.14-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for fwupd/2.0.14-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- gamehub (- to 0.16.3-2-master+ds-1.1)
- Migration status for gamehub (- to 0.16.3-2-master+ds-1.1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- gd4o (1.0~alpha5.git20220521.bb52fb2-2 to 1.1-1)
- Migration status for gd4o (1.0~alpha5.git20220521.bb52fb2-2 to 1.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- gdb (16.3-1 to 16.3-4)
- Migration status for gdb (16.3-1 to 16.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- geany-plugins (2.1+dfsg-1 to 2.1+dfsg-2)
- Migration status for geany-plugins (2.1+dfsg-1 to 2.1+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- gemmi (0.6.5+ds-3 to 0.7.1+ds-1)
- Migration status for gemmi (0.6.5+ds-3 to 0.7.1+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gemmi/0.7.1+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- genwqe-user (4.0.20-2 to 4.0.20-3)
- Migration status for genwqe-user (4.0.20-2 to 4.0.20-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- gftools (0.9.68+dfsg-2 to 0.9.85+dfsg-1)
- Migration status for gftools (0.9.68+dfsg-2 to 0.9.85+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ghostscript (10.05.1~dfsg-1 to 10.05.1~dfsg-2)
- Migration status for ghostscript (10.05.1~dfsg-1 to 10.05.1~dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing ghostscript/10.05.1~dfsg-1/armel from kali-rolling makes cups/2.4.10-3/armel uninstallable
- removing ghostscript/10.05.1~dfsg-1/armel from kali-rolling makes cups-filters/1.28.17-6/armel uninstallable
- Too young, only 1 of 2 days old
- Implicit dependency: ghostscript tgif
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ghostscript/10.05.1~dfsg-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- ginga (5.3.0-1 to 5.4.0-1)
- Migration status for ginga (5.3.0-1 to 5.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ginga/5.4.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- git-repo-updater (0.5.1-5 to 0.5.2-1)
- Migration status for git-repo-updater (0.5.1-5 to 0.5.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for git-repo-updater/0.5.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- gkrellm-reminder (2.0.0-4 to 2.0.0-5)
- Migration status for gkrellm-reminder (2.0.0-4 to 2.0.0-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- gkrellm-volume (2.1.13-2 to 2.1.13-3)
- Migration status for gkrellm-volume (2.1.13-2 to 2.1.13-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- golang-fortio-safecast (1.0.0-2 to 1.2.0-1)
- Migration status for golang-fortio-safecast (1.0.0-2 to 1.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-fortio-safecast/1.2.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-agnivade-levenshtein (1.2.0-1 to 1.2.1-1)
- Migration status for golang-github-agnivade-levenshtein (1.2.0-1 to 1.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-github-agnivade-levenshtein/1.2.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-gabriel-vasile-mimetype (1.4.8+dfsg1-1 to 1.4.10+dfsg1-1)
- Migration status for golang-github-gabriel-vasile-mimetype (1.4.8+dfsg1-1 to 1.4.10+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-github-gabriel-vasile-mimetype/1.4.10+dfsg1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-gogits-go-gogs-client (0.0~git20160830.0.d8aff57-2 to 0.0~git20210131.1d7215c-1)
- Migration status for golang-github-gogits-go-gogs-client (0.0~git20160830.0.d8aff57-2 to 0.0~git20210131.1d7215c-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- golang-github-gonvenience-bunt (1.3.4-3 to 1.4.2-1)
- Migration status for golang-github-gonvenience-bunt (1.3.4-3 to 1.4.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-github-gonvenience-bunt/1.4.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-gopkg-testfixtures.v2 (2.2.0-2 to 2.2.0-3)
- Migration status for golang-gopkg-testfixtures.v2 (2.2.0-2 to 2.2.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- govee-local-api (2.1.0-1 to 2.2.0-1)
- Migration status for govee-local-api (2.1.0-1 to 2.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for govee-local-api/2.2.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- grml2usb (0.20.6 to 0.20.9)
- Migration status for grml2usb (0.20.6 to 0.20.9): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- groonga (15.1.4+dfsg-1 to 15.1.5+dfsg-1)
- Migration status for groonga (15.1.4+dfsg-1 to 15.1.5+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for groonga/15.1.5+dfsg-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- gtk+3.0 (3.24.50-1 to 3.24.50-2)
- Migration status for gtk+3.0 (3.24.50-1 to 3.24.50-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gtk+3.0/3.24.50-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- habluetooth (5.1.0-1 to 5.2.0-1)
- Migration status for habluetooth (5.1.0-1 to 5.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: habluetooth sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for habluetooth/5.2.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- hamlib (4.6.2-1 to 4.6.4-3)
- Migration status for hamlib (4.6.2-1 to 4.6.4-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for hamlib/4.6.4-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- haskell-futhark (0.25.27-1 to 0.25.32-2)
- Migration status for haskell-futhark (0.25.27-1 to 0.25.32-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for haskell-futhark/0.25.32-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- haskell-futhark-data (1.1.1.0-1 to 1.1.2.0-1)
- Migration status for haskell-futhark-data (1.1.1.0-1 to 1.1.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- hatch-sphinx (- to 0.0.4-1)
- Migration status for hatch-sphinx (- to 0.0.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for hatch-sphinx/0.0.4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- iaqualink (0.5.3-1 to 0.6.0-1)
- Migration status for iaqualink (0.5.3-1 to 0.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for iaqualink/0.6.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- ibus-chewing (2.1.5-1 to 2.1.6-1)
- Migration status for ibus-chewing (2.1.5-1 to 2.1.6-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- imagemagick (8:7.1.1.43+dfsg1-1 to 8:7.1.1.43+dfsg1-1+deb13u1)
- Migration status for imagemagick (8:7.1.1.43+dfsg1-1 to 8:7.1.1.43+dfsg1-1+deb13u1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for imagemagick/8:7.1.1.43+dfsg1-1+deb13u1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- imediff (3.4.0-1 to 3.4.1-1)
- Migration status for imediff (3.4.0-1 to 3.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for imediff/3.4.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- intel-gpu-tools (2.0-1 to 2.1-1)
- Migration status for intel-gpu-tools (2.0-1 to 2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ipmitool (1.8.19-9 to 1.8.19-10)
- Migration status for ipmitool (1.8.19-9 to 1.8.19-10): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- isc-kea (2.6.3-1 to 2.6.4-1)
- Migration status for isc-kea (2.6.3-1 to 2.6.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for isc-kea/2.6.4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- isodate (0.7.0-1 to 0.7.2-1)
- Migration status for isodate (0.7.0-1 to 0.7.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for isodate/0.7.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- joserfc (1.2.2-1 to 1.3.1-1)
- Migration status for joserfc (1.2.2-1 to 1.3.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for joserfc/1.3.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- jupp (3.1.41-1 to 3.1.41-2)
- Migration status for jupp (3.1.41-1 to 3.1.41-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- kali-defaults (2025.3.2 to 2025.3.3)
- Migration status for kali-defaults (2025.3.2 to 2025.3.3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for kali-defaults/2025.3.3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- kali-undercover (2025.2.0 to 2025.3.0)
- Migration status for kali-undercover (2025.2.0 to 2025.3.0): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- kasts (25.04.3-1 to 25.08.0-1)
- Migration status for kasts (25.04.3-1 to 25.08.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- kbuild (1:0.1.9998svn3614+dfsg-2 to 1:0.1.9998svn3686+dfsg-2)
- Migration status for kbuild (1:0.1.9998svn3614+dfsg-2 to 1:0.1.9998svn3686+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- kdsoap (2.2.0+dfsg-3 to 2.2.0+dfsg-4)
- Migration status for kdsoap (2.2.0+dfsg-3 to 2.2.0+dfsg-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- kgb-bot (1.61-1 to 1.62-2)
- Migration status for kgb-bot (1.61-1 to 1.62-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for kgb-bot/1.62-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- klepto (0.2.6-2 to 0.2.7-1)
- Migration status for klepto (0.2.6-2 to 0.2.7-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: klepto sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for klepto/0.2.7-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- klutshnik (- to 0.2.1-1)
- Migration status for klutshnik (- to 0.2.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- kmail-account-wizard (4:24.12.3-1 to 4:24.12.3-2)
- Migration status for kmail-account-wizard (4:24.12.3-1 to 4:24.12.3-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- kqtquickcharts (4:25.04.0-1 to 4:25.08.0-1)
- Migration status for kqtquickcharts (4:25.04.0-1 to 4:25.08.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ktouch (4:25.04.0-2 to 4:25.08.0-1)
- Migration status for ktouch (4:25.04.0-2 to 4:25.08.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- kunifiedpush (25.04.0-2 to 25.08.0-1)
- Migration status for kunifiedpush (25.04.0-2 to 25.08.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- labplot (2.12.0-1 to 2.12.1-1)
- Migration status for labplot (2.12.0-1 to 2.12.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- lbreakouthd (1.1.9-1 to 1.1.11-1)
- Migration status for lbreakouthd (1.1.9-1 to 1.1.11-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- lebiniou (3.66.0-4 to 3.67.0-1)
- Migration status for lebiniou (3.66.0-4 to 3.67.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for lebiniou/3.67.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- lexicon (3.17.0-1 to 3.21.1-1)
- Migration status for lexicon (3.17.0-1 to 3.21.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- libblkio (1.5.0-2 to 1.5.0-3)
- Migration status for libblkio (1.5.0-2 to 1.5.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libcgi-simple-perl (1.281-1 to 1.282-1)
- Migration status for libcgi-simple-perl (1.281-1 to 1.282-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libcgi-simple-perl/1.282-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libclass-pluggable-perl (0.022-2.3 to 0.022-2.4)
- Migration status for libclass-pluggable-perl (0.022-2.3 to 0.022-2.4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libcoap3 (4.3.4-1.1 to 4.3.5-1)
- Migration status for libcoap3 (4.3.4-1.1 to 4.3.5-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libdancer2-session-cookie-perl (0.009-2 to 0.009-3)
- Migration status for libdancer2-session-cookie-perl (0.009-2 to 0.009-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libdancer2-session-cookie-perl/0.009-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libgeo-postcode-perl (0.17+dfsg1-1.1 to 0.17+dfsg1-1.2)
- Migration status for libgeo-postcode-perl (0.17+dfsg1-1.1 to 0.17+dfsg1-1.2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libhdf4 (4.3.0-1 to 4.3.1-1)
- Migration status for libhdf4 (4.3.0-1 to 4.3.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing libhdf4-dev/4.3.0-1+b1/armel from kali-rolling makes libgdal-dev/3.11.3+dfsg-1/armel uninstallable
- Too young, only 1 of 2 days old
- Implicit dependency: libhdf4 ncl
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libhdr-histogram (- to 0.11.8-4)
- Migration status for libhdr-histogram (- to 0.11.8-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libhdr-histogram/0.11.8-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libimagequant (2.18.0-1 to 4.4.0-3)
- Migration status for libimagequant (2.18.0-1 to 4.4.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing libimagequant-dev/2.18.0-1+b2/armel from kali-rolling makes libgd-dev/2.3.3-13/armel uninstallable
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- liblog-dispatch-filerotate-perl (1.19-1.3 to 1.19-1.4)
- Migration status for liblog-dispatch-filerotate-perl (1.19-1.3 to 1.19-1.4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libmail-field-received-perl (0.26-1.1 to 0.26-1.2)
- Migration status for libmail-field-received-perl (0.26-1.1 to 0.26-1.2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libmygpo-qt (1.1.0-4.1 to 1.2.0-2)
- Migration status for libmygpo-qt (1.1.0-4.1 to 1.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Implicit dependency: libmygpo-qt amarok
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libnftnl (1.2.9-1 to 1.3.0-1)
- Migration status for libnftnl (1.2.9-1 to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libnginx-mod-http-lua (1:0.10.28-2 to 1:0.10.28-3)
- Migration status for libnginx-mod-http-lua (1:0.10.28-2 to 1:0.10.28-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: libnginx-mod-http-lua nginx (not considered)
- Implicit dependency: libnginx-mod-http-lua nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-lua/1:0.10.28-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libpff (20180714-3.1 to 20231205-1)
- Migration status for libpff (20180714-3.1 to 20231205-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libpff/20231205-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- librdkafka (2.8.0-1 to 2.11.1-2)
- Migration status for librdkafka (2.8.0-1 to 2.11.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for librdkafka/2.11.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libsendmail-pmilter-perl (1.00-1.3 to 1.27-1)
- Migration status for libsendmail-pmilter-perl (1.00-1.3 to 1.27-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- libsfdo (0.1.3-1 to 0.1.4-1)
- Migration status for libsfdo (0.1.3-1 to 0.1.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libsoup3 (3.6.5-3 to 3.6.5-4)
- Migration status for libsoup3 (3.6.5-3 to 3.6.5-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libsoup3/3.6.5-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libuv1 (1.50.0-2 to 1.51.0-2)
- Migration status for libuv1 (1.50.0-2 to 1.51.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- link-grammar (5.12.5~dfsg-1 to 5.12.6+dfsg-1)
- Migration status for link-grammar (5.12.5~dfsg-1 to 5.12.6+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for link-grammar/5.12.6+dfsg-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- lintian (2.122.0 to 2.123.0)
- Migration status for lintian (2.122.0 to 2.123.0): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for lintian/2.123.0: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- lintian-brush (- to 0.162)
- Migration status for lintian-brush (- to 0.162): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for lintian-brush/0.162: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- logcheck (1.4.6 to 1.4.7)
- Migration status for logcheck (1.4.6 to 1.4.7): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for logcheck/1.4.7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- ltpanel (0.2-8 to 0.2-9)
- Migration status for ltpanel (0.2-8 to 0.2-9): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ltpanel/0.2-9: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- lua-md5 (1.2+git+1+8d87fee-2 to 1.3-1)
- Migration status for lua-md5 (1.2+git+1+8d87fee-2 to 1.3-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- lua-rings (1.3.0-4 to 1.3.0-5)
- Migration status for lua-rings (1.3.0-4 to 1.3.0-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- lua-soap (3.0+git91419a7-2 to 3.0+git91419a7-3)
- Migration status for lua-soap (3.0+git91419a7-2 to 3.0+git91419a7-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- lua-xmlrpc (1.2.1-8 to 1.2.2-1)
- Migration status for lua-xmlrpc (1.2.1-8 to 1.2.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- mayo (- to 0.9.0+ds-2)
- Migration status for mayo (- to 0.9.0+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- meson (1.7.0-1 to 1.9.0-1)
- Migration status for meson (1.7.0-1 to 1.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for meson/1.9.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- mfiutil (- to 1.0.15-rivoreo-r2~rc-20250214-e8c6289-1)
- Migration status for mfiutil (- to 1.0.15-rivoreo-r2~rc-20250214-e8c6289-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- mgetty (1.2.1-2 to 1.2.1-3)
- Migration status for mgetty (1.2.1-2 to 1.2.1-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- mgp (1.13a+upstream20090219-12 to 1.13a+upstream20090219-14)
- Migration status for mgp (1.13a+upstream20090219-12 to 1.13a+upstream20090219-14): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- miceamaze (4.2.2-2 to 4.2.2-3)
- Migration status for miceamaze (4.2.2-2 to 4.2.2-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- mini-buildd (2.4.2 to 2.4.4)
- Migration status for mini-buildd (2.4.2 to 2.4.4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- monit (1:5.35.2-1 to 1:5.35.2-3)
- Migration status for monit (1:5.35.2-1 to 1:5.35.2-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- mosquitto (2.0.22-2 to 2.0.22-3)
- Migration status for mosquitto (2.0.22-2 to 2.0.22-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for mosquitto/2.0.22-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- mtpaint (3.50.11-1 to 3.50.12-1)
- Migration status for mtpaint (3.50.11-1 to 3.50.12-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ncl (6.6.2.dfsg.1-10 to 6.6.2.dfsg.1-11)
- Migration status for ncl (6.6.2.dfsg.1-10 to 6.6.2.dfsg.1-11): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- netmiko (4.5.0-1 to 4.6.0-1)
- Migration status for netmiko (4.5.0-1 to 4.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- network-manager-openvpn (1.12.2-2 to 1.12.3-1)
- Migration status for network-manager-openvpn (1.12.2-2 to 1.12.3-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ng (1.5~beta1-13 to 1.5~beta1-14)
- Migration status for ng (1.5~beta1-13 to 1.5~beta1-14): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- node-debug (4.3.4+~cs4.1.7-1 to 4.4.1+~4.1.12-1)
- Migration status for node-debug (4.3.4+~cs4.1.7-1 to 4.4.1+~4.1.12-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for node-debug/4.4.1+~4.1.12-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- node-gyp (11.4.0+~5.0.0-1 to 11.4.0+~5.0.0-2)
- Migration status for node-gyp (11.4.0+~5.0.0-1 to 11.4.0+~5.0.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for node-gyp/11.4.0+~5.0.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- nvidia-open-gpu-kernel-modules (550.163.01-2 to 550.163.01-3)
- Migration status for nvidia-open-gpu-kernel-modules (550.163.01-2 to 550.163.01-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- ocaml-dssi (0.1.5-3 to 0.1.5-4)
- Migration status for ocaml-dssi (0.1.5-3 to 0.1.5-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-fdkaac (0.3.3~gitd3393eb-3 to 0.3.3-1)
- Migration status for ocaml-fdkaac (0.3.3~gitd3393eb-3 to 0.3.3-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-frei0r (0.1.2-3 to 0.1.2-4)
- Migration status for ocaml-frei0r (0.1.2-3 to 0.1.2-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-gstreamer (0.3.1-4 to 0.3.1-5)
- Migration status for ocaml-gstreamer (0.3.1-4 to 0.3.1-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-ladspa (0.2.2-3 to 0.2.2-4)
- Migration status for ocaml-ladspa (0.2.2-3 to 0.2.2-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Implicit dependency: ocaml-ladspa ocaml-dssi
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-lame (0.3.7-3 to 0.3.7-4)
- Migration status for ocaml-lame (0.3.7-3 to 0.3.7-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-lo (0.2.0.git20240724.0b43bdf-1 to 0.2.0.git20240724.0b43bdf-2)
- Migration status for ocaml-lo (0.2.0.git20240724.0b43bdf-1 to 0.2.0.git20240724.0b43bdf-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-mm (0.8.6-1 to 0.8.6-2)
- Migration status for ocaml-mm (0.8.6-1 to 0.8.6-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-portaudio (0.2.3-3 to 0.2.3-5)
- Migration status for ocaml-portaudio (0.2.3-3 to 0.2.3-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-shine (0.2.3-3 to 0.2.3-4)
- Migration status for ocaml-shine (0.2.3-3 to 0.2.3-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-soundtouch (0.1.9-4 to 0.1.9-5)
- Migration status for ocaml-soundtouch (0.1.9-4 to 0.1.9-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-time-now (0.17.0-2 to 0.17.0-3)
- Migration status for ocaml-time-now (0.17.0-2 to 0.17.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-voaacenc (0.1.1-2 to 0.1.1-3)
- Migration status for ocaml-voaacenc (0.1.1-2 to 0.1.1-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-xmlplaylist (0.1.5-4 to 0.1.5-5)
- Migration status for ocaml-xmlplaylist (0.1.5-4 to 0.1.5-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocrmypdf (16.7.0+dfsg1-3 to 16.10.4+dfsg1-1)
- Migration status for ocrmypdf (16.7.0+dfsg1-3 to 16.10.4+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ocrmypdf/16.10.4+dfsg1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- omins (0.2.0-8 to 0.2.0-9)
- Migration status for omins (0.2.0-8 to 0.2.0-9): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- openstack-cluster-installer (- to 43.0.12)
- Migration status for openstack-cluster-installer (- to 43.0.12): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- pan (0.163-1 to 0.164-1)
- Migration status for pan (0.163-1 to 0.164-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- parole (4.18.2-1 to 4.20.0-1)
- Migration status for parole (4.18.2-1 to 4.20.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- parolottero-languages (7-1 to 8-1)
- Migration status for parolottero-languages (7-1 to 8-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- partial-json-parser (- to 0.2.1.1.post5-2)
- Migration status for partial-json-parser (- to 0.2.1.1.post5-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for partial-json-parser/0.2.1.1.post5-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- patool (4.0.0-1 to 4.0.1-1)
- Migration status for patool (4.0.0-1 to 4.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for patool/4.0.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pcbasic (2.0.7-7 to 2.0.7-8)
- Migration status for pcbasic (2.0.7-7 to 2.0.7-8): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pcbasic/2.0.7-8: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pcre2 (10.45-1 to 10.46-1)
- Migration status for pcre2 (10.45-1 to 10.46-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- pdns-recursor (5.2.4-2 to 5.3.0-1)
- Migration status for pdns-recursor (5.2.4-2 to 5.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pdns-recursor/5.3.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pgauditlogtofile (1.6.4-1 to 1.7.2-1)
- Migration status for pgauditlogtofile (1.6.4-1 to 1.7.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pgauditlogtofile/1.7.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pgpool2 (4.6.1-2 to 4.6.3-1)
- Migration status for pgpool2 (4.6.1-2 to 4.6.3-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pgpool2/4.6.3-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- photoqt (4.8.1+ds-1 to 4.9.2+ds-1)
- Migration status for photoqt (4.8.1+ds-1 to 4.9.2+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- php-brick-varexporter (0.6.0-1 to 0.6.0-2)
- Migration status for php-brick-varexporter (0.6.0-1 to 0.6.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for php-brick-varexporter/0.6.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- php-di-invoker (2.3.6-1 to 2.3.6-2)
- Migration status for php-di-invoker (2.3.6-1 to 2.3.6-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for php-di-invoker/2.3.6-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- php-http-psr7-integration-tests (1.4.0-2 to 1.4.0-3)
- Migration status for php-http-psr7-integration-tests (1.4.0-2 to 1.4.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for php-http-psr7-integration-tests/1.4.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- php-mockery (1.6.12-4 to 1.6.12-5)
- Migration status for php-mockery (1.6.12-4 to 1.6.12-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: php-mockery sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for php-mockery/1.6.12-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pillow-sane (2.9.1-3 to 2.9.2-1)
- Migration status for pillow-sane (2.9.1-3 to 2.9.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pillow-sane/2.9.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- play.it (2.33.0-1 to 2.33.1-1)
- Migration status for play.it (2.33.0-1 to 2.33.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- pngphoon (1.3-3.1 to 1.4-0.1)
- Migration status for pngphoon (1.3-3.1 to 1.4-0.1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- pocsuite3 (2.0.3-3 to 2.1.0-1)
- Migration status for pocsuite3 (2.0.3-3 to 2.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- popa3d (1.0.3-1.1 to 1.0.3-2)
- Migration status for popa3d (1.0.3-1.1 to 1.0.3-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- poppler (25.03.0-5 to 25.03.0-6)
- Migration status for poppler (25.03.0-5 to 25.03.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for poppler/25.03.0-6: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- postgresql-17 (17.5-1 to 17.6-1)
- Migration status for postgresql-17 (17.5-1 to 17.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gvmd/26.2.0-2: amd64: Pass
- autopkgtest for postgresql-17/17.6-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- profanity (0.15.0-1 to 0.15.1-1)
- Migration status for profanity (0.15.0-1 to 0.15.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- proftpd-dfsg (1.3.8.c+dfsg-4 to 1.3.9~dfsg-2)
- Migration status for proftpd-dfsg (1.3.8.c+dfsg-4 to 1.3.9~dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for proftpd-dfsg/1.3.9~dfsg-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- proftpd-mod-sftp-ldap (0.2-1 to 0.2-2)
- Migration status for proftpd-mod-sftp-ldap (0.2-1 to 0.2-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: proftpd-mod-sftp-ldap proftpd-dfsg
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- prometheus-fastapi-instrumentator (- to 7.1.0-2)
- Migration status for prometheus-fastapi-instrumentator (- to 7.1.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for prometheus-fastapi-instrumentator/7.1.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- prometheus-mysqlrouter-exporter (6.0.0-5 to 6.0.1-1)
- Migration status for prometheus-mysqlrouter-exporter (6.0.0-5 to 6.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 22 days old
- Additional info:
- publicsuffix (20250328.1952-0.1 to 20250820.0948-0.1)
- Migration status for publicsuffix (20250328.1952-0.1 to 20250820.0948-0.1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for publicsuffix/20250820.0948-0.1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- py3status (3.61-1 to 3.62-1)
- Migration status for py3status (3.61-1 to 3.62-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- pyiskra (0.1.21-2 to 0.1.23-1)
- Migration status for pyiskra (0.1.21-2 to 0.1.23-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pyiskra/0.1.23-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pymssql (2.3.2-1 to 2.3.7-1)
- Migration status for pymssql (2.3.2-1 to 2.3.7-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 22 days old
- Additional info:
- pystache (0.6.5-1 to 0.6.8-1)
- Migration status for pystache (0.6.5-1 to 0.6.8-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- pytest-pretty (1.2.0-4 to 1.3.0-1)
- Migration status for pytest-pretty (1.2.0-4 to 1.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pytest-pretty/1.3.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-aioapns (3.3.1-1 to 4.0-1)
- Migration status for python-aioapns (3.3.1-1 to 4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- python-aiohasupervisor (0.3.1-1 to 0.3.2-1)
- Migration status for python-aiohasupervisor (0.3.1-1 to 0.3.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-aiohasupervisor/0.3.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-apischema (0.18.3-1 to 0.18.3-2)
- Migration status for python-apischema (0.18.3-1 to 0.18.3-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-apischema/0.18.3-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-aranet4 (2.4.0-2 to 2.5.1-1)
- Migration status for python-aranet4 (2.4.0-2 to 2.5.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-aranet4/2.5.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-codegen (1.0-5 to 1.0-6)
- Migration status for python-codegen (1.0-5 to 1.0-6): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- python-cyborgclient (2.5.0-2 to 2.6.0-1)
- Migration status for python-cyborgclient (2.5.0-2 to 2.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: python-cyborgclient sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-cyborgclient/2.6.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-datapoint (- to 0.13.0-2)
- Migration status for python-datapoint (- to 0.13.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: python-datapoint sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-datapoint/0.13.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-datrie (0.8.2-5 to 0.8.3-1)
- Migration status for python-datrie (0.8.2-5 to 0.8.3-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-datrie/0.8.3-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-django-crispy-forms-foundation (1.1.0+ds-1 to 1.1.0+ds-2)
- Migration status for python-django-crispy-forms-foundation (1.1.0+ds-1 to 1.1.0+ds-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: python-django-crispy-forms-foundation sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-django-crispy-forms-foundation/1.1.0+ds-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-django-dbconn-retry (0.1.8-1 to 0.1.9-1)
- Migration status for python-django-dbconn-retry (0.1.8-1 to 0.1.9-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-django-dbconn-retry/0.1.9-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-django-pgschemas (1.0.1-1 to 1.0.1-2)
- Migration status for python-django-pgschemas (1.0.1-1 to 1.0.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-django-pgschemas/1.0.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-elastic-transport (8.17.1-2 to 9.1.0-2)
- Migration status for python-elastic-transport (8.17.1-2 to 9.1.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 22 days old
- Additional info:
- python-eth-utils (- to 5.3.0-2)
- Migration status for python-eth-utils (- to 5.3.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: python-eth-utils sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-eth-utils/5.3.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-eventlet (0.39.1-2 to 0.40.1-2)
- Migration status for python-eventlet (0.39.1-2 to 0.40.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-eventlet/0.40.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-h5netcdf (1.6.1-1 to 1.6.4-1)
- Migration status for python-h5netcdf (1.6.1-1 to 1.6.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: python-h5netcdf sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-h5netcdf/1.6.4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-homewizard-energy (9.2.0-1 to 9.3.0-1)
- Migration status for python-homewizard-energy (9.2.0-1 to 9.3.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-homewizard-energy/9.3.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-maison (2.0.0-3 to 2.0.0-4)
- Migration status for python-maison (2.0.0-3 to 2.0.0-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: python-maison sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-maison/2.0.0-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-pika (1.3.2-1 to 1.3.2-2)
- Migration status for python-pika (1.3.2-1 to 1.3.2-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: python-pika sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-pika/1.3.2-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-pretty-yaml (25.1.0-1 to 25.7.0-1)
- Migration status for python-pretty-yaml (25.1.0-1 to 25.7.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- python-pywebview (5.0.5+dfsg-2 to 6.0+dfsg-1)
- Migration status for python-pywebview (5.0.5+dfsg-2 to 6.0+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- python-returns (0.25.0-1 to 0.26.0-1)
- Migration status for python-returns (0.25.0-1 to 0.26.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-returns/0.26.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-roborock (2.38.0-1 to 2.39.0-1)
- Migration status for python-roborock (2.38.0-1 to 2.39.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: python-roborock sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-roborock/2.39.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-scooby (0.10.0-1 to 0.10.1-1)
- Migration status for python-scooby (0.10.0-1 to 0.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-scooby/0.10.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-shtab (1.7.1-1 to 1.7.2-1)
- Migration status for python-shtab (1.7.1-1 to 1.7.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-shtab/1.7.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-snitun (0.42.0-1 to 0.45.0-1)
- Migration status for python-snitun (0.42.0-1 to 0.45.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-snitun/0.45.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-time-machine (2.17.0-1 to 2.19.0-1)
- Migration status for python-time-machine (2.17.0-1 to 2.19.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-time-machine/2.19.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-tokenize-rt (6.1.0-1 to 6.2.0-1)
- Migration status for python-tokenize-rt (6.1.0-1 to 6.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-tokenize-rt/6.2.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-vispy (0.14.3-1 to 0.15.2-1)
- Migration status for python-vispy (0.14.3-1 to 0.15.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- python-zaqarclient (3.0.0-3 to 4.1.0-1)
- Migration status for python-zaqarclient (3.0.0-3 to 4.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for python-zaqarclient/4.1.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pytouchlinesl (0.4.0-1 to 0.5.0-1)
- Migration status for pytouchlinesl (0.4.0-1 to 0.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pytouchlinesl/0.5.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pyupgrade (3.19.1-1 to 3.20.0-1)
- Migration status for pyupgrade (3.19.1-1 to 3.20.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pyupgrade/3.20.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- qbs (2.6.1-1 to 3.0.1-4)
- Migration status for qbs (2.6.1-1 to 3.0.1-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for qbs/3.0.1-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- (15 to 16)
- Migration status for qcom-firmware-extract (15 to 16): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- qdl (1.0+git20250319.30ac3a8-1 to 2.1+git20250704.cd32723-1)
- Migration status for qdl (1.0+git20250319.30ac3a8-1 to 2.1+git20250704.cd32723-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- qemu (1:10.0.3+ds-4 to 1:10.1.0+ds-2)
- Migration status for qemu (1:10.0.3+ds-4 to 1:10.1.0+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for qemu/1:10.1.0+ds-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- qingping-ble (0.10.0-3 to 1.0.1-1)
- Migration status for qingping-ble (0.10.0-3 to 1.0.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for qingping-ble/1.0.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- qmmp (2.2.7-1 to 2.2.8-1)
- Migration status for qmmp (2.2.7-1 to 2.2.8-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- qpwgraph (0.8.2-1 to 0.9.5-1)
- Migration status for qpwgraph (0.8.2-1 to 0.9.5-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- r-bioc-beachmat (2.22.0+ds-2 to 2.22.0+ds-3)
- Migration status for r-bioc-beachmat (2.22.0+ds-2 to 2.22.0+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for r-bioc-beachmat/2.22.0+ds-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- r-cran-dendextend (- to 1.19.1+dfsg-1)
- Migration status for r-cran-dendextend (- to 1.19.1+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for r-cran-dendextend/1.19.1+dfsg-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- r-cran-rvest (1.0.4-1 to 1.0.5-1)
- Migration status for r-cran-rvest (1.0.4-1 to 1.0.5-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: r-cran-rvest r-cran-xml2
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for r-cran-rvest/1.0.5-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- r-cran-xml2 (1.3.8-1 to 1.4.0-1)
- Migration status for r-cran-xml2 (1.3.8-1 to 1.4.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for r-cran-xml2/1.4.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- r8125 (9.016.00-1 to 9.016.01-1)
- Migration status for r8125 (9.016.00-1 to 9.016.01-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- radio-beam (0.3.8-2 to 0.3.9-1)
- Migration status for radio-beam (0.3.8-2 to 0.3.9-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for radio-beam/0.3.9-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- radlib (2.12.0-7 to 2.12.0-8)
- Migration status for radlib (2.12.0-7 to 2.12.0-8): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- rarcrack (0.2+20240214~413ea3a-1 to 0.2+20240214~413ea3a-2)
- Migration status for rarcrack (0.2+20240214~413ea3a-1 to 0.2+20240214~413ea3a-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- raritan-json-rpc-sdk (4.3.0+ds-1 to 4.3.10+ds-1)
- Migration status for raritan-json-rpc-sdk (4.3.0+ds-1 to 4.3.10+ds-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for raritan-json-rpc-sdk/4.3.10+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- readpe (0.84-2 to 0.85-1)
- Migration status for readpe (0.84-2 to 0.85-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for readpe/0.85-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rebind (0.3.4-1kali7 to 0.3.4-1kali8)
- Migration status for rebind (0.3.4-1kali7 to 0.3.4-1kali8): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- recoll (1.43.0-1 to 1.43.4-1)
- Migration status for recoll (1.43.0-1 to 1.43.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- reproject (0.14.1-4 to 0.15.0-2)
- Migration status for reproject (0.14.1-4 to 0.15.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for reproject/0.15.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- responses (0.25.7-1 to 0.25.8-1)
- Migration status for responses (0.25.7-1 to 0.25.8-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for responses/0.25.8-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- ros-bloom (0.13.0-1 to 0.13.0-2)
- Migration status for ros-bloom (0.13.0-1 to 0.13.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- routine-update (- to 0.2.3)
- Migration status for routine-update (- to 0.2.3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: routine-update lintian-brush
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- rtpengine (12.5.1.31-1 to 12.5.1.38-1)
- Migration status for rtpengine (12.5.1.31-1 to 12.5.1.38-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- ruby-propshaft (- to 1.2.1-2)
- Migration status for ruby-propshaft (- to 1.2.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- rust-abscissa-derive (0.7.0-1 to 0.8.2-1)
- Migration status for rust-abscissa-derive (0.7.0-1 to 0.8.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-abscissa-derive/0.8.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ahash (0.8.12-1 to 0.8.12-2)
- Migration status for rust-ahash (0.8.12-1 to 0.8.12-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- rust-backdown (1.1.2-4 to 1.1.2-5)
- Migration status for rust-backdown (1.1.2-4 to 1.1.2-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-backdown/1.1.2-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-backoff (0.4.0-4 to 0.4.0-5)
- Migration status for rust-backoff (0.4.0-4 to 0.4.0-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-backoff/0.4.0-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-bacon (3.12.0-3 to 3.12.0-4)
- Migration status for rust-bacon (3.12.0-3 to 3.12.0-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: rust-bacon rust-termimad (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-bacon/3.12.0-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-blocking (1.6.1-6 to 1.6.2-1)
- Migration status for rust-blocking (1.6.1-6 to 1.6.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-blocking/1.6.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-broot (1.47.0-2 to 1.47.0-3)
- Migration status for rust-broot (1.47.0-2 to 1.47.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-broot/1.47.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-camino (1.1.6-1 to 1.1.12-1)
- Migration status for rust-camino (1.1.6-1 to 1.1.12-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-camino/1.1.12-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-dysk (2.10.1-2 to 3.0.0-1)
- Migration status for rust-dysk (2.10.1-2 to 3.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- rust-dysk-cli (2.10.1-2 to 3.0.0-1)
- Migration status for rust-dysk-cli (2.10.1-2 to 3.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-dysk-cli/3.0.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-event-listener (5.4.0-3 to 5.4.1-3)
- Migration status for rust-event-listener (5.4.0-3 to 5.4.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-event-listener/5.4.1-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-filetime (0.2.24-1 to 0.2.26-1)
- Migration status for rust-filetime (0.2.24-1 to 0.2.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-filetime/0.2.26-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-fork (0.1.23-1 to 0.2.0-1)
- Migration status for rust-fork (0.1.23-1 to 0.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-fork/0.2.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-framehop (0.13.0-2 to 0.13.0-3)
- Migration status for rust-framehop (0.13.0-2 to 0.13.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-framehop/0.13.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gvdb (0.8.0-2 to 0.8.0-3)
- Migration status for rust-gvdb (0.8.0-2 to 0.8.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: rust-gvdb rust-zerocopy (not considered)
- Additional info:
- rust-human-panic (2.0.3-1 to 2.0.3-2)
- Migration status for rust-human-panic (2.0.3-1 to 2.0.3-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-human-panic/2.0.3-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-hypothesis (0.12.0-3 to 0.12.0-4)
- Migration status for rust-hypothesis (0.12.0-3 to 0.12.0-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-hypothesis/0.12.0-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-jpeg-encoder (0.6.0-1 to 0.6.1-1)
- Migration status for rust-jpeg-encoder (0.6.0-1 to 0.6.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-jpeg-encoder/0.6.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-kvm-bindings (0.10.0-2 to 0.10.0-4)
- Migration status for rust-kvm-bindings (0.10.0-2 to 0.10.0-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: rust-kvm-bindings rust-zerocopy (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-kvm-bindings/0.10.0-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-lcms2 (6.0.4-1 to 6.1.1-1)
- Migration status for rust-lcms2 (6.0.4-1 to 6.1.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-lcms2/6.1.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-lcms2-sys (4.0.4-1 to 4.0.6-1)
- Migration status for rust-lcms2-sys (4.0.4-1 to 4.0.6-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Implicit dependency: rust-lcms2-sys rust-lcms2
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-lcms2-sys/4.0.6-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-lfs-core (0.12.0-1 to 0.13.3-1)
- Migration status for rust-lfs-core (0.12.0-1 to 0.13.3-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Implicit dependency: rust-lfs-core rust-broot
- Implicit dependency: rust-lfs-core rust-dysk-cli
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-lfs-core/0.13.3-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-macho-unwind-info (0.4.0-1 to 0.5.0-1)
- Migration status for rust-macho-unwind-info (0.4.0-1 to 0.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-macho-unwind-info/0.5.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-openssl (0.10.72-1 to 0.10.73-1)
- Migration status for rust-openssl (0.10.72-1 to 0.10.73-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-openssl/0.10.73-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-pe-unwind-info (0.2.3-1 to 0.5.0-2)
- Migration status for rust-pe-unwind-info (0.2.3-1 to 0.5.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-pikchr (0.1.4-2 to 0.1.4-3)
- Migration status for rust-pikchr (0.1.4-2 to 0.1.4-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-pikchr/0.1.4-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-portable-atomic-util (- to 0.2.4-2)
- Migration status for rust-portable-atomic-util (- to 0.2.4-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-portable-atomic-util/0.2.4-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ppv-lite86 (0.2.20-1 to 0.2.21-2)
- Migration status for rust-ppv-lite86 (0.2.20-1 to 0.2.21-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-ppv-lite86/0.2.21-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-prettyplease (0.2.6-1 to 0.2.25-1)
- Migration status for rust-prettyplease (0.2.6-1 to 0.2.25-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-prettyplease/0.2.25-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-rebuildctl (0.24.0-1 to 0.25.0-1)
- Migration status for rust-rebuildctl (0.24.0-1 to 0.25.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- rust-rebuilderd (0.24.0-1 to 0.25.0-1)
- Migration status for rust-rebuilderd (0.24.0-1 to 0.25.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-rebuilderd/0.25.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-rebuilderd-common (0.23.0-1 to 0.25.0-1)
- Migration status for rust-rebuilderd-common (0.23.0-1 to 0.25.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Implicit dependency: rust-rebuilderd-common rust-rebuilderd
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-rebuilderd-common/0.25.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-rebuilderd-worker (0.24.0-1 to 0.25.0-1)
- Migration status for rust-rebuilderd-worker (0.24.0-1 to 0.25.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- rust-regalloc2 (0.10.2-4 to 0.10.2-5)
- Migration status for rust-regalloc2 (0.10.2-4 to 0.10.2-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-regalloc2/0.10.2-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-resource-proof (1.0.39-12 to 1.0.39-13)
- Migration status for rust-resource-proof (1.0.39-12 to 1.0.39-13): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-resource-proof/1.0.39-13: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ripcalc (0.1.12-1 to 0.2.5-1)
- Migration status for rust-ripcalc (0.1.12-1 to 0.2.5-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-ripcalc/0.2.5-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-roadmap (0.7.0-4 to 0.7.0-5)
- Migration status for rust-roadmap (0.7.0-4 to 0.7.0-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-roadmap/0.7.0-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ruma-state-res (- to 0.8.0-5)
- Migration status for rust-ruma-state-res (- to 0.8.0-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-ruma-state-res/0.8.0-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-semver (1.0.23-1 to 1.0.26-1)
- Migration status for rust-semver (1.0.23-1 to 1.0.26-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-semver/1.0.26-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-sequoia-sop (0.37.2-1 to 0.37.2-2)
- Migration status for rust-sequoia-sop (0.37.2-1 to 0.37.2-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-sequoia-sop/0.37.2-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-sequoia-wot (0.14.0-1 to 0.15.0-1)
- Migration status for rust-sequoia-wot (0.14.0-1 to 0.15.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Implicit dependency: rust-sequoia-wot rust-sequoia-sop
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-sequoia-wot/0.15.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-tempfile (3.15.0-1 to 3.21.0-1)
- Migration status for rust-tempfile (3.15.0-1 to 3.21.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-tempfile/3.21.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-termimad (0.31.1-1 to 0.33.0-1)
- Migration status for rust-termimad (0.31.1-1 to 0.33.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-termimad/0.33.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-tokio-socks (0.5.2-1 to 0.5.2-2)
- Migration status for rust-tokio-socks (0.5.2-1 to 0.5.2-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-tokio-socks/0.5.2-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ulid (1.2.1-2 to 1.2.1-3)
- Migration status for rust-ulid (1.2.1-2 to 1.2.1-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-ulid/1.2.1-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-utmp-classic-raw (0.1.3-1.1 to 0.1.3-2)
- Migration status for rust-utmp-classic-raw (0.1.3-1.1 to 0.1.3-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: rust-utmp-classic-raw rust-zerocopy (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-utmp-classic-raw/0.1.3-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-xcb (1.4.0-2 to 1.6.0-1)
- Migration status for rust-xcb (1.4.0-2 to 1.6.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-xcb/1.6.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-zbus-names (4.1.1-2 to 4.2.0-1)
- Migration status for rust-zbus-names (4.1.1-2 to 4.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-zbus-names/4.2.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-zerocopy (0.7.34-1 to 0.8.26-4)
- Migration status for rust-zerocopy (0.7.34-1 to 0.8.26-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-zerocopy/0.8.26-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-zerocopy-derive (0.7.34-1 to 0.8.26-3)
- Migration status for rust-zerocopy-derive (0.7.34-1 to 0.8.26-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-zerocopy-derive/0.8.26-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-zvariant-utils (3.1.0-2 to 3.2.1-1)
- Migration status for rust-zvariant-utils (3.1.0-2 to 3.2.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-zvariant-utils/3.2.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- scala-xml (1.0.3-3.1 to 1.0.3-4)
- Migration status for scala-xml (1.0.3-3.1 to 1.0.3-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- scheme9 (2025.08.11-1 to 2025.08.12-2)
- Migration status for scheme9 (2025.08.11-1 to 2025.08.12-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- scram (0.16.2-3 to 0.16.2-4)
- Migration status for scram (0.16.2-3 to 0.16.2-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- sdml (0.3.2+20250310-2 to 0.3.2+20250310-3)
- Migration status for sdml (0.3.2+20250310-2 to 0.3.2+20250310-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for sdml/0.3.2+20250310-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- shadow (1:4.17.4-2 to 1:4.18.0-1)
- Migration status for shadow (1:4.17.4-2 to 1:4.18.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- smuxi (1.2.1-2 to 1.2.1-3)
- Migration status for smuxi (1.2.1-2 to 1.2.1-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- sphinx (8.1.3-5 to 8.2.3-2)
- Migration status for sphinx (8.1.3-5 to 8.2.3-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- sphinx-autodoc-typehints (2.3.0-2 to 3.2.0-2)
- Migration status for sphinx-autodoc-typehints (2.3.0-2 to 3.2.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: sphinx-autodoc-typehints sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for sphinx-autodoc-typehints/3.2.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- sphinx-prompt (1.9.0-1 to 1.10.1-1)
- Migration status for sphinx-prompt (1.9.0-1 to 1.10.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: sphinx-prompt sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for sphinx-prompt/1.10.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- sphinx-pytest (- to 0.2.0-1)
- Migration status for sphinx-pytest (- to 0.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for sphinx-pytest/0.2.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- sphinxcontrib-video (- to 0.4.1-1)
- Migration status for sphinxcontrib-video (- to 0.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: sphinxcontrib-video sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for sphinxcontrib-video/0.4.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- sphinxcontrib-youtube (- to 1.4.1-1)
- Migration status for sphinxcontrib-youtube (- to 1.4.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: sphinxcontrib-youtube sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for sphinxcontrib-youtube/1.4.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- spike (2.9-1kali9 to 2.9-1kali10)
- Migration status for spike (2.9-1kali9 to 2.9-1kali10): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- (1.6.1+1.4.321.0-1 to 1.6.1+1.4.321.0-2)
- Migration status for spirv-headers (1.6.1+1.4.321.0-1 to 1.6.1+1.4.321.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- splash (3.11.2-1 to 3.11.4-1)
- Migration status for splash (3.11.2-1 to 3.11.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- spopt (0.6.1-3 to 0.6.1-4)
- Migration status for spopt (0.6.1-3 to 0.6.1-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for spopt/0.6.1-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- stardict (3.0.7+git20220909+dfsg-7 to 3.0.7+git20220909+dfsg-8)
- Migration status for stardict (3.0.7+git20220909+dfsg-7 to 3.0.7+git20220909+dfsg-8): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- statsmodels (0.14.4+dfsg-1 to 0.14.5+dfsg-1)
- Migration status for statsmodels (0.14.4+dfsg-1 to 0.14.5+dfsg-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Depends: statsmodels sphinx
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for statsmodels/0.14.5+dfsg-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- steam-installer (1:1.0.0.83~ds-3 to 1:1.0.0.84~ds-2)
- Migration status for steam-installer (1:1.0.0.83~ds-3 to 1:1.0.0.84~ds-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- storebackup (3.2.1-2 to 3.5.2-1)
- Migration status for storebackup (3.2.1-2 to 3.5.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- swugenerator (0.4-1 to 0.5-1)
- Migration status for swugenerator (0.4-1 to 0.5-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- syncevolution (2.0.0-3.1 to 2.0.0-3.3)
- Migration status for syncevolution (2.0.0-3.1 to 2.0.0-3.3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- systemd (257.7-1 to 258~rc3-1)
- Migration status for systemd (257.7-1 to 258~rc3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for systemd/258~rc3-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- systemd-boot-efi-amd64-signed (257.7+1 to 258~rc3+1)
- Migration status for systemd-boot-efi-amd64-signed (257.7+1 to 258~rc3+1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- systemd-boot-efi-arm64-signed (257.7+1 to 258~rc3+1)
- Migration status for systemd-boot-efi-arm64-signed (257.7+1 to 258~rc3+1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- sysv-rc-conf (1.1.0-1 to 1.1.1-1)
- Migration status for sysv-rc-conf (1.1.0-1 to 1.1.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for sysv-rc-conf/1.1.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- texlive-base (2025.20250727-2 to 2025.20250727-3)
- Migration status for texlive-base (2025.20250727-2 to 2025.20250727-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- (2025.20250727-2 to 2025.20250727-3)
- Migration status for texlive-extra (2025.20250727-2 to 2025.20250727-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- texlive-lang (2025.20250727-2 to 2025.20250727-3)
- Migration status for texlive-lang (2025.20250727-2 to 2025.20250727-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- tgif (1:4.2.5-2 to 1:4.2.5-3)
- Migration status for tgif (1:4.2.5-2 to 1:4.2.5-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- tgl (- to 2.0.1+git20160323.ffb04cac-5)
- Migration status for tgl (- to 2.0.1+git20160323.ffb04cac-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- thunar-dropbox-plugin (0.3.1-2 to 0.3.2-1)
- Migration status for thunar-dropbox-plugin (0.3.1-2 to 0.3.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- tifffile (20250611-1 to 20250828-1)
- Migration status for tifffile (20250611-1 to 20250828-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for tifffile/20250828-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- timemachine (0.3.3-5 to 0.3.3-6)
- Migration status for timemachine (0.3.3-5 to 0.3.3-6): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- udunits (2.2.28-7 to 2.2.28-8)
- Migration status for udunits (2.2.28-7 to 2.2.28-8): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Implicit dependency: udunits ncl
- Additional info:
- upgrade-system (1.9.9 to 1.9.11)
- Migration status for upgrade-system (1.9.9 to 1.9.11): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- vgabios (0.8a+ds-2 to 0.8a+ds-3)
- Migration status for vgabios (0.8a+ds-2 to 0.8a+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- virtualbox-guest-additions-iso (7.1.12-1 to 7.2.0-3)
- Migration status for virtualbox-guest-additions-iso (7.1.12-1 to 7.2.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- vulkan-tools (1.4.304.0+dfsg1-1 to 1.4.321.0+dfsg1-1)
- Migration status for vulkan-tools (1.4.304.0+dfsg1-1 to 1.4.321.0+dfsg1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- wev (1.0.0-3 to 1.1.0-1)
- Migration status for wev (1.0.0-3 to 1.1.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- whatweb (0.6.1-1 to 0.6.2-1)
- Migration status for whatweb (0.6.1-1 to 0.6.2-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- wireguard (1.0.20210914-3 to 1.0.20250521-1)
- Migration status for wireguard (1.0.20210914-3 to 1.0.20250521-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for wireguard/1.0.20250521-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- wlopm (0.1.0-1 to 1.0.0-1)
- Migration status for wlopm (0.1.0-1 to 1.0.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- (0.1.9-2 to 0.2.0-1)
- Migration status for wmenu (0.1.9-2 to 0.2.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- wokkel (18.0.0-5 to 18.0.0-6)
- Migration status for wokkel (18.0.0-5 to 18.0.0-6): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for wokkel/18.0.0-6: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- x2vnc (1.7.2+git20100909.01ced3d-1 to 1.7.2+git20100909.01ced3d-2)
- Migration status for x2vnc (1.7.2+git20100909.01ced3d-1 to 1.7.2+git20100909.01ced3d-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- xdg-user-dirs (0.18-2 to 0.18-3)
- Migration status for xdg-user-dirs (0.18-2 to 0.18-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- xdg-user-dirs-gtk (0.14-1 to 0.14-2)
- Migration status for xdg-user-dirs-gtk (0.14-1 to 0.14-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- xdiskusage (1.60-6 to 1.60-7)
- Migration status for xdiskusage (1.60-6 to 1.60-7): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- xmbmon (2.05-10 to 2.05-11)
- Migration status for xmbmon (2.05-10 to 2.05-11): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- xrootd-s3-http (0.4.1-2 to 0.5.0-3)
- Migration status for xrootd-s3-http (0.4.1-2 to 0.5.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- xtables-addons (3.28-1 to 3.29-1)
- Migration status for xtables-addons (3.28-1 to 3.29-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- xtermset (0.5.2-7 to 0.5.2-8)
- Migration status for xtermset (0.5.2-7 to 0.5.2-8): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- xwayland (2:24.1.6-1 to 2:24.1.8-1)
- Migration status for xwayland (2:24.1.6-1 to 2:24.1.8-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- yubico-pam (2.27-1 to 2.27-2)
- Migration status for yubico-pam (2.27-1 to 2.27-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- yubioath-desktop (5.1.0-4 to 5.1.0-5)
- Migration status for yubioath-desktop (5.1.0-4 to 5.1.0-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- zfs-linux (2.3.3-1 to 2.3.4-1)
- Migration status for zfs-linux (2.3.3-1 to 2.3.4-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for zfs-linux/2.3.4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- zutils (1.15-2 to 1.15-3)
- Migration status for zutils (1.15-2 to 1.15-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- nginx (1.26.3-3 to 1.28.0-3)
- Migration status for nginx (1.26.3-3 to 1.28.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for nginx/1.28.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 4 days old (needed 2 days)
- pyrate-limiter (3.8.1-1 to 3.9.0-1)
- Migration status for pyrate-limiter (3.8.1-1 to 3.9.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 4 of 22 days old
- Additional info:
- joplin (3.1.20+ds-0kali1 to 3.4.7+ds-0kali2)
- Migration status for joplin (3.1.20+ds-0kali1 to 3.4.7+ds-0kali2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 5 days old (needed 2 days)
- amass (4.2.0-0kali1 to 5.0.0-0kali2)
- Migration status for amass (4.2.0-0kali1 to 5.0.0-0kali2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 6 of 22 days old
- Additional info:
- cockpit-machines (332-1 to 338-1)
- Migration status for cockpit-machines (332-1 to 338-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 8 of 22 days old
- Additional info:
- etcd (3.5.16-4 to 3.5.16-7)
- Migration status for etcd (3.5.16-4 to 3.5.16-7): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for etcd/3.5.16-7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 11 days old (needed 2 days)
- gitaly (16.11.6+ds1-4 to 16.11.6+ds1-5)
- Migration status for gitaly (16.11.6+ds1-4 to 16.11.6+ds1-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 11 days old (needed 2 days)
- golang-github-bougou-go-ipmi (0.7.7-1 to 0.7.8-1)
- Migration status for golang-github-bougou-go-ipmi (0.7.7-1 to 0.7.8-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-github-bougou-go-ipmi/0.7.8-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 11 days old (needed 2 days)
- golang-github-jaytaylor-html2text (0.0~git20211013.90c08c5-2 to 0.0~git20230321.74c2419-1)
- Migration status for golang-github-jaytaylor-html2text (0.0~git20211013.90c08c5-2 to 0.0~git20230321.74c2419-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-github-jaytaylor-html2text/0.0~git20230321.74c2419-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 11 days old (needed 2 days)
- golang-github-olekukonko-tablewriter (0.0.5-2 to 1.0.9-1)
- Migration status for golang-github-olekukonko-tablewriter (0.0.5-2 to 1.0.9-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- golang-github-rubenv-sql-migrate (0.0~git20191213.0633851-3 to 0.0~git20191213.0633851-4)
- Migration status for golang-github-rubenv-sql-migrate (0.0~git20191213.0633851-3 to 0.0~git20191213.0633851-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-github-rubenv-sql-migrate/0.0~git20191213.0633851-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 11 days old (needed 2 days)
- golang-github-zitadel-oidc (3.37.0-1 to 3.44.0-2)
- Migration status for golang-github-zitadel-oidc (3.37.0-1 to 3.44.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: golang-github-zitadel-oidc incus (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-github-zitadel-oidc/3.44.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 11 days old (needed 2 days)
- incus (6.0.4-2 to 6.0.5-1)
- Migration status for incus (6.0.4-2 to 6.0.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for incus/6.0.5-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 11 days old (needed 2 days)
- init-system-helpers (1.68+kali2 to 1.69+kali1)
- Migration status for init-system-helpers (1.68+kali2 to 1.69+kali1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for init-system-helpers/1.69+kali1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 11 days old (needed 2 days)
- yggdrasil (0.5.12-2 to 0.5.12-3)
- Migration status for yggdrasil (0.5.12-2 to 0.5.12-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for yggdrasil/0.5.12-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 11 days old (needed 2 days)
- distrobuilder (3.2-2 to 3.2-3)
- Migration status for distrobuilder (3.2-2 to 3.2-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 12 of 22 days old
- Additional info:
- firmware-nonfree (20250410-2 to 20250808-1)
- Migration status for firmware-nonfree (20250410-2 to 20250808-1): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
- Issues preventing migration:
- Not touching package due to block request by kali (please contact kali-release if update is needed)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 12 days old (needed 2 days)
- libxml-libxml-perl (2.0207+dfsg+really+2.0134-5 to 2.0207+dfsg+really+2.0134-6)
- Migration status for libxml-libxml-perl (2.0207+dfsg+really+2.0134-5 to 2.0207+dfsg+really+2.0134-6): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- libxml-libxslt-perl (2.003000-2 to 2.003000-3)
- Migration status for libxml-libxslt-perl (2.003000-2 to 2.003000-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 12 of 22 days old
- Additional info:
- golang-github-armon-go-metrics (0.4.1-1 to 0.4.1-2)
- Migration status for golang-github-armon-go-metrics (0.4.1-1 to 0.4.1-2): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-github-armon-go-metrics/0.4.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 15 days old (needed 2 days)
- golang-github-golang-protobuf-1-5 (1.5.4-1 to 1.5.4-2)
- Migration status for golang-github-golang-protobuf-1-5 (1.5.4-1 to 1.5.4-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 15 of 22 days old
- Additional info:
- postgresql-common (264 to 282)
- Migration status for postgresql-common (264 to 282): BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)
- Issues preventing migration:
- Not touching package due to block request by kali (please contact kali-release if update is needed)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for debusine/0.11.3: amd64: Pass
- autopkgtest for postgresql-common/282: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 15 days old (needed 2 days)
- python-cvss (- to 3.4-2)
- Migration status for python-cvss (- to 3.4-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- python-cvss has no binaries on any arch
- missing build on all
- arch:all not built yet, autopkgtest delayed
- Too young, only 20 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- Required age increased by 20 days because of autopkgtest
- r-bioc-degnorm (- to 1.16.0+ds-2)
- Migration status for r-bioc-degnorm (- to 1.16.0+ds-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: r-bioc-degnorm r-cran-heatmaply (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for r-bioc-degnorm/1.16.0+ds-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 223 days old (needed 2 days)
- r-bioc-degreport (- to 1.42.0+dfsg-2)
- Migration status for r-bioc-degreport (- to 1.42.0+dfsg-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: r-bioc-degreport r-cran-dendextend (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for r-bioc-degreport/1.42.0+dfsg-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 223 days old (needed 2 days)
- r-bioc-demixt (- to 1.22.0-2)
- Migration status for r-bioc-demixt (- to 1.22.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for r-bioc-demixt/1.22.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 224 days old (needed 2 days)
- debian-cloud-images (0.0.8 to 0.0.9)
- Migration status for debian-cloud-images (0.0.8 to 0.0.9): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- debian-cloud-images-packages/arm64 has unsatisfiable dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 238 days old (needed 2 days)
- eluceo-ical (- to 0.16.1-3)
- Migration status for eluceo-ical (- to 0.16.1-3): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for eluceo-ical/0.16.1-3: amd64: Pass
- 382 days old (needed 2 days)
- r-cran-heatmaply (- to 1.5.0+dfsg-1)
- Migration status for r-cran-heatmaply (- to 1.5.0+dfsg-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: r-cran-heatmaply r-cran-dendextend (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for r-cran-heatmaply/1.5.0+dfsg-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 687 days old (needed 2 days)
- (- to 1.0.7-2)
- Migration status for r-cran-factoextra (- to 1.0.7-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: r-cran-factoextra r-cran-dendextend (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for r-cran-factoextra/1.0.7-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 1777 days old (needed 2 days)