Extracting portage binpkgs

Message

lordoftheworld · Post by **lordoftheworld** » Sat Apr 24, 2021 12:53 am

Is there a way to make or extract /usr/portage/packages/*/*.tbz2 packages without emerge -K/-B? I have BINPKG_COMPRESS="xz" in my make.conf, and neither tar -xJf or xz -df work for extracting. Both say compressed data is corrupt and opening in vi shows garbage. vi can usually look into compressed files. TIA.

Etal · Post by **Etal** » Sat Apr 24, 2021 1:37 am

I think using xz might what's causing the issue. The old bzip2 and new zstd binpkgs work fine with tar for me:

Code: Select all

$ tar tavf gnuconfig-20200621.tbz2
drwxr-xr-x root/root         0 2020-06-25 20:23 ./
drwxr-xr-x root/root         0 2020-06-25 20:23 ./usr/
drwxr-xr-x root/root         0 2020-06-25 20:23 ./usr/share/
drwxr-xr-x root/root         0 2020-06-25 20:23 ./usr/share/doc/
drwxr-xr-x root/root         0 2020-06-25 20:23 ./usr/share/doc/gnuconfig-20200621/
-rw-r--r-- root/root     28870 2020-06-25 20:23 ./usr/share/doc/gnuconfig-20200621/ChangeLog.bz2
drwxr-xr-x root/root         0 2020-06-25 20:23 ./usr/share/gnuconfig/
-rwxr-xr-x root/root     48858 2020-06-25 20:23 ./usr/share/gnuconfig/config.guess
-rwxr-xr-x root/root     31923 2020-06-25 20:23 ./usr/share/gnuconfig/config.sub

bzip2: (stdin): trailing garbage after EOF ignored

$ tar tavf gnuconfig-20210107.tbz2
drwxr-xr-x root/root         0 2021-01-14 22:59 ./
drwxr-xr-x root/root         0 2021-01-14 22:59 ./usr/
drwxr-xr-x root/root         0 2021-01-14 22:59 ./usr/share/
drwxr-xr-x root/root         0 2021-01-14 22:59 ./usr/share/doc/
drwxr-xr-x root/root         0 2021-01-14 22:59 ./usr/share/doc/gnuconfig-20210107/
-rw-r--r-- root/root      1088 2021-01-14 22:59 ./usr/share/doc/gnuconfig-20210107/ChangeLog.bz2
drwxr-xr-x root/root         0 2021-01-14 22:59 ./usr/share/gnuconfig/
-rwxr-xr-x root/root     49448 2021-01-14 22:59 ./usr/share/gnuconfig/config.guess
-rwxr-xr-x root/root     34491 2021-01-14 22:59 ./usr/share/gnuconfig/config.sub
zstd: /*stdin*\: unsupported format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

The binpkg file format is a compressed tar archive with xpak data appended at the end (which is why you see the errors at the end). If xz really can't handle it, you'd need to figure out how to strip it off. The format is described in the xpak(5) man page.

…or just switch compression to zstd which is the current default.

lordoftheworld · Post by **lordoftheworld** » Sat Apr 24, 2021 3:04 am

Thanks, I didn't notice it extracted files before giving me the corrupt error when using tar. Knowing it's xpak appended is helpful, qtbz2 and qxpak would be the two programs that help you split the file and look inside the xpak.

Post by **NeddySeagoon** » Sat Apr 24, 2021 9:20 am

lordoftheworld,

The format is like a single package stage3.
Its a tarball of the package followed by the content of /var/db/pkg for the package.

For recovery purposes, when all seems lost. its possimle to untar a binary package to the broken root filesystem and throw away the content of /var/db/pkg.
That's enough for the package to work.