[Bug 864302] New: GNU tar rpm cannot dealt with large uid_t
https://bugzilla.novell.com/show_bug.cgi?id=864302 https://bugzilla.novell.com/show_bug.cgi?id=864302#c0 Summary: GNU tar rpm cannot dealt with large uid_t Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: external.martin.konold@de.bosch.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 SUSE/31.0.1650.63 Name : tar Version : 1.26 Release : 19.1.2 Cannot deal with large uid_t. Reason: Default format got changed from GNU to POSIX. Problem: In contrast to what the GNU tar documentation claims --format=posix cannot deal with large uids. Reproducible: Always Steps to Reproduce: 1. create directory hierarchy testdir/ with large uidnumber e.g. 20000001. 2. tar cvf deleteme.tar testdir/ 3. echo $? will give a 2. Actual Results: $? is 2 Expected Results: $? should be 0. tar cvf --format=gnu gives the expected result. This is a regression from older versions of OpenSuSE which used to have --format=gnu as a default format. E.g. OpenSuSE 11.3: km82rt@rt-z9854:~> tar --version tar (GNU tar) 1.23 km82rt@rt-z9854:~> tar –help | tail -5 *Dieses* „tar“ hat als Voreinstellung: --format=gnu -f- -b20 --quoting-style=escape --rmt-command=/usr/libexec/rmt --rsh-command=/usr/bin/rsh OpenSuSE 13.1: km82rt@rt-ccs7560:tmp> tar --version tar (GNU tar) 1.26 km82rt@rt-ccs7560:tmp> tar --help | tail -5 *This* tar defaults to: --format=posix -f- -b20 --quoting-style=escape --rmt-command=/usr/lib/rmt --rsh-command=/usr/bin/rsh The misleading documentation is available from http://www.gnu.org/software/tar/manual/html_section/Formats.html Format | UID File Size File Name Devn -------+----------------------------------------- gnu | 1.8e19 Unlimited Unlimited 63 oldgnu | 1.8e19 Unlimited Unlimited 63 v7 | 2097151 8GB 99 n/a ustar | 2097151 8GB 256 21 posix | Unlimited Unlimited Unlimited Unlimited Workaround: Go back to +export DEFAULT_ARCHIVE_FORMAT="GNU" -export DEFAULT_ARCHIVE_FORMAT="POSIX" in tar.spec and recreate the tar RPM. The current bug breaks many existing shell scripts which evaluate the exit code of tar. The bug is often triggered in setups using idmap_rid. For obvious reasons there is no way in large installation to change the uid to values which accomodate the buggy tar implementation. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c
Xiyuan Liu
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c1
Vitezslav Cizek
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c2
--- Comment #2 from Martin Konold
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c3
Vitezslav Cizek
The errors are identical. Simply check the error level and $? will be 2 instead of 0 in your test. I did not reproduce the error text output (fd 2).
Right.
So regression with "--format=posix" is fixed in upstream 1.27.1.
So what is the OpenSuSE policy in order to provide a fix for OpenSuSE 13.1?
I'll just initiate a maintenance update for 12.3 and 13.1. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c4
--- Comment #4 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c7
--- Comment #7 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c8
--- Comment #8 from SMASH SMASH
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c10
--- Comment #10 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c15
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c16
--- Comment #16 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=864302
https://bugzilla.novell.com/show_bug.cgi?id=864302#c
Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=864302
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com