Re: [Bug-tar] Bug report

[Bruce Dubbs]

Please note that this bug report is filed by a new LFS user.  In LFS, an 
entire Linux system is built from source code in a chroot.  Our logs 
only show a single failure, link mismatch, which appears to be fixed by 
the patch below.


We build tar as one of the last packages in the system.  Only vim is 
unavailable when we build tar.


Our test log is at:

http://www.linuxfromscratch.org/lfs/build-logs/8.2/i7-5820K/test-logs/140-tar-1.30

  -- Bruce Dubbs
 linuxfromscratch.org


On 03/14/2018 12:04 AM, Marcus McDermand wrote:

Hello again.

I tried the patch, and it seems to have worked for one of the tests. The 
number of test failures went down from 3 failed tests to 2 failed tests. 
I am still expecting 1, although the shrinking of failed tests is good!


Have another log

Keep in mind that this was done on an LFS chroot environment (Since the 
system doesn't even work) that was built by someone who didn't even know 
what a patch really was until they were told to apply one to an 
archiving program. It could also be a shoddy toolchain, as a result.


On Mon, 12 Mar 2018 at 23:16 Sergey Poznyakoff > wrote:


Hi Marcus,

 > Tried an LFS install, expected only link-mismatch to fail, but 2
others
 > failed.
 >
 > To be fair, probably my own fault, but have a report, just in case

Thanks a lot. The testsuite did not expect absolute file names to start
with "//". I have installed the patch 2b7fc4aee[1]. Please, give it a
try.

Regards,
Sergey

[1]

http://git.savannah.gnu.org/cgit/tar.git/patch/?id=2b7fc4aee9b559cdee9e979ad35046532c2700b7

Re: [Bug-tar] Bug report

[Sergey Poznyakoff]

Hi Marcus,

> Tried an LFS install, expected only link-mismatch to fail, but 2 others
> failed.
> 
> To be fair, probably my own fault, but have a report, just in case

Thanks a lot. The testsuite did not expect absolute file names to start
with "//". I have installed the patch 2b7fc4aee[1]. Please, give it a
try.

Regards,
Sergey

[1] 
http://git.savannah.gnu.org/cgit/tar.git/patch/?id=2b7fc4aee9b559cdee9e979ad35046532c2700b7

Re: [Bug-tar] bug-report

[Dagobert Michelsen]

Hi,

Am 16.08.2013 um 10:26 schrieb "lixiangyu2...@gmail.com" 
:

> 
>  
> 
> 
> All these files cannot be unpacked，unless rename it
> 

Try adding --force-local. See for details
  
http://www.gnu.org/software/tar/manual/html_node/Remote-Tape-Server.html#SEC153


Best regards

  -- Dago

-- 
"You don't become great by trying to be great, you become great by wanting to 
do something,
and then doing it so hard that you become great in the process." - xkcd #896



smime.p7s
Description: S/MIME cryptographic signature

Re: [Bug-tar] BUG report: GNU tar 1.23 can't create incremental backups on '/' dir

[Ondrej Vasik]

- Original Message -
> MAILTO: bug-tar@gnu.org
> 
> Subject: BUG report: GNU tar 1.23 can't create incremental backups on
> '/' dir
> 
> Tar version affected:
> root@host2 ~]# tar --version
> tar (GNU tar) 1.23
> 
> Systems affected:
> (1) Linux host1 2.6.32-71.el6.i686 #1 SMP Fri Nov 12 04:17:17 GMT 2010
> i686 i686 i386 GNU/Linux
> (2) Linux host2 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27 19:49:27
> BST 2011 x86_64 x86_64 x86_64 GNU/Linux
> 
> 
> Hello bugreport,
> 
> Our house-made backup program can't create incremental backups any
> longer when we moved to CentOS 6, GNU tar 1.23.
> Both 32-bit and 64-bit CentOS6 systems have the problem.

Hi, current tar version is 1.26 and this problem you are experiencing
with CentOS 6 is probably fixed there ...

Try patches from http://www.mail-archive.com/bug-tar@gnu.org/msg02632.html
and 
http://git.savannah.gnu.org/gitweb/?p=tar.git;a=commit;h=40dea1ae7fc892a54eae2efd30ddd8559c697525

Issues with incremental backups on '/' dir were already reported in RHEL-6 as
https://bugzilla.redhat.com/show_bug.cgi?id=653433 ,
so it will hopefully get fixed in CentOS6 once approved for an update in RHEL-6.

Greetings,
 Ondrej Vasik

Re: [Bug-tar] bug report: tar backup script 'backup (GNU tar) 1.25: option '-l' is not recognized

[Dennis Wydra]

Thank you for your reply. Yes, that patch works for me as well!

Best Regards

Re: [Bug-tar] bug report: tar backup script 'backup (GNU tar) 1.25: option '-l' is not recognized

[Paul Eggert]

Thanks for your bug report.  That patch isn't quite right, since it'd
cause the script to accept "-l=3", which should be rejected.  Could
you please try this patch instead?  (I've installed it, but it'd be
nice if you could double-check it.)  Thanks.

>From 4490773f87195f042fa151bb6959d332801fc46c Mon Sep 17 00:00:00 2001
From: Paul Eggert 
Date: Mon, 22 Nov 2010 15:18:10 -0800
Subject: [PATCH] scripts: fix option parsing

