Debian Bug report logs - #375864
tar: "file name read contains nul character" warning

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Kevin B. McCarty" <kmccarty@Princeton.EDU>

To: submit@bugs.debian.org

Subject: tar: "file name read contains nul character" warning

Date: Wed, 28 Jun 2006 10:58:31 -0400

Package: tar
Version: 1.15.91-1

What's this all about?

> dh_builddeb -a
> dpkg-deb: building package `dzedit' in `../dzedit_2005.05.09.dfsg-8_i386.deb'.
> tar: -: file name read contains nul character
> dpkg-deb: building package `kuipc' in `../kuipc_2005.05.09.dfsg-8_i386.deb'.
> tar: -: file name read contains nul character
> dpkg-deb: building package `kxterm' in `../kxterm_2005.05.09.dfsg-8_i386.deb'.
> tar: -: file name read contains nul character
> dpkg-deb: building package `libcojets2-dev' in `../libcojets2-dev_2005.05.09.dfsg-8_i386.deb'.
> tar: -: file name read contains nul character
[etc.]

When instead version 1.15.1dfsg-3 of tar installed, these warnings don't
occur.

(Feel free to reassign to dpkg if these new warnings are valid and
dpkg-deb is doing something it shouldn't that tar had previously not
bothered to warn about.)

regards,

-- 
Kevin B. McCarty <kmccarty@princeton.edu>   Physics Department
WWW: http://www.princeton.edu/~kmccarty/    Princeton University
GPG: public key ID 4F83C751                 Princeton, NJ 08544

Message #10 received at 375864@bugs.debian.org (full text, mbox, reply):

From: Nicolas François <nicolas.francois@centraliens.net>

To: 375864@bugs.debian.org

Subject: Re: Bug#375864: tar: "file name read contains nul character" warning

Date: Wed, 28 Jun 2006 22:43:42 +0200

Hello,

dpkg-deb is basically doing something like:

    find . -path ./DEBIAN -prune -o -print0 | \
        tar -cf - -T - --null --no-recursion

I think that when --null is specified, tar should not warn.

Note: the warning is not displayed with the following command:

    find . -path ./DEBIAN -prune -o -print0 | \
        tar --null -cf - -T - --no-recursion


Do you think it could be possible to read all the arguments before calling
update_argv?
Or do you think dpkg-deb should specify --null before -T (is it OK for the
previous versions of tar)?

Kind Regards,
-- 
Nekral

Message #15 received at 375864@bugs.debian.org (full text, mbox, reply):

From: Ben Hutchings <ben@decadent.org.uk>

To: 375864@bugs.debian.org, 375749@bugs.debian.org

Subject: Incompatible change to tar argument processing

Date: Fri, 07 Jul 2006 00:41:20 +0100

[Message part 1 (text/plain, inline)]

From tar's NEWS:

"
version 1.15.90 - Sergey Poznyakoff, 2006-02-19

* New features

** Any number of -T (--files-from) options may be used in the command line.
The file specified with -T may include any valid `tar' options,
including another -T option.
Compatibility note: older versions of tar would only recognize -C
as an option name within the file list file.  Now any file whose name
starts with - is handled as an option.  To insert file names starting with
dash, use the --add-file option.

** List files containing null-separated file names are detected and processed
automatically.  It is no longer necessary to give the --null option.

** New option --no-unquote disables the unquoting of input file names.
This is useful for processing output from `find dir -print0'.
An orthogonal option --unquote is provided as well.
"

Given how much depends on the behaviour of tar, such incompatible
changes are extremely unwise, but I doubt we want to differ from
upstream on this.

Ben.

-- 
Ben Hutchings -- ben@decadentplace.org.uk shortened to ben@decadent.org.uk
If you've signed my GPG key, please send a signature on and to the new uid.
Usenet is essentially a HUGE group of people passing notes in class.
                      - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 375864-done@bugs.debian.org (full text, mbox, reply):

From: Phillip Susi <psusi@ubuntu.com>

To: 375864-done@bugs.debian.org

Date: Fri, 10 May 2013 09:18:29 -0400

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

After checking upstream, it seems that --null affects arguments that
follow it, so must be specified before the -T you want to contain nulls.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRjPOlAAoJEJrBOlT6nu75WGEH/1kfi8Xk+uTMAqIurCGv3s49
GBCPdT5+2jAs5ukdT6Rz6vRK5RtQ61xdywp48q05W8YAR7ZmnC217o8FpqhlgXx1
9KsQgnrgtUyo5goOvnwifNvauCxCATJOpynYw16V3VugMP7BKwHW/EfeP4EA2ZJj
Zb7kVsIf+PqGJg6prXo7YDoauExeVe//znL3Z/3jo5vVd/u+ZpeVe+nAKiVrzGdD
ohHaRBaqknwljmnRqT3HIQtWPg7d4ZJkEVUWphXEF99juMOHNLVDILgBG7eIbFsF
TDYt1w1OEvc5wFq4nRGyj0jdFEA6v8UC/cYY3vaGHz/coheYE1JMC3nxJ4ASOXk=
=IUGw
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.