You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working from my Void Linux system, I am doing my first pleasant experience with pkg2appimage.appimage for which I thank and congratulate you on such a beautiful project.
Sticking to the documentation, in my recipe I included the debs: section, which points to a local directory where I downloaded some official Ubuntu packages.
Now during appimage building I get this message
dpkg-deb: error: archive '<local DEB file name here>' uses unknown compression for member 'control.tar.zst', giving up
for each Ubuntu package I downloaded from jammy (22.04LTS) and subsequent sources mirrors while unpacking goes as expected for archives belonging to focal (20.04LTS) and earlier
Having never used Ubuntu, it took me a web search to find out why: starting from jammy, packages switched from xz to zstd compression format.
The most recent release pkg2appimage-1807-x86_64.AppImage is released Jun 2, 2021 so before jammy…
May we have a new release that could fix this current limitation?
The text was updated successfully, but these errors were encountered:
Working from my Void Linux system, I am doing my first pleasant experience with pkg2appimage.appimage for which I thank and congratulate you on such a beautiful project.
Sticking to the documentation, in my recipe I included the debs: section, which points to a local directory where I downloaded some official Ubuntu packages.
Now during appimage building I get this message
for each Ubuntu package I downloaded from jammy (22.04LTS) and subsequent sources mirrors while unpacking goes as expected for archives belonging to focal (20.04LTS) and earlier
Having never used Ubuntu, it took me a web search to find out why: starting from jammy, packages switched from xz to zstd compression format.
The most recent release
pkg2appimage-1807-x86_64.AppImage
is released Jun 2, 2021 so before jammy…May we have a new release that could fix this current limitation?
The text was updated successfully, but these errors were encountered: