Creating a deb package containing a directory using type: tree causes issues with the package on Ubuntu.
On Ubuntu 20 and 22, opening the package with Software Install fails with the error message `Failed to install file: not supported.
On Ubuntu 24, App Center opens and installs the package without issues.
On all three Ubuntu versions, gdebi reports List of files for 'package.deb' could not be read in the Included files tab.
How can we reproduce this?
Create a directory containing a single file using mkdir directory && echo content > directory/file.
Generate a deb package using the following config file
name: package
maintainer: Test
contents:
- src: directory
dst: /var/lib/directory
type: tree
The package will have the issues described above. However, a package generated with the following will not
name: package
maintainer: Test
contents:
- src: directory/file
dst: /var/lib/directory/file
[X] I did search for other open and closed issues before opening this.
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Additional context
The problem seems to come from the data.tar archive's format. The issue affects the package regardless of compression setting and decompressing and recompressing it does not solve the issue.
However, extracting the tar archive and recreating it creates a working package.
What happened?
Creating a
deb
package containing a directory usingtype: tree
causes issues with the package on Ubuntu.On Ubuntu 20 and 22, opening the package with
Software Install
fails with the error message `Failed to install file: not supported.On Ubuntu 24,
App Center
opens and installs the package without issues.On all three Ubuntu versions,
gdebi
reportsList of files for 'package.deb' could not be read
in theIncluded files
tab.How can we reproduce this?
Create a directory containing a single file using
mkdir directory && echo content > directory/file
. Generate adeb
package using the following config fileThe package will have the issues described above. However, a package generated with the following will not
nfpm version
Search
Code of Conduct
Additional context
The problem seems to come from the
data.tar
archive's format. The issue affects the package regardless of compression setting and decompressing and recompressing it does not solve the issue. However, extracting the tar archive and recreating it creates a working package.