Tcl Library Source Code

View Ticket
Login
2026-11-16
00:06 • Ticket [7446477f89] tar package: issues with long file name status still Open with 3 other changes artifact: 5c64864cc2 user: serhiy.storchaka
2026-11-15
23:36
Fix [7446477f89]: tar::create rejected names that do not fit into the prefix/name fields or are longer than 255 characters. Write a GNU ././@LongLink entry for them, which tar already reads. check-in: a773e07f3c user: serhiy.storchaka tags: tar-gnu-longlink
2015-02-12
01:28 • Ticket [7446477f89] tar package: issues with long file name status still Open with 4 other changes artifact: 9c39eec866 user: aku
2015-01-28
20:44 • New ticket [7446477f89]. artifact: a5cfc2b237 user: anonymous

Ticket UUID: 7446477f899a967a87ace5b487c595073f12df29
Title: tar package: issues with long file name
Type: Bug Version: 0.10
Submitter: anonymous Created on: 2015-01-28 20:44:51
Subsystem: tar Assigned To:
Priority: 5 Medium Severity: Minor
Status: Open Last Modified: 2026-11-16 00:06:15
Resolution: None Closed By: nobody
    Closed on:
Description:
I am having some issues with the function ::tar::add

My file name I want to add is really long and the ::tar::add is complaining “path name cannot be split into prefix and name”

Can you please help?


The file name I am using is

fo_STT_D1_T25_VCMAX_VIOMAX_VOTNOM_F533_CFG0_LN4_5_6_7_M1v2_LNRVS0_DIFF1_DL036_DL136_NOISEquiet_DT201501261449_1_COUNT0.txt

Thank You
Amit
User Comments: serhiy.storchaka added on 2026-11-16 00:06:15:

Proposed fix in branch tar-gnu-longlink: names that can't be split into the ustar prefix and name fields get a GNU ././@LongLink entry, which tar already reads. Test tar-tkt-7446477f89 checks the result with tar::contents and with the system tar tf. It runs only on Unix, because such names exceed MAX_PATH on Windows.


aku added on 2015-02-12 01:28:31:

Which version of Tcllib is used ? Which version of the "tar" package is used ?

I am asking because of Ticket [2840180fffffffffffff] and commit [9cefaa3479] which changed the package behaviour in this area.

Looking at [fdiff?v1=39116c3beaeef80c&v2=ccc1188a13c75865&sbs=1]

the code attempts to split a long path at a path separator. Your filename is long, but does not have a path separator, so it could not be split.

Is GNU tar able to handle your file ? If yes, then please attach the result tar file to this ticket. This would allow me to inspect how GNU tar performs the split.

Note that this type of example only requires a long file name. The content is not relevant, i.e. this could be done with an empty file.