New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #23457 (closed defect: worksforme)

Opened 3 years ago

Last modified 21 months ago

filename too long in fs-traverse during coreutils 8.4 upgrade

Reported by: theboergers@… Owned by: nox@…
Priority: Normal Milestone:
Component: base Version: 1.8.2
Keywords: Cc:
Port: coreutils

Description (last modified by macsforever2000@…) (diff)

coreutils 8.4 fails to build due to an extraordinarily long path.

The full debug output is attached to the report.

DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutils_coreutils/work" && /usr/bin/gzip -dc /opt/local/var/macports/distfiles/coreutils/coreutils-8.4.tar.gz | /usr/bin/gnutar --no-same-owner -xf -'
Error: Target org.macports.extract returned: file name too long
DEBUG: Backtrace: file name too long

Attachments

coreutils-debug.txt (21.6 KB) - added by theboergers@… 3 years ago.
Debug output

Change History

Changed 3 years ago by theboergers@…

Debug output

comment:1 Changed 3 years ago by macsforever2000@…

  • Keywords coreutils 8.4 file name too long removed
  • Owner changed from macports-tickets@… to nox@…
  • Description modified (diff)

comment:2 Changed 3 years ago by jmr@…

  • Component changed from ports to base
  • Summary changed from coreutils 8.4 upgrade fails to filename too long in fs-traverse during coreutils 8.4 upgrade

I can't reproduce this (also on 10.6). Need to add a little more debug output to see what the offending filename is.

comment:3 Changed 3 years ago by theboergers@…

See the attached file coreutils-debug.txt for the full debug output.

comment:4 Changed 3 years ago by jmr@…

I know you attached all the debug output that is currently produced; it needs to produce more. :-)

comment:5 Changed 21 months ago by jmr@…

  • Status changed from new to closed
  • Resolution set to worksforme

Never could reproduce this one. Extra debug output added in r83147 anyway.

Note: See TracTickets for help on using tickets.