failure in tar reading from stdin

MikeFultonDev commented 2 years ago

The gettext code performs:

case "$from" in
  dir*)
    { case "$from" in
        dir) cat < "$fromfile" ;;
        dirgz) gzip -d -c < "$fromfile" ;;
        dirbz2) bzip2 -d -c < "$fromfile" ;;
        dirxz) xz -d -c < "$fromfile" ;;
      esac
    } \
      | (cd "$unpacked" && tar xf -) \
      || func_fatal_error "file copy failed"
    ;;

inside of ./gettext-tools/misc/convert-archive which causes problems because it does a 'cat' of a file that should be treated as binary, but unfortunately the file has previously been tagged as ISO8859-1 (this is wrong). Wherever the tar file is being created, it should be created as binary - so this needs to be tracked down

MikeFultonDev commented 2 years ago

Error message from this attempt to untar a file tagged as ISO8859-1:

1 warning generated.
tar: checksum error on tape (got 3cfc, expected 0)

CEE5213S The signal SIGPIPE was received.

MikeFultonDev commented 2 years ago

The patch for now is to tag the generated tar file as ASCII (tar should do this?) (https://github.com/ZOSOpenTools/gettextport/blob/main/patches/PR1/tagtarball.patch)

ZOSOpenTools / gettextport

failure in tar reading from stdin #2