iucode-tool 2.0-1 source package in Ubuntu

Changelog

iucode-tool (2.0-1) unstable; urgency=low

  * New upstream release:
    + This new major version has several non-backwards-compatible
      changes.  Scripts that scrape iucode_tool's stdout/stderr messages
      might have to be updated, and the behavior for -s and -S options
      changed.
      + The microcode listing output format used by --list and
        --list-all changed: the processor flags mask field is now
        labeled "pf_mask" instead of "pf mask", and the first field
        (bundle id/microcode id) is wider for --list-all, and completely
        changed for --list (refer to next entry).
      + The output for the --list option now uses the same microcode
        numbering used in --list-all and error messages, and also the
        same indentation as --list-all.  For this reason, --list will
        output the bundle assignment list to stdout when not in --quiet
        mode, the same way --list-all does.
      + The --scan-system/-S option can now only be specified once, and
        it may be overridden by -s !<signature> options that come
        +after* it in command line ordering.  To emulate the previous
        behavior, always specify --scan-system just once, and as the
        last option (i.e. after any -s options).
      + Error and warning messages, as well as some verbose (and debug)
        messages were updated, and some of them were demoted to higher
        verbosity levels.
    + Other relevant changes since v1.6.1:
      + Microcodes are now sorted by signature (ascending) and processor
        flags mask (descending).  Before, microcodes with the same
        signature but different processor flags mask had unspecified
        ordering.
      + The .dat format loader was optimized to run a lot faster on
        files that match the Intel layout exactly, and improved its
        error detection.
      + iucode_tool now flushes output data files to permanent storage
        using fdatasync() before closing them, to better detect write
        errors.  This causes a performance hit, but it is much safer.
      + Fix large file support (LFS) on 32-bit builds.
      + Abort with an error when attempting to write more than 4GiB to a
        cpio (early initramfs) archive, due to a limitation of that cpio
        file format.

 -- Henrique de Moraes Holschuh <email address hidden>  Mon, 12 Sep 2016 20:17:39 -0300