Disqus - Latest Comments for markie_mark

Re: Corrupt download caused installation to hang, unzip lessons learned

markie_mark — Fri, 05 Sep 2008 10:52:21 -0000

Ah yeah - and a general good practice is to check the error code of the command you last ran (especially for important steps!).

$ echo $?

Will return the exit status of the last command - generally '0' implies a successful execution - consulting the man page for most commands will give a detailed description of the exit status meanings:

DIAGNOSTICS
The exit status (or error level) approximates the exit codes defined by PKWARE and takes on the following values, except under VMS:

0 normal; no errors or warnings detected.

1 one or more warning errors were encountered, but processing completed successfully anyway. This includes zipfiles where one or more files was skipped due to unsupported compression
method or encryption with an unknown password.

HTH

Mark

Re: Corrupt download caused installation to hang, unzip lessons learned

markie_mark — Fri, 05 Sep 2008 10:25:55 -0000

Another "gotya" of this nature is with tar files, especially with the non-GNU versions of tar, some of which have limitations with the length of basename and filename - resulting in tar spitting out files which are not usable - this is especially prevalent in older traditional unix systems (Solaris etc.). The problem is reported however because most people execute tar with the verbose flag that there is so much output you don't notice the errors - $ tar xfv mark.tar. If you drop the verbose flag - only errors and the tar summary are printed.

The resolution to opening tar files with long pathname is to install and use the GNU version of tar (often called gtar) and use it when manually creating and extracting tar files (Note: do not replace the system tar - it's used by pkginfo).

HTH