"tar --null" complains about NULs in filenames
Bug #57225 reported by
Matthias Urlichs
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GNU tar |
Fix Released
|
Unknown
|
|||
| debhelper |
Fix Released
|
Unknown
|
|||
| dpkg (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
$ fakeroot dh_builddeb
tar: -: file name read contains nul character
strace-ing the thing yields:
[pid 30927] execve("/bin/tar", ["tar", "-cf", "-", "-T", "-", "--null", "--no-recursion"], [/* 58 vars */]) = 0
Duh? Say what? That's exactly the point, isn't it?
That error message is spurious under "--null" and should be removed.
Revision history for this message
| Matthias Urlichs (smurf) wrote | #1 |
| Changed in debhelper: | |
| importance: | Untriaged → Low |
| status: | Unconfirmed → Confirmed |
| Changed in debhelper: | |
| status: | Unknown → Fix Committed |
| Changed in tar: | |
| status: | Unknown → Unconfirmed |
Revision history for this message
| Matti Lindell (mlind) wrote | #2 |
| Changed in debhelper: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Colin Watson (cjwatson) wrote | #3 |
| Changed in dpkg: | |
| status: | Confirmed → Fix Released |
| Changed in tar: | |
| status: | New → Fix Released |
To post a comment you must log in.
Actually, reading that Debian report, it seems that dh_builddeb should just have a changed argument order.