djview @4.12.3: tar: Ignoring malformed pax extended attribute

[angelog0 (Angelo Graziosi)]

As usual I did a selfupdate and then

sudo port outdated
The following installed ports are outdated:
djview                         4.12_1 < 4.12.3_0
leptonica                      1.84.1_1 < 1.86.0_0
libgpg-error                   1.57_0 < 1.58_0
libjpeg-turbo                  3.1.2_0 < 3.1.3_0
mpg123                         1.33.2_0 < 1.33.4_0
py312-cython                   3.2.2_0 < 3.2.3_0
py312-markdown                 3.8.2_0 < 3.10_0
py313-markdown                 3.8.2_0 < 3.10_0
unrar                          7.2.2_0 < 7.2.3_0

sudo port upgrade outdated
[...]

but the upgrade of djview failed in extracting. If I read correctly the main.log, the tarball does not exists.

I searched djview on ​Available Ports but it does not exist there too...

[ryandesign (Ryan Carsten Schmidt)]

Replying to angelog0:

but the upgrade of djview failed in extracting. If I read correctly the main.log, the tarball does not exists.

No, the tarball exists, and the log says:

:info:extract tar: Ignoring malformed pax extended attribute
:info:extract tar: Error exit delayed from previous errors.

This is an error with the way this tarball was created. It contains extended attributes that the tar program on your old version of macOS doesn't understand.

The best solution is to bring this problem to the attention of the developers of djview. They can release a new version whose tarball is created without the use of extended attributes, since they are unnecessary. Then we can update the port to that version.

I searched djview on ​Available Ports but it does not exist there too...

No, ​the port exists. The problem that searching doesn't find it is ​a bug in the web site.

[ryandesign (Ryan Carsten Schmidt)]

I don't see a new version available yet and I don't see a bug report about this yet.

If anybody is affected by this and wants it fixed, please head over to ​https://sourceforge.net/p/djvu/bugs/, see if a bug has been filed, and if not, file one and then share the URL here.

[angelog0 (Angelo Graziosi)]

I installed djview using gnutar and then reverting to the default tar (aka bsdtar). Maybe you have to abandon tar in favour of gnutar...

[angelog0 (Angelo Graziosi)]

They are other ports affected by this issue, for example p34-clone.. which I have upgraded with the above workaround..

[ryandesign (Ryan Carsten Schmidt)]

Replying to angelog0:

They are other ports affected by this issue, for example p34-clone..

Yes, there are. The ticket about p5.34-clone is #73560. For each affected port, somebody needs to inform the developers that they are distributing a distfile that has compatibility problems, and ask them to fix it in the next release.

[ryandesign (Ryan Carsten Schmidt)]

Every member of the djview 4.12.3 archive has the com.apple.provenance extended attribute; for example here it is on the top-level directory, as seen on macOS 12:

% sudo port extract djview
% ls -ld@ $(port work djview)/*
drwxr-xr-x@ 26 macports  wheel  832 Mar 16 00:54 /opt/local/var/macports/build/djview-30c12d0e/work/djview-4.12.3
	com.apple.provenance	 11 

As I've said ​elsewhere, upstream should package future distfiles using tar --no-xattrs.