Bug 654556 – dev-perl/DBD-SQLite: DBD-SQLite-1.54-patches-1.tar.xz fails to unpack

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Wyatt Draggoo 2018-05-01 19:42:06 UTC]

Created attachment 529284 [details]
emerge --info

>>> Emerging (1 of 1) dev-perl/DBD-SQLite-1.540.0-r1::gentoo
 * DBD-SQLite-1.54.tar.gz BLAKE2B SHA512 size ;-) ...                                                                           [ ok ]
 * DBD-SQLite-1.54-patches-1.tar.xz BLAKE2B SHA512 size ;-) ...                                                                 [ ok ]
>>> Unpacking source...                                                                                                                
>>> Unpacking DBD-SQLite-1.54.tar.gz to /var/tmp/portage/dev-perl/DBD-SQLite-1.540.0-r1/work                                           
>>> Unpacking DBD-SQLite-1.54-patches-1.tar.xz to /var/tmp/portage/dev-perl/DBD-SQLite-1.540.0-r1/work                                 
xz: /var/tmp/portage/dev-perl/DBD-SQLite-1.540.0-r1/distdir/DBD-SQLite-1.54-patches-1.tar.xz: Unsupported type of integrity check; not 
verifying file integrity                                                                                                               
tar: This does not look like a tar archive                                                                                             
tar: Exiting with failure status due to previous errors                                                                                
 * ERROR: dev-perl/DBD-SQLite-1.540.0-r1::gentoo failed (unpack phase):
 *   unpack: failure unpacking DBD-SQLite-1.54-patches-1.tar.xz
 *
 * Call stack:
 *               ebuild.sh, line 124:  Called src_unpack
 *             environment, line 883:  Called default
 *      phase-functions.sh, line 853:  Called default_src_unpack
 *      phase-functions.sh, line 880:  Called __eapi0_src_unpack
 *        phase-helpers.sh, line 740:  Called unpack 'DBD-SQLite-1.54.tar.gz' 
I've been running into this for a couple of weeks now and decided to troubleshoot. I have xz installed:

$ xz -V
xz (XZ Utils) 5.2.3                                                                                                                    
liblzma 5.2.3                                                                                                                          

I've tried two different NA mirrors to see if one of them was corrupt.

I've also tried uncompressing manually:
wyatt@royale ~/t3 $ ls -l
total 12
-rw-r--r-- 1 wyatt users 8376 May  1 12:40 DBD-SQLite-1.54-patches-1.tar.xz
wyatt@royale ~/t3 $ xz -d < DBD-SQLite-1.54-patches-1.tar.xz > DBD-SQLite-1.54-patches-1.tar                                           
xz: (stdin): Unsupported type of integrity check; not verifying file integrity
wyatt@royale ~/t3 $ ls -l
total 12
-rw-r--r-- 1 wyatt users    0 May  1 12:41 DBD-SQLite-1.54-patches-1.tar
-rw-r--r-- 1 wyatt users 8376 May  1 12:40 DBD-SQLite-1.54-patches-1.tar.xz

Here is the build:

'DBD-SQLite-1.54-patches-1.tar.xz'
 *        phase-helpers.sh, line 510:  Called __unpack_tar 'xz -d'
 *        phase-helpers.sh, line 318:  Called __assert_sigpipe_ok 'unpack: failure unpacking DBD-SQLite-1.54-patches-1.tar.xz'
 *   isolated-functions.sh, line  41:  Called __helpers_die 'unpack: failure unpacking DBD-SQLite-1.54-patches-1.tar.xz'
 *   isolated-functions.sh, line 117:  Called die
 * The specific snippet of code:
 *            die "$@"
 *
 * If you need support, post the output of `emerge --info '=dev-perl/DBD-SQLite-1.540.0-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-perl/DBD-SQLite-1.540.0-r1::gentoo'`.
 * The complete build log is located at '/var/log/portage/dev-perl:DBD-SQLite-1.540.0-r1:20180501-193228.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-perl/DBD-SQLite-1.540.0-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-perl/DBD-SQLite-1.540.0-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-perl/DBD-SQLite-1.540.0-r1/work'
 * S: '/var/tmp/portage/dev-perl/DBD-SQLite-1.540.0-r1/work/DBD-SQLite-1.54'
                                                                                                                                       
>>> Failed to emerge dev-perl/DBD-SQLite-1.540.0-r1, Log file:
                                                                                                                                       
>>>  '/var/log/portage/dev-perl:DBD-SQLite-1.540.0-r1:20180501-193228.log'

And emerge --info:

[Comment 1 Wyatt Draggoo 2018-05-01 20:43:55 UTC]

Forgot to mention that I removed everything from /usr/portage/distfiles between changing mirrors and several other times throughout testing. Same results after the new downloads.

[Comment 2 Jonas Stein 2018-05-01 22:05:44 UTC]

dev-perl/DBD-SQLite$ ebuild DBD-SQLite-1.560.0.ebuild install
and
dev-perl/DBD-SQLite$ ebuild DBD-SQLite-1.540.0-r1.ebuild install
worked fine here.

Could you sync your tree and retry, please?

which versions of portage and xz are installed?

[Comment 3 Kent Fredric (IRC: kent\n) (RETIRED) 2018-05-01 22:10:27 UTC]

Its likely that's a tar ball that I made with sha256 checksums, and you've probably installed xz-utils with USE="-extra-filters" ( which didn't exist as an option back then )

[Comment 4 Wyatt Draggoo 2018-05-01 22:20:36 UTC]

Tree synced, distfiles emptied, same result.

Running:
portage 2.3.24-r1
xv-utils 5.2.3

I'm reinstalling xz-utils with extra-filters now... Update in a minute.

[Comment 5 Wyatt Draggoo 2018-05-01 22:27:03 UTC]

Adding:

app-arch/xz-utils extra-filters

to package.use fixed it. If these are going to be used in ebuilds, should they be the default? I don't ever remember seeing anything about it, so I'm not sure where I would have found to enable them.

[Comment 6 Kent Fredric (IRC: kent\n) (RETIRED) 2018-05-01 22:38:41 UTC]

Prior to being a USE flag, it was always on.

Now its a USE flag, its now on by default, so you probably have  USE="-*" somewhere, and you explicitly disabled it.

However, this does instead mean I need to "re-roll" the tar.xz at some point not to require these filters ( it was an unintended accident due to having those configuration settings set in XZ_DEFAULTS in my ENV )

[Comment 7 Kent Fredric (IRC: kent\n) (RETIRED) 2018-06-03 04:22:34 UTC]

As of 2018-05-27 01:37:57 +1200 ( 9009e7cf59e18ab27179bcc9eb0ecb8eaf1e6b10 ), this bug is obsolete, as DBD-SQLite 1.560.0 and greater do not need the tarball.