Can't unpack latest GCM deb package

[dotCore-off]

GCM Version

2.0.886

OS Version

Debian 11 Bullseye

Description

Using dpkg -i on latest available .deb package returns an error and prevent unpacking GCM

Error log

~ sudo dpkg -i gcm-linux_amd64.2.0.886.deb
dpkg-deb: error: archive 'gcm-linux_amd64.2.0.886.deb' uses unknown compression for member 'control.tar.zst', giving up
dpkg: error processing archive gcm-linux_amd64.2.0.886.deb (--install):
 dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
 gcm-linux_amd64.2.0.886.deb

Expected log (using previous GCM release)

~ sudo dpkg -i gcm-linux_amd64.2.0.877.deb
Selecting previously unselected package gcm.
(Reading database ... 20058 files and directories currently installed.)
Preparing to unpack gcm-linux_amd64.2.0.877.deb ...
Unpacking gcm (2.0.877) ...

Setting up gcm (2.0.877) ...

[ldennington]

This appears to be a bug in Debian's dpkg tool (based on what I'm reading here). I would recommend instead attempting to install GCM as a .NET tool, using the tarball, or installing from source.

[dennmart]

Not sure if this is related but there might be an issue in Linux builds in general. I noticed when getting the latest Linux tarball from the v2.0.886 release that the file is only 481 bytes. Opening the file in a text editor shows a PGP signature.

[dotCore-off]

Indeed, it seems to be an issue from dpkg, but something changed on GCM side.
Latest release doesn't work while previous one (GCM 2.0.877) does.
Will ZST compression remains in future releases? Is it something that could be reverted? @ldennington

[ldennington]

The Debian package works as expected on Ubuntu, as you can see from the workflow validation, but there were a few things that changed in the last release that I can take a look at. We added signing for the tarball in the latest release, which is probably where the mixup with the signature happened. I will look into it today.

[ldennington]

All right, I have done the following:

1. Updated the latest release with the correct tarball. You should be able to install without issue now.
2. Put a fix in place for the next release - I will push this out next week when folks are back to review it.

I have not had a chance to dig into the Debian package issues, though.