MySQL Bugs: #39617: 5.0.68 gives error unpacking on Solaris 9

Bug #39617	5.0.68 gives error unpacking on Solaris 9
Submitted:	23 Sep 2008 20:09	Modified:	10 Sep 2009 11:20
Reporter:	Chris Calender	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	5.0.68	OS:	Solaris (Solaris9-sparc-64bit)
Assigned to:		CPU Architecture:	Any
Tags:	lone zero block, packaging error, unpacking error

Description:
Unpacking 5.0.68 on Solaris 9 gives an error (mysql-5.0.68-solaris9-sparc-64bit).

tar -xvf mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit.tar
...
tar: A lone zero block at 403260

How to repeat:
Simply gunzip and then untar the file on Solaris 9:

shell> gunzip mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit.tar.gz

shell> tar -xvf mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit.tar
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/comp_err
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/replace
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/perror
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/resolveip
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/my_print_defaults
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/resolve_stack_dump
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/mysql_waitpid
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/myisamchk
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/myisampack
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/myisamlog
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/myisam_ftdump
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/mysqld
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/mysqld-debug
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/mysql_tzinfo_to_sql
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/mysqlmanager
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/mysql
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/mysqlshow
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/mysqladmin
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/bin/mysqldump
...
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man1/perror.1
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man1/replace.1
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man1/resolve_stack_dump.1
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man1/resolveip.1
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man1/safe_mysqld.1
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man8/
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man8/mysqld.8
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man8/mysqlmanager.8
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man8/ndb_mgmd.8
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/man/man8/ndbd.8
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/data/
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/data/mysql/
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/data/test/
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/COPYING
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/README
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/INSTALL-BINARY
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/EXCEPTIONS-CLIENT
mysql-enterprise-gpl-5.0.68-solaris9-sparc-64bit/configure
tar: A lone zero block at 403260

Suggested fix:
If you untar and then retar the files, and then untar, the error goes away.  Perhaps an end-of-block is being written improperly to create the tarball.

Note that all files are extracted properly, so it is okay to simply ignore this warning/error messsage when extracting MySQL.

I've re-tested this with 5.0.85 on Solaris 9, and this bug no longer exists.

Furthermore, I wanted to note that this could also be a result of using the Solaris 'tar' as opposed to the GNU 'tar'.

In fact, the MySQL Manual recommends to use GNU tar instead of Solaris tar even when installing MySQL on Solaris (as there are some other known problems):

http://dev.mysql.com/doc/refman/5.1/en/solaris-installation.html

Closing as "Not a bug", because
1) note of 2008-Sep-23 says "all files are extracted properly", and
2) note of 2009-Aug-27 says it happened using Solaris tar,
   whereas the manual recommends to use GNU tar.