id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
13222	xf86-video-intel-20200218 (and others) file format	thomas	Bruce Dubbs	"The download file is named
''xf86-video-intel-20200218.tar.xz''

but it is a bzip2-compressed file:
 
{{{
$ file /mnt/LFS/conglomeration/xf86-video-intel-20200218.tar.xz
/mnt/LFS/conglomeration/xf86-video-intel-20200218.tar.xz: bzip2 compressed data, block size = 900k
}}}

So, either name of compression-type is not what it should be.

It does not harm if ""tar -xf <tarball>"" is used. That might be the reason why it hasn't came up so far. But it breaks if doing ""tar -xJf <tarball>"". The capital 'J' is what the extension of .xz suggests.

That breaks scripts which are using the file naming to prepare options for the tar command. Regardless if that approach (using ""extensions"" for controlling script functionality) is good or not, we should not mix extensions/file-formats."	defect	closed	normal	10.0	BOOK	SVN	medium	fixed