|Anonymous | Login||2018-07-16 22:23 UTC|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details|
|ID||Category||Severity||Type||Date Submitted||Last Update|
|0000814||[1003.1(2013)/Issue7+TC1] Shell and Utilities||Objection||Clarification Requested||2014-01-10 23:29||2014-05-01 10:54|
|Priority||normal||Resolution||Accepted As Marked|
|Final Accepted Text||See Note: 0002183.|
|Summary||0000814: unclear behavior when 'size' keyword deleted or overriden|
I can't figure out how pax should behave with
When writing an archive, it would presumably make it an error to try to store a file larger than the ustar format's size limit, but when reading it would appear to break the parsing of the archive, as pax would no longer expect the correct number of data blocks.
it should...act like all files were 100 octets in length, writing only one data block?? What data should it write if the file was actually shorter than that? If I'm reading things correctly, it should still store the real file size into the ustar header. Again, when using that while reading an archive the counting of data blocks will be screwed up.
Line 101359 says "If -okeyword:= is used, the affected attributes shall be ignored.", so the file size will be ignored, which is nonsense. Ditto for
Explicitly state that it's undefined behavior to delete, ignore, or override the 'size' keyword, or to ignore the 'path' or 'linkpath' keywords.
Don Cragun (manager)
edited on: 2014-03-13 15:51
The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.
If a user overrides data needed to determine where a file is in an archive, the results are undefined.
Notes to the Editor (not part of this interpretation):
Add after P3038, L100931:
If the -o delete=pattern, -o keyword=value, or -o keyword:=value options are used to override or remove any extended header data needed to find files in an archive (e.g., -o delete=size for a file whose size cannot be represented in a ustar header or -o size=100 for a file whose size is not 100 bytes), the behavior is undefined.
|Interpretation proposed: 1 April 2014|
|Interpretation approved May 1 2014|
|2014-01-10 23:29||philip-guenther||New Issue|
|2014-01-10 23:29||philip-guenther||Name||=> Philip Guenther|
|2014-01-10 23:29||philip-guenther||Organization||=> OpenBSD|
|2014-01-10 23:29||philip-guenther||Section||=> pax|
|2014-01-10 23:29||philip-guenther||Page Number||=> 3035-3048|
|2014-01-10 23:29||philip-guenther||Line Number||=> 100786-100798|
|2014-03-13 15:49||Don Cragun||Note Added: 0002183|
|2014-03-13 15:50||Don Cragun||Interp Status||=> Pending|
|2014-03-13 15:50||Don Cragun||Final Accepted Text||=> See Note: 0002183.|
|2014-03-13 15:50||Don Cragun||Status||New => Interpretation Required|
|2014-03-13 15:50||Don Cragun||Resolution||Open => Accepted As Marked|
|2014-03-13 15:51||Don Cragun||Note Edited: 0002183|
|2014-03-13 15:52||Don Cragun||Tag Attached: tc2-2008|
|2014-04-01 13:34||ajosey||Interp Status||Pending => Proposed|
|2014-04-01 13:34||ajosey||Note Added: 0002213|
|2014-05-01 10:54||ajosey||Interp Status||Proposed => Approved|
|2014-05-01 10:54||ajosey||Note Added: 0002238|
|Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group|