#70622 closed defect (fixed)
noarch archives fail to extract on Mac OS X 10.4 Tiger
| Reported by: | fhgwright (Fred Wright) | Owned by: | jmroot (Joshua Root) |
|---|---|---|---|
| Priority: | Normal | Milestone: | MacPorts 2.10.2 |
| Component: | base | Version: | 2.10.1 |
| Keywords: | tiger | Cc: | berg-michael (Michael Berg), ballapete (Peter "Pete" Dyballa) |
| Port: |
Description
This is solely an issue with installing the precompiled binary; it builds successfully from source. Precompiled binaries don't usually exist for 10.4, but this port has a wildcarded OS version.
Partial error output is:
... MacT @15:40:37.937: ---> Fetching archive for automake MacT @15:40:40.058: ---> Attempting to fetch automake-1.17_0.any_any.noarch.tbz2 from http://bos.us.packages.macports.org/automake MacT @15:40:46.148: ---> Attempting to fetch automake-1.17_0.any_any.noarch.tbz2.rmd160 from http://bos.us.packages.macports.org/automake MacT @15:40:50.445: ---> Installing automake @1.17_0 MacT @15:40:50.632:: /usr/bin/tar: Skipping to next header MacT @15:40:50.632:: /usr/bin/tar: Skipping to next header MacT @15:40:50.632:: /usr/bin/tar: Skipping to next header MacT @15:40:50.633:: /usr/bin/tar: Skipping to next header MacT @15:40:50.633:: /usr/bin/tar: Skipping to next header MacT @15:40:50.633:: /usr/bin/tar: Archive contains obsolescent base-64 headers MacT @15:40:50.635:: /usr/bin/tar: Skipping to next header ...
It appears to be an issue with /usr/bin/tar, which is GNU tar 1.14 on 10.4, and GNU tar 1.15.1 on 10.5. It's probably fixable by using the MacPorts gnutar on 10.4, though this would be a "binary extract dependency" rather than an "extract dependency". Alternatively, perhaps the binary archive could be constructed in a more compatible fashion.
It's not clear that this issue is limited to automake; this may simply be the first "any" port that's been updated since that mechanism was created (or the first that's been updated since a change in how binary archives are constructed).
Change History (22)
comment:1 follow-up: 2 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)
| Component: | ports → base |
|---|---|
| Version: | → 2.10.1 |
comment:2 follow-up: 3 Changed 3 months ago by fhgwright (Fred Wright)
Replying to ryandesign:
Since this has to do with binary archives, which are not under individual ports' control but are created at the direction of MacPorts base, this would be a base bug and not specific to automake.
As I suspected. That suggests making the summary more generic, which I don't have permissions to do.
I'm not aware of any change in how our binary archives are constructed. It may always have been the case that some or all archives created on newer macOS versions cannot be extracted on 10.4's version of tar, but that this has only become a problem since it has become possible for archives to be shared amongst OS versions (MacPorts 2.9.0?). I don't know which version of macOS created the automake 1.17 archive now on our servers.
Given that this issue just appeared between last Saturday and a little over a week earlier, it's probably whatever the buildbots are currently using.
You could try creating any tar archive on macOS 14 or other newer OS versions and then try extracting it on 10.4. If it fails the same way, and if you can then find some flags or options that can be used to create an archive on newer macOS that can be extracted on older macOS, base can be updated to use those flags or options.
If there's a read-side fix, that would be better, since it would be compatible with the existing archives. Though a write-side fix might be accompanied by a sweep to update the existing relevant archives (perhaps just by repackaging the existing tarballs, rather than rebuilding them).
The immediate workaround is for users to set buildfromsource on 10.4 to always (which I've confirmed works). If the problem can't be fixed soon, then it might make sense for base to make that the default on 10.4. That could even be done right away, to be reverted if and when a better fix comes along.
It would also be helpful, albeit in a rather verbose way (and the error output from this is really verbose), to have a failure to extract a binary archive fall back to building from source, just as it would do if a suitable binary archive didn't exist.
comment:3 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)
Replying to fhgwright:
I'm not aware of any change in how our binary archives are constructed. It may always have been the case that some or all archives created on newer macOS versions cannot be extracted on 10.4's version of tar, but that this has only become a problem since it has become possible for archives to be shared amongst OS versions (MacPorts 2.9.0?). I don't know which version of macOS created the automake 1.17 archive now on our servers.
Given that this issue just appeared between last Saturday and a little over a week earlier, it's probably whatever the buildbots are currently using.
The point is, we have over a dozen different machines running macOS versions between 10.6 and 14, and I don't know which one of those created the current automake 1.17 archive. It looks like most of the machines attempted the build, probably because there were no other builds running at the time that the commit came through, but I don't know which of them finished first or last, and I'm not sure whether the one that finishes first or the one that finishes last is the one that ends up on the server.
You could try creating any tar archive on macOS 14 or other newer OS versions and then try extracting it on 10.4. If it fails the same way, and if you can then find some flags or options that can be used to create an archive on newer macOS that can be extracted on older macOS, base can be updated to use those flags or options.
If there's a read-side fix, that would be better, since it would be compatible with the existing archives. Though a write-side fix might be accompanied by a sweep to update the existing relevant archives (perhaps just by repackaging the existing tarballs, rather than rebuilding them).
Sure, if you find a way to fix the problem at extract time, let us know that. It's obviously not as simple as just making all ports depend on MacPorts gnutar for extraction since that would introduce a dependency cycle for MacPorts gnutar and everything it depends on.
To rebuild archives with an OS version whose tar version is compatible with Tiger, we would first have to be able to identify which archives are affected. If you can provide a method to do that, let us know.
comment:4 follow-up: 7 Changed 2 months ago by berg-michael (Michael Berg)
I am not able to prove this definitively as I don't have a recent macOS machine to test.
However, I think this might be caused by recent versions of bsdtar which default to the pax archive format. I see rumblings about these changes (https://www.undeadly.org/cgi?action=article;sid=20240417053301, https://bugs.python.org/issue36268) in other environments and suspect it happened on macOS as well.
Nominally, gnutar 1.14 should be able to handle this. Actually, it does successfully extract the archive with no errors. It only produces an error when asked for a specific file in such an archive, and it's still able to extract the requested file first. It seems like there is just some bug in this old version of gnutar.
My evidence:
py310-setuptools 72.2.0 used to be broken in the same way on 10.4. 74.1.2 works fine.
If one runs
bzip2 -cd py310-setuptools-72.2.0_0.darwin_any.noarch.tbz2 | less -
or
bzip2 -cd automake-1.17_0.any_any.noarch.tbz2 | less -
one will find ./PaxHeader in the output. However, running
bzip2 -cd py310-setuptools-74.1.2_0.darwin_any.noarch.tbz2 | less -
i.e. the same test on a known working file, there is no ./PaxHeader.
(there's probably a more robust way to determine the format, but this was good enough for me).
I suspect there will not be a great way to work around this at extract time. gnutar is able to extract the file successfully, as I mentioned, but not if a specific file is requested.
Probably, the best solution is to ensure that tarballs are generated in the GNU format going forward. I believe this was the prior default, though I am open to being corrected. Virtually everything I know about tarballs was learned in the last few hours or so.
It should be possible to do a sweep of the existing tarballs and re-tarball them in the older format. This would not require rebuilding, just repackaging. The scope of the sweep probably could be narrowed by not considering files with a creation date before the default was changed to Pax, if such a date can be determined.
comment:5 Changed 2 months ago by berg-michael (Michael Berg)
| Cc: | berg-michael added |
|---|
comment:6 Changed 2 months ago by ryandesign (Ryan Carsten Schmidt)
Before we develop a script to identify and repack all affected archives, MacPorts base should be changed to ensure that new archives are made in the old format even on new versions of macOS. That's assuming there is a way to do so.
comment:7 follow-ups: 8 10 Changed 2 months ago by fhgwright (Fred Wright)
Replying to berg-michael:
I am not able to prove this definitively as I don't have a recent macOS machine to test.
However, I think this might be caused by recent versions of bsdtar which default to the pax archive format. I see rumblings about these changes (https://www.undeadly.org/cgi?action=article;sid=20240417053301, https://bugs.python.org/issue36268) in other environments and suspect it happened on macOS as well.
[...]
I don't think that's the issue, for a couple of reasons:
- AFAIK the extract phase normally unpacks entire tarballs, not individual files.
- The error message (excerpted above) doesn't sound like it relates to this issue.
It should be possible to do a sweep of the existing tarballs and re-tarball them in the older format. This would not require rebuilding, just repackaging. The scope of the sweep probably could be narrowed by not considering files with a creation date before the default was changed to Pax, if such a date can be determined.
Replying to ryandesign:
Before we develop a script to identify and repack all affected archives, MacPorts base should be changed to ensure that new archives are made in the old format even on new versions of macOS. That's assuming there is a way to do so.
Indeed.
But something that could be done right away (as I suggested above) and hasn't been (unless it was done without referencing this ticket) is to make always the default for build_from_source on 10.4. Then, if there's no better fix before the 2.10.2 release, it will at least have the workaround.
On a somewhat related note, it doesn't appear that the buildbot framework has been updated to optimally handle the darwin any case. Such ports still get unnecessarily built for all platforms. I don't know what determines which result winds up on the archive servers. In the most simple-minded treatment, it would probably be all of them, with the last one "winning".
comment:8 Changed 2 months ago by berg-michael (Michael Berg)
Replying to fhgwright:
Replying to berg-michael:
I am not able to prove this definitively as I don't have a recent macOS machine to test.
However, I think this might be caused by recent versions of bsdtar which default to the pax archive format. I see rumblings about these changes (https://www.undeadly.org/cgi?action=article;sid=20240417053301, https://bugs.python.org/issue36268) in other environments and suspect it happened on macOS as well.
[...]
I don't think that's the issue, for a couple of reasons:
- AFAIK the extract phase normally unpacks entire tarballs, not individual files.
Things are getting hung up on this command:
"exec -ignorestderr [findBinary tar ${portutil::autoconf::tar_path}] -xOj${qflag}f $archive_location ./+CONTENTS"
which evaluates to
tar -xOjf automake-1.17_0.any_any.noarch.tbz2 ./+CONTENTS
The intended output of this command AIUI is simply the contents of ./+CONTENTS to stdout. And we do see that output logged. If I drop the ./+CONTENTS gnutar unpacks the whole tarball without any complaints.
- The error message (excerpted above) doesn't sound like it relates to this issue.
I agree, with the caveat that I think this version of gnutar is probably just incapable of telling us what's going wrong.
Further investigation:
gnutar 1.34 on Ubuntu also dislikes the file and gives a more helpful error (truncated):
tar -xOvjf "automake-1.17_0.any_any.noarch.tbz2" ./+CONTENTS tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' ./+CONTENTS @name automake-1.17_0 @portname automake @portepoch 0 @portversion 1.17 @portrevision 0 @archs noarch opt/local/bin/aclocal @comment MD5:733b7a1979a407778c4970c48941270c @comment binary:0 opt/local/bin/aclocal-1.17 @comment MD5:733b7a1979a407778c4970c48941270c [...] tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags' tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
This lead me to a semi-informative discussion here https://github.com/nodejs/node/issues/22805, which included the following comment:
FWIW I've encountered some systems with older versions of (gnu) tar that will actually exit with a non-zero exit code and produce error messages when extracting the tarballs, despite the contents being extracted seemingly correctly. So I'd classify it as more than an annoyance.
The proposed solutions to this problem seem to be:
- Suppress the warning at extract-time with --warning=no-unknown-keyword. This doesn't exist on gnutar 1.14 so is not an option.
-or-
- Instead of using macOS bsdtar, use gnutar
-or-
- In macOS bsdtar, use --no-xattrs at archive-time
-or-
- In macOS bsdtar, use --format gnutar or --format ustar at archive time.
-or-
- Some amalgam of these options.
I like option 2 the most, followed by option 3. But I don't know if they work.
If someone with a recent macOS machine (ideally 14 as I think that's most likely to be the culprit) could try the following and send the files I'd like to see how Tiger handles each output.
Note that if one of these works, it implies that it should be possible to change base to that configuration before repacking affected archives.
#!/bin/bash # URL and file names url="https://packages.macports.org/automake/automake-1.17_0.any_any.noarch.tbz2" downloaded_file="automake-1.17_0.any_any.noarch.tbz2" # Download the file curl -O "$url" # Extract the downloaded archive mkdir -p extracted bsdtar -xvf "$downloaded_file" -C extracted # 1. Re-archive using --format ustar bsdtar -cvjf archive_ustar.tbz2 --format ustar -C extracted . # 2. Re-archive using --format gnutar bsdtar -cvjf archive_gnutar.tbz2 --format gnutar -C extracted . # 3. Re-archive using --format pax bsdtar -cvjf archive_pax.tbz2 --format pax -C extracted . # 4. Re-archive using --format ustar --no-xattrs bsdtar -cvjf archive_ustar_no_xattrs.tbz2 --format ustar --no-xattrs -C extracted . # 5. Re-archive using --format gnutar --no-xattrs bsdtar -cvjf archive_gnutar_no_xattrs.tbz2 --format gnutar --no-xattrs -C extracted . # 6. Re-archive using --format pax --no-xattrs bsdtar -cvjf archive_pax_no_xattrs.tbz2 --format pax --no-xattrs -C extracted . # 7. Re-archive using --no-xattrs bsdtar -cvjf archive_no_xattrs.tbz2 --no-xattrs -C extracted . # 8. Re-archive with no special arguments bsdtar -cvjf archive_default.tbz2 -C extracted . # Clean up rm -rf extracted rm "$downloaded_file" echo "Re-archiving and cleanup completed."
comment:9 follow-up: 12 Changed 2 months ago by berg-michael (Michael Berg)
I tried my script above to produce test files on bsdtar 3.5.2/Catalina. I tested whether they could be extracted on 10.4. My findings indicate that the pax archive format - which is the default for newer macOS - is the culprit.
In the text below, "doesn't work" means gnutar produced the usual Skipping to next header error on 10.4
"works" means gnutar extracted the file as expected and exited normally.
tar -xOvjf archive_default.tbz2 ./+CONTENTS - doesn't work tar -xOvjf archive_pax.tbz2 ./+CONTENTS - doesn't work tar -xOvjf archive_no_xattrs.tbz2 ./+CONTENTS - doesn't work tar -xOvjf archive_pax_no_xattrs.tbz2 ./+CONTENTS - doesn't work tar -xOvjf archive_gnutar.tbz2 ./+CONTENTS - works tar -xOvjf archive_gnutar_no_xattrs.tbz2 ./+CONTENTS - works tar -xOvjf archive_ustar.tbz2 ./+CONTENTS - works tar -xOvjf archive_ustar_no_xattrs.tbz2 ./+CONTENTS - works
This implies to me that in base we should pass either --format ustar or --format gnutar when producing archives. --no-xattrs seems to have no effect so there's no reason to include it.
comment:10 Changed 2 months ago by ryandesign (Ryan Carsten Schmidt)
Replying to fhgwright:
On a somewhat related note, it doesn't appear that the buildbot framework has been updated to optimally handle the
darwin anycase. Such ports still get unnecessarily built for all platforms. I don't know what determines which result winds up on the archive servers. In the most simple-minded treatment, it would probably be all of them, with the last one "winning".
Feel free to file a new ticket where we can discuss this.
comment:11 Changed 7 weeks ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ballapete added |
|---|---|
| Keywords: | tiger added |
| Summary: | automake @1.17_0 fails to install on 10.4 → noarch archives fail to extract on Mac OS X 10.4 Tiger |
Has duplicate #70920.
comment:12 Changed 7 weeks ago by ballapete (Peter "Pete" Dyballa)
Replying to berg-michael:
I have on PPC Tiger the problem with source file archives *.tar.gz. Simple invocation of tar <whatever> results in failure, but invoking tar z<whatever> seems to work fine… (with regular complaint tar: Record size = 8 blocks)
It also works to gunzip -c <ARCHIVE> | tar <whatever>.
But these files, fetched today until now while upgrading, do not fit into the latter method: Test-Simple-1.302204.tar.gz, ExtUtils-Config-0.010.tar.gz, ExtUtils-Helpers-0.028.tar.gz, ExtUtils-InstallPaths-0.014.tar.gz, JSON-MaybeXS-1.004008.tar.gz, Module-Build-Tiny-0.051.tar.gz, Try-Tiny-0.32.tar.gz.
comment:13 Changed 7 weeks ago by ryandesign (Ryan Carsten Schmidt)
While this ticket is about binary archives that we produce on our build system, we have also had several reports of source tarballs having been created by their developers in a way that Tiger could not extract them. So far, this only seemed to appear when extended attributes were inadvertently included in those tarballs, and so far upstreams have been willing to release repackaged versions omitting the extended attributes. However upstreams might not always be so accommodating, especially if on newer operating systems the default tar format has changed to one that Tiger cannot extract. Therefore it would be great if we could find a way to extract the new tar format on Tiger, both when extracting our binary archives and when extracting source tarballs, but I don't yet know how to do that. One source I found claims that the new format is a superset of the old format, implying that it should be possible, at least, to post-process a new tarball to convert it into an old tarball. One option, of course, it that we could start bundling a tar extraction utility such as libarchive with MacPorts and use that instead of the one that comes with macOS.
comment:14 follow-up: 15 Changed 7 weeks ago by ballapete (Peter "Pete" Dyballa)
Where is the cure for implausibly old time stamp 1970-01-01 01:00:00, #61276? Meanwhile I have on PPC Tiger 160 such "implausible" files installed in /opt/local:
75144607 8 -rw-r--r-- 1 root admin 6834 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-accessible.h 75144608 4 -rw-r--r-- 1 root admin 2332 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-action.h 75144609 4 -rw-r--r-- 1 root admin 2475 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-application.h 75144610 4 -rw-r--r-- 1 root admin 2686 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-collection.h 75144611 4 -rw-r--r-- 1 root admin 3747 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-component.h 75144612 68 -rw-r--r-- 1 root admin 68198 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-constants.h 75144613 8 -rw-r--r-- 1 root admin 4116 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-device-listener.h 75144614 4 -rw-r--r-- 1 root admin 2375 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-document.h 75144619 4 -rw-r--r-- 1 root admin 2591 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-editabletext.h 75144621 8 -rw-r--r-- 1 root admin 5064 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-event-listener.h 75144622 4 -rw-r--r-- 1 root admin 1299 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-gmain.h 75144623 4 -rw-r--r-- 1 root admin 2808 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-hyperlink.h 75144624 4 -rw-r--r-- 1 root admin 2018 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-hypertext.h 75144625 4 -rw-r--r-- 1 root admin 2105 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-image.h 75144626 4 -rw-r--r-- 1 root admin 2976 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-matchrule.h 75144627 4 -rw-r--r-- 1 root admin 1445 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-misc.h 75144628 4 -rw-r--r-- 1 root admin 2090 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-object.h 75144629 4 -rw-r--r-- 1 root admin 2497 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-registry.h 75144630 4 -rw-r--r-- 1 root admin 2195 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-relation.h 75144631 4 -rw-r--r-- 1 root admin 2543 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-selection.h 75144636 4 -rw-r--r-- 1 root admin 2872 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-stateset.h 75144637 4 -rw-r--r-- 1 root admin 2998 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-table-cell.h 75144642 4 -rw-r--r-- 1 root admin 3997 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-table.h 75144643 8 -rw-r--r-- 1 root admin 5410 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-text.h 75144648 8 -rw-r--r-- 1 root admin 5173 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-types.h 75144649 4 -rw-r--r-- 1 root admin 2069 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi-value.h 75144654 4 -rw-r--r-- 1 root admin 1745 Jan 1 1970 /opt/local/include/at-spi-2.0/atspi/atspi.h 75148731 4 -rw-r--r-- 1 root admin 1302 Jan 1 1970 /opt/local/include/at-spi2-atk/2.0/atk-bridge.h 89811491 4 -rw-r--r-- 1 root admin 2680 Jan 1 1970 /opt/local/include/atk-1.0/atk/atk-autocleanups.h 89811493 4 -rw-r--r-- 1 root admin 1943 Jan 1 1970 /opt/local/include/atk-1.0/atk/atk.h 89811494 8 -rw-r--r-- 1 root admin 4954 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkaction.h 89811495 16 -rw-r--r-- 1 root admin 14031 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkcomponent.h 89811496 8 -rw-r--r-- 1 root admin 4976 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkdocument.h 89811497 8 -rw-r--r-- 1 root admin 4957 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkeditabletext.h 89811498 4 -rw-r--r-- 1 root admin 2610 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkgobjectaccessible.h 89811499 8 -rw-r--r-- 1 root admin 4157 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkhyperlink.h 89811500 4 -rw-r--r-- 1 root admin 2448 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkhyperlinkimpl.h 89811501 4 -rw-r--r-- 1 root admin 2943 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkhypertext.h 89811502 4 -rw-r--r-- 1 root admin 3630 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkimage.h 89811503 4 -rw-r--r-- 1 root admin 3635 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkmisc.h 89811504 4 -rw-r--r-- 1 root admin 2174 Jan 1 1970 /opt/local/include/atk-1.0/atk/atknoopobject.h 89811505 4 -rw-r--r-- 1 root admin 2376 Jan 1 1970 /opt/local/include/atk-1.0/atk/atknoopobjectfactory.h 89811506 40 -rw-r--r-- 1 root admin 40484 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkobject.h 89811507 4 -rw-r--r-- 1 root admin 2720 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkobjectfactory.h 89811508 4 -rw-r--r-- 1 root admin 2215 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkplug.h 89811509 4 -rw-r--r-- 1 root admin 1982 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkrange.h 89811510 4 -rw-r--r-- 1 root admin 2699 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkregistry.h 89811511 4 -rw-r--r-- 1 root admin 3726 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkrelation.h 89811512 4 -rw-r--r-- 1 root admin 3790 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkrelationset.h 89811513 8 -rw-r--r-- 1 root admin 6226 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkrelationtype.h 89811514 4 -rw-r--r-- 1 root admin 3917 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkselection.h 89811515 4 -rw-r--r-- 1 root admin 2348 Jan 1 1970 /opt/local/include/atk-1.0/atk/atksocket.h 89811516 16 -rw-r--r-- 1 root admin 14517 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkstate.h 89811517 4 -rw-r--r-- 1 root admin 3749 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkstateset.h 89811518 8 -rw-r--r-- 1 root admin 4856 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkstreamablecontent.h 89811519 16 -rw-r--r-- 1 root admin 12805 Jan 1 1970 /opt/local/include/atk-1.0/atk/atktable.h 89811520 8 -rw-r--r-- 1 root admin 4671 Jan 1 1970 /opt/local/include/atk-1.0/atk/atktablecell.h 89811521 24 -rw-r--r-- 1 root admin 24342 Jan 1 1970 /opt/local/include/atk-1.0/atk/atktext.h 89811522 16 -rw-r--r-- 1 root admin 14675 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkutil.h 89811523 8 -rw-r--r-- 1 root admin 6182 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkvalue.h 89811525 4 -rw-r--r-- 1 root admin 1821 Jan 1 1970 /opt/local/include/atk-1.0/atk/atkwindow.h 75148735 4 -rw-r--r-- 1 root admin 213 Jan 1 1970 /opt/local/lib/gnome-settings-daemon-3.0/gtk-modules/at-spi2-atk.desktop 97887864 8 -rw-r--r-- 1 root admin 4575 Jan 1 1970 /opt/local/share/py-bootstrap-modules/install/__main__.py 97887866 4 -rw-r--r-- 1 root admin 170 Jan 1 1970 /opt/local/share/py-bootstrap-modules/install/_vendor/__init__.py 97887870 4 -rw-r--r-- 1 root admin 74 Jan 1 1970 /opt/local/share/py-bootstrap-modules/install/_vendor/installer/src/installer/__init__.py 97887872 4 -rw-r--r-- 1 root admin 71 Jan 1 1970 /opt/local/share/py-bootstrap-modules/install/_vendor/installer/src/installer/_compat/__init__.py 97887873 4 -rw-r--r-- 1 root admin 332 Jan 1 1970 /opt/local/share/py-bootstrap-modules/install/_vendor/installer/src/installer/_compat/importlib_resources.py 97887874 4 -rw-r--r-- 1 root admin 997 Jan 1 1970 /opt/local/share/py-bootstrap-modules/install/_vendor/installer/src/installer/_compat/typing.py 97887876 4 -rw-r--r-- 1 root admin 81 Jan 1 1970 /opt/local/share/py-bootstrap-modules/install/_vendor/installer/src/installer/_scripts/__init__.py 97887877 8 -rw-r--r-- 1 root admin 5647 Jan 1 1970 /opt/local/share/py-bootstrap-modules/install/_vendor/installer/src/installer/records.py 97887903 4 -rw-r--r-- 1 root admin 661 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/__about__.py 97887904 4 -rw-r--r-- 1 root admin 497 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/__init__.py 97887905 12 -rw-r--r-- 1 root admin 11488 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/_manylinux.py 97887906 8 -rw-r--r-- 1 root admin 4378 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/_musllinux.py 97887907 4 -rw-r--r-- 1 root admin 1431 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/_structures.py 97887908 12 -rw-r--r-- 1 root admin 8475 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/markers.py 97887909 0 -rw-r--r-- 1 root admin 0 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/py.typed 97887910 8 -rw-r--r-- 1 root admin 4664 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/requirements.py 97887911 32 -rw-r--r-- 1 root admin 30110 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/specifiers.py 97887912 16 -rw-r--r-- 1 root admin 15699 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/tags.py 97887913 8 -rw-r--r-- 1 root admin 4200 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/utils.py 97887914 16 -rw-r--r-- 1 root admin 14665 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging/version.py 97887916 16 -rw-r--r-- 1 root admin 15104 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging.egg-info/PKG-INFO 97887917 4 -rw-r--r-- 1 root admin 1754 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging.egg-info/SOURCES.txt 97887918 4 -rw-r--r-- 1 root admin 1 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging.egg-info/dependency_links.txt 97887919 4 -rw-r--r-- 1 root admin 25 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging.egg-info/requires.txt 97887920 4 -rw-r--r-- 1 root admin 10 Jan 1 1970 /opt/local/share/py-bootstrap-modules/packaging.egg-info/top_level.txt 97887937 12 -rw-r--r-- 1 root admin 9159 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/__init__.py 97887938 8 -rw-r--r-- 1 root admin 6426 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/actions.py 97887939 16 -rw-r--r-- 1 root admin 12936 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/common.py 97887940 212 -rw-r--r-- 1 root admin 213310 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/core.py 97887942 24 -rw-r--r-- 1 root admin 23668 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/diagram/__init__.py 97887943 12 -rw-r--r-- 1 root admin 9023 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/exceptions.py 97887944 40 -rw-r--r-- 1 root admin 39129 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/helpers.py 97887945 0 -rw-r--r-- 1 root admin 0 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/py.typed 97887946 28 -rw-r--r-- 1 root admin 25341 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/results.py 97887947 16 -rw-r--r-- 1 root admin 13402 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/testing.py 97887948 12 -rw-r--r-- 1 root admin 10787 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/unicode.py 97887949 8 -rw-r--r-- 1 root admin 6805 Jan 1 1970 /opt/local/share/py-bootstrap-modules/pyparsing/util.py 97887953 4 -rw-r--r-- 1 root admin 2239 Jan 1 1970 /opt/local/share/py-bootstrap-modules/python_install.egg-info/PKG-INFO 97887954 4 -rw-r--r-- 1 root admin 777 Jan 1 1970 /opt/local/share/py-bootstrap-modules/python_install.egg-info/SOURCES.txt 97887955 4 -rw-r--r-- 1 root admin 1 Jan 1 1970 /opt/local/share/py-bootstrap-modules/python_install.egg-info/dependency_links.txt 97887956 4 -rw-r--r-- 1 root admin 98 Jan 1 1970 /opt/local/share/py-bootstrap-modules/python_install.egg-info/requires.txt 97887957 4 -rw-r--r-- 1 root admin 8 Jan 1 1970 /opt/local/share/py-bootstrap-modules/python_install.egg-info/top_level.txt 97887959 8 -rw-r--r-- 1 root admin 5511 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/__init__.py 97887960 4 -rw-r--r-- 1 root admin 2688 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/__main__.py 97887961 4 -rw-r--r-- 1 root admin 1760 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/_entrypoints.py 97887962 4 -rw-r--r-- 1 root admin 1077 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/_overrides.py 97887963 4 -rw-r--r-- 1 root admin 619 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/_types.py 97887964 4 -rw-r--r-- 1 root admin 2244 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/_version_cls.py 97887965 8 -rw-r--r-- 1 root admin 7325 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/config.py 97887966 4 -rw-r--r-- 1 root admin 1557 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/discover.py 97887967 4 -rw-r--r-- 1 root admin 2554 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/file_finder.py 97887968 4 -rw-r--r-- 1 root admin 3244 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/file_finder_git.py 97887969 4 -rw-r--r-- 1 root admin 1492 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/file_finder_hg.py 97887970 8 -rw-r--r-- 1 root admin 6439 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/git.py 97887971 4 -rw-r--r-- 1 root admin 1342 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/hacks.py 97887972 8 -rw-r--r-- 1 root admin 5074 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/hg.py 97887973 4 -rw-r--r-- 1 root admin 3498 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/hg_git.py 97887974 4 -rw-r--r-- 1 root admin 2971 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/integration.py 97887975 4 -rw-r--r-- 1 root admin 322 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/scm_workdir.py 97887976 4 -rw-r--r-- 1 root admin 3596 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/utils.py 97887977 16 -rw-r--r-- 1 root admin 15067 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm/version.py 97887979 24 -rw-r--r-- 1 root admin 23539 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm.egg-info/PKG-INFO 97887980 4 -rw-r--r-- 1 root admin 1400 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm.egg-info/SOURCES.txt 97887981 4 -rw-r--r-- 1 root admin 1 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm.egg-info/dependency_links.txt 97887982 4 -rw-r--r-- 1 root admin 1495 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm.egg-info/entry_points.txt 97887983 4 -rw-r--r-- 1 root admin 97 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm.egg-info/requires.txt 97887984 4 -rw-r--r-- 1 root admin 15 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm.egg-info/top_level.txt 97887985 4 -rw-r--r-- 1 root admin 1 Jan 1 1970 /opt/local/share/py-bootstrap-modules/setuptools_scm.egg-info/zip-safe 97887987 4 -rw-r--r-- 1 root admin 299 Jan 1 1970 /opt/local/share/py-bootstrap-modules/tomli/__init__.py 97887988 24 -rw-r--r-- 1 root admin 21659 Jan 1 1970 /opt/local/share/py-bootstrap-modules/tomli/_parser.py 97887989 4 -rw-r--r-- 1 root admin 2818 Jan 1 1970 /opt/local/share/py-bootstrap-modules/tomli/_re.py 97887990 4 -rw-r--r-- 1 root admin 126 Jan 1 1970 /opt/local/share/py-bootstrap-modules/tomli/_types.py 97887991 4 -rw-r--r-- 1 root admin 26 Jan 1 1970 /opt/local/share/py-bootstrap-modules/tomli/py.typed 97887995 4 -rw-r--r-- 1 root admin 23 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/__init__.py 97887996 4 -rw-r--r-- 1 root admin 417 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/__main__.py 97887997 20 -rw-r--r-- 1 root admin 19075 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/bdist_wheel.py 97887999 4 -rw-r--r-- 1 root admin 2572 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/cli/__init__.py 97888000 12 -rwxr-xr-x 1 root admin 9498 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/cli/convert.py 97888001 4 -rw-r--r-- 1 root admin 3364 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/cli/pack.py 97888002 4 -rw-r--r-- 1 root admin 673 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/cli/unpack.py 97888003 16 -rw-r--r-- 1 root admin 15930 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/macosx_libfile.py 97888004 8 -rw-r--r-- 1 root admin 4344 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/metadata.py 97888005 4 -rw-r--r-- 1 root admin 1257 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/pkginfo.py 97888006 4 -rw-r--r-- 1 root admin 938 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/util.py 97888008 0 -rw-r--r-- 1 root admin 0 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/vendored/__init__.py 97888010 0 -rw-r--r-- 1 root admin 0 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/vendored/packaging/__init__.py 97888011 4 -rw-r--r-- 1 root admin 1812 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/vendored/packaging/_typing.py 97888012 32 -rw-r--r-- 1 root admin 29560 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/vendored/packaging/tags.py 97888013 4 -rw-r--r-- 1 root admin 16 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/vendored/vendor.txt 97888014 8 -rw-r--r-- 1 root admin 7574 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel/wheelfile.py 97888016 4 -rw-r--r-- 1 root admin 2509 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel.egg-info/PKG-INFO 97888017 4 -rw-r--r-- 1 root admin 2337 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel.egg-info/SOURCES.txt 97888018 4 -rw-r--r-- 1 root admin 1 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel.egg-info/dependency_links.txt 97888019 4 -rw-r--r-- 1 root admin 108 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel.egg-info/entry_points.txt 97888020 4 -rw-r--r-- 1 root admin 1 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel.egg-info/not-zip-safe 97888021 4 -rw-r--r-- 1 root admin 33 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel.egg-info/requires.txt 97888022 4 -rw-r--r-- 1 root admin 6 Jan 1 1970 /opt/local/share/py-bootstrap-modules/wheel.egg-info/top_level.txt
On PPC Leopard, not up-to-date, it's only 70 files plus these ones:
66211676 4 -rw-r--r-- 1 root admin 88 Jan 1 1970 /opt/local/var/cache/fontconfig/936DAD87-93B1-4B81-934C-5D5AC459A6FD-be32d4.cache-7 66211684 4 -rw-r--r-- 1 root admin 88 Jan 1 1970 /opt/local/var/cache/fontconfig/530A746E-D83E-4C45-8CEC-5DAF8F543B30-be32d4.cache-7 66211692 4 -rw-r--r-- 1 root admin 96 Jan 1 1970 /opt/local/var/cache/fontconfig/1106B294-6EB3-469C-8E83-7B84AC061320-be32d4.cache-7 66211700 4 -rw-r--r-- 1 root admin 88 Jan 1 1970 /opt/local/var/cache/fontconfig/D7EA6F59-4BC4-45F7-9BE9-AAB8069B072B-be32d4.cache-7 66211708 4 -rw-r--r-- 1 root admin 88 Jan 1 1970 /opt/local/var/cache/fontconfig/46C63AAB-F30C-498C-B53F-7E20672A6383-be32d4.cache-7 66211716 4 -rw-r--r-- 1 root admin 88 Jan 1 1970 /opt/local/var/cache/fontconfig/078F412E-B626-40E5-9C89-053E7FB0AF9B-be32d4.cache-7 66211724 4 -rw-r--r-- 1 root admin 96 Jan 1 1970 /opt/local/var/cache/fontconfig/1074219C-1C22-42CE-BD04-EA9C2020F78A-be32d4.cache-7 66211732 4 -rw-r--r-- 1 root admin 88 Jan 1 1970 /opt/local/var/cache/fontconfig/1C273A26-44C3-401D-9EDA-02609965320D-be32d4.cache-7
comment:15 Changed 7 weeks ago by ryandesign (Ryan Carsten Schmidt)
Replying to ballapete:
Where is the cure for
implausibly old time stamp 1970-01-01 01:00:00, #61276? Meanwhile I have onPPC Tiger160 such "implausible" files installed in/opt/local:
I don't know, and I would say that this ticket is not about that, except to the extent that bundling a newer tar dearchiver with MacPorts would presumably solve that as well. But let's keep individual tickets focused on individual issues.
comment:16 Changed 7 weeks ago by jmroot (Joshua Root)
Another option, which I know will be unpopular with the segment of the user base that cares about this ticket, would be to document that MacPorts requires a tar that handles pax extended headers correctly, formally de-supporting stock Tiger systems.
comment:17 Changed 7 weeks ago by jmroot (Joshua Root)
| Owner: | set to jmroot |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:18 Changed 7 weeks ago by jmroot (Joshua Root)
Not pretty but it does successfully install automake.
comment:19 Changed 7 weeks ago by jmroot (Joshua Root)
| Milestone: | → MacPorts Future |
|---|
comment:20 follow-up: 22 Changed 7 weeks ago by ballapete (Peter "Pete" Dyballa)
Does not seem to work on PPC Tiger, Mac OS X 10.4.11, after port selfupdate some minutes ago:
---> Fetching archive for automake
---> automake-1.17_0.any_any.noarch.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
---> Attempting to fetch automake-1.17_0.any_any.noarch.tbz2 from http://packages.macports.org/automake
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 869k 0 5001 0 0 2473 0 0:05:59 0:00:02 0:05:57 2473
100 869k 100 869k 0 0 265k 0 0:00:03 0:00:03 --:--:-- 690k---> Attempting to fetch automake-1.17_0.any_any.noarch.tbz2.rmd160 from http://packages.macports.org/automake
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 512 100 512 0 0 243 0 0:00:02 0:00:02 --:--:-- 243
100 512 100 512 0 0 164 0 0:00:03 0:00:03 --:--:-- 0---> Installing automake @1.17_0
/usr/bin/tar: Skipping to next header
/usr/bin/tar: Skipping to next header
/usr/bin/tar: Skipping to next header
/usr/bin/tar: Skipping to next header
/usr/bin/tar: Skipping to next header
/usr/bin/tar: Archive contains obsolescent base-64 headers
comment:21 Changed 7 weeks ago by jmroot (Joshua Root)
| Milestone: | MacPorts Future → MacPorts 2.10.2 |
|---|
comment:22 Changed 6 weeks ago by ryandesign (Ryan Carsten Schmidt)
Replying to ballapete:
Does not seem to work on
PPC Tiger, Mac OS X 10.4.11, afterport selfupdatesome minutes ago:
You would need to build a version of MacPorts base from source that includes the fix or wait for MacPorts 2.10.2 to be released. (Josh appears to be working on the release now.)
Since this has to do with binary archives, which are not under individual ports' control but are created at the direction of MacPorts base, this would be a base bug and not specific to automake.
I'm not aware of any change in how our binary archives are constructed. It may always have been the case that some or all archives created on newer macOS versions cannot be extracted on 10.4's version of tar, but that this has only become a problem since it has become possible for archives to be shared amongst OS versions (MacPorts 2.9.0?). I don't know which version of macOS created the automake 1.17 archive now on our servers.
You could try creating any tar archive on macOS 14 or other newer OS versions and then try extracting it on 10.4. If it fails the same way, and if you can then find some flags or options that can be used to create an archive on newer macOS that can be extracted on older macOS, base can be updated to use those flags or options.