[Bug 244154] New: tar on x86-64 does not recognize --exclude
https://bugzilla.novell.com/show_bug.cgi?id=244154 Summary: tar on x86-64 does not recognize --exclude Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jvb@multisoft.de QAContact: qa@suse.de None of the --exclude tar options is recognized: tar cvzf /tmp/my.tgz /my/dir --exclude='*.tgz' --exclude=/my/dir/myfile.tgz nor the exclude-file (containing above entries): tar cvzf /tmp/my.tgz /my/dir -X /tmp/myfile.excl Previous (32bit) versions worked fine this way. Workaround: using the 32bit version of tar (from SuSE9 or 10) Used OS: openSuSE-10.2-GM-x86-64 CD images HW: AMD Sempron64 2600+ 1GB -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244154 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |mkoenig@novell.com |screening@forge.provo.novell| |.com | Severity|Major |Normal -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244154 mkoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jvb@multisoft.de ------- Comment #1 from mkoenig@novell.com 2007-02-12 02:26 MST ------- Works for me. However there have been some changes and new options for the --exclude option. Did you try with the --wildcard option? from /usr/share/doc/packages/tar/NEWS: * New options --anchored, --ignore-case, --wildcards, --wildcards-match-slash, and their negations (e.g., --no-anchored). Along with --recursion and --no-recursion, these options control how exclude patterns are interpreted. * The default interpretation of exclude patterns is now --no-anchored --no-ignore-case --recursion --wildcards --wildcards-match-slash. This is a quiet change to the semantics of --exclude. The previous semantics were a failed attempt at backward compatibility but it became clear that the semantics were puzzling and did not satisfy everybody. Rather than continue to try to revive that dead horse we thought it better to substitute cleaner semantics, with options so that you can change the behavior more to your liking. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244154 jvb@multisoft.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jvb@multisoft.de Status|NEEDINFO |NEW Info Provider|jvb@multisoft.de | ------- Comment #2 from jvb@multisoft.de 2007-02-17 04:11 MST ------- I have found the reported tar problem: as opposite to all previous tar versions, the --exclude option must be given _before_ the tar-ed files. Hence, tar cvzf /tmp/my2.tgz /tmp/my --exclude='/tmp/my/aaa.tgz' \ --exclude='/tmp/my/dir/*.tgz' does not work anymore (with/or without --wildcards), but tar cvzf /tmp/my2.tgz --exclude='/tmp/my/aaa.tgz' \ --exclude='/tmp/my/dir/*.tgz' /tmp/my works now, even without the --wildcard option. However, this needs to change all available scrips :-(( Greetings, Jan -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=244154 mkoenig@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #3 from mkoenig@novell.com 2007-02-19 02:37 MST ------- Yes, but this is the documented syntax. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com