Opened 4 years ago

Last modified 4 years ago

#13222 closed defect

xf86-video-intel-20200218 (and others) file format — at Version 2

Reported by: thomas Owned by: blfs-book
Priority: normal Milestone: 10.0
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description (last modified by thomas)

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.

Change History (2)

comment:1 by thomas, 4 years ago

Summary: xf86-video-intel-20200218 file formatxf86-video-intel-20200218 (and others) file format

Same for cairo-1.17.2+f93fc72c03e.tar.xz

$ file /mnt/LFS/conglomeration/cairo-1.17.2+f93fc72c03e.tar.xz
/mnt/LFS/conglomeration/cairo-1.17.2+f93fc72c03e.tar.xz: bzip2 compressed data, block size = 900k}}}

comment:2 by thomas, 4 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.