Server Version#: 1.40.0.7775
I get an error when trying to cmdline install the new server 1.40.0.7996 where the compression is not compatible. (ZDST on DPKG).
dpkg-deb: error: archive 'newplex.deb' uses unknown compression for member 'control.tar.zst', giving up
dpkg: error processing archive newplex.deb (--install):
dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:```
I think this is a Ubuntu vs pure Debian thing. Any workarounds?
This appears to work in BULLSEYE (Deb 11).
# Extract files from the archive
ar x some-package.deb
# Uncompress zstd files an re-compress them using xz
zstd -d < control.tar.zst | xz > control.tar.xz
zstd -d < data.tar.zst | xz > data.tar.xz
# Re-create the Debian package in /tmp/
ar -m -c -a sdsd /tmp/some-package.deb debian-binary control.tar.xz data.tar.xz
# Clean up
rm debian-binary control.tar.xz data.tar.xz control.tar.zst data.tar.zst
sudo apt install /tmp/some-package.deb
Will upgrade to BOOKWORM (12) and see if it works better 
100% a Debian 11 issue. Upgrading to 12 (bookworm) works perfectly.
Here’s what I did to upgrade (to save people from searching)
-
Backup the system.
-
Update existing packages and reboot the Debian 11 system:
apt get update && apt get upgrade
reboot
-
Edit the file /etc/apt/sources.list replace bullseye with bookworm.
Next find the update line, replace keyword bullseye-updates with bookworm-updates.
Finally, replace keyword bullseye-security with bookworm-security
-
Update the packages index on Debian Linux, run:
sudo apt update
-
Prepare for the operating system minimal system upgrade, run:
sudo apt upgrade --without-new-pkgs
-
Finally, update Debian 11 to Debian 12 Bookworm by running:
sudo apt full-upgrade
-
Reboot the Linux system so that you can boot into Debian 12 Bookworm
Thank you for bringing this to our attention! We recently upgraded our CI systems, which brought in a newer dpkg with a new default compression. Unfortunately zdst compression is not supported in the dpkg shipped with Debian 11 or earlier. This will be addressed before 1.40 is pushed to public.
Happy to be of some help - hopefully this lets others know to keep on their updates, lol!