On Sun, 8 Mar 2026 19:43:09 +0100 Slávek Banko via tde-devels devels@trinitydesktop.org wrote:

Dne ne 8. března 2026 13:56:43 E. Liddell via tde-devels napsal(a):

...

When upgrading to 14.1.4 and then to 14.1.5, I was bombarded with the following messages indicating the .tar.xz files have some issue:

• Messages for package trinity-base/kcheckpass-14.1.5:

• tar extract command failed at least partially - continuing anyway

• Messages for package trinity-base/tdm-14.1.5:

• tar extract command failed at least partially - continuing anyway

• Messages for package trinity-base/kdesktop-14.1.5:

• tar extract command failed at least partially - continuing anyway

This happens for all the TDE core packages (but not for k3b). I don't remember whether it was an issue with versions before 14.1.4. It would just be a mildly irritating bit of log spam except for one thing: one of my machines is behind a corporate firewall that I do not control, and it *hates* compressed files it can't open and inspect. So I have to move the files to it via sneakernet.

Is whatever method is being used to create these files adding trailing garbage or something?

E. Liddell ____________________________________________________

Hi E. Liddell,

I tested the tarball as I have it on my archive, i.e. the mirroring source - it unpacked without any problems. I downloaded the tarball from the automatically selected mirror (in my case from Germany) and compared it with my original - there are no differences reported there. Can you verify if there is a match in sha512sum for the tarball you obtained?

The tarballs were checksum-verified by the package maanger upon download. All of them passed, indicating that the checksums matched what was expected.

I've attached the Manifest file containing the checksums that would have been used for verification for tdebase-trinity-14.1.4.tar.xz and tdebase-trinity-14.1.5.tar.xz If these are not the expected checksums, there is something amiss with the Gentoo packaging repository.

Note that after the first failure on the corporate-firewalled machine, I tried all the mirrors one at a time manually and the firewall refused each one, so I assume the files all had the same problem.

Note also that only the composite core desktop packages (tdebase, tdeutils . . .) are affected by whatever is going on here. Dependencies like the tqt packages are not affected, tdelibs is not affected, non-core software like k3b and filelight is not affected.

The script create_tarball is used to create tarballs, which you can see in the GIT repository "scripts". Nothing unexpected is added there. The only thing special there is to ensure reproducibility of tarball creation.

In any case, I am very concerned that there is some corruption during the download. Could it be due to the size of the tarball? For example, in applications there are also large tarballs for koffice and koffice translations. Do you also observe the problem on those?

I've never installed koffice. However, the largest tarball I *did* pull, tdeartwork, isn't even in the top ten largest packages I have installed for tarball size, so that's unlikely to be an issue unless there's some kind of breakage in all the tde mirrors, and it somehow resulted in broken files that all passed the checksum and were of the same size on different machines downloading them separately.

Manually untarring one of the files did not produce any kind of error, so this may be related to something in how Portage, the Gentoo package manager, uses and polices the tar command. I suppose I'll have to do more digging.

E. Liddell