Generated: 2025.09.16 12:03:35 +0000
- -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:
- a7xpg/arm64 (0.11.dfsg1-12 to 0.11.dfsg1-12)
- Migration status for a7xpg/arm64 (0.11.dfsg1-12 to 0.11.dfsg1-12): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: a7xpg/arm64 gcc-15 (not considered)
- Invalidated by dependency
- a7xpg/armhf (0.11.dfsg1-12 to 0.11.dfsg1-12)
- Migration status for a7xpg/armhf (0.11.dfsg1-12 to 0.11.dfsg1-12): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: a7xpg/armhf gcc-15 (not considered)
- Invalidated by dependency
- a7xpg/i386 (0.11.dfsg1-12 to 0.11.dfsg1-12)
- Migration status for a7xpg/i386 (0.11.dfsg1-12 to 0.11.dfsg1-12): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: a7xpg/i386 gcc-15 (not considered)
- Invalidated by dependency
- abootimg/armel (0.6-2 to 0.6-2)
- Migration status for abootimg/armel (0.6-2 to 0.6-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: abootimg/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: aesfix/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- aflplusplus/armel (4.21c-5 to 4.21c-5)
- Migration status for aflplusplus/armel (4.21c-5 to 4.21c-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: aflplusplus/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- removing aircrack-ng/1:1.7+git20230807.4bf83f1a-2/armel from kali-rolling makes bully/1.4.00-2+b1/armel uninstallable
- removing aircrack-ng/1:1.7+git20230807.4bf83f1a-2/armel from kali-rolling makes mdk3/6.0-9/armel uninstallable
- removing aircrack-ng/1:1.7+git20230807.4bf83f1a-2/armel from kali-rolling makes mdk4/4.2-5/armel uninstallable
- Implicit dependency: aircrack-ng/armel airgeddon (not considered)
- Implicit dependency: aircrack-ng/armel kali-meta (not considered)
- 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:
- 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:
- appstream-generator/armhf (0.9.1-1 to 0.9.1-1)
- Migration status for appstream-generator/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: appstream-generator/armhf gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: argyll/armel colord (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ark/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: arp-scan/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- arpwatch/armel (2.1a15-9 to 2.1a15-9)
- Migration status for arpwatch/armel (2.1a15-9 to 2.1a15-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: arpwatch/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: assetfinder/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: autossh/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: bind9/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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-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)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: bluez-tools/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- braa/armel (0.82-7 to 0.82-7)
- Migration status for braa/armel (0.82-7 to 0.82-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: braa/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- bsd-finger/armel (0.17-17 to 0.17-17)
- Migration status for bsd-finger/armel (0.17-17 to 0.17-17): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: bsd-finger/armel legion (not considered)
- Invalidated by implicit-dependency
- btscanner/armel (2.1-9 to 2.1-9)
- Migration status for btscanner/armel (2.1-9 to 2.1-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: btscanner/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: bully/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- (1.11-2 to 1.11-2)
- Migration status for cabextract/armel (1.11-2 to 1.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: cabextract/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: cadaver/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ccrypt/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: cherrytree/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- chkrootkit/armel (0.58b-5 to 0.58b-5)
- Migration status for chkrootkit/armel (0.58b-5 to 0.58b-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: chkrootkit/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- chntpw/armel (140201-1.2 to 140201-1.2)
- Migration status for chntpw/armel (140201-1.2 to 140201-1.2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: chntpw/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: cifs-utils/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: clamav/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: contourpy/armel matplotlib (not considered)
- Invalidated by implicit-dependency
- 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)
- cowpatty/armel (4.8-3 to 4.8-3)
- Migration status for cowpatty/armel (4.8-3 to 4.8-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: cowpatty/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: cryptsetup-nuke-password/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: curlftpfs/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: cutecom/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dc3dd/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dcfldd/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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)
- dde-qt5integration/amd64 (5.7.12-1 to 5.7.12-1)
- Migration status for dde-qt5integration/amd64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dde-qt5integration/arm64 (5.7.12-1 to 5.7.12-1)
- Migration status for dde-qt5integration/arm64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dde-qt5integration/armhf (5.7.12-1 to 5.7.12-1)
- Migration status for dde-qt5integration/armhf (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dde-qt5integration/i386 (5.7.12-1 to 5.7.12-1)
- Migration status for dde-qt5integration/i386 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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:
- deepin-image-viewer/amd64 (5.8.2-4 to 5.8.2-4)
- Migration status for deepin-image-viewer/amd64 (5.8.2-4 to 5.8.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-image-viewer/arm64 (5.8.2-4 to 5.8.2-4)
- Migration status for deepin-image-viewer/arm64 (5.8.2-4 to 5.8.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-image-viewer/armhf (5.8.2-4 to 5.8.2-4)
- Migration status for deepin-image-viewer/armhf (5.8.2-4 to 5.8.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-image-viewer/i386 (5.8.2-4 to 5.8.2-4)
- Migration status for deepin-image-viewer/i386 (5.8.2-4 to 5.8.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-qt5dxcb-plugin/amd64 (5.7.12-1 to 5.7.12-1)
- Migration status for deepin-qt5dxcb-plugin/amd64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-qt5dxcb-plugin/arm64 (5.7.12-1 to 5.7.12-1)
- Migration status for deepin-qt5dxcb-plugin/arm64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-qt5dxcb-plugin/armhf (5.7.12-1 to 5.7.12-1)
- Migration status for deepin-qt5dxcb-plugin/armhf (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-qt5dxcb-plugin/i386 (5.7.12-1 to 5.7.12-1)
- Migration status for deepin-qt5dxcb-plugin/i386 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-terminal/amd64 (5.9.51+dfsg-1 to 5.9.51+dfsg-1)
- Migration status for deepin-terminal/amd64 (5.9.51+dfsg-1 to 5.9.51+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-terminal/arm64 (5.9.51+dfsg-1 to 5.9.51+dfsg-1)
- Migration status for deepin-terminal/arm64 (5.9.51+dfsg-1 to 5.9.51+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-terminal/armhf (5.9.51+dfsg-1 to 5.9.51+dfsg-1)
- Migration status for deepin-terminal/armhf (5.9.51+dfsg-1 to 5.9.51+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- deepin-terminal/i386 (5.9.51+dfsg-1 to 5.9.51+dfsg-1)
- Migration status for deepin-terminal/i386 (5.9.51+dfsg-1 to 5.9.51+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- diet-ng/armhf (1.8.1-3 to 1.8.1-3)
- Migration status for diet-ng/armhf (1.8.1-3 to 1.8.1-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: diet-ng/armhf gcc-15 (not considered)
- Invalidated by 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dillo/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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): Will attempt migration (Any information below is purely informational)
- dmitry/armel (1.3a-6 to 1.3a-6)
- Migration status for dmitry/armel (1.3a-6 to 1.3a-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dmitry/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- dnsmap/armel (0.36-4 to 0.36-4)
- Migration status for dnsmap/armel (0.36-4 to 0.36-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dnsmap/armel legion (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: dnsmap/armel kali-meta (not considered)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dnstracer/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dolphin/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dos2unix/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dragon/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: driftnet/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- dtkcore/amd64 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkcore/amd64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkcore/arm64 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkcore/arm64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkcore/armhf (5.7.12-1 to 5.7.12-1)
- Migration status for dtkcore/armhf (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkcore/i386 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkcore/i386 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkdeclarative/amd64 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkdeclarative/amd64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkdeclarative/arm64 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkdeclarative/arm64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkgui/amd64 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkgui/amd64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkgui/arm64 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkgui/arm64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkgui/armhf (5.7.12-1 to 5.7.12-1)
- Migration status for dtkgui/armhf (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkgui/i386 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkgui/i386 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtklog/amd64 (0.0.3-1 to 0.0.3-1)
- Migration status for dtklog/amd64 (0.0.3-1 to 0.0.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtklog/arm64 (0.0.3-1 to 0.0.3-1)
- Migration status for dtklog/arm64 (0.0.3-1 to 0.0.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtklog/armhf (0.0.3-1 to 0.0.3-1)
- Migration status for dtklog/armhf (0.0.3-1 to 0.0.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtklog/i386 (0.0.3-1 to 0.0.3-1)
- Migration status for dtklog/i386 (0.0.3-1 to 0.0.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkwidget/amd64 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkwidget/amd64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkwidget/arm64 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkwidget/arm64 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkwidget/armhf (5.7.12-1 to 5.7.12-1)
- Migration status for dtkwidget/armhf (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dtkwidget/i386 (5.7.12-1 to 5.7.12-1)
- Migration status for dtkwidget/i386 (5.7.12-1 to 5.7.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- dub/armhf (1.40.0-1 to 1.40.0-1)
- Migration status for dub/armhf (1.40.0-1 to 1.40.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: dub/armhf gcc-15 (not considered)
- Invalidated by dependency
- dustmite/amd64 (0.0.430-2.1 to 0.0.430-2.1)
- Migration status for dustmite/amd64 (0.0.430-2.1 to 0.0.430-2.1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: dustmite/amd64 gcc-15 (not considered)
- Invalidated by dependency
- dustmite/arm64 (0.0.430-2.1 to 0.0.430-2.1)
- Migration status for dustmite/arm64 (0.0.430-2.1 to 0.0.430-2.1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: dustmite/arm64 gcc-15 (not considered)
- Invalidated by dependency
- dustmite/armhf (0.0.430-2.1 to 0.0.430-2.1)
- Migration status for dustmite/armhf (0.0.430-2.1 to 0.0.430-2.1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: dustmite/armhf gcc-15 (not considered)
- Invalidated by dependency
- dustmite/i386 (0.0.430-2.1 to 0.0.430-2.1)
- Migration status for dustmite/i386 (0.0.430-2.1 to 0.0.430-2.1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: dustmite/i386 gcc-15 (not considered)
- Invalidated by 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:
- 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:
- 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)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: esnacc/armel wireshark (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: exifprobe/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: expect/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ext3grep/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ext4magic/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: extundelete/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- fcitx-qt5/amd64 (1.2.7-3 to 1.2.7-3)
- Migration status for fcitx-qt5/amd64 (1.2.7-3 to 1.2.7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- fcitx-qt5/arm64 (1.2.7-3 to 1.2.7-3)
- Migration status for fcitx-qt5/arm64 (1.2.7-3 to 1.2.7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- fcitx-qt5/armhf (1.2.7-3 to 1.2.7-3)
- Migration status for fcitx-qt5/armhf (1.2.7-3 to 1.2.7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- fcitx-qt5/i386 (1.2.7-3 to 1.2.7-3)
- Migration status for fcitx-qt5/i386 (1.2.7-3 to 1.2.7-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: fcrackzip/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- ffmpeg/amd64 (7:7.1.1-1 to 7:7.1.1-1)
- Migration status for ffmpeg/amd64 (7:7.1.1-1 to 7:7.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ffmpeg/amd64 libplacebo (not considered)
- Invalidated by dependency
- ffmpeg/arm64 (7:7.1.1-1 to 7:7.1.1-1)
- Migration status for ffmpeg/arm64 (7:7.1.1-1 to 7:7.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ffmpeg/arm64 libplacebo (not considered)
- Invalidated by dependency
- ffmpeg/armhf (7:7.1.1-1 to 7:7.1.1-1)
- Migration status for ffmpeg/armhf (7:7.1.1-1 to 7:7.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ffmpeg/armhf libplacebo (not considered)
- Invalidated by dependency
- ffmpeg/i386 (7:7.1.1-1 to 7:7.1.1-1)
- Migration status for ffmpeg/i386 (7:7.1.1-1 to 7:7.1.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ffmpeg/i386 libplacebo (not considered)
- Invalidated by dependency
- 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:
- 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:
- 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:
- 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:
- flightgear/arm64 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1)
- Migration status for flightgear/arm64 (1:2020.3.19+dfsg-1 to 1:2020.3.19+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: foremost/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- forensics-colorize/armel (1.1-7 to 1.1-7)
- Migration status for forensics-colorize/armel (1.1-7 to 1.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: forensics-colorize/armel kali-meta (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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: fping/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: fribidi/armel vte2.91 (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: fribidi/armel gtk+3.0 (not considered)
- Implicit dependency: fribidi/armel gtk4 (not considered)
- Implicit dependency: fribidi/armel pango1.0 (not considered)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: fwbuilder/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: galleta/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gcc-arm-none-eabi/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- gcin/amd64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
- Migration status for gcin/amd64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- gcin/arm64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
- Migration status for gcin/arm64 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- gcin/armhf (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
- Migration status for gcin/armhf (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- gcin/i386 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3)
- Migration status for gcin/i386 (2.9.4+dfsg1-3 to 2.9.4+dfsg1-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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:
- 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:
- 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:
- gir-to-d/armhf (0.23.4-1 to 0.23.4-1)
- Migration status for gir-to-d/armhf (0.23.4-1 to 0.23.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gir-to-d/armhf gcc-15 (not considered)
- Invalidated by dependency
- 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:
- glib-d/armhf (2.4.3-3 to 2.4.3-3)
- Migration status for glib-d/armhf (2.4.3-3 to 2.4.3-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: glib-d/armhf gcc-15 (not considered)
- Invalidated by dependency
- 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:
- 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:
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: gnome-desktop-testing/armel fwupd (not considered)
- Invalidated by implicit-dependency
- 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-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-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:
- gnss-sdr/amd64 (0.0.20-1 to 0.0.20-1)
- Migration status for gnss-sdr/amd64 (0.0.20-1 to 0.0.20-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gnss-sdr/amd64 uhd (not considered)
- Invalidated by dependency
- gnss-sdr/arm64 (0.0.20-1 to 0.0.20-1)
- Migration status for gnss-sdr/arm64 (0.0.20-1 to 0.0.20-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gnss-sdr/arm64 uhd (not considered)
- Invalidated by dependency
- gnss-sdr/armhf (0.0.20-1 to 0.0.20-1)
- Migration status for gnss-sdr/armhf (0.0.20-1 to 0.0.20-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gnss-sdr/armhf uhd (not considered)
- Invalidated by dependency
- gnss-sdr/i386 (0.0.20-1 to 0.0.20-1)
- Migration status for gnss-sdr/i386 (0.0.20-1 to 0.0.20-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gnss-sdr/i386 uhd (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gnuradio/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gnustep-make/armel gnustep-base (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gparted/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- gpsd/armel (3.25-5 to 3.25-5)
- Migration status for gpsd/armel (3.25-5 to 3.25-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gpsd/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gqrx-sdr/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gr-air-modes/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gr-iqbal/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- gr-osmosdr/amd64 (0.2.6-4 to 0.2.6-4)
- Migration status for gr-osmosdr/amd64 (0.2.6-4 to 0.2.6-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gr-osmosdr/amd64 uhd (not considered)
- Invalidated by dependency
- gr-osmosdr/arm64 (0.2.6-4 to 0.2.6-4)
- Migration status for gr-osmosdr/arm64 (0.2.6-4 to 0.2.6-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gr-osmosdr/arm64 uhd (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gr-osmosdr/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- gr-osmosdr/armhf (0.2.6-4 to 0.2.6-4)
- Migration status for gr-osmosdr/armhf (0.2.6-4 to 0.2.6-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gr-osmosdr/armhf uhd (not considered)
- Invalidated by dependency
- gr-osmosdr/i386 (0.2.6-4 to 0.2.6-4)
- Migration status for gr-osmosdr/i386 (0.2.6-4 to 0.2.6-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gr-osmosdr/i386 uhd (not considered)
- Invalidated by dependency
- gr-radar/amd64 (0.0.0.20220920-2 to 0.0.0.20220920-2)
- Migration status for gr-radar/amd64 (0.0.0.20220920-2 to 0.0.0.20220920-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gr-radar/amd64 uhd (not considered)
- Invalidated by dependency
- gr-radar/arm64 (0.0.0.20220920-2 to 0.0.0.20220920-2)
- Migration status for gr-radar/arm64 (0.0.0.20220920-2 to 0.0.0.20220920-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gr-radar/arm64 uhd (not considered)
- Invalidated by dependency
- gr-radar/armhf (0.0.0.20220920-2 to 0.0.0.20220920-2)
- Migration status for gr-radar/armhf (0.0.0.20220920-2 to 0.0.0.20220920-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gr-radar/armhf uhd (not considered)
- Invalidated by dependency
- gr-radar/i386 (0.0.0.20220920-2 to 0.0.0.20220920-2)
- Migration status for gr-radar/i386 (0.0.0.20220920-2 to 0.0.0.20220920-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gr-radar/i386 uhd (not considered)
- Invalidated by dependency
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: graphene/armel rust-graphene-sys (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: graphene/armel gtk4 (not considered)
- Implicit dependency: graphene/armel vte2.91
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: graphite2/armel harfbuzz (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: graphviz/armel gnustep-base (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- gtk2hs-buildtools/amd64 (0.13.11.0-1 to 0.13.11.0-1)
- Migration status for gtk2hs-buildtools/amd64 (0.13.11.0-1 to 0.13.11.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gtk2hs-buildtools/amd64 haskell-hashtables (not considered)
- Invalidated by dependency
- gtk2hs-buildtools/arm64 (0.13.11.0-1 to 0.13.11.0-1)
- Migration status for gtk2hs-buildtools/arm64 (0.13.11.0-1 to 0.13.11.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gtk2hs-buildtools/arm64 haskell-hashtables (not considered)
- Invalidated by dependency
- gtk2hs-buildtools/armhf (0.13.11.0-1 to 0.13.11.0-1)
- Migration status for gtk2hs-buildtools/armhf (0.13.11.0-1 to 0.13.11.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gtk2hs-buildtools/armhf haskell-hashtables (not considered)
- Invalidated by dependency
- gtk2hs-buildtools/i386 (0.13.11.0-1 to 0.13.11.0-1)
- Migration status for gtk2hs-buildtools/i386 (0.13.11.0-1 to 0.13.11.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gtk2hs-buildtools/i386 haskell-hashtables (not considered)
- Invalidated by dependency
- gtkhash/armel (1.5-3 to 1.5-3)
- Migration status for gtkhash/armel (1.5-3 to 1.5-3): Will attempt migration (Any information below is purely informational)
- 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:
- gunroar/arm64 (0.15.dfsg1-10 to 0.15.dfsg1-10)
- Migration status for gunroar/arm64 (0.15.dfsg1-10 to 0.15.dfsg1-10): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gunroar/arm64 gcc-15 (not considered)
- Invalidated by dependency
- gunroar/armhf (0.15.dfsg1-10 to 0.15.dfsg1-10)
- Migration status for gunroar/armhf (0.15.dfsg1-10 to 0.15.dfsg1-10): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gunroar/armhf gcc-15 (not considered)
- Invalidated by dependency
- gunroar/i386 (0.15.dfsg1-10 to 0.15.dfsg1-10)
- Migration status for gunroar/i386 (0.15.dfsg1-10 to 0.15.dfsg1-10): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gunroar/i386 gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gwenview/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: hashdeep/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: hashrat/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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-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-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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-base16-bytestring/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-blaze-html/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-bmp/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- haskell-bv-sized/amd64 (1.0.5-2 to 1.0.5-2)
- Migration status for haskell-bv-sized/amd64 (1.0.5-2 to 1.0.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-bv-sized/arm64 (1.0.5-2 to 1.0.5-2)
- Migration status for haskell-bv-sized/arm64 (1.0.5-2 to 1.0.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-bv-sized/armhf (1.0.5-2 to 1.0.5-2)
- Migration status for haskell-bv-sized/armhf (1.0.5-2 to 1.0.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-bv-sized/i386 (1.0.5-2 to 1.0.5-2)
- Migration status for haskell-bv-sized/i386 (1.0.5-2 to 1.0.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-bytestring-to-vector/armel haskell-futhark-data (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: haskell-bytestring-to-vector/armel haskell-futhark
- 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-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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- 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-copilot-language/amd64 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-language/amd64 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-language/arm64 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-language/arm64 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-language/armhf (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-language/armhf (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-language/i386 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-language/i386 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-libraries/amd64 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-libraries/amd64 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-libraries/arm64 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-libraries/arm64 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-libraries/armhf (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-libraries/armhf (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-libraries/i386 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-libraries/i386 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-theorem/amd64 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-theorem/amd64 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-theorem/arm64 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-theorem/arm64 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-theorem/armhf (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-theorem/armhf (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot-theorem/i386 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot-theorem/i386 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot/amd64 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot/amd64 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot/arm64 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot/arm64 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot/armhf (4.5-1 to 4.5-1)
- Migration status for haskell-copilot/armhf (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-copilot/i386 (4.5-1 to 4.5-1)
- Migration status for haskell-copilot/i386 (4.5-1 to 4.5-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-cryptohash-md5/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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-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-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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-githash/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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-hledger-lib/amd64 (1.32.3-1 to 1.32.3-1)
- Migration status for haskell-hledger-lib/amd64 (1.32.3-1 to 1.32.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-hledger-lib/arm64 (1.32.3-1 to 1.32.3-1)
- Migration status for haskell-hledger-lib/arm64 (1.32.3-1 to 1.32.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-hledger-lib/armhf (1.32.3-1 to 1.32.3-1)
- Migration status for haskell-hledger-lib/armhf (1.32.3-1 to 1.32.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-hledger-lib/i386 (1.32.3-1 to 1.32.3-1)
- Migration status for haskell-hledger-lib/i386 (1.32.3-1 to 1.32.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-hledger/amd64 (1.32.3-1 to 1.32.3-1)
- Migration status for haskell-hledger/amd64 (1.32.3-1 to 1.32.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-hledger/arm64 (1.32.3-1 to 1.32.3-1)
- Migration status for haskell-hledger/arm64 (1.32.3-1 to 1.32.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-hledger/armhf (1.32.3-1 to 1.32.3-1)
- Migration status for haskell-hledger/armhf (1.32.3-1 to 1.32.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-hledger/i386 (1.32.3-1 to 1.32.3-1)
- Migration status for haskell-hledger/i386 (1.32.3-1 to 1.32.3-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- 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-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-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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-lens/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- 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-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-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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-neat-interpolation/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- 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-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-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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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-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-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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-regex-tdfa/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- 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-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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-statistics/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- 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-tasty-checklist/amd64 (1.0.6.0-2 to 1.0.6.0-2)
- Migration status for haskell-tasty-checklist/amd64 (1.0.6.0-2 to 1.0.6.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-tasty-checklist/arm64 (1.0.6.0-2 to 1.0.6.0-2)
- Migration status for haskell-tasty-checklist/arm64 (1.0.6.0-2 to 1.0.6.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-tasty-checklist/armhf (1.0.6.0-2 to 1.0.6.0-2)
- Migration status for haskell-tasty-checklist/armhf (1.0.6.0-2 to 1.0.6.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-tasty-checklist/i386 (1.0.6.0-2 to 1.0.6.0-2)
- Migration status for haskell-tasty-checklist/i386 (1.0.6.0-2 to 1.0.6.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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-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-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-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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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-what4/amd64 (1.5.1-4 to 1.5.1-4)
- Migration status for haskell-what4/amd64 (1.5.1-4 to 1.5.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-what4/arm64 (1.5.1-4 to 1.5.1-4)
- Migration status for haskell-what4/arm64 (1.5.1-4 to 1.5.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-what4/armhf (1.5.1-4 to 1.5.1-4)
- Migration status for haskell-what4/armhf (1.5.1-4 to 1.5.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- haskell-what4/i386 (1.5.1-4 to 1.5.1-4)
- Migration status for haskell-what4/i386 (1.5.1-4 to 1.5.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haskell-zlib/armel haskell-futhark (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: haveged/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- hedgewars/amd64 (1.0.3-4 to 1.0.3-4)
- Migration status for hedgewars/amd64 (1.0.3-4 to 1.0.3-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- hedgewars/arm64 (1.0.3-4 to 1.0.3-4)
- Migration status for hedgewars/arm64 (1.0.3-4 to 1.0.3-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- hedgewars/armhf (1.0.3-4 to 1.0.3-4)
- Migration status for hedgewars/armhf (1.0.3-4 to 1.0.3-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- hedgewars/i386 (1.0.3-4 to 1.0.3-4)
- Migration status for hedgewars/i386 (1.0.3-4 to 1.0.3-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- hime/amd64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
- Migration status for hime/amd64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- hime/arm64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
- Migration status for hime/arm64 (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- hime/armhf (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
- Migration status for hime/armhf (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- hime/i386 (0.9.11+dfsg-4 to 0.9.11+dfsg-4)
- Migration status for hime/i386 (0.9.11+dfsg-4 to 0.9.11+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: httrack/armel kali-meta (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)
- i2c-tools/armel (4.4-2 to 4.4-2)
- Migration status for i2c-tools/armel (4.4-2 to 4.4-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: i2c-tools/armel kali-meta (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:
- ii-esu/arm64 (1.0a.dfsg2-2 to 1.0a.dfsg2-2)
- Migration status for ii-esu/arm64 (1.0a.dfsg2-2 to 1.0a.dfsg2-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ii-esu/arm64 gcc-15 (not considered)
- Invalidated by dependency
- ii-esu/armhf (1.0a.dfsg2-2 to 1.0a.dfsg2-2)
- Migration status for ii-esu/armhf (1.0a.dfsg2-2 to 1.0a.dfsg2-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ii-esu/armhf gcc-15 (not considered)
- Invalidated by dependency
- ii-esu/i386 (1.0a.dfsg2-2 to 1.0a.dfsg2-2)
- Migration status for ii-esu/i386 (1.0a.dfsg2-2 to 1.0a.dfsg2-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ii-esu/i386 gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ike-scan/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: inspectrum/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: iodine/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: irpas/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: jbigkit/armel tiff (not considered)
- Invalidated by implicit-dependency
- 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:
- 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
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: kate/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: kcalc/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: kde-spectacle/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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)
- 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-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/amd64 (5.116.0-1 to 5.116.0-1)
- Migration status for ki18n/amd64 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- ki18n/arm64 (5.116.0-1 to 5.116.0-1)
- Migration status for ki18n/arm64 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- ki18n/armhf (5.116.0-1 to 5.116.0-1)
- Migration status for ki18n/armhf (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- ki18n/i386 (5.116.0-1 to 5.116.0-1)
- Migration status for ki18n/i386 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kiconthemes/amd64 (5.116.0-1 to 5.116.0-1)
- Migration status for kiconthemes/amd64 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kiconthemes/arm64 (5.116.0-1 to 5.116.0-1)
- Migration status for kiconthemes/arm64 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- kiconthemes/armhf (5.116.0-1 to 5.116.0-1)
- Migration status for kiconthemes/armhf (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kiconthemes/i386 (5.116.0-1 to 5.116.0-1)
- Migration status for kiconthemes/i386 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- kirigami-addons5/amd64 (0.11.0-7 to 0.11.0-7)
- Migration status for kirigami-addons5/amd64 (0.11.0-7 to 0.11.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kirigami-addons5/arm64 (0.11.0-7 to 0.11.0-7)
- Migration status for kirigami-addons5/arm64 (0.11.0-7 to 0.11.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kirigami-addons5/armhf (0.11.0-7 to 0.11.0-7)
- Migration status for kirigami-addons5/armhf (0.11.0-7 to 0.11.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kirigami-addons5/i386 (0.11.0-7 to 0.11.0-7)
- Migration status for kirigami-addons5/i386 (0.11.0-7 to 0.11.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kirigami2/amd64 (5.116.0-1 to 5.116.0-1)
- Migration status for kirigami2/amd64 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kirigami2/arm64 (5.116.0-1 to 5.116.0-1)
- Migration status for kirigami2/arm64 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- kirigami2/armhf (5.116.0-1 to 5.116.0-1)
- Migration status for kirigami2/armhf (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kirigami2/i386 (5.116.0-1 to 5.116.0-1)
- Migration status for kirigami2/i386 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: kiwisolver/armel matplotlib (not considered)
- Invalidated by implicit-dependency
- 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:
- kmymoney/amd64 (5.1.3-2 to 5.1.3-2)
- Migration status for kmymoney/amd64 (5.1.3-2 to 5.1.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kmymoney/arm64 (5.1.3-2 to 5.1.3-2)
- Migration status for kmymoney/arm64 (5.1.3-2 to 5.1.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kmymoney/armhf (5.1.3-2 to 5.1.3-2)
- Migration status for kmymoney/armhf (5.1.3-2 to 5.1.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kmymoney/i386 (5.1.3-2 to 5.1.3-2)
- Migration status for kmymoney/i386 (5.1.3-2 to 5.1.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: konsole/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- krita/amd64 (1:5.2.11+dfsg-1 to 1:5.2.11+dfsg-1)
- Migration status for krita/amd64 (1:5.2.11+dfsg-1 to 1:5.2.11+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- krita/arm64 (1:5.2.11+dfsg-1 to 1:5.2.11+dfsg-1)
- Migration status for krita/arm64 (1:5.2.11+dfsg-1 to 1:5.2.11+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- krita/armhf (1:5.2.11+dfsg-1 to 1:5.2.11+dfsg-1)
- Migration status for krita/armhf (1:5.2.11+dfsg-1 to 1:5.2.11+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- krita/i386 (1:5.2.11+dfsg-1 to 1:5.2.11+dfsg-1)
- Migration status for krita/i386 (1:5.2.11+dfsg-1 to 1:5.2.11+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- 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)
- kwayland-integration/amd64 (6.3.4-1 to 6.3.4-1)
- Migration status for kwayland-integration/amd64 (6.3.4-1 to 6.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kwayland-integration/arm64 (6.3.4-1 to 6.3.4-1)
- Migration status for kwayland-integration/arm64 (6.3.4-1 to 6.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kwayland-integration/armhf (6.3.4-1 to 6.3.4-1)
- Migration status for kwayland-integration/armhf (6.3.4-1 to 6.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kwayland-integration/i386 (6.3.4-1 to 6.3.4-1)
- Migration status for kwayland-integration/i386 (6.3.4-1 to 6.3.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kwayland-kf5/amd64 (4:5.116.0-1 to 4:5.116.0-1)
- Migration status for kwayland-kf5/amd64 (4:5.116.0-1 to 4:5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kwayland-kf5/arm64 (4:5.116.0-1 to 4:5.116.0-1)
- Migration status for kwayland-kf5/arm64 (4:5.116.0-1 to 4:5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kwayland-kf5/armhf (4:5.116.0-1 to 4:5.116.0-1)
- Migration status for kwayland-kf5/armhf (4:5.116.0-1 to 4:5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kwayland-kf5/i386 (4:5.116.0-1 to 4:5.116.0-1)
- Migration status for kwayland-kf5/i386 (4:5.116.0-1 to 4:5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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/amd64 (5.116.0-1 to 5.116.0-1)
- Migration status for kxmlgui/amd64 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kxmlgui/arm64 (5.116.0-1 to 5.116.0-1)
- Migration status for kxmlgui/arm64 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- kxmlgui/armhf (5.116.0-1 to 5.116.0-1)
- Migration status for kxmlgui/armhf (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- kxmlgui/i386 (5.116.0-1 to 5.116.0-1)
- Migration status for kxmlgui/i386 (5.116.0-1 to 5.116.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: lerc/armel tiff (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- 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:
- removing libbsd-dev/0.12.2-2/armel from kali-rolling makes ghc/9.6.6-4/armel uninstallable
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libdeflate/armel tiff (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- removing libepoxy-dev/1.5.10-2/armel from kali-rolling makes kwin-dev/4:6.3.6-1/armel uninstallable
- Implicit dependency: libepoxy/armel gtk+3.0 (not considered)
- Implicit dependency: libepoxy/armel gtk4 (not considered)
- 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)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libewf/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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): Will attempt migration (Any information below is purely informational)
- 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-qt5/amd64 (1.4.0-7 to 1.4.0-7)
- Migration status for libfm-qt5/amd64 (1.4.0-7 to 1.4.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libfm-qt5/arm64 (1.4.0-7 to 1.4.0-7)
- Migration status for libfm-qt5/arm64 (1.4.0-7 to 1.4.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libfm-qt5/armhf (1.4.0-7 to 1.4.0-7)
- Migration status for libfm-qt5/armhf (1.4.0-7 to 1.4.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libfm-qt5/i386 (1.4.0-7 to 1.4.0-7)
- Migration status for libfm-qt5/i386 (1.4.0-7 to 1.4.0-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libfreefare/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libglvnd/armel mesa (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libgusb/armel colord (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libinih/armel xfsprogs (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libinput/armel qtbase-opensource-src (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: libinput/armel qt6-base (not considered)
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- 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:
- 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)
- 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): Will attempt migration (Any information below is purely informational)
- 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)
- 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-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-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-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
- 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:
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libpst/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- libqt5qxlsx/amd64 (1.4.4-1.1 to 1.4.4-1.1)
- Migration status for libqt5qxlsx/amd64 (1.4.4-1.1 to 1.4.4-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libqt5qxlsx/arm64 (1.4.4-1.1 to 1.4.4-1.1)
- Migration status for libqt5qxlsx/arm64 (1.4.4-1.1 to 1.4.4-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libqt5qxlsx/armhf (1.4.4-1.1 to 1.4.4-1.1)
- Migration status for libqt5qxlsx/armhf (1.4.4-1.1 to 1.4.4-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libqt5qxlsx/i386 (1.4.4-1.1 to 1.4.4-1.1)
- Migration status for libqt5qxlsx/i386 (1.4.4-1.1 to 1.4.4-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libqt5xdg/amd64 (3.12.0-2 to 3.12.0-2)
- Migration status for libqt5xdg/amd64 (3.12.0-2 to 3.12.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libqt5xdg/arm64 (3.12.0-2 to 3.12.0-2)
- Migration status for libqt5xdg/arm64 (3.12.0-2 to 3.12.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libqt5xdg/armhf (3.12.0-2 to 3.12.0-2)
- Migration status for libqt5xdg/armhf (3.12.0-2 to 3.12.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- libqt5xdg/i386 (3.12.0-2 to 3.12.0-2)
- Migration status for libqt5xdg/i386 (3.12.0-2 to 3.12.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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): Will attempt migration (Any information below is purely informational)
- 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)
- 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)
- 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)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libthai/armel pango1.0 (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: liburcu/armel xfsprogs (not considered)
- Invalidated by implicit-dependency
- 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:
- 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)
- 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:
- removing libsharpyuv-dev/1.5.0-0.1/armel from kali-rolling makes libheif-dev/1.20.2-2/armel uninstallable
- Implicit dependency: libwebp/armel tiff (not considered)
- 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): Will attempt migration (Any information below is purely informational)
- 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:
- removing libxcomposite-dev/1:0.4.6-1/armel from kali-rolling makes compiz-dev/2:0.8.18-8+b1/armel uninstallable
- removing libxcomposite-dev/1:0.4.6-1/armel from kali-rolling makes libgtk2.0-dev/2.24.33-8/armel uninstallable
- Implicit dependency: libxcomposite/armel gtk+3.0 (not considered)
- Implicit dependency: libxcomposite/armel gtk4 (not considered)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libxcvt/armel xorg-server (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libxfont/armel xorg-server (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libxkbcommon/armel qtbase-opensource-src (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: libxkbcommon/armel gnome-desktop (not considered)
- Implicit dependency: libxkbcommon/armel gtk+3.0 (not considered)
- Implicit dependency: libxkbcommon/armel gtk4 (not considered)
- Implicit dependency: libxkbcommon/armel qt6-base (not considered)
- 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:
- 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:
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: libxmu/armel rust-x11 (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: libxshmfence/armel xorg-server (not considered)
- Invalidated by implicit-dependency
- 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)
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: libxtst/armel rust-x11 (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: libxtst/armel at-spi2-core (not considered)
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- 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:
- 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)
- 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:
- 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)
- lomiri-ui-toolkit/amd64 (1.3.5110+dfsg-2 to 1.3.5110+dfsg-2)
- Migration status for lomiri-ui-toolkit/amd64 (1.3.5110+dfsg-2 to 1.3.5110+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- lomiri-ui-toolkit/arm64 (1.3.5110+dfsg-2 to 1.3.5110+dfsg-2)
- Migration status for lomiri-ui-toolkit/arm64 (1.3.5110+dfsg-2 to 1.3.5110+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- lomiri-ui-toolkit/armhf (1.3.5110+dfsg-2 to 1.3.5110+dfsg-2)
- Migration status for lomiri-ui-toolkit/armhf (1.3.5110+dfsg-2 to 1.3.5110+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- lomiri-ui-toolkit/i386 (1.3.5110+dfsg-2 to 1.3.5110+dfsg-2)
- Migration status for lomiri-ui-toolkit/i386 (1.3.5110+dfsg-2 to 1.3.5110+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- 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:
- lxqt-qt5plugin/amd64 (1.4.1-2 to 1.4.1-2)
- Migration status for lxqt-qt5plugin/amd64 (1.4.1-2 to 1.4.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- lxqt-qt5plugin/arm64 (1.4.1-2 to 1.4.1-2)
- Migration status for lxqt-qt5plugin/arm64 (1.4.1-2 to 1.4.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- lxqt-qt5plugin/armhf (1.4.1-2 to 1.4.1-2)
- Migration status for lxqt-qt5plugin/armhf (1.4.1-2 to 1.4.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- lxqt-qt5plugin/i386 (1.4.1-2 to 1.4.1-2)
- Migration status for lxqt-qt5plugin/i386 (1.4.1-2 to 1.4.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: m2crypto/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- mac-robber/armel (1.02-13 to 1.02-13)
- Migration status for mac-robber/armel (1.02-13 to 1.02-13): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: mac-robber/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: macchanger/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: magicrescue/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- maliit-framework/amd64 (2.3.0-6 to 2.3.0-6)
- Migration status for maliit-framework/amd64 (2.3.0-6 to 2.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- maliit-framework/arm64 (2.3.0-6 to 2.3.0-6)
- Migration status for maliit-framework/arm64 (2.3.0-6 to 2.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- maliit-framework/armhf (2.3.0-6 to 2.3.0-6)
- Migration status for maliit-framework/armhf (2.3.0-6 to 2.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- maliit-framework/i386 (2.3.0-6 to 2.3.0-6)
- Migration status for maliit-framework/i386 (2.3.0-6 to 2.3.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: maskprocessor/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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-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): Will attempt migration (Any information below is purely informational)
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: mdbtools/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- mdk3/armel (6.0-9 to 6.0-9)
- Migration status for mdk3/armel (6.0-9 to 6.0-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: mdk3/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- mdk4/armel (4.2-5 to 4.2-5)
- Migration status for mdk4/armel (4.2-5 to 4.2-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: mdk4/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- mediastreamer2/amd64 (1:5.3.105+dfsg-5 to 1:5.3.105+dfsg-5)
- Migration status for mediastreamer2/amd64 (1:5.3.105+dfsg-5 to 1:5.3.105+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- mediastreamer2/arm64 (1:5.3.105+dfsg-5 to 1:5.3.105+dfsg-5)
- Migration status for mediastreamer2/arm64 (1:5.3.105+dfsg-5 to 1:5.3.105+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- mediastreamer2/armhf (1:5.3.105+dfsg-5 to 1:5.3.105+dfsg-5)
- Migration status for mediastreamer2/armhf (1:5.3.105+dfsg-5 to 1:5.3.105+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- mediastreamer2/i386 (1:5.3.105+dfsg-5 to 1:5.3.105+dfsg-5)
- Migration status for mediastreamer2/i386 (1:5.3.105+dfsg-5 to 1:5.3.105+dfsg-5): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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:
- removing medusa/2.3-2/armel from kali-rolling makes offsec-pwk/2025.3.0/armel uninstallable
- Implicit dependency: medusa/armel kali-meta (not considered)
- Implicit dependency: medusa/armel legion (not considered)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: memdump/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- metacam/armel (1.2-14 to 1.2-14)
- Migration status for metacam/armel (1.2-14 to 1.2-14): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: metacam/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: mfcuk/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: mfoc/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- minicom/armel (2.10-1 to 2.10-1)
- Migration status for minicom/armel (2.10-1 to 2.10-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: minicom/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- mir-core/armhf (1.7.0-1 to 1.7.0-1)
- Migration status for mir-core/armhf (1.7.0-1 to 1.7.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: mir-core/armhf gcc-15 (not considered)
- Invalidated by 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: miredo/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- missidentify/armel (1.0-11 to 1.0-11)
- Migration status for missidentify/armel (1.0-11 to 1.0-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: missidentify/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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)
- 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:
- mpv/amd64 (0.40.0-3 to 0.40.0-3)
- Migration status for mpv/amd64 (0.40.0-3 to 0.40.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: mpv/amd64 libplacebo (not considered)
- Invalidated by dependency
- mpv/arm64 (0.40.0-3 to 0.40.0-3)
- Migration status for mpv/arm64 (0.40.0-3 to 0.40.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: mpv/arm64 libplacebo (not considered)
- Invalidated by dependency
- mpv/armhf (0.40.0-3 to 0.40.0-3)
- Migration status for mpv/armhf (0.40.0-3 to 0.40.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: mpv/armhf libplacebo (not considered)
- Invalidated by dependency
- mpv/i386 (0.40.0-3 to 0.40.0-3)
- Migration status for mpv/i386 (0.40.0-3 to 0.40.0-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: mpv/i386 libplacebo (not considered)
- Invalidated by dependency
- 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:
- mu-cade/arm64 (0.11.dfsg1-14 to 0.11.dfsg1-14)
- Migration status for mu-cade/arm64 (0.11.dfsg1-14 to 0.11.dfsg1-14): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: mu-cade/arm64 gcc-15 (not considered)
- Invalidated by dependency
- mu-cade/armhf (0.11.dfsg1-14 to 0.11.dfsg1-14)
- Migration status for mu-cade/armhf (0.11.dfsg1-14 to 0.11.dfsg1-14): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: mu-cade/armhf gcc-15 (not considered)
- Invalidated by dependency
- mu-cade/i386 (0.11.dfsg1-14 to 0.11.dfsg1-14)
- Migration status for mu-cade/i386 (0.11.dfsg1-14 to 0.11.dfsg1-14): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: mu-cade/i386 gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: multimon-ng/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- mustache-d/armhf (0.1.4-1 to 0.1.4-1)
- Migration status for mustache-d/armhf (0.1.4-1 to 0.1.4-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: mustache-d/armhf gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: myrescue/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: nasty/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ncrack/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ncurses-hexedit/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- removing netcat-traditional/1.10-50/armel from kali-rolling makes offsec-awae/2025.3.0/armel uninstallable
- removing netcat-traditional/1.10-50/armel from kali-rolling makes offsec-pwk/2025.3.0/armel uninstallable
- Implicit dependency: netcat/armel kali-meta (not considered)
- Implicit dependency: netcat/armel legion (not considered)
- netdiscover/armel (0.21-1 to 0.21-1)
- Migration status for netdiscover/armel (0.21-1 to 0.21-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: netdiscover/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: netkit-ftp-ssl/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: netmask/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- netsed/armel (1.4-1 to 1.4-1)
- Migration status for netsed/armel (1.4-1 to 1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: netsed/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: nfs-utils/armel legion (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: nfs-utils/armel kali-meta (not considered)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: nftables/armel vopono (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ntpsec/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- removing libnuma-dev/2.0.19-1/armel from kali-rolling makes ghc/9.6.6-4/armel uninstallable
- Implicit dependency: numactl/armel hwloc (not considered)
- ocaml-multicoretests/amd64 (0.9-1 to 0.9-1)
- Migration status for ocaml-multicoretests/amd64 (0.9-1 to 0.9-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ocaml-multicoretests/amd64 ocaml-qcheck (not considered)
- Invalidated by dependency
- ocaml-multicoretests/arm64 (0.9-1 to 0.9-1)
- Migration status for ocaml-multicoretests/arm64 (0.9-1 to 0.9-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ocaml-multicoretests/arm64 ocaml-qcheck (not considered)
- Invalidated by dependency
- ocaml-multicoretests/armhf (0.9-1 to 0.9-1)
- Migration status for ocaml-multicoretests/armhf (0.9-1 to 0.9-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ocaml-multicoretests/armhf ocaml-qcheck (not considered)
- Invalidated by dependency
- ocaml-multicoretests/i386 (0.9-1 to 0.9-1)
- Migration status for ocaml-multicoretests/i386 (0.9-1 to 0.9-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: ocaml-multicoretests/i386 ocaml-qcheck (not considered)
- Invalidated by 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: okular/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: omniorb-dfsg/armel wireshark (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: onboard/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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): Will attempt migration (Any information below is purely informational)
- 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): Will attempt migration (Any information below is purely informational)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: openocd/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- openorienteering-mapper/amd64 (0.9.5-3.1 to 0.9.5-3.1)
- Migration status for openorienteering-mapper/amd64 (0.9.5-3.1 to 0.9.5-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- openorienteering-mapper/arm64 (0.9.5-3.1 to 0.9.5-3.1)
- Migration status for openorienteering-mapper/arm64 (0.9.5-3.1 to 0.9.5-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- openorienteering-mapper/armhf (0.9.5-3.1 to 0.9.5-3.1)
- Migration status for openorienteering-mapper/armhf (0.9.5-3.1 to 0.9.5-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- openorienteering-mapper/i386 (0.9.5-3.1 to 0.9.5-3.1)
- Migration status for openorienteering-mapper/i386 (0.9.5-3.1 to 0.9.5-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: openssh-ssh1/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ophcrack/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: outguess/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- p0f/armel (3.09b-4 to 3.09b-4)
- Migration status for p0f/armel (3.09b-4 to 3.09b-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: p0f/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: packagekit/armel gnome-software (not considered)
- Invalidated by implicit-dependency
- 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)
- parsec47/arm64 (0.2.dfsg1-10 to 0.2.dfsg1-10)
- Migration status for parsec47/arm64 (0.2.dfsg1-10 to 0.2.dfsg1-10): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: parsec47/arm64 gcc-15 (not considered)
- Invalidated by dependency
- parsec47/armhf (0.2.dfsg1-10 to 0.2.dfsg1-10)
- Migration status for parsec47/armhf (0.2.dfsg1-10 to 0.2.dfsg1-10): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: parsec47/armhf gcc-15 (not considered)
- Invalidated by dependency
- parsec47/i386 (0.2.dfsg1-10 to 0.2.dfsg1-10)
- Migration status for parsec47/i386 (0.2.dfsg1-10 to 0.2.dfsg1-10): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: parsec47/i386 gcc-15 (not considered)
- Invalidated by dependency
- pasco/armel (20040505-4 to 20040505-4)
- Migration status for pasco/armel (20040505-4 to 20040505-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: pasco/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: pcapy/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: pdfcrack/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- peruse/amd64 (1.80+dfsg-3 to 1.80+dfsg-3)
- Migration status for peruse/amd64 (1.80+dfsg-3 to 1.80+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- peruse/arm64 (1.80+dfsg-3 to 1.80+dfsg-3)
- Migration status for peruse/arm64 (1.80+dfsg-3 to 1.80+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- peruse/armhf (1.80+dfsg-3 to 1.80+dfsg-3)
- Migration status for peruse/armhf (1.80+dfsg-3 to 1.80+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- peruse/i386 (1.80+dfsg-3 to 1.80+dfsg-3)
- Migration status for peruse/i386 (1.80+dfsg-3 to 1.80+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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-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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: pigpio/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: plasma-desktop/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- plasma-integration/amd64 (6.3.6-1 to 6.3.6-1)
- Migration status for plasma-integration/amd64 (6.3.6-1 to 6.3.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- plasma-integration/arm64 (6.3.6-1 to 6.3.6-1)
- Migration status for plasma-integration/arm64 (6.3.6-1 to 6.3.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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-integration/armhf (6.3.6-1 to 6.3.6-1)
- Migration status for plasma-integration/armhf (6.3.6-1 to 6.3.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- plasma-integration/i386 (6.3.6-1 to 6.3.6-1)
- Migration status for plasma-integration/i386 (6.3.6-1 to 6.3.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: plasma-nm/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: plasma-systemmonitor/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: plocate/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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)
- 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:
- 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:
- 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:
- projectl/arm64 (1.001.dfsg2-1 to 1.001.dfsg2-1)
- Migration status for projectl/arm64 (1.001.dfsg2-1 to 1.001.dfsg2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: projectl/arm64 gcc-15 (not considered)
- Invalidated by dependency
- projectl/armhf (1.001.dfsg2-1 to 1.001.dfsg2-1)
- Migration status for projectl/armhf (1.001.dfsg2-1 to 1.001.dfsg2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: projectl/armhf gcc-15 (not considered)
- Invalidated by dependency
- projectl/i386 (1.001.dfsg2-1 to 1.001.dfsg2-1)
- Migration status for projectl/i386 (1.001.dfsg2-1 to 1.001.dfsg2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: projectl/i386 gcc-15 (not considered)
- Invalidated by dependency
- 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): Will attempt migration (Any information below is purely informational)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: proxytunnel/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ptunnel/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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)
- 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)
- 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:
- pyotherside/amd64 (1.6.2-1 to 1.6.2-1)
- Migration status for pyotherside/amd64 (1.6.2-1 to 1.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- pyotherside/arm64 (1.6.2-1 to 1.6.2-1)
- Migration status for pyotherside/arm64 (1.6.2-1 to 1.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- pyotherside/armhf (1.6.2-1 to 1.6.2-1)
- Migration status for pyotherside/armhf (1.6.2-1 to 1.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- pyotherside/i386 (1.6.2-1 to 1.6.2-1)
- Migration status for pyotherside/i386 (1.6.2-1 to 1.6.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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/amd64 (5.15.11+dfsg-2 to 5.15.11+dfsg-2)
- Migration status for pyqt5/amd64 (5.15.11+dfsg-2 to 5.15.11+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- pyqt5/arm64 (5.15.11+dfsg-2 to 5.15.11+dfsg-2)
- Migration status for pyqt5/arm64 (5.15.11+dfsg-2 to 5.15.11+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- pyqt5/armhf (5.15.11+dfsg-2 to 5.15.11+dfsg-2)
- Migration status for pyqt5/armhf (5.15.11+dfsg-2 to 5.15.11+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- pyqt5/i386 (5.15.11+dfsg-2 to 5.15.11+dfsg-2)
- Migration status for pyqt5/i386 (5.15.11+dfsg-2 to 5.15.11+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: pyqt6/armel legion (not considered)
- Invalidated by implicit-dependency
- pyside2/amd64 (5.15.16-3.1 to 5.15.16-3.1)
- Migration status for pyside2/amd64 (5.15.16-3.1 to 5.15.16-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- pyside2/arm64 (5.15.16-3.1 to 5.15.16-3.1)
- Migration status for pyside2/arm64 (5.15.16-3.1 to 5.15.16-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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:
- pyside2/armhf (5.15.16-3.1 to 5.15.16-3.1)
- Migration status for pyside2/armhf (5.15.16-3.1 to 5.15.16-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- pyside2/i386 (5.15.16-3.1 to 5.15.16-3.1)
- Migration status for pyside2/i386 (5.15.16-3.1 to 5.15.16-3.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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-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-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:
- removing python3-cryptography/43.0.0-3/armel from kali-rolling makes python3-aioquic/1.2.0-1/armel uninstallable
- Implicit dependency: python-cryptography/armel samba (not considered)
- 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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: python-lz4/armel fonttools (not considered)
- Invalidated by implicit-dependency
- 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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: python-zopfli/armel fonttools (not considered)
- Invalidated by implicit-dependency
- 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-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:
- removing python3-tk/3.13.5-1/armel from kali-rolling makes unhide-gui/20240510-2/armel uninstallable
- Implicit dependency: python3-stdlib-extensions/armel avahi (not considered)
- Implicit dependency: python3-stdlib-extensions/armel pillow (not considered)
- Implicit dependency: python3-stdlib-extensions/armel python3-defaults (not considered)
- 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:
- qgis/amd64 (3.40.10+dfsg-1 to 3.40.10+dfsg-1)
- Migration status for qgis/amd64 (3.40.10+dfsg-1 to 3.40.10+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qgis/arm64 (3.40.10+dfsg-1 to 3.40.10+dfsg-1)
- Migration status for qgis/arm64 (3.40.10+dfsg-1 to 3.40.10+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qgis/armhf (3.40.10+dfsg-1 to 3.40.10+dfsg-1)
- Migration status for qgis/armhf (3.40.10+dfsg-1 to 3.40.10+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qgis/i386 (3.40.10+dfsg-1 to 3.40.10+dfsg-1)
- Migration status for qgis/i386 (3.40.10+dfsg-1 to 3.40.10+dfsg-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qgnomeplatform/amd64 (0.9.2-4 to 0.9.2-4)
- Migration status for qgnomeplatform/amd64 (0.9.2-4 to 0.9.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qgnomeplatform/arm64 (0.9.2-4 to 0.9.2-4)
- Migration status for qgnomeplatform/arm64 (0.9.2-4 to 0.9.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qgnomeplatform/armhf (0.9.2-4 to 0.9.2-4)
- Migration status for qgnomeplatform/armhf (0.9.2-4 to 0.9.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qgnomeplatform/i386 (0.9.2-4 to 0.9.2-4)
- Migration status for qgnomeplatform/i386 (0.9.2-4 to 0.9.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- qqc2-suru-style/amd64 (0.20230630-1 to 0.20230630-1)
- Migration status for qqc2-suru-style/amd64 (0.20230630-1 to 0.20230630-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qqc2-suru-style/arm64 (0.20230630-1 to 0.20230630-1)
- Migration status for qqc2-suru-style/arm64 (0.20230630-1 to 0.20230630-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qqc2-suru-style/armhf (0.20230630-1 to 0.20230630-1)
- Migration status for qqc2-suru-style/armhf (0.20230630-1 to 0.20230630-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qqc2-suru-style/i386 (0.20230630-1 to 0.20230630-1)
- Migration status for qqc2-suru-style/i386 (0.20230630-1 to 0.20230630-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qt5-ukui-platformtheme/amd64 (1.0.9-1 to 1.0.9-1)
- Migration status for qt5-ukui-platformtheme/amd64 (1.0.9-1 to 1.0.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qt5-ukui-platformtheme/arm64 (1.0.9-1 to 1.0.9-1)
- Migration status for qt5-ukui-platformtheme/arm64 (1.0.9-1 to 1.0.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qt5-ukui-platformtheme/armhf (1.0.9-1 to 1.0.9-1)
- Migration status for qt5-ukui-platformtheme/armhf (1.0.9-1 to 1.0.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qt5-ukui-platformtheme/i386 (1.0.9-1 to 1.0.9-1)
- Migration status for qt5-ukui-platformtheme/i386 (1.0.9-1 to 1.0.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qt5ct/amd64 (1.9-1 to 1.9-1)
- Migration status for qt5ct/amd64 (1.9-1 to 1.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qt5ct/arm64 (1.9-1 to 1.9-1)
- Migration status for qt5ct/arm64 (1.9-1 to 1.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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)
- qt5ct/armhf (1.9-1 to 1.9-1)
- Migration status for qt5ct/armhf (1.9-1 to 1.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qt5ct/i386 (1.9-1 to 1.9-1)
- Migration status for qt5ct/i386 (1.9-1 to 1.9-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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)
- qtchooser/armel (66-2 to 66-2)
- Migration status for qtchooser/armel (66-2 to 66-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qtcurve/amd64 (1.9-7.1 to 1.9-7.1)
- Migration status for qtcurve/amd64 (1.9-7.1 to 1.9-7.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qtcurve/arm64 (1.9-7.1 to 1.9-7.1)
- Migration status for qtcurve/arm64 (1.9-7.1 to 1.9-7.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qtcurve/armhf (1.9-7.1 to 1.9-7.1)
- Migration status for qtcurve/armhf (1.9-7.1 to 1.9-7.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- qtcurve/i386 (1.9-7.1 to 1.9-7.1)
- Migration status for qtcurve/i386 (1.9-7.1 to 1.9-7.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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)
- (0.66-1 to 0.66-1)
- Migration status for qtlomiri-appmenutheme/amd64 (0.66-1 to 0.66-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- (0.66-1 to 0.66-1)
- Migration status for qtlomiri-appmenutheme/arm64 (0.66-1 to 0.66-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- (0.66-1 to 0.66-1)
- Migration status for qtlomiri-appmenutheme/armhf (0.66-1 to 0.66-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- (0.66-1 to 0.66-1)
- Migration status for qtlomiri-appmenutheme/i386 (0.66-1 to 0.66-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: reaver/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: recordmydesktop/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- recoverdm/armel (0.20-9 to 0.20-9)
- Migration status for recoverdm/armel (0.20-9 to 0.20-9): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: recoverdm/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: recoverjpeg/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: redsocks/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: reglookup/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rephrase/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rfdump/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- rifiuti/armel (20040505-4 to 20040505-4)
- Migration status for rifiuti/armel (20040505-4 to 20040505-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rifiuti/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rifiuti2/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rkflashtool/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rpi.gpio/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rsakeyfind/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-annotate-snippets/armel rust-bindgen (not considered)
- Invalidated by implicit-dependency
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-anyhow/armel rust-bacon (not considered)
- Invalidated by implicit-dependency
- 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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-async-compression/armel rust-reqwest (not considered)
- Invalidated by implicit-dependency
- 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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-atomic-refcell/armel rust-gstreamer-base (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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-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-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-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-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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-cexpr/armel rust-bindgen (not considered)
- Invalidated by implicit-dependency
- 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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-clang-sys/armel rust-bindgen (not considered)
- Invalidated by implicit-dependency
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-clap-complete/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-clap-complete/armel rust-bacon
- Implicit dependency: rust-clap-complete/armel rust-bindgen
- 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-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/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-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-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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-cookie-store/armel rust-reqwest (not considered)
- Invalidated by implicit-dependency
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-crc-catalog/armel rust-crc (not considered)
- Invalidated by implicit-dependency
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- 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-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): 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-data-encoding/armel rust-hickory-proto (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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-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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-downcast-rs/armel rust-wayland-server (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-downcast-rs/armel rust-wayland-backend (not considered)
- 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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-endi/armel rust-zvariant (not considered)
- Invalidated by implicit-dependency
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-enum-as-inner/armel rust-hickory-proto (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-equivalent/armel rust-indexmap (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-equivalent/armel rust-hashbrown (not considered)
- 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-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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-field-offset/armel rust-gtk4 (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-freetype-rs/armel rust-cairo-rs (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-gl/armel rust-gdk4 (not considered)
- Invalidated by implicit-dependency
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-gst-plugin-version-helper/armel rust-gst-plugin-gtk4 (not considered)
- Invalidated by implicit-dependency
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-h3-quinn/armel rust-hickory-proto (not considered)
- Invalidated by implicit-dependency
- 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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-hyper-tls/armel rust-reqwest (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-iana-time-zone/armel rust-chrono (not considered)
- Invalidated by implicit-dependency
- 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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-inotify-sys/armel rust-inotify (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-ipnet/armel rust-reqwest (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-ipnet/armel rust-hickory-proto
- 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-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-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-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-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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-lru-cache/armel rust-hickory-resolver (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-mime-guess/armel rust-reqwest (not considered)
- Invalidated by implicit-dependency
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-muldiv/armel rust-gstreamer (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-munge/armel rust-rkyv (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-num-rational/armel rust-gstreamer (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-option-operations/armel rust-gstreamer (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-owning-ref/armel rust-lock-api (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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-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): Will attempt migration (Any information below is purely informational)
- 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-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-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-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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-pure-rust-locales/armel rust-chrono (not considered)
- Invalidated by implicit-dependency
- 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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-raw-window-handle/armel rust-wayland-backend (not considered)
- Invalidated by implicit-dependency
- 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): Will attempt migration (Any information below is purely informational)
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-rend/armel rust-rkyv (not considered)
- Invalidated by implicit-dependency
- 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-resolv-conf/armel rust-hickory-resolver (not considered)
- Invalidated by implicit-dependency
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-rkyv-derive/armel rust-rkyv (not considered)
- Invalidated by implicit-dependency
- 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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-rustc-hash/armel rust-broot (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-rustc-hash/armel rust-bindgen
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-rustls-pemfile/armel rust-reqwest (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-rustls-pemfile/armel rust-hickory-proto
- 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-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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-scoped-tls/armel rust-wayland-backend (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-serde-bytes/armel rust-zvariant (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-serde-bytes/armel rust-gstreamer
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-serde-urlencoded/armel rust-reqwest (not considered)
- Invalidated by implicit-dependency
- 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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-sha2-asm/armel rust-sha2 (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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-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-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-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-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-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-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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- 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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-terminal-light/armel rust-clap-help (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-terminal-light/armel rust-broot
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-thin-vec/armel rust-rkyv (not considered)
- Invalidated by implicit-dependency
- 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-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): Waiting for another item to be ready to migrate (no action required now - check later)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-tower/armel rust-reqwest (not considered)
- Invalidated by implicit-dependency
- 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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-triomphe/armel rust-rkyv (not considered)
- Invalidated by implicit-dependency
- 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-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-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-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-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-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-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-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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-value-bag/armel rust-log (not considered)
- Invalidated by implicit-dependency
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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-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-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-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-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-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-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-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/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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: safecopy/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: samdump2/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: scalpel/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: screen/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- scrounge-ntfs/armel (0.9-11 to 0.9-11)
- Migration status for scrounge-ntfs/armel (0.9-11 to 0.9-11): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: scrounge-ntfs/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: siege/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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)
- sipcrack/armel (0.2-4 to 0.2-4)
- Migration status for sipcrack/armel (0.2-4 to 0.2-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: sipcrack/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: sipsak/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: slowhttptest/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: snapd/armel gnome-software (not considered)
- Invalidated by implicit-dependency
- 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)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: soapysdr/armel limesuite (not considered)
- Invalidated by implicit-dependency
- soapyuhd/amd64 (0.4.1-5 to 0.4.1-5)
- Migration status for soapyuhd/amd64 (0.4.1-5 to 0.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: soapyuhd/amd64 uhd (not considered)
- Invalidated by dependency
- soapyuhd/arm64 (0.4.1-5 to 0.4.1-5)
- Migration status for soapyuhd/arm64 (0.4.1-5 to 0.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: soapyuhd/arm64 uhd (not considered)
- Invalidated by dependency
- 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:
- soapyuhd/armhf (0.4.1-5 to 0.4.1-5)
- Migration status for soapyuhd/armhf (0.4.1-5 to 0.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: soapyuhd/armhf uhd (not considered)
- Invalidated by dependency
- soapyuhd/i386 (0.4.1-5 to 0.4.1-5)
- Migration status for soapyuhd/i386 (0.4.1-5 to 0.4.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: soapyuhd/i386 uhd (not considered)
- Invalidated by dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: sox/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: spectools/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: sqlitebrowser/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ssdeep/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ssldump/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: sslh/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: sslsniff/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: sslsplit/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: statsprocessor/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- stegsnow/armel (20130616-8 to 20130616-8)
- Migration status for stegsnow/armel (20130616-8 to 20130616-8): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: stegsnow/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: stunnel4/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- subtitlecomposer/amd64 (0.8.1-2 to 0.8.1-2)
- Migration status for subtitlecomposer/amd64 (0.8.1-2 to 0.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- subtitlecomposer/arm64 (0.8.1-2 to 0.8.1-2)
- Migration status for subtitlecomposer/arm64 (0.8.1-2 to 0.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- subtitlecomposer/armhf (0.8.1-2 to 0.8.1-2)
- Migration status for subtitlecomposer/armhf (0.8.1-2 to 0.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- subtitlecomposer/i386 (0.8.1-2 to 0.8.1-2)
- Migration status for subtitlecomposer/i386 (0.8.1-2 to 0.8.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: subversion/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: sunxi-tools/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: t50/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- tatan/arm64 (1.0.dfsg2-1 to 1.0.dfsg2-1)
- Migration status for tatan/arm64 (1.0.dfsg2-1 to 1.0.dfsg2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: tatan/arm64 gcc-15 (not considered)
- Invalidated by dependency
- tatan/armhf (1.0.dfsg2-1 to 1.0.dfsg2-1)
- Migration status for tatan/armhf (1.0.dfsg2-1 to 1.0.dfsg2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: tatan/armhf gcc-15 (not considered)
- Invalidated by dependency
- tatan/i386 (1.0.dfsg2-1 to 1.0.dfsg2-1)
- Migration status for tatan/i386 (1.0.dfsg2-1 to 1.0.dfsg2-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: tatan/i386 gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: tcpick/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: tcptrace/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: testdisk/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- texmaker/amd64 (5.1.3+dfsg-3 to 5.1.3+dfsg-3)
- Migration status for texmaker/amd64 (5.1.3+dfsg-3 to 5.1.3+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- texmaker/arm64 (5.1.3+dfsg-3 to 5.1.3+dfsg-3)
- Migration status for texmaker/arm64 (5.1.3+dfsg-3 to 5.1.3+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- texmaker/armhf (5.1.3+dfsg-3 to 5.1.3+dfsg-3)
- Migration status for texmaker/armhf (5.1.3+dfsg-3 to 5.1.3+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- texmaker/i386 (5.1.3+dfsg-3 to 5.1.3+dfsg-3)
- Migration status for texmaker/i386 (5.1.3+dfsg-3 to 5.1.3+dfsg-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: tftp-hpa/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- thc-ipv6/armel (3.8-1 to 3.8-1)
- Migration status for thc-ipv6/armel (3.8-1 to 3.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: thc-ipv6/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: tiger/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: tightvnc/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- tilix/armhf (1.9.6-3 to 1.9.6-3)
- Migration status for tilix/armhf (1.9.6-3 to 1.9.6-3): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: tilix/armhf gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: time/armel samba (not considered)
- Invalidated by implicit-dependency
- 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)
- titanion/arm64 (0.3.dfsg1-8 to 0.3.dfsg1-8)
- Migration status for titanion/arm64 (0.3.dfsg1-8 to 0.3.dfsg1-8): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: titanion/arm64 gcc-15 (not considered)
- Invalidated by dependency
- titanion/armhf (0.3.dfsg1-8 to 0.3.dfsg1-8)
- Migration status for titanion/armhf (0.3.dfsg1-8 to 0.3.dfsg1-8): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: titanion/armhf gcc-15 (not considered)
- Invalidated by dependency
- titanion/i386 (0.3.dfsg1-8 to 0.3.dfsg1-8)
- Migration status for titanion/i386 (0.3.dfsg1-8 to 0.3.dfsg1-8): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: titanion/i386 gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: tmux/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: tmux/armel airgeddon (not considered)
- 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:
- torus-trooper/arm64 (0.22.dfsg1-14 to 0.22.dfsg1-14)
- Migration status for torus-trooper/arm64 (0.22.dfsg1-14 to 0.22.dfsg1-14): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: torus-trooper/arm64 gcc-15 (not considered)
- Invalidated by dependency
- torus-trooper/armhf (0.22.dfsg1-14 to 0.22.dfsg1-14)
- Migration status for torus-trooper/armhf (0.22.dfsg1-14 to 0.22.dfsg1-14): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: torus-trooper/armhf gcc-15 (not considered)
- Invalidated by dependency
- torus-trooper/i386 (0.22.dfsg1-14 to 0.22.dfsg1-14)
- Migration status for torus-trooper/i386 (0.22.dfsg1-14 to 0.22.dfsg1-14): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: torus-trooper/i386 gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: triggerhappy/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- tumiki-fighters/arm64 (0.2.dfsg1-10 to 0.2.dfsg1-10)
- Migration status for tumiki-fighters/arm64 (0.2.dfsg1-10 to 0.2.dfsg1-10): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: tumiki-fighters/arm64 gcc-15 (not considered)
- Invalidated by dependency
- tumiki-fighters/armhf (0.2.dfsg1-10 to 0.2.dfsg1-10)
- Migration status for tumiki-fighters/armhf (0.2.dfsg1-10 to 0.2.dfsg1-10): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: tumiki-fighters/armhf gcc-15 (not considered)
- Invalidated by dependency
- tumiki-fighters/i386 (0.2.dfsg1-10 to 0.2.dfsg1-10)
- Migration status for tumiki-fighters/i386 (0.2.dfsg1-10 to 0.2.dfsg1-10): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: tumiki-fighters/i386 gcc-15 (not considered)
- Invalidated by dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: udptunnel/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- uim/amd64 (1:1.9.6-1 to 1:1.9.6-1)
- Migration status for uim/amd64 (1:1.9.6-1 to 1:1.9.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- uim/arm64 (1:1.9.6-1 to 1:1.9.6-1)
- Migration status for uim/arm64 (1:1.9.6-1 to 1:1.9.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- uim/armhf (1:1.9.6-1 to 1:1.9.6-1)
- Migration status for uim/armhf (1:1.9.6-1 to 1:1.9.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- uim/i386 (1:1.9.6-1 to 1:1.9.6-1)
- Migration status for uim/i386 (1:1.9.6-1 to 1:1.9.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: unar/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- undbx/armel (0.21-4 to 0.21-4)
- Migration status for undbx/armel (0.21-4 to 0.21-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: undbx/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- unhide/armel (20240510-2 to 20240510-2)
- Migration status for unhide/armel (20240510-2 to 20240510-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: unhide/armel kali-meta (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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: upx-ucl/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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)
- val-and-rick/arm64 (0.1a.dfsg1-7 to 0.1a.dfsg1-7)
- Migration status for val-and-rick/arm64 (0.1a.dfsg1-7 to 0.1a.dfsg1-7): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: val-and-rick/arm64 gcc-15 (not considered)
- Invalidated by dependency
- val-and-rick/armhf (0.1a.dfsg1-7 to 0.1a.dfsg1-7)
- Migration status for val-and-rick/armhf (0.1a.dfsg1-7 to 0.1a.dfsg1-7): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: val-and-rick/armhf gcc-15 (not considered)
- Invalidated by dependency
- val-and-rick/i386 (0.1a.dfsg1-7 to 0.1a.dfsg1-7)
- Migration status for val-and-rick/i386 (0.1a.dfsg1-7 to 0.1a.dfsg1-7): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: val-and-rick/i386 gcc-15 (not considered)
- Invalidated by dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: vboot-utils/armel kali-meta (not considered)
- Invalidated by implicit-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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: vpnc/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: vulkan-loader/armel qtbase-opensource-src (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: vulkan-loader/armel gtk4 (not considered)
- Implicit dependency: vulkan-loader/armel qt6-base (not considered)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: winregfs/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- wipe/armel (0.24-10 to 0.24-10)
- Migration status for wipe/armel (0.24-10 to 0.24-10): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: wipe/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: wpa/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: x11-apps/armel legion (not considered)
- Invalidated by implicit-dependency
- 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:
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: xclip/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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): Will attempt migration (Any information below is purely informational)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: xfwm4/armel openjdk-21 (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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: xmount/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- xterm/armel (398-1 to 398-1)
- Migration status for xterm/armel (398-1 to 398-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: xterm/armel airgeddon (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: yara/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- 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:
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: zsh/armel kali-meta (not considered)
- Invalidated by implicit-dependency
- aioairzone (1.0.0-1 to 1.0.1-1)
- Migration status for aioairzone (1.0.0-1 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 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ansible-core (2.19.1-1 to 2.19.2-1)
- Migration status for ansible-core (2.19.1-1 to 2.19.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:
- audacity (3.7.3+dfsg-1 to 3.7.5+dfsg-1)
- Migration status for audacity (3.7.3+dfsg-1 to 3.7.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 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- bliss (0.77-3 to 0.77-4)
- Migration status for bliss (0.77-3 to 0.77-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 22 days old
- Additional info:
- brltty (6.8-2 to 6.8-3)
- Migration status for brltty (6.8-2 to 6.8-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 22 days old
- Depends: brltty liblouis
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for qemu: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- buici-clock (0.4.9.4+nmu2 to 0.4.9.4.2021+git20210423.e6fed84+ds-1)
- Migration status for buici-clock (0.4.9.4+nmu2 to 0.4.9.4.2021+git20210423.e6fed84+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)
- casacore (3.7.1-1 to 3.7.1-2)
- Migration status for casacore (3.7.1-1 to 3.7.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 22 days old
- Additional info:
- cccl (2.3.2-2 to 2.3.2-3)
- Migration status for cccl (2.3.2-2 to 2.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:
- cl-plus-ssl (20220328.git8b91648-6 to 20220328.git8b91648-7)
- Migration status for cl-plus-ssl (20220328.git8b91648-6 to 20220328.git8b91648-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 22 days old
- Additional info:
- commitizen (4.8.3-1 to 4.9.1-1)
- Migration status for commitizen (4.8.3-1 to 4.9.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)
- darktable (5.0.1-2 to 5.2.1-1)
- Migration status for darktable (5.0.1-2 to 5.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)
- dh-builtusing (0.0.7 to 0.0.8)
- Migration status for dh-builtusing (0.0.7 to 0.0.8): 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 dh-builtusing: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- efibootguard (0.20-2 to 0.21-1)
- Migration status for efibootguard (0.20-2 to 0.21-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)
- flatpak-builder (1.4.4-2 to 1.4.5-1)
- Migration status for flatpak-builder (1.4.4-2 to 1.4.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:
- folding-mode-el (0.0~git20240308.b27c4a1-2 to 0.0~git20250120.b82696b-1)
- Migration status for folding-mode-el (0.0~git20240308.b27c4a1-2 to 0.0~git20250120.b82696b-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)
- foma (1:0.10.0+s311.20240712-1 to 1:0.10.0+s311.20250909-1)
- Migration status for foma (1:0.10.0+s311.20240712-1 to 1:0.10.0+s311.20250909-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)
- geocode-glib (3.26.4-1 to 3.26.4-2)
- Migration status for geocode-glib (3.26.4-1 to 3.26.4-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 geocode-glib: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- ginac (1.8.8-1 to 1.8.9-1)
- Migration status for ginac (1.8.8-1 to 1.8.9-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)
- gmpc (11.8.16-22 to 11.8.16-23)
- Migration status for gmpc (11.8.16-22 to 11.8.16-23): 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)
- golang-github-puerkitobio-goquery (1.10.2-1 to 1.10.3-1)
- Migration status for golang-github-puerkitobio-goquery (1.10.2-1 to 1.10.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 22 days old
- Additional info:
- goobox (3.6.0-15 to 3.6.0-16)
- Migration status for goobox (3.6.0-15 to 3.6.0-16): 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 goobox: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- gource (0.54-1 to 0.55-2)
- Migration status for gource (0.54-1 to 0.55-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)
- gpm (1.20.7-11 to 1.20.7-12)
- Migration status for gpm (1.20.7-11 to 1.20.7-12): 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:
- graphql-core (3.2.6-1 to 3.2.6-2)
- Migration status for graphql-core (3.2.6-1 to 3.2.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:
- groonga-normalizer-mysql (1.2.8-1 to 1.2.9-1)
- Migration status for groonga-normalizer-mysql (1.2.8-1 to 1.2.9-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:
- gtkmm4.0 (4.18.0-1 to 4.19.1-4)
- Migration status for gtkmm4.0 (4.18.0-1 to 4.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 0 of 22 days old
- Depends: gtkmm4.0 gtk4 (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gtkmm4.0: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- gtksourceview5 (5.16.0-2 to 5.18.0-1)
- Migration status for gtksourceview5 (5.16.0-2 to 5.18.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:
- haskell-hashtables (1.3.1-2 to 1.4.2-1)
- Migration status for haskell-hashtables (1.3.1-2 to 1.4.2-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)
- haskell-parameterized-utils (2.1.9.0-1 to 2.1.9.0-2)
- Migration status for haskell-parameterized-utils (2.1.9.0-1 to 2.1.9.0-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)
- hass-nabucasa (1.1.0-1 to 1.1.1-1)
- Migration status for hass-nabucasa (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 0 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for hass-nabucasa: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- hatasmota (0.10.0-1 to 0.10.1-1)
- Migration status for hatasmota (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 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- identify (2.6.13-1 to 2.6.14-1)
- Migration status for identify (2.6.13-1 to 2.6.14-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)
- initramfs-tools (0.148.3 to 0.150)
- Migration status for initramfs-tools (0.148.3 to 0.150): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- ioquake3 (1.36+u20250901.45788d2+dfsg-1 to 1.36+u20250908.3d8979f+dfsg-1)
- Migration status for ioquake3 (1.36+u20250901.45788d2+dfsg-1 to 1.36+u20250908.3d8979f+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 22 days old
- Additional info:
- ipe-tools (1:7.2.29.1-1 to 1:7.2.29.1-2)
- Migration status for ipe-tools (1:7.2.29.1-1 to 1:7.2.29.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)
- irqbalance (1.9.4-1 to 1.9.4-3)
- Migration status for irqbalance (1.9.4-1 to 1.9.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)
- json-glib (1.10.6+ds-3 to 1.10.8+ds-1)
- Migration status for json-glib (1.10.6+ds-3 to 1.10.8+ds-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- jupyter-client (8.6.3-2 to 8.6.3-3)
- Migration status for jupyter-client (8.6.3-2 to 8.6.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 22 days old
- Additional info:
- kamailio (6.0.2-3 to 6.0.3-2)
- Migration status for kamailio (6.0.2-3 to 6.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 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- kid3 (3.9.6-3 to 3.9.7-1)
- Migration status for kid3 (3.9.6-3 to 3.9.7-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)
- kissat (4.0.3-1 to 4.0.3-2)
- Migration status for kissat (4.0.3-1 to 4.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 0 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for kissat: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- libace-perl (1.92-12 to 1.92-13)
- Migration status for libace-perl (1.92-12 to 1.92-13): 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:
- libfilter-perl (1.64-2 to 1.65-1)
- Migration status for libfilter-perl (1.64-2 to 1.65-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:
- libnginx-mod-rtmp (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-7)
- Migration status for libnginx-mod-rtmp (1:1.2.2+dfsg-6 to 1:1.2.2+dfsg-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 22 days old
- Depends: libnginx-mod-rtmp nginx (not considered)
- Additional info:
- libnss-mysql (1.6.1-3 to 1.6.1-5)
- Migration status for libnss-mysql (1.6.1-3 to 1.6.1-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)
- libpanel (1.10.0-1 to 1.10.2-1)
- Migration status for libpanel (1.10.0-1 to 1.10.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:
- libplacebo (7.349.0-3 to 7.351.0-2)
- Migration status for libplacebo (7.349.0-3 to 7.351.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 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ffmpeg: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- libssh (0.11.2-1 to 0.11.3-1)
- Migration status for libssh (0.11.2-1 to 0.11.3-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing libssh-dev/0.11.2-1/armel from kali-rolling makes libgvm-dev/22.24.0-1/armel uninstallable
- Too young, only 0 of 22 days old
- Additional info:
- libstb (0.0~git20241109.5c20573+ds-1 to 0.0~git20250907.fede005+ds-1)
- Migration status for libstb (0.0~git20241109.5c20573+ds-1 to 0.0~git20250907.fede005+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 22 days old
- Additional info:
- libxt (1:1.2.1-1.2 to 1:1.2.1-1.3)
- Migration status for libxt (1:1.2.1-1.2 to 1:1.2.1-1.3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- lighttpd (1.4.79-2 to 1.4.82-2)
- Migration status for lighttpd (1.4.79-2 to 1.4.82-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:
- limesuite (23.11.0+dfsg-3 to 23.11.0+dfsg-4)
- Migration status for limesuite (23.11.0+dfsg-3 to 23.11.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- lmbench (3.0-a9+debian.1-9 to 3.0-a9+debian.1-10)
- Migration status for lmbench (3.0-a9+debian.1-9 to 3.0-a9+debian.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)
- lollypop (1.4.42-1 to 1.4.44-1)
- Migration status for lollypop (1.4.42-1 to 1.4.44-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)
- lttng-modules (2.14.0-1 to 2.14.1-1)
- Migration status for lttng-modules (2.14.0-1 to 2.14.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 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for lttng-modules: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- mame (0.280+dfsg.1-2 to 0.280+dfsg.1-3)
- Migration status for mame (0.280+dfsg.1-2 to 0.280+dfsg.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)
- mapcode (2.5.5-7 to 2.5.6-1)
- Migration status for mapcode (2.5.5-7 to 2.5.6-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)
- maven-debian-helper (2.6.8 to 2.6.9)
- Migration status for maven-debian-helper (2.6.8 to 2.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)
- montage (6.1+dfsg-1 to 6.1+dfsg-2)
- Migration status for montage (6.1+dfsg-1 to 6.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 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for montage: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- ngtcp2 (1.11.0-1 to 1.15.1-1)
- Migration status for ngtcp2 (1.11.0-1 to 1.15.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- normality (3.0.1-1 to 3.0.2-1)
- Migration status for normality (3.0.1-1 to 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 0 of 22 days old
- Additional info:
- nwipe (0.38-1.1 to 0.39-1)
- Migration status for nwipe (0.38-1.1 to 0.39-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)
- nyquist (3.24+ds-1 to 3.24+ds-2)
- Migration status for nyquist (3.24+ds-1 to 3.24+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)
- ocaml-iter (1.9-1 to 1.9-2)
- Migration status for ocaml-iter (1.9-1 to 1.9-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:
- ocaml-qcheck (0.25-1 to 0.26-2)
- Migration status for ocaml-qcheck (0.25-1 to 0.26-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- octave-control (4.1.2-2 to 4.1.3-1)
- Migration status for octave-control (4.1.2-2 to 4.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 22 days old
- Additional info:
- ovn (25.03.0-1 to 25.09.0-1)
- Migration status for ovn (25.03.0-1 to 25.09.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ovn: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- pgformatter (5.7-1 to 5.8-1)
- Migration status for pgformatter (5.7-1 to 5.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 pgformatter: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- (20071108-4.1 to 20071108-5)
- Migration status for phpwebcounter-extra (20071108-4.1 to 20071108-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)
- postsrsd (1.10-2.2 to 2.0.11-1)
- Migration status for postsrsd (1.10-2.2 to 2.0.11-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)
- pygobject (3.50.0-4 to 3.50.0-6)
- Migration status for pygobject (3.50.0-4 to 3.50.0-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- pytest-relaxed (2.0.2-4 to 2.0.2-5)
- Migration status for pytest-relaxed (2.0.2-4 to 2.0.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 22 days old
- Additional info:
- python-biopython (1.85+dfsg-4 to 1.85+dfsg-5)
- Migration status for python-biopython (1.85+dfsg-4 to 1.85+dfsg-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:
- python-dbusmock (0.36.0-2 to 0.37.0-1)
- Migration status for python-dbusmock (0.36.0-2 to 0.37.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:
- python-expandvars (1.1.1-1 to 1.1.2-1)
- Migration status for python-expandvars (1.1.1-1 to 1.1.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:
- python-itemadapter (0.12.1-1 to 0.12.2-1)
- Migration status for python-itemadapter (0.12.1-1 to 0.12.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:
- python-jsmin (3.0.1-1 to 3.0.1-3)
- Migration status for python-jsmin (3.0.1-1 to 3.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 22 days old
- Additional info:
- python-packageurl (0.16.0-2 to 0.17.5-1)
- Migration status for python-packageurl (0.16.0-2 to 0.17.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:
- python-pygit2 (1.17.0-2 to 1.18.2-2)
- Migration status for python-pygit2 (1.17.0-2 to 1.18.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 22 days old
- Additional info:
- python-zeroconf (0.147.0-2 to 0.147.2-1)
- Migration status for python-zeroconf (0.147.0-2 to 0.147.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:
- pywayland (0.4.18-4 to 0.4.18-5)
- Migration status for pywayland (0.4.18-4 to 0.4.18-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 pywayland: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- qtwebengine-opensource-src (5.15.18+dfsg-2 to 5.15.19+dfsg-3)
- Migration status for qtwebengine-opensource-src (5.15.18+dfsg-2 to 5.15.19+dfsg-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- r-bioc-rhdf5lib (1.28.0+dfsg-2 to 1.28.0+dfsg-3)
- Migration status for r-bioc-rhdf5lib (1.28.0+dfsg-2 to 1.28.0+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 22 days old
- Additional info:
- racket-mode (20250828~git.172b7d4-1 to 20250830~git.f3952cd-1)
- Migration status for racket-mode (20250828~git.172b7d4-1 to 20250830~git.f3952cd-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 racket-mode: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- routine-update (0.2.3 to 0.2.4)
- Migration status for routine-update (0.2.3 to 0.2.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)
- rust-ammonia (4.0.0-3 to 4.1.1-1)
- Migration status for rust-ammonia (4.0.0-3 to 4.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 0 of 22 days old
- Additional info:
- rust-cargo-debstatus (0.6.3-2 to 0.6.5-1)
- Migration status for rust-cargo-debstatus (0.6.3-2 to 0.6.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)
- rust-gdk4 (0.9.6-2 to 0.10.0-3)
- Migration status for rust-gdk4 (0.9.6-2 to 0.10.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-gdk4-wayland-sys (0.9.6-2 to 0.10.0-3)
- Migration status for rust-gdk4-wayland-sys (0.9.6-2 to 0.10.0-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 22 days old
- Depends: rust-gdk4-wayland-sys gtk4 (not considered)
- Depends: rust-gdk4-wayland-sys rust-glib-sys
- Implicit dependency: rust-gdk4-wayland-sys rust-gdk4-wayland
- Additional info:
- rust-gsk4-sys (0.9.6-1 to 0.10.0-3)
- Migration status for rust-gsk4-sys (0.9.6-1 to 0.10.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-libbpf-cargo (0.25.0~beta.1-2 to 0.26.0~beta.1-1)
- Migration status for rust-libbpf-cargo (0.25.0~beta.1-2 to 0.26.0~beta.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 22 days old
- Depends: rust-libbpf-cargo rust-libbpf-rs
- Additional info:
- rust-libbpf-rs (0.25.0~beta.1-1 to 0.26.0~beta.1-1)
- Migration status for rust-libbpf-rs (0.25.0~beta.1-1 to 0.26.0~beta.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 22 days old
- Implicit dependency: rust-libbpf-rs rust-libbpf-cargo
- Additional info:
- rust-roaring (0.10.2-1 to 0.10.12-2)
- Migration status for rust-roaring (0.10.2-1 to 0.10.12-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 rust-roaring: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- rust-smol (2.0.2-5 to 2.0.2-6)
- Migration status for rust-smol (2.0.2-5 to 2.0.2-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 22 days old
- Additional info:
- samba (2:4.22.4+dfsg-1 to 2:4.23.0+dfsg-2)
- Migration status for samba (2:4.22.4+dfsg-1 to 2:4.23.0+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- shelldap (1.5.2-1 to 1.5.2-2)
- Migration status for shelldap (1.5.2-1 to 1.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 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for shelldap: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- sipgrep (2.2.0-2 to 2.2.0-3)
- Migration status for sipgrep (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 0 of 22 days old
- Additional info:
- sphinxcontrib-jquery (4.1-5 to 4.1-6)
- Migration status for sphinxcontrib-jquery (4.1-5 to 4.1-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 22 days old
- Additional info:
- splash (3.11.4-1 to 3.11.5-1)
- Migration status for splash (3.11.4-1 to 3.11.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)
- streamripper (1.64.6-2 to 1.64.6-3)
- Migration status for streamripper (1.64.6-2 to 1.64.6-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)
- stterm (0.9.2-1 to 0.9.3-1)
- Migration status for stterm (0.9.2-1 to 0.9.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 22 days old
- Additional info:
- surf-display (0.0.5-2 to 0.0.5-3)
- Migration status for surf-display (0.0.5-2 to 0.0.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- systemd-cron (2.5.1-2 to 2.6.0-1)
- Migration status for systemd-cron (2.5.1-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 0 of 22 days old
- Additional info:
- theme-d (7.0.0-1 to 7.1.0-1)
- Migration status for theme-d (7.0.0-1 to 7.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 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- theme-d-intr (0.20.0-1 to 0.20.1-1)
- Migration status for theme-d-intr (0.20.0-1 to 0.20.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
- Depends: theme-d-intr theme-d
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- tinyexr (1.0.10+dfsg-1 to 1.0.12+dfsg-1)
- Migration status for tinyexr (1.0.10+dfsg-1 to 1.0.12+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 22 days old
- Additional info:
- tinygltf (2.9.5+dfsg-1 to 2.9.6+dfsg-1)
- Migration status for tinygltf (2.9.5+dfsg-1 to 2.9.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 0 of 22 days old
- Additional info:
- tk-table (2.10.8-2 to 2.10.8-3)
- Migration status for tk-table (2.10.8-2 to 2.10.8-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 22 days old
- Additional info:
- tlswrapper (0~20250201-1 to 0~20250201-2)
- Migration status for tlswrapper (0~20250201-1 to 0~20250201-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 tlswrapper: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- tree-sitter (0.22.6-6 to 0.22.6-8)
- Migration status for tree-sitter (0.22.6-6 to 0.22.6-8): 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:
- tsocks (1.8beta5+ds1-3 to 1.8beta5+ds1-4)
- Migration status for tsocks (1.8beta5+ds1-3 to 1.8beta5+ds1-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)
- uwsgi (2.0.29-1 to 2.0.30-1)
- Migration status for uwsgi (2.0.29-1 to 2.0.30-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:
- vlfeat (0.9.21+full-2.1 to 0.9.21+full-3)
- Migration status for vlfeat (0.9.21+full-2.1 to 0.9.21+full-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)
- xchpst (0.6.2-1 to 0.7.0-1)
- Migration status for xchpst (0.6.2-1 to 0.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 0 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for xchpst: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- xjadeo (0.8.14+really0.8.14-1 to 0.8.14+really0.8.14-3)
- Migration status for xjadeo (0.8.14+really0.8.14-1 to 0.8.14+really0.8.14-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)
- xlax (2.4-2 to 2.4-3)
- Migration status for xlax (2.4-2 to 2.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)
- xloadimage (4.1-26 to 4.1-27)
- Migration status for xloadimage (4.1-26 to 4.1-27): 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)
- xmlrpc-c (1.59.03-10 to 1.59.03-10.1)
- Migration status for xmlrpc-c (1.59.03-10 to 1.59.03-10.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)
- xmountains (2.11-3 to 2.15-1)
- Migration status for xmountains (2.11-3 to 2.15-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)
- xnee (3.19-9.2 to 3.19-9.4)
- Migration status for xnee (3.19-9.2 to 3.19-9.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 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for wmanager: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- zigpy-deconz (0.25.1-1 to 0.25.2-1)
- Migration status for zigpy-deconz (0.25.1-1 to 0.25.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 zigpy-deconz: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- znc (1.9.1-2 to 1.10.1-1)
- Migration status for znc (1.9.1-2 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 0 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- afflib (3.7.21-1 to 3.7.22-1)
- Migration status for afflib (3.7.21-1 to 3.7.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
- Implicit dependency: afflib kali-meta (not considered)
- Additional info:
- aiohappyeyeballs (2.6.1-1 to 2.6.1-2)
- Migration status for aiohappyeyeballs (2.6.1-1 to 2.6.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 aiohappyeyeballs/2.6.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- airgeddon (11.51-0kali1 to 11.52-0kali1)
- Migration status for airgeddon (11.51-0kali1 to 11.52-0kali1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- missing build on armel
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- aisleriot (1:3.22.35-1 to 1:3.22.35-2)
- Migration status for aisleriot (1:3.22.35-1 to 1:3.22.35-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)
- ansible (12.0.0~b5+dfsg-1 to 12.0.0+dfsg-1)
- Migration status for ansible (12.0.0~b5+dfsg-1 to 12.0.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ansible/12.0.0+dfsg-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- apertium-eval-translator (1.2.1-3 to 1.2.2-1)
- Migration status for apertium-eval-translator (1.2.1-3 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)
- apertium-get (1.0.0-3 to 1.0.2-1)
- Migration status for apertium-get (1.0.0-3 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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- apostrophe (3.2-3 to 3.2-4)
- Migration status for apostrophe (3.2-3 to 3.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)
- aspell-en (2020.12.07-0-1 to 2020.12.07-0-1.1)
- Migration status for aspell-en (2020.12.07-0-1 to 2020.12.07-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)
- astroscrappy (1.2.0-1 to 1.2.0-2)
- Migration status for astroscrappy (1.2.0-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
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for astroscrappy/1.2.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- babl (1:0.1.114-2 to 1:0.1.114-3)
- Migration status for babl (1:0.1.114-2 to 1:0.1.114-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:
- binutils (2.45-4 to 2.45-7)
- Migration status for binutils (2.45-4 to 2.45-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- bluemaestro-ble (0.4.1-1 to 1.0.0-1)
- Migration status for bluemaestro-ble (0.4.1-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)
- autopkgtest for bluemaestro-ble/1.0.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- brian (2.8.0.4-1 to 2.9.0-2)
- Migration status for brian (2.8.0.4-1 to 2.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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for brian/2.9.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- btrfs-progs (6.16-1 to 6.16-2)
- Migration status for btrfs-progs (6.16-1 to 6.16-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)
- bucardo (5.6.0-4 to 5.6.0-6)
- Migration status for bucardo (5.6.0-4 to 5.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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for bucardo/5.6.0-6: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- buildtorrent (0.9.1-2 to 0.9.1-3)
- Migration status for buildtorrent (0.9.1-2 to 0.9.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)
- bustle (0.11.0-2 to 0.12.0-3)
- Migration status for bustle (0.11.0-2 to 0.12.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)
- butt (1.45.0-1 to 1.45.0-1.1)
- Migration status for butt (1.45.0-1 to 1.45.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 butt/1.45.0-1.1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- cacti-spine (1.2.30-1 to 1.2.30-2)
- Migration status for cacti-spine (1.2.30-1 to 1.2.30-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)
- caido (0.49.0-0kali1 to 0.51.1-0kali1)
- Migration status for caido (0.49.0-0kali1 to 0.51.1-0kali1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- missing build on armel
- missing build on armhf
- missing build on i386
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- caido-cli (0.49.0-0kali1 to 0.51.1-0kali1)
- Migration status for caido-cli (0.49.0-0kali1 to 0.51.1-0kali1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- missing build on armel
- missing build on armhf
- missing build on i386
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- cardpeek (0.8.4-3 to 0.8.4-5)
- Migration status for cardpeek (0.8.4-3 to 0.8.4-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)
- cdtool (2.1.8-release-8 to 2.1.8-release-9)
- Migration status for cdtool (2.1.8-release-8 to 2.1.8-release-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)
- cenon.app (4.0.6+ds1-5 to 4.0.6+ds1-6)
- Migration status for cenon.app (4.0.6+ds1-5 to 4.0.6+ds1-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)
- cgreen (1.6.4-1 to 1.6.4-2)
- Migration status for cgreen (1.6.4-1 to 1.6.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:
- chromium (140.0.7339.80-1 to 140.0.7339.127-1)
- Migration status for chromium (140.0.7339.80-1 to 140.0.7339.127-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)
- cli11 (2.4.1+ds-2 to 2.5.0+ds-1)
- Migration status for cli11 (2.4.1+ds-2 to 2.5.0+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 cli11/2.5.0+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- cmor (3.11.0-2 to 3.12.0-1)
- Migration status for cmor (3.11.0-2 to 3.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- collada-dom (2.5.0+ds1-3 to 2.5.0+ds1-4)
- Migration status for collada-dom (2.5.0+ds1-3 to 2.5.0+ds1-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)
- crawl (2:0.28.0-1.1 to 2:0.33.1-1)
- Migration status for crawl (2:0.28.0-1.1 to 2:0.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)
- cruft-ng (0.9.72 to 0.9.74)
- Migration status for cruft-ng (0.9.72 to 0.9.74): Waiting for test results or another package, or too young (no action required now - check later)
- 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 cruft-ng/0.9.74: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- cuneiform (1.1.0+dfsg-12 to 1.1.0+dfsg-13)
- Migration status for cuneiform (1.1.0+dfsg-12 to 1.1.0+dfsg-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 cuneiform/1.1.0+dfsg-13: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- dbus-fast (2.44.1-1 to 2.44.3-1)
- Migration status for dbus-fast (2.44.1-1 to 2.44.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 22 days old
- Additional info:
- dclock (2.2.2-15 to 2.2.2-16)
- Migration status for dclock (2.2.2-15 to 2.2.2-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)
- dconf-editor (45.0.1-2 to 49~rc-1)
- Migration status for dconf-editor (45.0.1-2 to 49~rc-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)
- ddcui (0.6.0-4 to 0.6.0-5)
- Migration status for ddcui (0.6.0-4 to 0.6.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)
- ddcutil (2.2.1-4 to 2.2.1-5)
- Migration status for ddcutil (2.2.1-4 to 2.2.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)
- deal (3.1.9-13 to 3.1.9-14)
- Migration status for deal (3.1.9-13 to 3.1.9-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)
- autopkgtest for deal/3.1.9-14: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- debian-edu-artwork-legacy (20220131-1 to 20220131-1.1)
- Migration status for debian-edu-artwork-legacy (20220131-1 to 20220131-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)
- deviceinfo (0.2.3-3 to 0.2.4-1)
- Migration status for deviceinfo (0.2.3-3 to 0.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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- dh-fortran-mod (0.43 to 0.45)
- Migration status for dh-fortran-mod (0.43 to 0.45): Waiting for test results or another package, or too young (no action required now - check later)
- 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 dh-fortran-mod/0.45: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- dia (0.98+git20250126-2 to 0.98+git20250827-2)
- Migration status for dia (0.98+git20250126-2 to 0.98+git20250827-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 dia/0.98+git20250827-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- dijitso (2019.2.0~git20190418.c92dcb0-4 to 2019.2.0~git20190418.c92dcb0-5)
- Migration status for dijitso (2019.2.0~git20190418.c92dcb0-4 to 2019.2.0~git20190418.c92dcb0-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 dijitso/2019.2.0~git20190418.c92dcb0-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- dislocker (0.7.3+git20240607-3 to 0.7.3+git20250907-1)
- Migration status for dislocker (0.7.3+git20240607-3 to 0.7.3+git20250907-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:
- django-graphiql-debug-toolbar (0.2.0-7 to 0.2.0-8)
- Migration status for django-graphiql-debug-toolbar (0.2.0-7 to 0.2.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)
- autopkgtest for django-graphiql-debug-toolbar/0.2.0-8: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- django-htmx (1.23.2-2 to 1.24.1-1)
- Migration status for django-htmx (1.23.2-2 to 1.24.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 django-htmx/1.24.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- django-rich (2.0.0-1 to 2.1.0-1)
- Migration status for django-rich (2.0.0-1 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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for django-rich/2.1.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- djangorestframework (3.16.0-1 to 3.16.1-1)
- Migration status for djangorestframework (3.16.0-1 to 3.16.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 djangorestframework/3.16.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- dlt-daemon (2.18.10-10 to 2.18.10-12)
- Migration status for dlt-daemon (2.18.10-10 to 2.18.10-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)
- dmz-cursor-theme (0.4.5.2 to 0.4.5.3)
- Migration status for dmz-cursor-theme (0.4.5.2 to 0.4.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)
- dnsdist (2.0.0-3 to 2.0.0-6)
- Migration status for dnsdist (2.0.0-3 to 2.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)
- (20241201-5 to 20241201-6)
- Migration status for dokuwiki-plugins-extra (20241201-5 to 20241201-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)
- (20241201-5 to 20241201-6)
- Migration status for dokuwiki-templates-extra (20241201-5 to 20241201-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)
- dsniff (2.4b1+debian-34 to 2.4b1+debian-35)
- Migration status for dsniff (2.4b1+debian-34 to 2.4b1+debian-35): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- missing build on armel
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- dvbstreamer (2.1.0-5.7 to 2.1.0-5.8)
- Migration status for dvbstreamer (2.1.0-5.7 to 2.1.0-5.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)
- emacs-oauth2 (0.18.2-1 to 0.18.3-1)
- Migration status for emacs-oauth2 (0.18.2-1 to 0.18.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 emacs-oauth2/0.18.3-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- eog (47.0-2 to 47.0-3)
- Migration status for eog (47.0-2 to 47.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)
- fangfrisch (1.9.0-3 to 1.9.2-1)
- Migration status for fangfrisch (1.9.0-3 to 1.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 fangfrisch/1.9.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- fcitx5 (5.1.14-1 to 5.1.14-3)
- Migration status for fcitx5 (5.1.14-1 to 5.1.14-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)
- fcitx5-m17n (5.1.4-1 to 5.1.4-2)
- Migration status for fcitx5-m17n (5.1.4-1 to 5.1.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
- Depends: fcitx5-m17n m17n-lib
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- fdm (- to 2.2+git20250202-3)
- Migration status for fdm (- to 2.2+git20250202-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)
- feh (3.11.1-1 to 3.11.2-1)
- Migration status for feh (3.11.1-1 to 3.11.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 feh/3.11.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- flann (1.9.2+dfsg-2 to 1.9.2+dfsg-3)
- Migration status for flann (1.9.2+dfsg-2 to 1.9.2+dfsg-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)
- fonts-nafees (1.2-6 to 1.2-7)
- Migration status for fonts-nafees (1.2-6 to 1.2-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)
- fortunes-it (2.16-2 to 2.17-1)
- Migration status for fortunes-it (2.16-2 to 2.17-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)
- freediameter (1.5.0-1 to 1.5.0-2)
- Migration status for freediameter (1.5.0-1 to 1.5.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 freediameter/1.5.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- freefilesync (13.7-1 to 13.7-2)
- Migration status for freefilesync (13.7-1 to 13.7-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)
- frotz (2.55+dfsg-2 to 2.55+dfsg-3)
- Migration status for frotz (2.55+dfsg-2 to 2.55+dfsg-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)
- fsearch (0.2.3-5 to 0.2.3-6)
- Migration status for fsearch (0.2.3-5 to 0.2.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)
- funtools (1.4.8-1.1 to 1.4.8-2)
- Migration status for funtools (1.4.8-1.1 to 1.4.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)
- furo (2025.07.19+dfsg-1 to 2025.07.19+dfsg-2)
- Migration status for furo (2025.07.19+dfsg-1 to 2025.07.19+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)
- fwupd (2.0.13-2 to 2.0.16-1)
- Migration status for fwupd (2.0.13-2 to 2.0.16-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: fwupd gnome-software (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for fwupd/2.0.16-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- gedit (48.1-4 to 48.1-5)
- Migration status for gedit (48.1-4 to 48.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 22 days old
- Additional info:
- gegl (1:0.4.62-2 to 1:0.4.62-3)
- Migration status for gegl (1:0.4.62-2 to 1:0.4.62-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:
- gexiv2 (0.14.6-1 to 0.14.6-2)
- Migration status for gexiv2 (0.14.6-1 to 0.14.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:
- gimp (3.0.4-4 to 3.0.4-6)
- Migration status for gimp (3.0.4-4 to 3.0.4-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:
- glycin (1.2.1+ds-3 to 2.0~rc+ds-2)
- Migration status for glycin (1.2.1+ds-3 to 2.0~rc+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
- Implicit dependency: glycin loupe (not considered)
- Additional info:
- glyr (1.0.10-2.1 to 1.0.10-3)
- Migration status for glyr (1.0.10-2.1 to 1.0.10-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:
- gnome-2048 (3.38.2-5 to 3.38.2-6)
- Migration status for gnome-2048 (3.38.2-5 to 3.38.2-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)
- gnome-contacts (48.0-2 to 48.0-3)
- Migration status for gnome-contacts (48.0-2 to 48.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)
- gnome-online-accounts (3.54.5-1 to 3.55.2-1)
- Migration status for gnome-online-accounts (3.54.5-1 to 3.55.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- (20250312-1 to 20250312-2)
- Migration status for gnome-shell-extensions-extra (20250312-1 to 20250312-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)
- gnome-sudoku (1:48.1-1 to 1:49~rc-1)
- Migration status for gnome-sudoku (1:48.1-1 to 1:49~rc-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)
- gnome-text-editor (48.3-3 to 48.3-4)
- Migration status for gnome-text-editor (48.3-3 to 48.3-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- gnome-tweaks (49~rc-1 to 49~rc-2)
- Migration status for gnome-tweaks (49~rc-1 to 49~rc-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)
- gnome-user-share (48.1-1 to 48.1-3)
- Migration status for gnome-user-share (48.1-1 to 48.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)
- gnome-weather (48.0-2 to 48.0-3)
- Migration status for gnome-weather (48.0-2 to 48.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)
- golang-1.25 (- to 1.25.0-1)
- Migration status for golang-1.25 (- to 1.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)
- autopkgtest for golang-1.25/1.25.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-bitbucket-pkg-inflect (0.0~hg20130829.20.8961c37-6.1 to 0.0.2-1)
- Migration status for golang-bitbucket-pkg-inflect (0.0~hg20130829.20.8961c37-6.1 to 0.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)
- autopkgtest for golang-bitbucket-pkg-inflect/0.0.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-14rcole-gopopulate (0.0~git20171207.91c73a7-1.1 to 0.0~git20180821.b175b21-1)
- Migration status for golang-github-14rcole-gopopulate (0.0~git20171207.91c73a7-1.1 to 0.0~git20180821.b175b21-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-14rcole-gopopulate/0.0~git20180821.b175b21-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-alecthomas-colour (0.0~git20160524.60882d9-1.1 to 0.0~git20191101.a1c6bd8-1)
- Migration status for golang-github-alecthomas-colour (0.0~git20160524.60882d9-1.1 to 0.0~git20191101.a1c6bd8-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-alecthomas-colour/0.0~git20191101.a1c6bd8-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-containerd-plugin (- to 1.0.0-1)
- Migration status for golang-github-containerd-plugin (- 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)
- autopkgtest for golang-github-containerd-plugin/1.0.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-dchest-bcrypt-pbkdf (- to 0.0~git20150205.83f37f9-1)
- Migration status for golang-github-dchest-bcrypt-pbkdf (- to 0.0~git20150205.83f37f9-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-dchest-bcrypt-pbkdf/0.0~git20150205.83f37f9-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-holiman-uint256 (- to 1.3.2-1)
- Migration status for golang-github-holiman-uint256 (- to 1.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 golang-github-holiman-uint256/1.3.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-huandu-go-clone (- to 1.6.0-1)
- Migration status for golang-github-huandu-go-clone (- 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 golang-github-huandu-go-clone/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
- golang-github-influxdata-toml (0.0~git20160905.0.ad49a5c-1.1 to 0.0~git20180607.2a2e301-1)
- Migration status for golang-github-influxdata-toml (0.0~git20160905.0.ad49a5c-1.1 to 0.0~git20180607.2a2e301-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-influxdata-toml/0.0~git20180607.2a2e301-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-jacobsa-fuse (0.0~git20150806.0.9a7512a-4 to 0.0~git20250829.cbc61fa-1)
- Migration status for golang-github-jacobsa-fuse (0.0~git20150806.0.9a7512a-4 to 0.0~git20250829.cbc61fa-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-jacobsa-fuse/0.0~git20250829.cbc61fa-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-jacobsa-gcloud (0.0~git20150709-3 to 0.0~git20240721.15c4fa4-1)
- Migration status for golang-github-jacobsa-gcloud (0.0~git20150709-3 to 0.0~git20240721.15c4fa4-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-jacobsa-gcloud/0.0~git20240721.15c4fa4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-jacobsa-oglematchers (0.0~git20150320-3 to 0.0~git20150720.141901e-1)
- Migration status for golang-github-jacobsa-oglematchers (0.0~git20150320-3 to 0.0~git20150720.141901e-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-jacobsa-oglematchers/0.0~git20150720.141901e-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-jacobsa-oglemock (0.0~git20150428-5 to 0.0~git20150831.e94d794-1)
- Migration status for golang-github-jacobsa-oglemock (0.0~git20150428-5 to 0.0~git20150831.e94d794-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-jacobsa-oglemock/0.0~git20150831.e94d794-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-jacobsa-reqtrace (0.0~git20150505-6 to 0.0~git20150505-7)
- Migration status for golang-github-jacobsa-reqtrace (0.0~git20150505-6 to 0.0~git20150505-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 golang-github-jacobsa-reqtrace/0.0~git20150505-7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-jacobsa-timeutil (0.0~git20150615-2 to 0.0~git20170205-1)
- Migration status for golang-github-jacobsa-timeutil (0.0~git20150615-2 to 0.0~git20170205-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-jacobsa-timeutil/0.0~git20170205-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-jacobsa-util (0.0~git20150504-2 to 0.0~git20150810-1)
- Migration status for golang-github-jacobsa-util (0.0~git20150504-2 to 0.0~git20150810-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-jacobsa-util/0.0~git20150810-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-jeremywohl-flatten (- to 1.0.1-1)
- Migration status for golang-github-jeremywohl-flatten (- 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 golang-github-jeremywohl-flatten/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
- golang-github-johanneskaufmann-html-to-markdown (2.3.1-1 to 2.4.0-1)
- Migration status for golang-github-johanneskaufmann-html-to-markdown (2.3.1-1 to 2.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:
- golang-github-pingcap-kvproto (- to 6.1.0~alpha-1)
- Migration status for golang-github-pingcap-kvproto (- to 6.1.0~alpha-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-pingcap-kvproto/6.1.0~alpha-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-pkg-xattr (0.4.10-1 to 0.4.12-1)
- Migration status for golang-github-pkg-xattr (0.4.10-1 to 0.4.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 golang-github-pkg-xattr/0.4.12-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-samalba-dockerclient (0.0~git20160531.0.a303626-2 to 0.0~git20160531.0.a303626-3)
- Migration status for golang-github-samalba-dockerclient (0.0~git20160531.0.a303626-2 to 0.0~git20160531.0.a303626-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 golang-github-samalba-dockerclient/0.0~git20160531.0.a303626-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-github-sethvargo-go-password (- to 0.3.1-1)
- Migration status for golang-github-sethvargo-go-password (- 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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-github-sethvargo-go-password/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
- golang-github-vaughan0-go-ini (0.0~git20130923.0.a98ad7e-3 to 0.0~git20130923.0.a98ad7e-4)
- Migration status for golang-github-vaughan0-go-ini (0.0~git20130923.0.a98ad7e-3 to 0.0~git20130923.0.a98ad7e-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 golang-github-vaughan0-go-ini/0.0~git20130923.0.a98ad7e-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-go-cache (0.0~git20150304-2 to 0.0~git20191004-1)
- Migration status for golang-go-cache (0.0~git20150304-2 to 0.0~git20191004-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-go-cache/0.0~git20191004-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- golang-gocolorize (1.0.0-3 to 1.0.0-4)
- Migration status for golang-gocolorize (1.0.0-3 to 1.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
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for golang-gocolorize/1.0.0-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- gr-hpsdr (3.0-2 to 3.10-1)
- Migration status for gr-hpsdr (3.0-2 to 3.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)
- grandorgue (3.16.0-1 to 3.16.1-1)
- Migration status for grandorgue (3.16.0-1 to 3.16.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)
- gtk4 (4.18.6+ds-2 to 4.20.1+ds-2)
- Migration status for gtk4 (4.18.6+ds-2 to 4.20.1+ds-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- gucharmap (1:15.1.5-1 to 1:16.0.2-3)
- Migration status for gucharmap (1:15.1.5-1 to 1:16.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
- Additional info:
- habluetooth (5.3.1-1 to 5.6.2-1)
- Migration status for habluetooth (5.3.1-1 to 5.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 habluetooth/5.6.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- hdapsd (1:20141203-3 to 1:20250908-1)
- Migration status for hdapsd (1:20141203-3 to 1:20250908-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)
- hsqldb1.8.0 (1.8.0.10+dfsg-12.1 to 1.8.0.10+dfsg-14)
- Migration status for hsqldb1.8.0 (1.8.0.10+dfsg-12.1 to 1.8.0.10+dfsg-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 22 days old
- Additional info:
- httptunnel (3.3+dfsg-5 to 3.3+dfsg-6)
- Migration status for httptunnel (3.3+dfsg-5 to 3.3+dfsg-6): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing httptunnel/3.3+dfsg-5/armel from kali-rolling makes offsec-pwk/2025.3.0/armel uninstallable
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- icom (20120228-6 to 20120228-7)
- Migration status for icom (20120228-6 to 20120228-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)
- icon (9.5.24b-1 to 9.5.25a-1)
- Migration status for icon (9.5.24b-1 to 9.5.25a-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)
- ijs (0.35-15.3 to 0.35-16)
- Migration status for ijs (0.35-15.3 to 0.35-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)
- imhex-patterns (1.35.4-0kali1 to 1.37.4-0kali1)
- Migration status for imhex-patterns (1.35.4-0kali1 to 1.37.4-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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ink (0.5.3-6 to 0.5.3-7)
- Migration status for ink (0.5.3-6 to 0.5.3-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:
- inkscape (1.4-6 to 1.4.2-3)
- Migration status for inkscape (1.4-6 to 1.4.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)
- ipython (8.35.0-1 to 8.35.0-2)
- Migration status for ipython (8.35.0-1 to 8.35.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:
- irstlm (6.00.05-6 to 6.00.05-7)
- Migration status for irstlm (6.00.05-6 to 6.00.05-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)
- jlha-utils (0.1.6-5 to 0.1.6-6)
- Migration status for jlha-utils (0.1.6-5 to 0.1.6-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 jlha-utils/0.1.6-6: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- jzip (210r20001005d-5 to 210r20001005d-6)
- Migration status for jzip (210r20001005d-5 to 210r20001005d-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)
- kcov (43+dfsg-1 to 43+dfsg-2)
- Migration status for kcov (43+dfsg-1 to 43+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)
- autopkgtest for kcov/43+dfsg-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- keepass2-plugin-keepassrpc (2.0.2+dfsg2-2 to 2.0.2+dfsg2-3)
- Migration status for keepass2-plugin-keepassrpc (2.0.2+dfsg2-2 to 2.0.2+dfsg2-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)
- koules (1.4-28 to 1.4-29)
- Migration status for koules (1.4-28 to 1.4-29): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- lcdproc (0.5.9-7 to 0.5.9-8)
- Migration status for lcdproc (0.5.9-7 to 0.5.9-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)
- lcov (2.3.1-1 to 2.3.2-1)
- Migration status for lcov (2.3.1-1 to 2.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)
- legion (0.4.3-0kali7 to 0.4.7-0kali2)
- Migration status for legion (0.4.3-0kali7 to 0.4.7-0kali2): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- missing build on armel
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- levee (4.0-2 to 4.0-3)
- Migration status for levee (4.0-2 to 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)
- libauthen-smb-perl (0.91-8 to 0.91-9)
- Migration status for libauthen-smb-perl (0.91-8 to 0.91-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 libauthen-smb-perl/0.91-9: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libccp4 (8.0.0-4 to 8.0.0-5)
- Migration status for libccp4 (8.0.0-4 to 8.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)
- libcsfml (3.0.0~rc2-2 to 3.0.0~rc3-1)
- Migration status for libcsfml (3.0.0~rc2-2 to 3.0.0~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)
- autopkgtest for libcsfml/3.0.0~rc3-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libdate-calc-xs-perl (6.4-2 to 6.4-3)
- Migration status for libdate-calc-xs-perl (6.4-2 to 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 libdate-calc-xs-perl/6.4-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libdc1394 (2.2.6-5 to 2.2.6-6)
- Migration status for libdc1394 (2.2.6-5 to 2.2.6-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)
- libdex (0.10.1-1 to 1.0.0-1)
- Migration status for libdex (0.10.1-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
- Implicit dependency: libdex sysprof (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libei (1.5.0-1 to 1.5.0-2)
- Migration status for libei (1.5.0-1 to 1.5.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 libei/1.5.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libfiu (1.2-3 to 1.2-4)
- Migration status for libfiu (1.2-3 to 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)
- autopkgtest for libfiu/1.2-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libgdf (0.1.3-11.1 to 0.1.3-12)
- Migration status for libgdf (0.1.3-11.1 to 0.1.3-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)
- autopkgtest for libgdf/0.1.3-12: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libgedit-amtk (5.9.1-1 to 5.9.1-2)
- Migration status for libgedit-amtk (5.9.1-1 to 5.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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libgepub (0.7.3-1 to 0.7.3-2)
- Migration status for libgepub (0.7.3-1 to 0.7.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 libgepub/0.7.3-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libgweather4 (4.4.4-1 to 4.4.4-3)
- Migration status for libgweather4 (4.4.4-1 to 4.4.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)
- libgxps (0.3.2-4 to 0.3.2-5)
- Migration status for libgxps (0.3.2-4 to 0.3.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)
- libhx (4.26-1 to 4.27-1)
- Migration status for libhx (4.26-1 to 4.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libhx/4.27-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libigloo (0.9.2-1.1 to 0.9.4-1)
- Migration status for libigloo (0.9.2-1.1 to 0.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)
- libjson-xs-perl (4.030-2 to 4.040-1)
- Migration status for libjson-xs-perl (4.030-2 to 4.040-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 libjson-xs-perl/4.040-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- liblouis (3.33.0-1 to 3.35.0-2)
- Migration status for liblouis (3.33.0-1 to 3.35.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 liblouis/3.35.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnet-interface-perl (1.016-3 to 1.016-4)
- Migration status for libnet-interface-perl (1.016-3 to 1.016-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 libnet-interface-perl/1.016-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-http-cache-purge (1:2.5.3-3 to 1:2.5.3-4)
- Migration status for libnginx-mod-http-cache-purge (1:2.5.3-3 to 1:2.5.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
- Depends: libnginx-mod-http-cache-purge nginx (not considered)
- Implicit dependency: libnginx-mod-http-cache-purge nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-cache-purge/1:2.5.3-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-http-dav-ext (1:3.0.0-6 to 1:3.0.0-7)
- Migration status for libnginx-mod-http-dav-ext (1:3.0.0-6 to 1:3.0.0-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
- Depends: libnginx-mod-http-dav-ext nginx (not considered)
- Implicit dependency: libnginx-mod-http-dav-ext nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-dav-ext/1:3.0.0-7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-http-echo (1:0.63-7 to 1:0.63-8)
- Migration status for libnginx-mod-http-echo (1:0.63-7 to 1:0.63-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
- Depends: libnginx-mod-http-echo nginx (not considered)
- Implicit dependency: libnginx-mod-http-echo nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-echo/1:0.63-8: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-http-fancyindex (1:0.5.2-6 to 1:0.5.2-7)
- Migration status for libnginx-mod-http-fancyindex (1:0.5.2-6 to 1:0.5.2-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
- Depends: libnginx-mod-http-fancyindex nginx (not considered)
- Implicit dependency: libnginx-mod-http-fancyindex nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-fancyindex/1:0.5.2-7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-http-geoip2 (1:3.4-6 to 1:3.4-7)
- Migration status for libnginx-mod-http-geoip2 (1:3.4-6 to 1:3.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
- Depends: libnginx-mod-http-geoip2 nginx (not considered)
- Implicit dependency: libnginx-mod-http-geoip2 nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-geoip2/1:3.4-7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- (1:0.39-1 to 1:0.39-2)
- Migration status for libnginx-mod-http-headers-more-filter (1:0.39-1 to 1:0.39-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: libnginx-mod-http-headers-more-filter nginx (not considered)
- Implicit dependency: libnginx-mod-http-headers-more-filter nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-headers-more-filter/1:0.39-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-http-ndk (1:0.3.4-2 to 1:0.3.4-4)
- Migration status for libnginx-mod-http-ndk (1:0.3.4-2 to 1:0.3.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
- Depends: libnginx-mod-http-ndk nginx (not considered)
- Implicit dependency: libnginx-mod-http-ndk libnginx-mod-http-lua
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-ndk/1:0.3.4-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-http-subs-filter (1:0.6.4-7 to 1:0.6.4-8)
- Migration status for libnginx-mod-http-subs-filter (1:0.6.4-7 to 1:0.6.4-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
- Depends: libnginx-mod-http-subs-filter nginx (not considered)
- Implicit dependency: libnginx-mod-http-subs-filter nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-subs-filter/1:0.6.4-8: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-http-uploadprogress (1:0.9.4-2 to 1:0.9.4-3)
- Migration status for libnginx-mod-http-uploadprogress (1:0.9.4-2 to 1:0.9.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
- Depends: libnginx-mod-http-uploadprogress nginx (not considered)
- Implicit dependency: libnginx-mod-http-uploadprogress nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-uploadprogress/1:0.9.4-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-http-upstream-fair (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-7)
- Migration status for libnginx-mod-http-upstream-fair (1:0.0~git20120408.a18b409-6 to 1:0.0~git20120408.a18b409-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
- Depends: libnginx-mod-http-upstream-fair nginx (not considered)
- Implicit dependency: libnginx-mod-http-upstream-fair nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-http-upstream-fair/1:0.0~git20120408.a18b409-7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libnginx-mod-nchan (1:1.3.7+dfsg-2 to 1:1.3.7+dfsg-4)
- Migration status for libnginx-mod-nchan (1:1.3.7+dfsg-2 to 1:1.3.7+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
- Depends: libnginx-mod-nchan nginx (not considered)
- Implicit dependency: libnginx-mod-nchan nginx (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libnginx-mod-nchan/1:1.3.7+dfsg-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libquicktime (2:1.2.4-16 to 2:1.2.4-17)
- Migration status for libquicktime (2:1.2.4-16 to 2:1.2.4-17): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- librelp (1.11.0-3 to 1.12.0-1)
- Migration status for librelp (1.11.0-3 to 1.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libsdl2 (2.32.10+dfsg-2 to 2.32.10+dfsg-4)
- Migration status for libsdl2 (2.32.10+dfsg-2 to 2.32.10+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)
- autopkgtest for libsdl2/2.32.10+dfsg-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libsession-token-perl (1.503-2 to 1.503-3)
- Migration status for libsession-token-perl (1.503-2 to 1.503-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 libsession-token-perl/1.503-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libsigc++-2.0 (2.12.1-3 to 2.12.1-4)
- Migration status for libsigc++-2.0 (2.12.1-3 to 2.12.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)
- libslirp (4.8.0-1 to 4.9.1-1)
- Migration status for libslirp (4.8.0-1 to 4.9.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)
- libtfbs-perl (0.7.1+ds-4 to 0.7.1+ds-5)
- Migration status for libtfbs-perl (0.7.1+ds-4 to 0.7.1+ds-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 libtfbs-perl/0.7.1+ds-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- libtpl (1.6.1-1.1 to 1.6.1-1.2)
- Migration status for libtpl (1.6.1-1.1 to 1.6.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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- libxmlb (0.3.23-1 to 0.3.24-1)
- Migration status for libxmlb (0.3.23-1 to 0.3.24-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: libxmlb gnome-software (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libxmlb/0.3.24-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- linbox (1.7.0-5 to 1.7.1-2)
- Migration status for linbox (1.7.0-5 to 1.7.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 linbox/1.7.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- lintian (2.123.0 to 2.124.0)
- Migration status for lintian (2.123.0 to 2.124.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.124.0: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- loupe (48.1-3 to 49~rc-3)
- Migration status for loupe (48.1-3 to 49~rc-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)
- luminance-hdr (2.6.1.1+dfsg-5 to 2.6.1.1+dfsg-6)
- Migration status for luminance-hdr (2.6.1.1+dfsg-5 to 2.6.1.1+dfsg-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)
- lynkeos.app (3.8+dfsg-1 to 3.9+dfsg-1)
- Migration status for lynkeos.app (3.8+dfsg-1 to 3.9+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)
- m17n-lib (1.8.5-1 to 1.8.6-1)
- Migration status for m17n-lib (1.8.5-1 to 1.8.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)
- mah-jong (1.17-1 to 1.17.2-1)
- Migration status for mah-jong (1.17-1 to 1.17.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)
- mailutils (1:3.20-1 to 1:3.20-2)
- Migration status for mailutils (1:3.20-1 to 1:3.20-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)
- matplotlib (3.10.1+dfsg1-4 to 3.10.1+dfsg1-5)
- Migration status for matplotlib (3.10.1+dfsg1-4 to 3.10.1+dfsg1-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 matplotlib/3.10.1+dfsg1-5: amd64: Pass
- autopkgtest for metpy/1.7.0+ds-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- mercurial (7.0.1-2 to 7.1-2)
- Migration status for mercurial (7.0.1-2 to 7.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
- Implicit dependency: mercurial kali-meta (not considered)
- Implicit dependency: mercurial tortoisehg
- Additional info:
- minlog (4.0.99.20100221-7 to 4.0.99.20100221-8)
- Migration status for minlog (4.0.99.20100221-7 to 4.0.99.20100221-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)
- morse (2.6-2 to 2.6-3)
- Migration status for morse (2.6-2 to 2.6-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)
- mousai (0.7.8-4 to 0.7.9-2)
- Migration status for mousai (0.7.8-4 to 0.7.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)
- mwrap (1.1.1-6 to 1.2.1-2)
- Migration status for mwrap (1.1.1-6 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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for mwrap/1.2.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- mycli (1.38.3-2 to 1.38.4-1)
- Migration status for mycli (1.38.3-2 to 1.38.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)
- mydumper (- to 0.10.1-2)
- Migration status for mydumper (- to 0.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 1 of 2 days old
- Additional info:
- nageru (2.3.0-2 to 2.3.1-1)
- Migration status for nageru (2.3.0-2 to 2.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)
- nanovna-saver (0.7.3-1.1 to 0.7.3-2)
- Migration status for nanovna-saver (0.7.3-1.1 to 0.7.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)
- ne10 (1.2.1-5.1 to 1.2.1-6)
- Migration status for ne10 (1.2.1-5.1 to 1.2.1-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)
- neon-2-sse (0.0.0~git20220912.a15b489-2 to 0.0.0~git20220912.a15b489-3)
- Migration status for neon-2-sse (0.0.0~git20220912.a15b489-2 to 0.0.0~git20220912.a15b489-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)
- nethack (3.6.7-1 to 3.6.7-2)
- Migration status for nethack (3.6.7-1 to 3.6.7-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)
- nghttp3 (1.8.0-1 to 1.11.0-1)
- Migration status for nghttp3 (1.8.0-1 to 1.11.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)
- ngspice (44.2+ds-1 to 45.2+ds-1)
- Migration status for ngspice (44.2+ds-1 to 45.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)
- autopkgtest for ngspice/45.2+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- node-esutils (2.0.3+~2.0.0-1 to 2.0.3+~2.0.2-1)
- Migration status for node-esutils (2.0.3+~2.0.0-1 to 2.0.3+~2.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)
- autopkgtest for node-esutils/2.0.3+~2.0.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- node-regenerate-unicode-properties (10.1.0+ds-1 to 10.2.0+ds-2)
- Migration status for node-regenerate-unicode-properties (10.1.0+ds-1 to 10.2.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
- Implicit dependency: node-regenerate-unicode-properties node-regexpu-core
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for node-regenerate-unicode-properties/10.2.0+ds-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- node-regexpu-core (5.2.2-3 to 6.2.0-2)
- Migration status for node-regexpu-core (5.2.2-3 to 6.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)
- autopkgtest for node-regexpu-core/6.2.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- node-regjsparser (0.9.1+ds-2 to 0.12.0+ds-1)
- Migration status for node-regjsparser (0.9.1+ds-2 to 0.12.0+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 node-regjsparser/0.12.0+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- node-unicode-data (0~20220914+gitb601441-2 to 1.6.7+ds-1)
- Migration status for node-unicode-data (0~20220914+gitb601441-2 to 1.6.7+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:
- numad (0.5+20150602-8 to 0.5+20150602-10)
- Migration status for numad (0.5+20150602-8 to 0.5+20150602-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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- obfuscate (0.0.10-9 to 0.0.10-11)
- Migration status for obfuscate (0.0.10-9 to 0.0.10-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)
- obs-retro-effects (1.0.0-2 to 1.0.1-1)
- Migration status for obs-retro-effects (1.0.0-2 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:
- ocaml-astring (0.8.5-2 to 0.8.5-3)
- Migration status for ocaml-astring (0.8.5-2 to 0.8.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)
- ocaml-ffmpeg (1.2.4-1 to 1.2.6-1)
- Migration status for ocaml-ffmpeg (1.2.4-1 to 1.2.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)
- autopkgtest for ocaml-ffmpeg/1.2.6-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- ocaml-hmap (0.8.1-2 to 0.8.1-3)
- Migration status for ocaml-hmap (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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- ocaml-mtime (2.1.0-2 to 2.1.0-3)
- Migration status for ocaml-mtime (2.1.0-2 to 2.1.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-ptime (1.2.0-2 to 1.2.0-3)
- Migration status for ocaml-ptime (1.2.0-2 to 1.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)
- ocaml-uuseg (16.0.0-1 to 16.0.0-2)
- Migration status for ocaml-uuseg (16.0.0-1 to 16.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)
- octave-optics (0.1.4-4 to 0.1.4-5)
- Migration status for octave-optics (0.1.4-4 to 0.1.4-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 octave-optics/0.1.4-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- onak (0.6.3-1 to 0.6.4-1)
- Migration status for onak (0.6.3-1 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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for onak/0.6.4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- onedrive (2.5.5-1 to 2.5.6-1)
- Migration status for onedrive (2.5.5-1 to 2.5.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)
- onscripter (20220816-1 to 20230825-1)
- Migration status for onscripter (20220816-1 to 20230825-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 onscripter/20230825-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- opencl-clang-17 (17.0.1-1 to 17.0.1-2)
- Migration status for opencl-clang-17 (17.0.1-1 to 17.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)
- opencl-clang-18 (18.1.1-1 to 18.1.1-2)
- Migration status for opencl-clang-18 (18.1.1-1 to 18.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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- openrct2 (0.4.25+ds-1 to 0.4.26+ds-1)
- Migration status for openrct2 (0.4.25+ds-1 to 0.4.26+ds-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)
- openrct2-objects (1.7.2+dfsg-1 to 1.7.3+dfsg-1)
- Migration status for openrct2-objects (1.7.2+dfsg-1 to 1.7.3+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)
- openscad (2021.01-8 to 2021.01-9)
- Migration status for openscad (2021.01-8 to 2021.01-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 openscad/2021.01-9: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- otpw (1.5-3 to 1.5-5)
- Migration status for otpw (1.5-3 to 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)
- owlrl (- to 7.1.4-1)
- Migration status for owlrl (- to 7.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:
- oxigraph (0.4.11-3 to 0.4.11-4)
- Migration status for oxigraph (0.4.11-3 to 0.4.11-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: oxigraph rust-oxhttp
- Additional info:
- pcc (1.2.0~DEVEL+20220331-1 to 1.2.0~DEVEL+20220331-2)
- Migration status for pcc (1.2.0~DEVEL+20220331-1 to 1.2.0~DEVEL+20220331-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)
- pdb-tools (2.5.1-2 to 2.5.2-1)
- Migration status for pdb-tools (2.5.1-2 to 2.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 pdb-tools/2.5.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pdns-recursor (5.3.0-2 to 5.3.0-5)
- Migration status for pdns-recursor (5.3.0-2 to 5.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)
- autopkgtest for pdns-recursor/5.3.0-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- phosh-osk-stevia (0.49.0-2 to 0.49.0-3)
- Migration status for phosh-osk-stevia (0.49.0-2 to 0.49.0-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing phosh-osk-stevia/0.49.0-2/armel from kali-rolling makes phrog/0.46.0-2/armel uninstallable
- Too young, only 1 of 2 days old
- Additional info:
- picolisp (25.3-1 to 25.6-2)
- Migration status for picolisp (25.3-1 to 25.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)
- pipemixer (0.2.1+ds-1 to 0.2.2+ds-1)
- Migration status for pipemixer (0.2.1+ds-1 to 0.2.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)
- platformdirs (4.3.7-1 to 4.4.0-1)
- Migration status for platformdirs (4.3.7-1 to 4.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 22 days old
- Implicit dependency: platformdirs python-fs
- Additional info:
- pngcheck (3.0.3-3 to 4.0.0+git20250707.6419815-1)
- Migration status for pngcheck (3.0.3-3 to 4.0.0+git20250707.6419815-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 pngcheck/4.0.0+git20250707.6419815-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- progress-linux (20250601-1 to 20250601-3)
- Migration status for progress-linux (20250601-1 to 20250601-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)
- progress-linux-metapackages (20221002-26 to 20221002-27)
- Migration status for progress-linux-metapackages (20221002-26 to 20221002-27): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- properties-cpp (0.0.3-2 to 0.0.4-1)
- Migration status for properties-cpp (0.0.3-2 to 0.0.4-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)
- psutils (3.3.12-1 to 3.3.14-1)
- Migration status for psutils (3.3.12-1 to 3.3.14-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)
- pybdsf (1.13.0-1 to 1.13.0-2)
- Migration status for pybdsf (1.13.0-1 to 1.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pybdsf/1.13.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pyexploitdb (0.2.95-0kali1 to 0.2.97-0kali1)
- Migration status for pyexploitdb (0.2.95-0kali1 to 0.2.97-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:
- pyicloud (2.0.1-1 to 2.0.1-2)
- Migration status for pyicloud (2.0.1-1 to 2.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)
- pylibtiff (0.6.1-2 to 0.6.1-3)
- Migration status for pylibtiff (0.6.1-2 to 0.6.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 pylibtiff/0.6.1-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- pysmarty2 (0.10.2-2 to 0.10.3-1)
- Migration status for pysmarty2 (0.10.2-2 to 0.10.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 pysmarty2/0.10.3-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-bcrypt (4.2.0-2.1 to 4.3.0-1)
- Migration status for python-bcrypt (4.2.0-2.1 to 4.3.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 python-bcrypt/4.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-django (3:4.2.23-1 to 3:4.2.24-1)
- Migration status for python-django (3:4.2.23-1 to 3:4.2.24-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/3:4.2.24-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-fs (2.4.16-7 to 2.4.16-8)
- Migration status for python-fs (2.4.16-7 to 2.4.16-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:
- python-gssapi (1.9.0-1 to 1.10.0-1)
- Migration status for python-gssapi (1.9.0-1 to 1.10.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-jenkinsapi (0.3.14-1 to 0.3.15-1)
- Migration status for python-jenkinsapi (0.3.14-1 to 0.3.15-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-pyo (1.0.6-2 to 1.0.6-3)
- Migration status for python-pyo (1.0.6-2 to 1.0.6-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 python-pyo/1.0.6-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-pyorick (1.5-1 to 1.5-2)
- Migration status for python-pyorick (1.5-1 to 1.5-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-pyorick/1.5-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- python-watchfiles (0.24.0-1 to 1.1.0-1)
- Migration status for python-watchfiles (0.24.0-1 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:
- python-zxcvbn-rs-py (0.2.0-1 to 0.2.0-2)
- Migration status for python-zxcvbn-rs-py (0.2.0-1 to 0.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:
- python3-defaults (3.13.5-1 to 3.13.7-1)
- Migration status for python3-defaults (3.13.5-1 to 3.13.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- qdl (2.1+git20250704.cd32723-1 to 2.2-1)
- Migration status for qdl (2.1+git20250704.cd32723-1 to 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)
- qrq (0.3.5-2 to 0.3.5-3)
- Migration status for qrq (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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- qtmir (- to 0.8.0~git20250407.ea2f477-4)
- Migration status for qtmir (- to 0.8.0~git20250407.ea2f477-4): 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)
- quickflux (1.1.3+git20201110.2a37acf-4 to 1.1.3+git20201110.2a37acf-5)
- Migration status for quickflux (1.1.3+git20201110.2a37acf-4 to 1.1.3+git20201110.2a37acf-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)
- qzxing (3.3.0+dfsg-7 to 3.3.0+dfsg-8)
- Migration status for qzxing (3.3.0+dfsg-7 to 3.3.0+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)
- r-cran-rcpparmadillo (15.0.1-1-1 to 15.0.2-1-1)
- Migration status for r-cran-rcpparmadillo (15.0.1-1-1 to 15.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)
- r-cran-th.data (1.1-3-1 to 1.1-4-1)
- Migration status for r-cran-th.data (1.1-3-1 to 1.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)
- racket (8.16+dfsg1-3 to 8.18+dfsg1-1)
- Migration status for racket (8.16+dfsg1-3 to 8.18+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)
- railway-gtk (2.7.3-3 to 2.8.2-2)
- Migration status for railway-gtk (2.7.3-3 to 2.8.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
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- react (1.2.2-1 to 1.2.2-2)
- Migration status for react (1.2.2-1 to 1.2.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
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- readability (0.8.1+dfsg1-4 to 0.8.4.1+dfsg1-1)
- Migration status for readability (0.8.1+dfsg1-4 to 0.8.4.1+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:
- rednotebook (2.41+ds-2 to 2.41+ds-3)
- Migration status for rednotebook (2.41+ds-2 to 2.41+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)
- reform-setup-wizard (1.0-13 to 1.0-14)
- Migration status for reform-setup-wizard (1.0-13 to 1.0-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:
- regina-rexx (3.9.5+dfsg1-0.1 to 3.9.5+dfsg1-0.2)
- Migration status for regina-rexx (3.9.5+dfsg1-0.1 to 3.9.5+dfsg1-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)
- remind (06.00.02-1 to 06.01.00-1)
- Migration status for remind (06.00.02-1 to 06.01.00-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)
- renameutils (0.12.0-12 to 0.12.0-13)
- Migration status for renameutils (0.12.0-12 to 0.12.0-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)
- repo (2.58-3 to 2.58-4)
- Migration status for repo (2.58-3 to 2.58-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 repo/2.58-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- requests (2.32.4+dfsg-1 to 2.32.5+dfsg-1)
- Migration status for requests (2.32.4+dfsg-1 to 2.32.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 requests/2.32.5+dfsg-1: amd64: Pass
- autopkgtest for sphinx/8.2.3-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- riseup-vpn (0.24.10+ds1-1 to 0.25.8+ds2-2)
- Migration status for riseup-vpn (0.24.10+ds1-1 to 0.25.8+ds2-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 riseup-vpn/0.25.8+ds2-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- ros-geometric-shapes (0.7.6-2 to 0.7.7-1)
- Migration status for ros-geometric-shapes (0.7.6-2 to 0.7.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)
- ros-navigation-msgs (1.14.1-4 to 1.14.2-1)
- Migration status for ros-navigation-msgs (1.14.1-4 to 1.14.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 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for ros-actionlib: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- ros2-ament-lint (0.19.1-1 to 0.20.2-1)
- Migration status for ros2-ament-lint (0.19.1-1 to 0.20.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)
- rudof (0.1.81+ds-2 to 0.1.81+ds-3)
- Migration status for rudof (0.1.81+ds-2 to 0.1.81+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)
- rust-aperture (0.9.3-1 to 0.11.0-2)
- Migration status for rust-aperture (0.9.3-1 to 0.11.0-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-aperture/0.11.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ashpd (0.11.0-1 to 0.12.0-2)
- Migration status for rust-ashpd (0.11.0-1 to 0.12.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-async-tls (0.13.0-3 to 0.13.0-4)
- Migration status for rust-async-tls (0.13.0-3 to 0.13.0-4): 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-async-tls/0.13.0-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-async-tungstenite (0.28.2-2 to 0.28.2-4)
- Migration status for rust-async-tungstenite (0.28.2-2 to 0.28.2-4): 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-async-tungstenite/0.28.2-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-auditable-info (0.9.0-2 to 0.10.0-1)
- Migration status for rust-auditable-info (0.9.0-2 to 0.10.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-auditable-info/0.10.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-cairo-rs (0.20.7-2 to 0.21.1-2)
- Migration status for rust-cairo-rs (0.20.7-2 to 0.21.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-cairo-sys-rs (0.20.7-1 to 0.21.1-2)
- Migration status for rust-cairo-sys-rs (0.20.7-1 to 0.21.1-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-cairo-sys-rs/0.21.1-2: amd64: Pass
- autopkgtest for rust-gsk4-sys/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-cargo-lock (9.0.0-1 to 10.1.0-1)
- Migration status for rust-cargo-lock (9.0.0-1 to 10.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 rust-cargo-lock/10.1.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-colorgrad (- to 0.7.2-1)
- Migration status for rust-colorgrad (- 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:
- rust-cvss (2.0.0-1 to 2.1.1-1)
- Migration status for rust-cvss (2.0.0-1 to 2.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 rust-cvss/2.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-diesel (2.2.7-2 to 2.2.7-3)
- Migration status for rust-diesel (2.2.7-2 to 2.2.7-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 22 days old
- Additional info:
- rust-display-error-chain (0.2.1-1 to 0.2.2-1)
- Migration status for rust-display-error-chain (0.2.1-1 to 0.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)
- autopkgtest for rust-display-error-chain/0.2.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-fastrand (2.1.1-4 to 2.3.0-1)
- Migration status for rust-fastrand (2.1.1-4 to 2.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- rust-gdk-pixbuf (0.20.9-1 to 0.21.1-2)
- Migration status for rust-gdk-pixbuf (0.20.9-1 to 0.21.1-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-gdk-pixbuf/0.21.1-2: amd64: Pass
- autopkgtest for rust-gdk4/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gdk-pixbuf-sys (0.20.7-1 to 0.21.1-2)
- Migration status for rust-gdk-pixbuf-sys (0.20.7-1 to 0.21.1-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-gdk-pixbuf-sys/0.21.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gdk4-sys (0.9.6-1 to 0.10.0-3)
- Migration status for rust-gdk4-sys (0.9.6-1 to 0.10.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-gdk4/0.10.0-2: amd64: Pass
- autopkgtest for rust-gdk4-sys/0.10.0-3: amd64: Pass
- autopkgtest for rust-gsk4-sys/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gdk4-wayland (0.9.6-1 to 0.10.0-3)
- Migration status for rust-gdk4-wayland (0.9.6-1 to 0.10.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-gdk4-wayland/0.10.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gdk4-x11 (0.9.6-1 to 0.10.0-3)
- Migration status for rust-gdk4-x11 (0.9.6-1 to 0.10.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-gdk4-x11/0.10.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gdk4-x11-sys (0.9.6-1 to 0.10.0-2)
- Migration status for rust-gdk4-x11-sys (0.9.6-1 to 0.10.0-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-gdk4-x11-sys/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gio (0.20.9-1 to 0.21.1-2)
- Migration status for rust-gio (0.20.9-1 to 0.21.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-gio-sys (0.20.9-1 to 0.21.1-2)
- Migration status for rust-gio-sys (0.20.9-1 to 0.21.1-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-gio-sys/0.21.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-glib (0.20.9-1 to 0.21.1-4)
- Migration status for rust-glib (0.20.9-1 to 0.21.1-4): 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-gdk4/0.10.0-2: amd64: Pass
- autopkgtest for rust-glib/0.21.1-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-glib-build-tools (0.20.0-1 to 0.21.0-2)
- Migration status for rust-glib-build-tools (0.20.0-1 to 0.21.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: rust-glib-build-tools rust-gio
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-glib-build-tools/0.21.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-glib-macros (0.20.7-1 to 0.21.0-2)
- Migration status for rust-glib-macros (0.20.7-1 to 0.21.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: rust-glib-macros rust-glib
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-glib-macros/0.21.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-glib-sys (0.20.9-1 to 0.21.1-2)
- Migration status for rust-glib-sys (0.20.9-1 to 0.21.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-glycin (2.1.1-1 to 3.0.0~rc.1-2)
- Migration status for rust-glycin (2.1.1-1 to 3.0.0~rc.1-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-glycin-common (- to 1.0.0~rc-3)
- Migration status for rust-glycin-common (- to 1.0.0~rc-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-glycin-utils (3.0.1-1 to 4.0.0~rc-3)
- Migration status for rust-glycin-utils (3.0.1-1 to 4.0.0~rc-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-gobject-sys (0.20.9-1 to 0.21.1-2)
- Migration status for rust-gobject-sys (0.20.9-1 to 0.21.1-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-gobject-sys/0.21.1-2: amd64: Pass
- autopkgtest for rust-gsk4-sys/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-graphene-rs (0.20.9-1 to 0.21.1-2)
- Migration status for rust-graphene-rs (0.20.9-1 to 0.21.1-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-graphene-rs/0.21.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-graphene-sys (0.20.7-2 to 0.21.1-2)
- Migration status for rust-graphene-sys (0.20.7-2 to 0.21.1-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-graphene-sys/0.21.1-2: amd64: Pass
- autopkgtest for rust-gsk4-sys/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gsettings-macro (0.2.1-2 to 0.2.2-1)
- Migration status for rust-gsettings-macro (0.2.1-2 to 0.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 22 days old
- Additional info:
- rust-gsk4 (0.9.6-1 to 0.10.0-2)
- Migration status for rust-gsk4 (0.9.6-1 to 0.10.0-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-gsk4/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gst-plugin-gif (0.13.0-3 to 0.14.0-2)
- Migration status for rust-gst-plugin-gif (0.13.0-3 to 0.14.0-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-gst-plugin-gif/0.14.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gst-plugin-gtk4 (0.13.5-1 to 0.14.0-4)
- Migration status for rust-gst-plugin-gtk4 (0.13.5-1 to 0.14.0-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-gst-plugin-gtk4/0.14.0-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer (0.23.5-2 to 0.24.1-2)
- Migration status for rust-gstreamer (0.23.5-2 to 0.24.1-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-gstreamer/0.24.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-allocators (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-allocators (0.23.5-2 to 0.24.0-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-gstreamer-allocators/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-allocators-sys (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-allocators-sys (0.23.5-2 to 0.24.0-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-gstreamer-allocators-sys/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-audio (0.23.5-4 to 0.24.0-2)
- Migration status for rust-gstreamer-audio (0.23.5-4 to 0.24.0-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-gstreamer-audio/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-audio-sys (0.23.5-2 to 0.24.0-3)
- Migration status for rust-gstreamer-audio-sys (0.23.5-2 to 0.24.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-gstreamer-audio-sys/0.24.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-base (0.23.5-2 to 0.24.0-3)
- Migration status for rust-gstreamer-base (0.23.5-2 to 0.24.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-gstreamer-base/0.24.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-base-sys (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-base-sys (0.23.5-2 to 0.24.0-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-gstreamer-base-sys/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-gl (0.23.5-2 to 0.24.1-2)
- Migration status for rust-gstreamer-gl (0.23.5-2 to 0.24.1-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-gstreamer-gl/0.24.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-gl-egl (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-gl-egl (0.23.5-2 to 0.24.0-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-gstreamer-gl-egl/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-gl-egl-sys (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-gl-egl-sys (0.23.5-2 to 0.24.0-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-gstreamer-gl-egl-sys/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-gl-sys (0.23.5-2 to 0.24.1-2)
- Migration status for rust-gstreamer-gl-sys (0.23.5-2 to 0.24.1-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-gstreamer-gl-sys/0.24.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-gl-wayland (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-gl-wayland (0.23.5-2 to 0.24.0-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-gstreamer-gl-wayland/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-gl-wayland-sys (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-gl-wayland-sys (0.23.5-2 to 0.24.0-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-gstreamer-gl-wayland-sys/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-gl-x11 (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-gl-x11 (0.23.5-2 to 0.24.0-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-gstreamer-gl-x11/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-gl-x11-sys (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-gl-x11-sys (0.23.5-2 to 0.24.0-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-gstreamer-gl-x11-sys/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-pbutils (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-pbutils (0.23.5-2 to 0.24.0-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-gstreamer-pbutils/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-pbutils-sys (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-pbutils-sys (0.23.5-2 to 0.24.0-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-gstreamer-pbutils-sys/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-play (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-play (0.23.5-2 to 0.24.0-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-gstreamer-play/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-play-sys (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-play-sys (0.23.5-2 to 0.24.0-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-gstreamer-play-sys/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-sys (0.23.5-2 to 0.24.0-2)
- Migration status for rust-gstreamer-sys (0.23.5-2 to 0.24.0-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-gstreamer-sys/0.24.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-video (0.23.5-2 to 0.24.1-2)
- Migration status for rust-gstreamer-video (0.23.5-2 to 0.24.1-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-gstreamer-video/0.24.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gstreamer-video-sys (0.23.5-2 to 0.24.1-2)
- Migration status for rust-gstreamer-video-sys (0.23.5-2 to 0.24.1-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-gstreamer-video-sys/0.24.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gtk4 (0.9.6-2 to 0.10.0-2)
- Migration status for rust-gtk4 (0.9.6-2 to 0.10.0-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-gtk4/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gtk4-layer-shell (0.4.0-2 to 0.6.1-2)
- Migration status for rust-gtk4-layer-shell (0.4.0-2 to 0.6.1-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-gtk4-layer-shell/0.6.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gtk4-layer-shell-sys (0.3.0-2 to 0.4.0-2)
- Migration status for rust-gtk4-layer-shell-sys (0.3.0-2 to 0.4.0-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-gtk4-layer-shell-sys/0.4.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gtk4-macros (0.9.5-1 to 0.10.0-2)
- Migration status for rust-gtk4-macros (0.9.5-1 to 0.10.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: rust-gtk4-macros rust-gtk4
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-gtk4-macros/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gtk4-sys (0.9.6-2 to 0.10.0-2)
- Migration status for rust-gtk4-sys (0.9.6-2 to 0.10.0-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-gtk4-sys/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gufo (0.2.3-1 to 0.3.0-2)
- Migration status for rust-gufo (0.2.3-1 to 0.3.0-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-gufo/0.3.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gufo-common (0.2.0-1 to 1.0.1-2)
- Migration status for rust-gufo-common (0.2.0-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:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-gufo-common/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
- rust-gufo-exif (0.2.2-1 to 0.3.0-2)
- Migration status for rust-gufo-exif (0.2.2-1 to 0.3.0-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-gufo-exif/0.3.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gufo-jpeg (0.2.0-1 to 0.3.0-3)
- Migration status for rust-gufo-jpeg (0.2.0-1 to 0.3.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-gufo-jpeg/0.3.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gufo-png (0.2.3-1 to 0.3.0-2)
- Migration status for rust-gufo-png (0.2.3-1 to 0.3.0-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-gufo-png/0.3.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gufo-tiff (0.2.1-1 to 0.3.0-2)
- Migration status for rust-gufo-tiff (0.2.1-1 to 0.3.0-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-gufo-tiff/0.3.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gufo-webp (0.2.1-1 to 0.3.0-2)
- Migration status for rust-gufo-webp (0.2.1-1 to 0.3.0-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-gufo-webp/0.3.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-gufo-xmp (0.2.0-1 to 0.3.0-2)
- Migration status for rust-gufo-xmp (0.2.0-1 to 0.3.0-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-gufo-xmp/0.3.0-2: 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.9.0-2)
- Migration status for rust-gvdb (0.8.0-2 to 0.9.0-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-gvdb-macros (0.1.14-2 to 0.1.15-2)
- Migration status for rust-gvdb-macros (0.1.14-2 to 0.1.15-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-gvdb-macros rust-gvdb
- Additional info:
- rust-gweather-sys (4.5.0-2 to 4.6.0-2)
- Migration status for rust-gweather-sys (4.5.0-2 to 4.6.0-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-gweather-sys/4.6.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-hickory-proto (0.24.4-4.1 to 0.24.4-6)
- Migration status for rust-hickory-proto (0.24.4-4.1 to 0.24.4-6): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-hickory-resolver (0.24.4-1 to 0.24.4-4)
- Migration status for rust-hickory-resolver (0.24.4-1 to 0.24.4-4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-hyper-rustls (0.27.6-2 to 0.27.6-3)
- Migration status for rust-hyper-rustls (0.27.6-2 to 0.27.6-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-hyper-rustls/0.27.6-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-hyper-rustls-0.24 (0.24.2-1 to 0.24.2-3)
- Migration status for rust-hyper-rustls-0.24 (0.24.2-1 to 0.24.2-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-hyper-rustls-0.24/0.24.2-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ipnetwork (0.17.0-1 to 0.21.1-1)
- Migration status for rust-ipnetwork (0.17.0-1 to 0.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 22 days old
- Implicit dependency: rust-ipnetwork rust-diesel
- Additional info:
- rust-irc (1.1.0-1~sid1 to 1.1.0-2)
- Migration status for rust-irc (1.1.0-1~sid1 to 1.1.0-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-irc/1.1.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-khronos-egl (4.1.0-5 to 6.0.0-2)
- Migration status for rust-khronos-egl (4.1.0-5 to 6.0.0-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-khronos-egl/6.0.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-libadwaita (0.7.2-1 to 0.8.0-2)
- Migration status for rust-libadwaita (0.7.2-1 to 0.8.0-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-libadwaita/0.8.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-libadwaita-sys (0.7.2-1 to 0.8.0-3)
- Migration status for rust-libadwaita-sys (0.7.2-1 to 0.8.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-libadwaita-sys/0.8.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-libgweather (4.5.0-2 to 4.6.0-2)
- Migration status for rust-libgweather (4.5.0-2 to 4.6.0-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-libgweather/4.6.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-librsvg (2.60.0-1 to 2.60.0-3)
- Migration status for rust-librsvg (2.60.0-1 to 2.60.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-librsvg/2.60.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-librsvg-rebind (0.1.0-2 to 0.2.1-3)
- Migration status for rust-librsvg-rebind (0.1.0-2 to 0.2.1-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-librsvg-rebind/0.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-librsvg-rebind-sys (0.1.0-3 to 0.2.1-2)
- Migration status for rust-librsvg-rebind-sys (0.1.0-3 to 0.2.1-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-librsvg-rebind-sys/0.2.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-libseccomp (0.3.0-11 to 0.4.0-3)
- Migration status for rust-libseccomp (0.3.0-11 to 0.4.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-libseccomp-sys (0.2.1-2 to 0.3.0-2)
- Migration status for rust-libseccomp-sys (0.2.1-2 to 0.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 22 days old
- Implicit dependency: rust-libseccomp-sys rust-libseccomp
- Implicit dependency: rust-libseccomp-sys rust-virtiofsd
- Additional info:
- rust-libshumate (0.6.0-2 to 0.7.0-2)
- Migration status for rust-libshumate (0.6.0-2 to 0.7.0-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-libshumate/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
- rust-libshumate-sys (0.6.0-2 to 0.7.0-2)
- Migration status for rust-libshumate-sys (0.6.0-2 to 0.7.0-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-libshumate-sys/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
- rust-line-index (- to 0.1.2-1)
- Migration status for rust-line-index (- to 0.1.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:
- rust-lock-api (0.4.12-1 to 0.4.13-1)
- Migration status for rust-lock-api (0.4.12-1 to 0.4.13-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- rust-minreq (- to 2.13.4-4)
- Migration status for rust-minreq (- to 2.13.4-4): 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-minreq/2.13.4-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ntp-proto (1.4.0-4 to 1.6.2-2)
- Migration status for rust-ntp-proto (1.4.0-4 to 1.6.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-ntp-proto/1.6.2-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ntpd (1.4.0-6 to 1.6.2-1)
- Migration status for rust-ntpd (1.4.0-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:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-ntpd/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-outref (- to 0.5.2-1)
- Migration status for rust-outref (- 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 rust-outref/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
- rust-oxhttp (0.2.7-3 to 0.3.1-3)
- Migration status for rust-oxhttp (0.2.7-3 to 0.3.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 22 days old
- Implicit dependency: rust-oxhttp oxigraph
- Additional info:
- rust-pango (0.20.9-4 to 0.21.1-2)
- Migration status for rust-pango (0.20.9-4 to 0.21.1-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-gdk4/0.10.0-2: amd64: Pass
- autopkgtest for rust-pango/0.21.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-pango-sys (0.20.9-2 to 0.21.1-2)
- Migration status for rust-pango-sys (0.20.9-2 to 0.21.1-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-gsk4-sys/0.10.0-2: amd64: Pass
- autopkgtest for rust-pango-sys/0.21.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-pangocairo (0.20.7-1 to 0.21.1-2)
- Migration status for rust-pangocairo (0.20.7-1 to 0.21.1-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-pangocairo/0.21.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-pangocairo-sys (0.20.7-1 to 0.21.1-2)
- Migration status for rust-pangocairo-sys (0.20.7-1 to 0.21.1-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-pangocairo-sys/0.21.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-platforms (3.1.2-1 to 3.6.0-1)
- Migration status for rust-platforms (3.1.2-1 to 3.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-platforms/3.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-poppler-sys-rs (0.24.0-2 to 0.25.0-2)
- Migration status for rust-poppler-sys-rs (0.24.0-2 to 0.25.0-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-poppler-sys-rs/0.25.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-reqwest (0.12.15-1 to 0.12.15-5)
- Migration status for rust-reqwest (0.12.15-1 to 0.12.15-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- rust-reqwest-0.11 (0.11.27-9 to 0.11.27-11)
- Migration status for rust-reqwest-0.11 (0.11.27-9 to 0.11.27-11): 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-reqwest-0.11/0.11.27-11: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-rqrr (0.9.3-1 to 0.10.0-2)
- Migration status for rust-rqrr (0.9.3-1 to 0.10.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: rust-rqrr rust-aperture
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-rqrr/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-rustls (0.23.31+ds-4 to 0.23.31+ds-7)
- Migration status for rust-rustls (0.23.31+ds-4 to 0.23.31+ds-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- rust-rustls-0.21 (0.21.12-14 to 0.21.12-15)
- Migration status for rust-rustls-0.21 (0.21.12-14 to 0.21.12-15): 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:
- rust-rustls-native-certs (0.6.3-7 to 0.8.1-5)
- Migration status for rust-rustls-native-certs (0.6.3-7 to 0.8.1-5): 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-rustls-native-certs/0.8.1-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-rustls-platform-verifier (0.5.3+ds-2 to 0.5.3+ds-3)
- Migration status for rust-rustls-platform-verifier (0.5.3+ds-2 to 0.5.3+ds-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-search-provider (0.10.0-4 to 0.12.0-2)
- Migration status for rust-search-provider (0.10.0-4 to 0.12.0-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-search-provider/0.12.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-serde-json-path-macros-internal (- to 0.1.2-1)
- Migration status for rust-serde-json-path-macros-internal (- to 0.1.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:
- rust-snapbox (0.4.17-1 to 0.6.21-1)
- Migration status for rust-snapbox (0.4.17-1 to 0.6.21-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-snapbox rust-trycmd
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-snapbox/0.6.21-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-soup3 (0.7.0-4 to 0.8.0-2)
- Migration status for rust-soup3 (0.7.0-4 to 0.8.0-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-soup3/0.8.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-soup3-sys (0.7.0-3 to 0.8.0-2)
- Migration status for rust-soup3-sys (0.7.0-3 to 0.8.0-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-soup3-sys/0.8.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-sourceview5 (0.9.1-2 to 0.10.0-2)
- Migration status for rust-sourceview5 (0.9.1-2 to 0.10.0-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-sourceview5/0.10.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-sourceview5-sys (0.9.0-3 to 0.10.1-2)
- Migration status for rust-sourceview5-sys (0.9.0-3 to 0.10.1-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-sourceview5-sys/0.10.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-sqlx-core (0.8.3-2 to 0.8.3-3)
- Migration status for rust-sqlx-core (0.8.3-2 to 0.8.3-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-sqlx-core/0.8.3-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-subfeature (- to 0.0.3-1)
- Migration status for rust-subfeature (- to 0.0.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:
- rust-swtchr (0.1.3-1 to 0.1.3-3)
- Migration status for rust-swtchr (0.1.3-1 to 0.1.3-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-swtchr/0.1.3-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-tagptr (- to 0.2.0-1)
- Migration status for rust-tagptr (- 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:
- rust-tl (- to 0.7.8-1)
- Migration status for rust-tl (- to 0.7.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:
- rust-tokio-tungstenite (0.24.0-4 to 0.24.0-5)
- Migration status for rust-tokio-tungstenite (0.24.0-4 to 0.24.0-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-tonic (0.12.3+dfsg-4 to 0.12.3+dfsg-5)
- Migration status for rust-tonic (0.12.3+dfsg-4 to 0.12.3+dfsg-5): 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-tonic/0.12.3+dfsg-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-transmission-gobject (0.1.6-1 to 0.1.7-2)
- Migration status for rust-transmission-gobject (0.1.6-1 to 0.1.7-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-transmission-gobject rust-gio
- Depends: rust-transmission-gobject rust-glib
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-transmission-gobject/0.1.7-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-trycmd (0.14.20-1 to 0.15.10-1)
- Migration status for rust-trycmd (0.14.20-1 to 0.15.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
- Depends: rust-trycmd rust-snapbox
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-trycmd/0.15.10-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-tungstenite (0.24.0-4 to 0.24.0-5)
- Migration status for rust-tungstenite (0.24.0-4 to 0.24.0-5): 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-tungstenite/0.24.0-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rust-ultraviolet (- to 0.10.0-1)
- Migration status for rust-ultraviolet (- to 0.10.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:
- rust-unit-prefix (- to 0.5.1-1)
- Migration status for rust-unit-prefix (- to 0.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:
- rust-virtiofsd (1.13.2-1 to 1.13.2-2)
- Migration status for rust-virtiofsd (1.13.2-1 to 1.13.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-virtiofsd/1.13.2-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- rygel (0.44.2-1 to 45~rc-2)
- Migration status for rygel (0.44.2-1 to 45~rc-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)
- saods9 (8.6+repack-5 to 8.6+repack-6)
- Migration status for saods9 (8.6+repack-5 to 8.6+repack-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 saods9/8.6+repack-6: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- satellite-gtk (0.9.0-1 to 0.9.1-1)
- Migration status for satellite-gtk (0.9.0-1 to 0.9.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for satellite-gtk: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- scottfree (1.14-12 to 1.14-13)
- Migration status for scottfree (1.14-12 to 1.14-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)
- sdcc (4.5.0+dfsg-1 to 4.5.0+dfsg-3)
- Migration status for sdcc (4.5.0+dfsg-1 to 4.5.0+dfsg-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)
- sdl2-compat (2.32.56+ds-2 to 2.32.56+ds-3)
- Migration status for sdl2-compat (2.32.56+ds-2 to 2.32.56+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 22 days old
- Additional info:
- seabios (1.16.3-2 to 1.17.0-1)
- Migration status for seabios (1.16.3-2 to 1.17.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 22 days old
- Additional info:
- seqan3 (3.4.0~rc.3+ds-4 to 3.4.0+ds-1)
- Migration status for seqan3 (3.4.0~rc.3+ds-4 to 3.4.0+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 seqan3/3.4.0+ds-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- shortwave (5.0.0-5 to 5.0.0-6)
- Migration status for shortwave (5.0.0-5 to 5.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)
- silversearcher-ag-el (0.48-2 to 0.48-3)
- Migration status for silversearcher-ag-el (0.48-2 to 0.48-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)
- simple-cdd (0.6.9 to 0.6.10)
- Migration status for simple-cdd (0.6.9 to 0.6.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- slashem (0.0.7E7F3-12 to 0.0.7E7F3-13)
- Migration status for slashem (0.0.7E7F3-12 to 0.0.7E7F3-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)
- slcurl (0.2.2~pre.12-2 to 0.2.2~pre.14-2)
- Migration status for slcurl (0.2.2~pre.12-2 to 0.2.2~pre.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)
- slexpat (0.5.0-9 to 0.5.0-11)
- Migration status for slexpat (0.5.0-9 to 0.5.0-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)
- slgdbm (1.7.1-14 to 1.7.1-17)
- Migration status for slgdbm (1.7.1-14 to 1.7.1-17): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- slwildcard (0.5.0-8 to 0.5.0-10)
- Migration status for slwildcard (0.5.0-8 to 0.5.0-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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- snaphu (2.0.7-1 to 2.0.7-2)
- Migration status for snaphu (2.0.7-1 to 2.0.7-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:
- sos (4.9.2-3 to 4.10.0-1)
- Migration status for sos (4.9.2-3 to 4.10.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 22 days old
- Additional info:
- spice (0.15.2-1 to 0.16.0-1)
- Migration status for spice (0.15.2-1 to 0.16.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 qemu: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- spice-protocol (0.14.3-1 to 0.14.5-1)
- Migration status for spice-protocol (0.14.3-1 to 0.14.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)
- spip (4.4.3+dfsg-1 to 4.4.5+dfsg-1)
- Migration status for spip (4.4.3+dfsg-1 to 4.4.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)
- spirv-llvm-translator-18 (18.1.15-1 to 18.1.16-1)
- Migration status for spirv-llvm-translator-18 (18.1.15-1 to 18.1.16-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 spirv-llvm-translator-18/18.1.16-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- spirv-llvm-translator-19 (19.1.10-1 to 19.1.11-1)
- Migration status for spirv-llvm-translator-19 (19.1.10-1 to 19.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 22 days old
- Additional info:
- sqlglot (27.9.0-1 to 27.12.0-1)
- Migration status for sqlglot (27.9.0-1 to 27.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:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- starlink-ast (9.2.10+dfsg-2 to 9.2.10+dfsg-3)
- Migration status for starlink-ast (9.2.10+dfsg-2 to 9.2.10+dfsg-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 starlink-ast/9.2.10+dfsg-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- supertuxkart (1.4+dfsg-5 to 1.4+dfsg-6)
- Migration status for supertuxkart (1.4+dfsg-5 to 1.4+dfsg-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)
- swarp (2.41.5-1 to 2.41.5-2)
- Migration status for swarp (2.41.5-1 to 2.41.5-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 swarp/2.41.5-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- systemtap (5.1-5 to 5.3-1)
- Migration status for systemtap (5.1-5 to 5.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:
- task-spooler (1.0.3+dfsg1-1 to 1.0.3+dfsg1-2)
- Migration status for task-spooler (1.0.3+dfsg1-1 to 1.0.3+dfsg1-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)
- td1.8.11 (1.8.11~git20230202.3179d35+dfsg-3 to 1.8.11~git20230202.3179d35+dfsg-4)
- Migration status for td1.8.11 (1.8.11~git20230202.3179d35+dfsg-3 to 1.8.11~git20230202.3179d35+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)
- template-glib (3.36.3-1 to 3.36.3-2)
- Migration status for template-glib (3.36.3-1 to 3.36.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)
- tenace (0.17-1 to 0.18-2)
- Migration status for tenace (0.17-1 to 0.18-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)
- tensorflow (2.14.1+dfsg-2 to 2.14.1+dfsg-3)
- Migration status for tensorflow (2.14.1+dfsg-2 to 2.14.1+dfsg-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:
- tiff (4.7.0-4 to 4.7.0-5)
- Migration status for tiff (4.7.0-4 to 4.7.0-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- tinyobjloader (2.0.0~rc13+dfsg-2 to 2.0.0~rc13+dfsg-3)
- Migration status for tinyobjloader (2.0.0~rc13+dfsg-2 to 2.0.0~rc13+dfsg-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:
- tortoisehg (6.9-1 to 7.0.1-1)
- Migration status for tortoisehg (6.9-1 to 7.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)
- trippy (0.13.0+dfsg-1 to 0.13.0+dfsg-1.1)
- Migration status for trippy (0.13.0+dfsg-1 to 0.13.0+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 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- trivy (0.65.0-0kali1 to 0.66.0-0kali1)
- Migration status for trivy (0.65.0-0kali1 to 0.66.0-0kali1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- missing build on armel
- Too young, only 1 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for trivy: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- trn4 (4.0-test77-18 to 4.0-test77-19)
- Migration status for trn4 (4.0-test77-18 to 4.0-test77-19): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 1 of 2 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- tuned (2.25.1-1 to 2.26.0-1)
- Migration status for tuned (2.25.1-1 to 2.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 tuned/2.26.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- uclibc (1.0.35-1 to 1.0.54-1)
- Migration status for uclibc (1.0.35-1 to 1.0.54-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)
- uhd (4.8.0.0+ds1-2 to 4.9.0.0+ds1-1)
- Migration status for uhd (4.8.0.0+ds1-2 to 4.9.0.0+ds1-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: uhd kali-meta (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- uhttpmock (0.11.0-2 to 0.11.0-3)
- Migration status for uhttpmock (0.11.0-2 to 0.11.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)
- units-cpp (2.3.4+ds-1 to 2.3.4+ds-2)
- Migration status for units-cpp (2.3.4+ds-1 to 2.3.4+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)
- unl0kr (2.0.3+dfsg-2 to 2.0.3+dfsg-3)
- Migration status for unl0kr (2.0.3+dfsg-2 to 2.0.3+dfsg-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)
- unsort (1.2.1-1 to 1.3.1-1)
- Migration status for unsort (1.2.1-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)
- urdfdom (4.0.0-3 to 4.0.0-4)
- Migration status for urdfdom (4.0.0-3 to 4.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
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for urdfdom/4.0.0-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- util-linux (2.41.1-1 to 2.41.1-3)
- Migration status for util-linux (2.41.1-1 to 2.41.1-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- uutf (1.0.4-1 to 1.0.4-2)
- Migration status for uutf (1.0.4-1 to 1.0.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)
- uwsgi-plugin-java (0.0.5 to 0.0.6)
- Migration status for uwsgi-plugin-java (0.0.5 to 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 22 days old
- Additional info:
- virtualbox (7.1.12-dfsg-2 to 7.2.0-dfsg-3)
- Migration status for virtualbox (7.1.12-dfsg-2 to 7.2.0-dfsg-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 virtualbox: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- virtualbox-ext-pack (7.1.12-1 to 7.2.0-3)
- Migration status for virtualbox-ext-pack (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
- Depends: virtualbox-ext-pack virtualbox
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- voms-api-java (3.3.6-1 to 3.3.6-2)
- Migration status for voms-api-java (3.3.6-1 to 3.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)
- warp (0.9.2-3 to 0.9.2-4)
- Migration status for warp (0.9.2-3 to 0.9.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)
- wily (0.13.42-3 to 0.13.42-4)
- Migration status for wily (0.13.42-3 to 0.13.42-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)
- x264 (2:0.164.3108+git31e19f9-2 to 2:0.164.3108+git31e19f9-3)
- Migration status for x264 (2:0.164.3108+git31e19f9-2 to 2:0.164.3108+git31e19f9-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 22 days old
- Additional info:
- xfce4-eyes-plugin (4.6.2-1 to 4.7.0-1)
- Migration status for xfce4-eyes-plugin (4.6.2-1 to 4.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)
- xmake (3.0.1+ds-1 to 3.0.2+ds-1)
- Migration status for xmake (3.0.1+ds-1 to 3.0.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 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for xmake: amd64: Test in progress
- Required age increased by 20 days because of autopkgtest
- xsysinfo (1.7-10 to 1.7-11)
- Migration status for xsysinfo (1.7-10 to 1.7-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)
- yagiuda (1.19-12 to 1.19-13)
- Migration status for yagiuda (1.19-12 to 1.19-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)
- zdbsp (1.19+20181027+dfsg.1-5 to 1.19+20181027+dfsg.1-6)
- Migration status for zdbsp (1.19+20181027+dfsg.1-5 to 1.19+20181027+dfsg.1-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)
- zope.component (6.0-1 to 6.1-1)
- Migration status for zope.component (6.0-1 to 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 zope.component/6.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- elfutils (0.192-4 to 0.193-3)
- Migration status for elfutils (0.192-4 to 0.193-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)
- 4 days old (needed 2 days)
- hydra (9.5-3 to 9.6-1)
- Migration status for hydra (9.5-3 to 9.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)
- 4 days old (needed 2 days)
- netpbm-free (2:11.11.00-2 to 2:11.11.01-1)
- Migration status for netpbm-free (2:11.11.00-2 to 2:11.11.01-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)
- 4 days old (needed 2 days)
- ngrep (1.47+ds1-6 to 1.47+ds1-7)
- Migration status for ngrep (1.47+ds1-6 to 1.47+ds1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: ngrep kali-meta (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 4 days old (needed 2 days)
- onetbb (2022.1.0-1 to 2022.1.0-2)
- Migration status for onetbb (2022.1.0-1 to 2022.1.0-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: onetbb hwloc (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for onetbb/2022.1.0-2: 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)
- pyzmq (26.4.0-1 to 27.1.0-1)
- Migration status for pyzmq (26.4.0-1 to 27.1.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 pyzmq/27.1.0-1: 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)
- rust-breezyshim (0.1.227-2 to 0.6.5-1)
- Migration status for rust-breezyshim (0.1.227-2 to 0.6.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-inotify (0.9.6-1 to 0.11.0-2)
- Migration status for rust-inotify (0.9.6-1 to 0.11.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-inotify rust-notify (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-inotify/0.11.0-2: 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)
- rust-kanata (- to 1.9.0-2)
- Migration status for rust-kanata (- to 1.9.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: rust-kanata rust-inotify (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-kanata/1.9.0-2: 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)
- rust-notify (6.1.1-3 to 6.1.1-5)
- Migration status for rust-notify (6.1.1-3 to 6.1.1-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-notify rust-bacon (not considered)
- Invalidated by implicit-dependency
- Depends: rust-notify rust-inotify
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-notify/6.1.1-5: 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)
- rust-upstream-ontologist (0.2.4-1 to 0.2.11-2)
- Migration status for rust-upstream-ontologist (0.2.4-1 to 0.2.11-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-upstream-ontologist rust-ognibuild (not considered)
- Invalidated by implicit-dependency
- Depends: rust-upstream-ontologist rust-breezyshim
- Additional info:
- sqlite3 (3.46.1-7 to 3.46.1-8)
- Migration status for sqlite3 (3.46.1-7 to 3.46.1-8): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 4 days old (needed 2 days)
- amass (4.2.0-0kali1 to 5.0.1-0kali1)
- Migration status for amass (4.2.0-0kali1 to 5.0.1-0kali1): 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 amass/5.0.1-0kali1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- avahi (0.8-16 to 0.8-17)
- Migration status for avahi (0.8-16 to 0.8-17): 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 avahi/0.8-17: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- f2fs-tools (1.16.0-1.1 to 1.16.0-2)
- Migration status for f2fs-tools (1.16.0-1.1 to 1.16.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)
- 5 days old (needed 2 days)
- fonttools (4.57.0-1 to 4.57.0-2)
- Migration status for fonttools (4.57.0-1 to 4.57.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: fonttools unicode-data (not considered)
- Invalidated by dependency
- Implicit dependency: fonttools matplotlib (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for fonttools/4.57.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- gcc-14 (14.3.0-5 to 14.3.0-7)
- Migration status for gcc-14 (14.3.0-5 to 14.3.0-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- gcc-15 (15.2.0-1 to 15.2.0-3)
- Migration status for gcc-15 (15.2.0-1 to 15.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 5 of 22 days old
- Additional info:
- gcc-defaults (1.220 to 1.226)
- Migration status for gcc-defaults (1.220 to 1.226): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- gdb (16.3-1 to 16.3-5)
- Migration status for gdb (16.3-1 to 16.3-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)
- 5 days old (needed 2 days)
- gnome-software (48.4-1 to 49~rc-1)
- Migration status for gnome-software (48.4-1 to 49~rc-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)
- 5 days old (needed 2 days)
- gnustep-base (1.31.1-3 to 1.31.1-4)
- Migration status for gnustep-base (1.31.1-3 to 1.31.1-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 gnustep-base/1.31.1-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- gtk-d (3.10.0-4 to 3.10.0-5)
- Migration status for gtk-d (3.10.0-4 to 3.10.0-5): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: gtk-d gcc-15 (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 5 days old (needed 2 days)
- libglib-object-introspection-perl (0.051-2 to 0.052-1)
- Migration status for libglib-object-introspection-perl (0.051-2 to 0.052-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for libglib-object-introspection-perl/0.052-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- libksysguard (4:6.3.5-1 to 4:6.3.5-2)
- Migration status for libksysguard (4:6.3.5-1 to 4:6.3.5-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libksysguard libnl3 (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 5 days old (needed 2 days)
- lximage-qt (2.1.1-1 to 2.2.0-1)
- Migration status for lximage-qt (2.1.1-1 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 5 days old (needed 2 days)
- lxqt-qtplugin (2.1.0-1 to 2.2.0-2)
- Migration status for lxqt-qtplugin (2.1.0-1 to 2.2.0-2): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 5 days old (needed 2 days)
- nginx (1.26.3-3 to 1.28.0-6)
- Migration status for nginx (1.26.3-3 to 1.28.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 nginx/1.28.0-6: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- numpy (1:2.2.4+ds-1 to 1:2.2.4+ds-1.2)
- Migration status for numpy (1:2.2.4+ds-1 to 1:2.2.4+ds-1.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 metpy/1.7.0+ds-2: amd64: Pass
- autopkgtest for numpy/1:2.2.4+ds-1.2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- pango1.0 (1.56.3-1 to 1.56.3-2)
- Migration status for pango1.0 (1.56.3-1 to 1.56.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)
- autopkgtest for pango1.0/1.56.3-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- pcmanfm-qt (2.1.0-2 to 2.2.0-1)
- Migration status for pcmanfm-qt (2.1.0-2 to 2.2.0-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 5 days old (needed 2 days)
- poppler (25.03.0-5 to 25.03.0-9)
- Migration status for poppler (25.03.0-5 to 25.03.0-9): 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-9: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- qt6-base (6.8.2+dfsg-10 to 6.8.2+dfsg-10.1)
- Migration status for qt6-base (6.8.2+dfsg-10 to 6.8.2+dfsg-10.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 cmake/3.31.6-2: amd64: Pass
- 5 days old (needed 2 days)
- (5.15.15-2 to 5.15.17-2)
- Migration status for qtx11extras-opensource-src (5.15.15-2 to 5.15.17-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- readline (8.2-6 to 8.3-3)
- Migration status for readline (8.2-6 to 8.3-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)
- 5 days old (needed 2 days)
- rust-bindgen (0.71.1-4 to 0.72.1-1)
- Migration status for rust-bindgen (0.71.1-4 to 0.72.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-chrono (0.4.39-2 to 0.4.42-1)
- Migration status for rust-chrono (0.4.39-2 to 0.4.42-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-chrono/0.4.42-1: amd64: Pass
- autopkgtest for rust-tera/1.20.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- rust-libsqlite3-sys (0.26.0-1 to 0.26.0-2)
- Migration status for rust-libsqlite3-sys (0.26.0-1 to 0.26.0-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: rust-libsqlite3-sys rust-bindgen (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-libsqlite3-sys/0.26.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- rust-libxml (0.3.5-1 to 0.3.5-2)
- Migration status for rust-libxml (0.3.5-1 to 0.3.5-2): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: rust-libxml rust-bindgen (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-libxml/0.3.5-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- rust-openssl-sys (0.9.109-1 to 0.9.109-2)
- Migration status for rust-openssl-sys (0.9.109-1 to 0.9.109-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-openssl-sys/0.9.109-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- rust-parsec-service (1.4.1-3 to 1.4.1-4)
- Migration status for rust-parsec-service (1.4.1-3 to 1.4.1-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: rust-parsec-service rust-bindgen (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-parsec-service/1.4.1-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- rust-regex (1.11.1-2 to 1.11.2-1)
- Migration status for rust-regex (1.11.1-2 to 1.11.2-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-regex/1.11.2-1: amd64: Pass
- autopkgtest for rust-tera/1.20.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- rust-zstd-sys (2.0.13-2 to 2.0.13-3)
- Migration status for rust-zstd-sys (2.0.13-2 to 2.0.13-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-zstd-sys/2.0.13-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- scipy (1.15.3-1 to 1.15.3-1.1)
- Migration status for scipy (1.15.3-1 to 1.15.3-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 metpy/1.7.0+ds-2: amd64: Pass
- autopkgtest for scipy/1.15.3-1.1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- snappy (1.2.2-1 to 1.2.2-2)
- Migration status for snappy (1.2.2-1 to 1.2.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)
- 5 days old (needed 2 days)
- sysprof (48.0-2 to 49~rc-1)
- Migration status for sysprof (48.0-2 to 49~rc-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- systemd (257.7-1 to 258~rc4-1)
- Migration status for systemd (257.7-1 to 258~rc4-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~rc4-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 5 days old (needed 2 days)
- tasmanian (8.1-4 to 8.1-5)
- Migration status for tasmanian (8.1-4 to 8.1-5): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 5 of 22 days old
- Additional info:
- unicode-data (15.1.0-1 to 16.0.0-1)
- Migration status for unicode-data (15.1.0-1 to 16.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 5 of 22 days old
- Additional info:
- utf8proc (2.9.0-1 to 2.10.0-2)
- Migration status for utf8proc (2.9.0-1 to 2.10.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing libutf8proc-dev/2.9.0-1+b2/armel from kali-rolling makes libmongoc-dev/2.1.0-1/armel uninstallable
- Too young, only 5 of 22 days old
- Additional info:
- xfsprogs (6.15.0-1 to 6.16.0-1)
- Migration status for xfsprogs (6.15.0-1 to 6.16.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)
- 5 days old (needed 2 days)
- alfred (2025.0-2 to 2025.3-1)
- Migration status for alfred (2025.0-2 to 2025.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: alfred libnl3 (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 6 days old (needed 2 days)
- batctl (2025.0-2 to 2025.3-1)
- Migration status for batctl (2025.0-2 to 2025.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: batctl libnl3 (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 6 days old (needed 2 days)
- chatty (0.8.7-2 to 0.8.7-3)
- Migration status for chatty (0.8.7-2 to 0.8.7-3): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- ettercap (1:0.8.3.1-14 to 1:0.8.3.1-15)
- Migration status for ettercap (1:0.8.3.1-14 to 1:0.8.3.1-15): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 6 days old (needed 2 days)
- ghostscript (10.05.1~dfsg-1 to 10.05.1~dfsg-3)
- Migration status for ghostscript (10.05.1~dfsg-1 to 10.05.1~dfsg-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 ghostscript/10.05.1~dfsg-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 6 days old (needed 2 days)
- gnome-desktop (44.3-4 to 44.4-1)
- Migration status for gnome-desktop (44.3-4 to 44.4-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- harfbuzz (10.2.0-1 to 11.4.5-1)
- Migration status for harfbuzz (10.2.0-1 to 11.4.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: harfbuzz pango1.0 (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: harfbuzz gtk+3.0 (not considered)
- Implicit dependency: harfbuzz gtk4 (not considered)
- Additional info:
- libffi (3.4.8-2 to 3.5.2-2)
- Migration status for libffi (3.4.8-2 to 3.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)
- 6 days old (needed 2 days)
- mpclib3 (1.3.1-1 to 1.3.1-2)
- Migration status for mpclib3 (1.3.1-1 to 1.3.1-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 gcc-13/13.4.0-1: amd64: Pass
- 6 days old (needed 2 days)
- mpfr4 (4.2.2-1 to 4.2.2-2)
- Migration status for mpfr4 (4.2.2-1 to 4.2.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: mpfr4 mpclib3 (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gcc-13/13.4.0-1: amd64: Pass
- 6 days old (needed 2 days)
- ostree (2025.4-1 to 2025.6-1)
- Migration status for ostree (2025.4-1 to 2025.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 ostree/2025.6-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 6 days old (needed 2 days)
- python-hypothesis (6.138.0-1 to 6.138.14-1)
- Migration status for python-hypothesis (6.138.0-1 to 6.138.14-1): 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:
- vte2.91 (0.80.3-2 to 0.80.3-3)
- Migration status for vte2.91 (0.80.3-2 to 0.80.3-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: vte2.91 pcre2 (not considered)
- Invalidated by dependency
- Depends: vte2.91 at-spi2-core (not considered)
- Additional info:
- wireplumber (0.5.10-3 to 0.5.11-1)
- Migration status for wireplumber (0.5.10-3 to 0.5.11-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- colord (1.4.7-3 to 1.4.8-1)
- Migration status for colord (1.4.7-3 to 1.4.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)
- autopkgtest for colord/1.4.8-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 7 days old (needed 2 days)
- fcitx5-qt (5.1.10-1 to 5.1.10-2)
- Migration status for fcitx5-qt (5.1.10-1 to 5.1.10-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- fontconfig (2.15.0-2.3 to 2.15.0-2.4)
- Migration status for fontconfig (2.15.0-2.3 to 2.15.0-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)
- 7 days old (needed 2 days)
- hwloc (2.12.0-4 to 2.12.2-1)
- Migration status for hwloc (2.12.0-4 to 2.12.2-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 hwloc/2.12.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 7 days old (needed 2 days)
- hwloc-contrib (2.12.0-3 to 2.12.2-2)
- Migration status for hwloc-contrib (2.12.0-3 to 2.12.2-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: hwloc-contrib hwloc (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- kali-meta (2025.3.2 to 2025.4.2)
- Migration status for kali-meta (2025.3.2 to 2025.4.2): 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)
- 7 days old (needed 2 days)
- libnl3 (3.7.0-2 to 3.11.0-2)
- Migration status for libnl3 (3.7.0-2 to 3.11.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)
- 7 days old (needed 2 days)
- liburing (2.11-1 to 2.12-1)
- Migration status for liburing (2.11-1 to 2.12-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: liburing libdex (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for liburing/2.12-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 7 days old (needed 2 days)
- mesa (25.0.7-2 to 25.2.2-1)
- Migration status for mesa (25.0.7-2 to 25.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- openvpn (2.6.14-1 to 2.6.14-2)
- Migration status for openvpn (2.6.14-1 to 2.6.14-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 openvpn/2.6.14-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 7 days old (needed 2 days)
- qt3d-opensource-src (5.15.15+dfsg-3 to 5.15.17+dfsg-2)
- Migration status for qt3d-opensource-src (5.15.15+dfsg-3 to 5.15.17+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtbase-opensource-src (5.15.15+dfsg-6 to 5.15.17+dfsg-2)
- Migration status for qtbase-opensource-src (5.15.15+dfsg-6 to 5.15.17+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- qtbase-opensource-src-gles (5.15.15+dfsg-2 to 5.15.17+dfsg-2)
- Migration status for qtbase-opensource-src-gles (5.15.15+dfsg-2 to 5.15.17+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 7 of 22 days old
- Depends: qtbase-opensource-src-gles qtbase-opensource-src (not considered)
- Additional info:
- qtcharts-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtcharts-opensource-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtconnectivity-opensource-src (5.15.15-3 to 5.15.17-2)
- Migration status for qtconnectivity-opensource-src (5.15.15-3 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtdatavis3d-everywhere-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtdatavis3d-everywhere-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtdeclarative-opensource-src (5.15.15+dfsg-3 to 5.15.17+dfsg-2)
- Migration status for qtdeclarative-opensource-src (5.15.15+dfsg-3 to 5.15.17+dfsg-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- qtdeclarative-opensource-src-gles (5.15.15+dfsg-2 to 5.15.17+dfsg-2)
- Migration status for qtdeclarative-opensource-src-gles (5.15.15+dfsg-2 to 5.15.17+dfsg-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- qtgamepad-everywhere-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtgamepad-everywhere-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtgraphicaleffects-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtgraphicaleffects-opensource-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtimageformats-opensource-src (5.15.15-4 to 5.15.17-2)
- Migration status for qtimageformats-opensource-src (5.15.15-4 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtlocation-opensource-src (5.15.15+dfsg-3 to 5.15.17+dfsg-2)
- Migration status for qtlocation-opensource-src (5.15.15+dfsg-3 to 5.15.17+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtmultimedia-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtmultimedia-opensource-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtnetworkauth-everywhere-src (5.15.15-3 to 5.15.17-2)
- Migration status for qtnetworkauth-everywhere-src (5.15.15-3 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtpim-opensource-src (5.0~git20201102.f9a8f0fc+dfsg1-6 to 5.0~git20201102.f9a8f0fc+dfsg1-7)
- Migration status for qtpim-opensource-src (5.0~git20201102.f9a8f0fc+dfsg1-6 to 5.0~git20201102.f9a8f0fc+dfsg1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtquickcontrols-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtquickcontrols-opensource-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtquickcontrols2-opensource-src (5.15.15+dfsg-2 to 5.15.17+dfsg-2)
- Migration status for qtquickcontrols2-opensource-src (5.15.15+dfsg-2 to 5.15.17+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtscript-opensource-src (5.15.15+dfsg-2 to 5.15.17+dfsg-2)
- Migration status for qtscript-opensource-src (5.15.15+dfsg-2 to 5.15.17+dfsg-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)
- 7 days old (needed 2 days)
- qtsensors-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtsensors-opensource-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtserialport-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtserialport-opensource-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtspeech-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtspeech-opensource-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtsvg-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtsvg-opensource-src (5.15.15-2 to 5.15.17-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)
- 7 days old (needed 2 days)
- qtsystems-opensource-src (5.0~git20230712.81e08ee+dfsg-3 to 5.0~git20230712.81e08ee+dfsg-4)
- Migration status for qtsystems-opensource-src (5.0~git20230712.81e08ee+dfsg-3 to 5.0~git20230712.81e08ee+dfsg-4): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qttools-opensource-src (5.15.15-6 to 5.15.17-3)
- Migration status for qttools-opensource-src (5.15.15-6 to 5.15.17-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)
- 7 days old (needed 2 days)
- qtvirtualkeyboard-opensource-src (5.15.15+dfsg-2 to 5.15.17+dfsg-2)
- Migration status for qtvirtualkeyboard-opensource-src (5.15.15+dfsg-2 to 5.15.17+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtwayland-opensource-src (5.15.15-3 to 5.15.17-3)
- Migration status for qtwayland-opensource-src (5.15.15-3 to 5.15.17-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtwebchannel-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtwebchannel-opensource-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtwebsockets-opensource-src (5.15.15-2 to 5.15.17-3)
- Migration status for qtwebsockets-opensource-src (5.15.15-2 to 5.15.17-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- qtwebview-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtwebview-opensource-src (5.15.15-2 to 5.15.17-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)
- 7 days old (needed 2 days)
- qtxmlpatterns-opensource-src (5.15.15-2 to 5.15.17-2)
- Migration status for qtxmlpatterns-opensource-src (5.15.15-2 to 5.15.17-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 7 days old (needed 2 days)
- rust-errno (0.3.8-1 to 0.3.13-2)
- Migration status for rust-errno (0.3.8-1 to 0.3.13-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-errno/0.3.13-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 7 days old (needed 2 days)
- rust-syn (2.0.98-1 to 2.0.105-1)
- Migration status for rust-syn (2.0.98-1 to 2.0.105-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-syn/2.0.105-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 7 days old (needed 2 days)
- tini (0.19.0-3 to 0.19.0-4)
- Migration status for tini (0.19.0-3 to 0.19.0-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)
- 7 days old (needed 2 days)
- xorg-server (2:21.1.16-1.3 to 2:21.1.18-2)
- Migration status for xorg-server (2:21.1.16-1.3 to 2:21.1.18-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- accountsservice (23.13.9-7 to 23.13.9-8)
- Migration status for accountsservice (23.13.9-7 to 23.13.9-8): 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 accountsservice/23.13.9-8: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- bash (5.2.37-2 to 5.3-1)
- Migration status for bash (5.2.37-2 to 5.3-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: bash airgeddon (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 8 days old (needed 2 days)
- binutils-gold (2.44-2 to 2.44-3)
- Migration status for binutils-gold (2.44-2 to 2.44-3): 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
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for binutils-gold/2.44-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- dwz (0.15-1 to 0.16-2)
- Migration status for dwz (0.15-1 to 0.16-2): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 8 days old (needed 2 days)
- epiphany-browser (48.5-2 to 48.5-3)
- Migration status for epiphany-browser (48.5-2 to 48.5-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)
- 8 days old (needed 2 days)
- folium (0.20.0+dfsg-1 to 0.20.0+dfsg-2)
- Migration status for folium (0.20.0+dfsg-1 to 0.20.0+dfsg-2): 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:
- git (1:2.50.1-0.1 to 1:2.51.0-1)
- Migration status for git (1:2.50.1-0.1 to 1:2.51.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)
- 8 days old (needed 2 days)
- gmp (2:6.3.0+dfsg-4 to 2:6.3.0+dfsg-5)
- Migration status for gmp (2:6.3.0+dfsg-4 to 2:6.3.0+dfsg-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 gmp/2:6.3.0+dfsg-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- gsettings-desktop-schemas (49~beta-1 to 49~rc-1)
- Migration status for gsettings-desktop-schemas (49~beta-1 to 49~rc-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- removing gsettings-desktop-schemas-dev/49~beta-1/armel from kali-rolling makes phosh-dev/0.49.0-1/armel uninstallable
- Implicit dependency: gsettings-desktop-schemas gnome-desktop (not considered)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 8 days old (needed 2 days)
- imagemagick (8:7.1.1.43+dfsg1-1 to 8:7.1.2.3+dfsg1-1)
- Migration status for imagemagick (8:7.1.1.43+dfsg1-1 to 8:7.1.2.3+dfsg1-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for imagemagick/8:7.1.2.3+dfsg1-1: amd64: Pass
- autopkgtest for sphinx/8.2.3-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- java-atk-wrapper (0.42.1-1 to 0.42.1-2)
- Migration status for java-atk-wrapper (0.42.1-1 to 0.42.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: java-atk-wrapper openjdk-21 (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 8 days old (needed 2 days)
- kf6-kfilemetadata (6.13.0-1 to 6.13.0-2)
- Migration status for kf6-kfilemetadata (6.13.0-1 to 6.13.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)
- autopkgtest for kf6-kfilemetadata/6.13.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- libgudev (238-6 to 238-7)
- Migration status for libgudev (238-6 to 238-7): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 8 days old (needed 2 days)
- libsys-virt-perl (11.1.0-1 to 11.6.0-1)
- Migration status for libsys-virt-perl (11.1.0-1 to 11.6.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 libsys-virt-perl/11.6.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- libxklavier (5.4-5 to 5.4-6)
- Migration status for libxklavier (5.4-5 to 5.4-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)
- 8 days old (needed 2 days)
- libzstd (1.5.7+dfsg-1 to 1.5.7+dfsg-1.1)
- Migration status for libzstd (1.5.7+dfsg-1 to 1.5.7+dfsg-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 libzstd/1.5.7+dfsg-1.1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- lxml (5.4.0-1 to 6.0.1-1)
- Migration status for lxml (5.4.0-1 to 6.0.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- mdadm (4.4-11 to 4.4-12)
- Migration status for mdadm (4.4-11 to 4.4-12): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- openpyxl (3.1.5+dfsg-2 to 3.1.5+dfsg-3)
- Migration status for openpyxl (3.1.5+dfsg-2 to 3.1.5+dfsg-3): 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:
- playwright-python (1.42.0-0kali2 to 1.42.0-0kali3)
- Migration status for playwright-python (1.42.0-0kali2 to 1.42.0-0kali3): Will attempt migration (Any information below is purely informational)
- Additional info:
- python-cvss (- to 3.6-1)
- Migration status for python-cvss (- to 3.6-1): 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 8 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
- python-geopandas (1.1.1-1 to 1.1.1-2)
- Migration status for python-geopandas (1.1.1-1 to 1.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 8 of 22 days old
- Additional info:
- readpe (0.84-2 to 0.85.1-1)
- Migration status for readpe (0.84-2 to 0.85.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: readpe kali-meta (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for readpe/0.85.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-async-trait (0.1.83-1 to 0.1.89-1)
- Migration status for rust-async-trait (0.1.83-1 to 0.1.89-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-async-trait/0.1.89-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-broot (1.47.0-2 to 1.48.0-1)
- Migration status for rust-broot (1.47.0-2 to 1.48.0-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 rust-broot/1.48.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-clap-help (1.4.0-3 to 1.5.0-1)
- Migration status for rust-clap-help (1.4.0-3 to 1.5.0-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Additional info:
- rust-crc (3.2.1-1 to 3.3.0-1)
- Migration status for rust-crc (3.2.1-1 to 3.3.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-crc/3.3.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-dysk-cli (2.10.1-2 to 3.1.0-1)
- Migration status for rust-dysk-cli (2.10.1-2 to 3.1.0-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 rust-dysk-cli/3.1.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-lfs-core (0.12.0-1 to 0.14.1-1)
- Migration status for rust-lfs-core (0.12.0-1 to 0.14.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-lfs-core rust-dysk-cli (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-lfs-core rust-broot
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-lfs-core/0.14.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-log (0.4.26-1 to 0.4.27-1)
- Migration status for rust-log (0.4.26-1 to 0.4.27-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-log/0.4.27-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-memchr (2.7.4-1 to 2.7.5-1)
- Migration status for rust-memchr (2.7.4-1 to 2.7.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 rust-memchr/2.7.5-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-railway-api (0.1.2-7 to 0.2.0-1)
- Migration status for rust-railway-api (0.1.2-7 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-railway-api-derive (0.1.2-1 to 0.2.0-1)
- Migration status for rust-railway-api-derive (0.1.2-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-railway-api-derive rust-railway-api (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-railway-api-derive/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
- 8 days old (needed 2 days)
- rust-railway-core (0.1.2-4 to 0.2.0-1)
- Migration status for rust-railway-core (0.1.2-4 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-railway-core/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
- 8 days old (needed 2 days)
- rust-railway-provider-db-movas (0.1.1-2 to 0.2.0-1)
- Migration status for rust-railway-provider-db-movas (0.1.1-2 to 0.2.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- librust-railway-provider-db-movas-dev/amd64 has unsatisfiable dependency
- librust-railway-provider-db-movas-dev/arm64 has unsatisfiable dependency
- librust-railway-provider-db-movas-dev/armhf has unsatisfiable dependency
- librust-railway-provider-db-movas-dev/i386 has unsatisfiable dependency
- Too young, only 8 of 22 days old
- Implicit dependency: rust-railway-provider-db-movas rust-railway-api
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- uninstallable on arch amd64, not running autopkgtest there
- Required age increased by 20 days because of autopkgtest
- rust-railway-provider-hafas (0.1.2-3 to 0.2.0-1)
- Migration status for rust-railway-provider-hafas (0.1.2-3 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-railway-provider-motis (0.2.0-2 to 0.3.0-1)
- Migration status for rust-railway-provider-motis (0.2.0-2 to 0.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-railway-provider-motis/0.3.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-railway-provider-search-ch (0.1.1-1 to 0.2.0-1)
- Migration status for rust-railway-provider-search-ch (0.1.1-1 to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: rust-railway-provider-search-ch rust-railway-core (not considered)
- Invalidated by dependency
- Implicit dependency: rust-railway-provider-search-ch rust-railway-api
- Additional info:
- rust-rkyv (0.8.9-2 to 0.8.9-5)
- Migration status for rust-rkyv (0.8.9-2 to 0.8.9-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 rust-rkyv/0.8.9-5: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-smallvec (1.13.2-1 to 1.15.1-1)
- Migration status for rust-smallvec (1.13.2-1 to 1.15.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-smallvec/1.15.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-tokio-vsock (0.5.0-3 to 0.7.0-1)
- Migration status for rust-tokio-vsock (0.5.0-3 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-tokio-vsock rust-zbus (not considered)
- Invalidated by implicit-dependency
- Depends: rust-tokio-vsock rust-vsock
- Additional info:
- rust-trawldb (0.2.9-3 to 0.2.9-4)
- Migration status for rust-trawldb (0.2.9-3 to 0.2.9-4): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: rust-trawldb rust-zbus (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-trawldb/0.2.9-4: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-unique-id (- to 0.1.7~20250804-2)
- Migration status for rust-unique-id (- to 0.1.7~20250804-2): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- librust-unique-id-dev/amd64 has unsatisfiable dependency
- Too young, only 8 of 22 days old
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- uninstallable on arch amd64, not running autopkgtest there
- Required age increased by 20 days because of autopkgtest
- rust-vsock (0.4.0-5 to 0.5.1-1)
- Migration status for rust-vsock (0.4.0-5 to 0.5.1-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-vsock rust-zbus (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-vsock rust-tokio-vsock
- Additional info:
- rust-wayland-backend (0.3.8-3 to 0.3.11-2)
- Migration status for rust-wayland-backend (0.3.8-3 to 0.3.11-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-wayland-backend/0.3.11-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-zbus (5.3.0-2 to 5.6.0-3)
- Migration status for rust-zbus (5.3.0-2 to 5.6.0-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 rust-zbus/5.6.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-zbus-macros (5.3.0-2 to 5.10.0-1)
- Migration status for rust-zbus-macros (5.3.0-2 to 5.10.0-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 rust-zbus-macros/5.10.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-zvariant (5.2.0-4 to 5.7.0-1)
- Migration status for rust-zvariant (5.2.0-4 to 5.7.0-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 rust-zvariant/5.7.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- rust-zvariant-derive (5.2.0-2 to 5.7.0-1)
- Migration status for rust-zvariant-derive (5.2.0-2 to 5.7.0-1): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Additional info:
- spice-vdagent (0.22.1-4.1 to 0.22.1-5)
- Migration status for spice-vdagent (0.22.1-4.1 to 0.22.1-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- tcpreplay (4.5.1-1 to 4.5.2-1)
- Migration status for tcpreplay (4.5.1-1 to 4.5.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: tcpreplay kali-meta (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for tcpreplay/4.5.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- tecla (48.0.2-1 to 49~rc-1)
- Migration status for tecla (48.0.2-1 to 49~rc-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)
- 8 days old (needed 2 days)
- timescaledb (2.21.3+dfsg-1 to 2.22.0+dfsg-1)
- Migration status for timescaledb (2.21.3+dfsg-1 to 2.22.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 8 of 22 days old
- Additional info:
- udisks2 (2.10.90-3 to 2.10.91-1)
- Migration status for udisks2 (2.10.90-3 to 2.10.91-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- xz-utils (5.8.1-1 to 5.8.1-1.1)
- Migration status for xz-utils (5.8.1-1 to 5.8.1-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 cmake/3.31.6-2: amd64: Pass
- autopkgtest for distrobuilder/3.2-2: amd64: Pass
- autopkgtest for xz-utils/5.8.1-1.1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 8 days old (needed 2 days)
- cockpit-machines (332-1 to 339-1)
- Migration status for cockpit-machines (332-1 to 339-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- Too young, only 11 of 22 days old
- Additional info:
- exiv2 (0.28.5+dfsg-1 to 0.28.7+dfsg-2)
- Migration status for exiv2 (0.28.5+dfsg-1 to 0.28.7+dfsg-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: exiv2 kali-meta (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 11 days old (needed 2 days)
- firebird4.0 (4.0.6.3221.ds6-1 to 4.0.6.3221.ds6-2)
- Migration status for firebird4.0 (4.0.6.3221.ds6-1 to 4.0.6.3221.ds6-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 firebird4.0/4.0.6.3221.ds6-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)
- gcr (3.41.2-3 to 3.41.2-4)
- Migration status for gcr (3.41.2-3 to 3.41.2-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- rust-rayon (1.10.0-1 to 1.11.0-1)
- Migration status for rust-rayon (1.10.0-1 to 1.11.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-rayon/1.11.0-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)
- rust-rayon-core (1.12.1-1 to 1.13.0-1)
- Migration status for rust-rayon-core (1.12.1-1 to 1.13.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-rayon-core/1.13.0-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)
- at-spi2-core (2.57.1-1 to 2.57.2-1)
- Migration status for at-spi2-core (2.57.1-1 to 2.57.2-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 at-spi2-core/2.57.2-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- libtool (2.5.4-4 to 2.5.4-5)
- Migration status for libtool (2.5.4-4 to 2.5.4-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)
- 12 days old (needed 2 days)
- m4 (1.4.19-8 to 1.4.20-1)
- Migration status for m4 (1.4.19-8 to 1.4.20-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 m4/1.4.20-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- openjdk-21 (21.0.8+9-1 to 21.0.9~5ea-1)
- Migration status for openjdk-21 (21.0.8+9-1 to 21.0.9~5ea-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 openjdk-21/21.0.9~5ea-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- parted (3.6-5 to 3.6-6)
- Migration status for parted (3.6-5 to 3.6-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)
- 12 days old (needed 2 days)
- rust-async-channel (2.3.1-9 to 2.5.0-2)
- Migration status for rust-async-channel (2.3.1-9 to 2.5.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)
- autopkgtest for rust-async-channel/2.5.0-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-deb822-derive (0.2.0-1 to 0.3.0-1)
- Migration status for rust-deb822-derive (0.2.0-1 to 0.3.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-deb822-derive rust-deb822-lossless (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-deb822-derive/0.3.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-deb822-fast (- to 0.2.0-1)
- Migration status for rust-deb822-fast (- to 0.2.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-deb822-fast/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
- 12 days old (needed 2 days)
- rust-deb822-lossless (0.2.3-1 to 0.3.2-1)
- Migration status for rust-deb822-lossless (0.2.3-1 to 0.3.2-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-debian-analyzer (0.158.27-1 to 0.159.3-2)
- Migration status for rust-debian-analyzer (0.158.27-1 to 0.159.3-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-debian-control (0.1.39-1 to 0.1.48-1)
- Migration status for rust-debian-control (0.1.39-1 to 0.1.48-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-debian-copyright (0.1.27-1 to 0.1.28-1)
- Migration status for rust-debian-copyright (0.1.27-1 to 0.1.28-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: rust-debian-copyright rust-deb822-fast (not considered)
- Invalidated by dependency
- Additional info:
- rust-debversion (0.4.4-2 to 0.4.7-1)
- Migration status for rust-debversion (0.4.4-2 to 0.4.7-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- rust-dep3 (0.1.28-1 to 0.1.28-2)
- Migration status for rust-dep3 (0.1.28-1 to 0.1.28-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-event-listener-strategy (0.5.3-1 to 0.5.4-2)
- Migration status for rust-event-listener-strategy (0.5.3-1 to 0.5.4-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 rust-event-listener-strategy/0.5.4-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-hashbrown (0.14.5-5 to 0.15.5-1)
- Migration status for rust-hashbrown (0.14.5-5 to 0.15.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 rust-hashbrown/0.15.5-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-indexmap (2.7.0-1 to 2.7.0-3)
- Migration status for rust-indexmap (2.7.0-1 to 2.7.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 rust-indexmap/2.7.0-3: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-jiter (0.7.1-1 to 0.10.0-1)
- Migration status for rust-jiter (0.7.1-1 to 0.10.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-launchpadlib (- to 0.4.6-2)
- Migration status for rust-launchpadlib (- to 0.4.6-2): Will attempt migration (Any information below is purely informational)
- Additional info:
- rust-lexical-parse-float (0.8.5-1 to 1.0.5-1)
- Migration status for rust-lexical-parse-float (0.8.5-1 to 1.0.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-lexical-parse-float/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
- 12 days old (needed 2 days)
- rust-lexical-parse-integer (0.8.6-1 to 1.0.5-1)
- Migration status for rust-lexical-parse-integer (0.8.6-1 to 1.0.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-lexical-parse-integer/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
- 12 days old (needed 2 days)
- rust-lexical-util (0.8.5-1 to 1.0.6-1)
- Migration status for rust-lexical-util (0.8.5-1 to 1.0.6-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-lexical-util/1.0.6-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-ognibuild (0.0.34-1 to 0.1.4-1)
- Migration status for rust-ognibuild (0.0.34-1 to 0.1.4-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-pyo3 (0.22.6-3 to 0.25.1-5)
- Migration status for rust-pyo3 (0.22.6-3 to 0.25.1-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)
- uninstallable on arch amd64, not running autopkgtest there
- Required age increased by 20 days because of autopkgtest
- rust-pyo3-async-runtimes (0.22.0-3 to 0.25.0-1)
- Migration status for rust-pyo3-async-runtimes (0.22.0-3 to 0.25.0-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- rust-pyo3-async-runtimes-macros (0.22.0-1 to 0.25.0-1)
- Migration status for rust-pyo3-async-runtimes-macros (0.22.0-1 to 0.25.0-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-pyo3-async-runtimes-macros/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
- 12 days old (needed 2 days)
- rust-pyo3-build-config (0.22.6-1 to 0.25.1-1)
- Migration status for rust-pyo3-build-config (0.22.6-1 to 0.25.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-pyo3-build-config rust-pyo3 (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-pyo3-build-config rust-jiter
- Implicit dependency: rust-pyo3-build-config rust-pyo3-ffi
- Implicit dependency: rust-pyo3-build-config rust-pyo3-macros-backend
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-pyo3-build-config/0.25.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-pyo3-ffi (0.22.6-2 to 0.25.1-2)
- Migration status for rust-pyo3-ffi (0.22.6-2 to 0.25.1-2): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-pyo3-ffi/0.25.1-2: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-pyo3-filelike (0.3.0-2 to 0.5.0-1)
- Migration status for rust-pyo3-filelike (0.3.0-2 to 0.5.0-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- rust-pyo3-log (0.11.0-1 to 0.12.4-1)
- Migration status for rust-pyo3-log (0.11.0-1 to 0.12.4-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- rust-pyo3-macros (0.22.6-1 to 0.25.1-1)
- Migration status for rust-pyo3-macros (0.22.6-1 to 0.25.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-pyo3-macros/0.25.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-pyo3-macros-backend (0.22.6-1 to 0.25.1-1)
- Migration status for rust-pyo3-macros-backend (0.22.6-1 to 0.25.1-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-pyo3-macros-backend/0.25.1-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-pythonize (0.21.1-1 to 0.25.0-1)
- Migration status for rust-pythonize (0.21.1-1 to 0.25.0-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- rust-r-description (0.3.1-2 to 0.3.5-1)
- Migration status for rust-r-description (0.3.1-2 to 0.3.5-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- rust-speedate (0.15.0-1 to 0.16.0-1)
- Migration status for rust-speedate (0.15.0-1 to 0.16.0-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-speedate/0.16.0-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-wayland-client (0.31.8-1 to 0.31.11-1)
- Migration status for rust-wayland-client (0.31.8-1 to 0.31.11-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-client/0.31.11-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-wayland-cursor (0.31.3-1 to 0.31.11-1)
- Migration status for rust-wayland-cursor (0.31.3-1 to 0.31.11-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-wayland-cursor/0.31.11-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-wayland-egl (0.32.0-2 to 0.32.8-1)
- Migration status for rust-wayland-egl (0.32.0-2 to 0.32.8-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for rust-wayland-egl/0.32.8-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- rust-wayland-server (0.31.7-1 to 0.31.10-1)
- Migration status for rust-wayland-server (0.31.7-1 to 0.31.10-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-server/0.31.10-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 12 days old (needed 2 days)
- vopono (0.10.12-0kali1 to 0.10.14-0kali1)
- Migration status for vopono (0.10.12-0kali1 to 0.10.14-0kali1): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below)
- Issues preventing migration:
- Additional info:
- wayland (1.23.1-3 to 1.24.0-2)
- Migration status for wayland (1.23.1-3 to 1.24.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)
- 12 days old (needed 2 days)
- willow (1.6.2-3 to 1.11.0-0.1)
- Migration status for willow (1.6.2-3 to 1.11.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 12 of 22 days old
- Additional info:
- cmark-gfm (0.29.0.gfm.13-4 to 0.29.0.gfm.13-7)
- Migration status for cmark-gfm (0.29.0.gfm.13-4 to 0.29.0.gfm.13-7): 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 cmark-gfm/0.29.0.gfm.13-7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 13 days old (needed 2 days)
- gcr4 (4.4.0.1-6 to 4.4.0.1-7)
- Migration status for gcr4 (4.4.0.1-6 to 4.4.0.1-7): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: gcr4 gcr (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for gcr4/4.4.0.1-7: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 13 days old (needed 2 days)
- mc (3:4.8.33-1 to 3:4.8.33-1.1)
- Migration status for mc (3:4.8.33-1 to 3:4.8.33-1.1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: mc kali-meta (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 13 days old (needed 2 days)
- pillow (11.1.0-5 to 11.3.0-1)
- Migration status for pillow (11.1.0-5 to 11.3.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Additional info:
- rust-sha2 (0.10.8-1 to 0.10.9-1)
- Migration status for rust-sha2 (0.10.8-1 to 0.10.9-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-sha2/0.10.9-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 13 days old (needed 2 days)
- rust-wayland-scanner (0.31.6-1 to 0.31.7-1)
- Migration status for rust-wayland-scanner (0.31.6-1 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-scanner/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
- 13 days old (needed 2 days)
- wireshark (4.4.7-1 to 4.4.9-1)
- Migration status for wireshark (4.4.7-1 to 4.4.9-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 wireshark/4.4.9-1: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 13 days old (needed 2 days)
- darkstat (3.0.721-2 to 3.0.721-3)
- Migration status for darkstat (3.0.721-2 to 3.0.721-3): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: darkstat kali-meta (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 14 days old (needed 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: dns2tcp kali-meta (not considered)
- Invalidated by implicit-dependency
- 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
- 14 days old (needed 2 days)
- firewalk (5.0-5 to 5.0-6)
- Migration status for firewalk (5.0-5 to 5.0-6): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: firewalk kali-meta (not considered)
- Invalidated by implicit-dependency
- Additional info:
- lomiri (- to 0.5.0-6)
- Migration status for lomiri (- to 0.5.0-6): 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)
- 14 days old (needed 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-wayland-sys rust-wayland-backend (not considered)
- Invalidated by implicit-dependency
- 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
- 14 days old (needed 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): 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 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
- 14 days old (needed 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
- 15 days old (needed 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 15 of 22 days old
- Additional info:
- 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
- 15 days old (needed 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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
- 15 days old (needed 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)
- 15 days old (needed 2 days)
- 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: libnginx-mod-http-lua nginx (not considered)
- Implicit dependency: libnginx-mod-http-lua nginx (not considered)
- Invalidated by dependency
- Invalidated by implicit-dependency
- 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
- 15 days old (needed 2 days)
- 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
- 15 days old (needed 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)
- 15 days old (needed 2 days)
- parole (4.18.2-1 to 4.20.0-1)
- Migration status for parole (4.18.2-1 to 4.20.0-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 15 days old (needed 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)
- 15 days old (needed 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 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
- 15 days old (needed 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 15 of 22 days old
- Additional info:
- pymssql (2.3.2-1 to 2.3.7-1)
- Migration status for pymssql (2.3.2-1 to 2.3.7-1): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- autopkgtest for pymssql/2.3.7-1: 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)
- 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
- 15 days old (needed 2 days)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rarcrack kali-meta (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 15 days old (needed 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-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 another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: rust-bacon rust-termimad (not considered)
- Invalidated by dependency
- 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
- 15 days old (needed 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
- 15 days old (needed 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): Will attempt migration (Any information below is purely informational)
- 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
- 15 days old (needed 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
- 15 days old (needed 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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
- 15 days old (needed 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: rust-kvm-bindings rust-zerocopy (not considered)
- Invalidated by dependency
- 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
- 15 days old (needed 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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
- 15 days old (needed 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
- 15 days old (needed 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Additional info:
- 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
- 15 days old (needed 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-prettyplease rust-bindgen (not considered)
- Invalidated by implicit-dependency
- 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
- 15 days old (needed 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
- 15 days old (needed 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
- 15 days old (needed 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-termimad rust-clap-help (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-termimad rust-bacon
- Implicit dependency: rust-termimad rust-broot
- Implicit dependency: rust-termimad rust-dysk-cli
- 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
- 15 days old (needed 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: rust-tokio-socks rust-reqwest (not considered)
- Invalidated by implicit-dependency
- 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
- 15 days old (needed 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Depends: rust-utmp-classic-raw rust-zerocopy (not considered)
- Invalidated by dependency
- 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
- 15 days old (needed 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
- 15 days old (needed 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): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- 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
- 15 days old (needed 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): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Implicit dependency: rust-zvariant-utils rust-zvariant (not considered)
- Invalidated by implicit-dependency
- Implicit dependency: rust-zvariant-utils rust-zvariant-derive
- 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
- 15 days old (needed 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:
- xdg-user-dirs (0.18-2 to 0.18-3)
- Migration status for xdg-user-dirs (0.18-2 to 0.18-3): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 15 days old (needed 2 days)
- 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): Will attempt migration (Any information below is purely informational)
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 15 days old (needed 2 days)
- 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)
- 15 days old (needed 2 days)
- 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: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- Implicit dependency: joplin kali-meta (not considered)
- Invalidated by implicit-dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 19 days old (needed 2 days)
- 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 postgresql-common/282: amd64: Pass
- Required age reduced by 3 days because of autopkgtest
- Required age is not allowed to drop below 2 days
- 29 days old (needed 2 days)
- lomiri-session (- to 0.3-11)
- Migration status for lomiri-session (- to 0.3-11): Waiting for another item to be ready to migrate (no action required now - check later)
- Issues preventing migration:
- Depends: lomiri-session lomiri (not considered)
- Invalidated by dependency
- Additional info:
- Cannot be tested by piuparts (not a blocker) - (no link yet)
- 90 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)
- 252 days old (needed 2 days)