Bug 205877

Description of problem:

After upgrade from RHEL4u3 to RHEL4u4 tar started to spew out verbose messages
about unchanged files when used with the --newer option even though the -v
verbose option is not used.  This seems to be caused by the upgrade from
tar-1.14-9 to tar-1.14-10 since the older tar did not behave like this.

Version-Release number of selected component (if applicable):

tar-1.14-10


How reproducible:

[root@srvr ]# mkdir demo
[root@srvr ]# cd demo/
[root@srvr demo]# touch file1
[root@srvr demo]# touch file2
[root@srvr demo]# touch file4
[root@srvr demo]# touch timemarker
[root@srvr demo]# touch file5 
[root@srvr demo]# tar cf allfiles.tar file*
[root@srvr demo]# tar tvf allfiles.tar 
-rw-r--r-- root/root         0 2006-09-09 10:38:05 file1
-rw-r--r-- root/root         0 2006-09-09 10:38:07 file2
-rw-r--r-- root/root         0 2006-09-09 10:38:11 file4
-rw-r--r-- root/root         0 2006-09-09 10:38:27 file5
[root@srvr demo]# tar cf newerthantimemarker.tar --newer="`date -r timemarker`"
file*
tar: file1: file is unchanged; not dumped
tar: file2: file is unchanged; not dumped
tar: file4: file is unchanged; not dumped
[root@srvr demo]# tar tvf newerthantimemarker.tar 
-rw-r--r-- root/root         0 2006-09-09 10:38:27 file5
[root@srvr demo]# 

Steps to Reproduce:

See above
  
Actual results / Expected results:

The "tar: file1: file is unchanged; not dumped" messages should only be
displayed when the -v (verbose) option is used with tar.

Additional info:

According to the following web pages this seems to be an old bug that resurfaced
in the tar-1.14-9 to tar-1.14-10 upgrade.
http://lists.gnu.org/archive/html/bug-tar/2005-03/msg00001.html
http://groups.google.is/group/linux.debian.bugs.dist/browse_thread/thread/ee0595e2a5f4631a/56a7419b18f9b6a2%2356a7419b18f9b6a2

Attached is a diff of tar-1.14-9 and tar-1.14.10.  (src packages patched with
rpmbuild -bp).  The diff seems to point to that the bug is similar to the one
mentioned in the above urls.