Problem reported by Dennis Wydra in
.
* scripts/backup.in: Accept "-l LEVEL".  Be more systematic about
backslashes inside ``; it shouldn't matter for modern shells but
it might matter for older ones.
* scripts/restore.in: Likewise.
* scripts/backup.in: Adjust implementation of -t/--time to match
the new implementation of -l/--level.
---
 scripts/backup.in  |   12 ++--
 scripts/restore.in |5 +++--
 2 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/scripts/backup.in b/scripts/backup.in
index 6a50e51..37bfed3 100644
--- a/scripts/backup.in
+++ b/scripts/backup.in
@@ -72,8 +72,9 @@ do
   --l=*|--le=*|--lev=*|--leve=*|--level=*)
  DUMP_LEVEL=$optarg
 ;;
+  -l?*)  DUMP_LEVEL=`expr $option : '-l\(.*\)'`;;
   -l|--l|--le|--lev|--leve|--level)
- prev=$option
+prev=--level
 ;;
   --verb=*|--verbo=*|--verbos=*|--verbose=*)
  VERBOSE=$optarg
@@ -81,14 +82,13 @@ do
   -v|--verb|--verbo|--verbos|--verbose)
  VERBOSE=100
 ;;
-  -v*)   VERBOSE=`expr $option : "-v\(.*\)"`;;
+  -v*)   VERBOSE=`expr $option : '-v\(.*\)'`;;
   --t=*|--ti=*|--tim=*|--time=*)
  TIME=$optarg
 ;;
-  -t)prev=--t;;
-  -t*)   TIME=`expr $option : "-t\(.*\)"`;;
-  --t|--ti|--tim|--time)
- prev=$option
+  -t?*)  TIME=`expr $option : '-t\(.*\)'`;;
+  -t|--t|--ti|--tim|--time)
+prev=--time
 ;;
   -V|--v|--ve|--ver|--vers|--versi|--versio|--version)
 echo "backup (@PACKAGE_NAME@) @VERSION@"
diff --git a/scripts/restore.in b/scripts/restore.in
index efc320a..2f86bac 100644
--- a/scripts/restore.in
+++ b/scripts/restore.in
@@ -60,8 +60,9 @@ do
   --l=*|--le=*|--lev=*|--leve=*|--level=*)
  DUMP_LEVEL=$optarg
 ;;
+  -l?*)  DUMP_LEVEL=`expr $option : '-l\(.*\)'`;;
   -l|--l|--le|--lev|--leve|--level)
- prev=$option
+prev=--level
 ;;
   --verb=*|--verbo=*|--verbos=*|--verbose=*)
  VERBOSE=$optarg
@@ -69,7 +70,7 @@ do
   -v|--verb|--verbo|--verbos|--verbose)
  VERBOSE=100
 ;;
-  -v*)   VERBOSE=`expr $option : "-v\(.*\)"`;;
+  -v*)   VERBOSE=`expr $option : '-v\(.*\)'`;;
   -V|--v|--ve|--ver|--vers|--versi|--versio|--version)
 echo "restore (@PACKAGE_NAME@) @VERSION@"
 license
-- 
1.7.2

Re: [Bug-tar] Bug report: tar-1.24 creates empty directories in the current working directory due to a bug in the new openat() code

[Sergey Poznyakoff]

Volker Schmidt  ha escrit:

> There is a bug in tar-1.24 which causes tar to create empty
> directories in the current working directory when it is not supposed
> to do that.

This has already been fixed.  Thank you.

Regards,
Sergey

Re: [Bug-tar] Bug report regarding the manual

[Sergey Poznyakoff]

Helmut Waitzmann <[EMAIL PROTECTED]> ha escrit:

> $ (cd / && tar -c -f archive.tar home)
> 
> is buggy:  The archive will be written to the directory "/", which is not
> necessarily the case with

Thanks, Helmut. I'll remove it.

Regards,
Sergey

Re: [Bug-tar] Bug Report

[Helmut Waitzmann]

"Felix Riemann" <[EMAIL PROTECTED]> writes:

>Using
>$ tar xf FILE.tar
>where FILE contains colons (in my case, FILE contained the time in
>HH:MM:SS) does not seem to work.

Yes.  It's a feature, not a bug.  See the tar option '--force-local'.  If
you want that option to be the default, consider using the TAR_OPTIONS
environment variable.
-- 
Wer mir E-Mail schreiben will, stelle   |   When writing me e-mail, please
bitte vor meine E-Mail-Adresse meinen   |   precede my e-mail address with
Vor- und Nachnamen, etwa so:|   my full name, like
Helmut Waitzmann <[EMAIL PROTECTED]>, (Helmut Waitzmann) [EMAIL PROTECTED]

Re: [Bug-tar] Bug Report: tar 1.15.1: option --listed-incremental does not store symbolic links pointing outside the filsystem

[Sergey Poznyakoff]

> ### Bug Report
> ### tar --listed-incremental does not store symbolic links pointing
> ### outside the filsystem

And it is not supposed to. That's not related to --listed-incremental in any
way: tar never archives any links pointing outside the directory
(directories) it is told to archive.

Regards,
Sergey


___
Bug-tar mailing list
Bug-tar@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-tar