append02.at 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990
  1. # Process this file with autom4te to create testsuite. -*- Autotest -*-
  2. # Test suite for GNU tar.
  3. # Copyright 2006-2007, 2009, 2013-2014, 2016 Free Software Foundation,
  4. # Inc.
  5. # This file is part of GNU tar.
  6. # GNU tar is free software; you can redistribute it and/or modify
  7. # it under the terms of the GNU General Public License as published by
  8. # the Free Software Foundation; either version 3 of the License, or
  9. # (at your option) any later version.
  10. # GNU tar is distributed in the hope that it will be useful,
  11. # but WITHOUT ANY WARRANTY; without even the implied warranty of
  12. # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  13. # GNU General Public License for more details.
  14. # You should have received a copy of the GNU General Public License
  15. # along with this program. If not, see <http://www.gnu.org/licenses/>.
  16. # Using tar 1.15.x the following equivalent command sets:
  17. #
  18. # 1. tar cf archive file1 file2
  19. # and
  20. # 2. tar cfT archive /dev/null
  21. # tar rf archive file1
  22. # tar rt archive file2
  23. #
  24. # produced different archives (GNU format is assumed). It was reported
  25. # by TAMUKI Shoichi on 2006-07-21 [1].
  26. #
  27. # The bug was due to tar being unable to discern between GNU and OLDGNU
  28. # formats and always assuming the latter. The main difference between
  29. # the two is that OLDGNU preserves all bits in the mode field, whereas
  30. # GNU format keeps only the lower 9 ones (mode & 0777).
  31. #
  32. # This was fixed on 2006-07-24 (commit f4e4adea80a) by making tar truncate
  33. # the mode field even in OLDGNU format. Obviously, the fix broke the
  34. # format backward compatibility, but it went unnoticed until 2009-10-03
  35. # (after all, the OLDGNU format is not in much use nowadays), when
  36. # Igor Zhbanov reported it [2].
  37. #
  38. # The final fix was applied on 2009-10-04.
  39. #
  40. # References:
  41. # [1] <[email protected]>
  42. # http://lists.gnu.org/archive/html/bug-tar/2006-07/msg00029.html
  43. # [2] <[email protected]>
  44. # http://lists.gnu.org/archive/html/bug-tar/2009-10/msg00006.html
  45. # The test case below verifies that the equivalent create and append commands
  46. # produce binary equivalent archives for all formats.
  47. AT_SETUP([append vs. create])
  48. AT_KEYWORDS([append append02 append-gnu])
  49. AT_TAR_CHECK([
  50. genfile --file file1
  51. genfile --file file2
  52. # Make sure file timestamps in the archive will not differ
  53. MTIME="--mtime=@0"
  54. # For PAX archives, we need to make sure extended header names are
  55. # reproducible and that their contents won't change with time
  56. if test $[]TEST_TAR_FORMAT = posix; then
  57. TAR_OPTIONS="$TAR_OPTIONS --pax-option=exthdr.name=%d/PaxHeaders/%f,delete=mtime,delete=atime,delete=ctime"
  58. fi
  59. echo Creating archive.1
  60. tar $MTIME -cf archive.1 file1 file2
  61. echo Creating archive.2
  62. tar $MTIME -cf archive.2 -T /dev/null
  63. tar $MTIME -rf archive.2 file1
  64. tar $MTIME -rf archive.2 file2
  65. echo Comparing archives
  66. cmp archive.1 archive.2
  67. ],
  68. [0],
  69. [Creating archive.1
  70. Creating archive.2
  71. Comparing archives
  72. ])
  73. AT_CLEANUP
  74. # End of append02.at