-
iucode-tool (1.0.3-1~ubuntu14.04.1) trusty-backports; urgency=medium
* No-change backport to trusty (LP: #1361340)
iucode-tool (1.0.3-1) unstable; urgency=medium
* New upstream release
+ Properly check microcode metadata date to be valid packed BCD in
strict mode
+ Do not assume a non-zero microcode Total Size field to be valid, it
is valid only when the Data Size field is non-zero. Fortunately,
Intel always set reserved fields to zero on released microcode, so
this bug was never (and is unlikely to ever be) triggered
+ Linux kernel bug workaround: when generating the early initramfs
archive, append NULs to the microcode data file name to pad the
start of the microcode data inside the initramfs archive to a
16-byte boundary. Document this issue on the manpage, the
workaround is only effective if the start of our early initramfs
cpio segment is 16-byte aligned in the final initramfs archive
+ Fix several cosmetic and minor code issues
+ Manpage fixes and enhancements
* debian/control: add debian/master branch information to Vcs-Git field
* debian/control: bump standards-version to 3.9.5
iucode-tool (1.0.2-1) unstable; urgency=low
* New upstream maintenance release
+ Mention iucode-tool's new home at gitorious in documentation
+ Warn user when --scan-system fails due to errors such as a lack
of permission to access the cpuid devices
+ Use the libc optimized memcmp() to compare microcode
+ Minor manpage updates
+ --strict-checks now verifies that the microcode update date
is not utterly insane
* debian/control: update for new upstream location at Gitorious
-- Iain Lane <email address hidden> Mon, 25 Aug 2014 21:35:46 +0100
-
iucode-tool (1.0.1-1) unstable; urgency=low
* New upstream maintenance release
+ Fix several cosmetic code issues
+ Manpage updates
+ Make it clear that the output order of microcodes is not stabilized
+ Make it clear that iucode_tool always break links when writing a
data file, and that it doesn't replace files atomically, so they
can get corrupted/lost if iucode-tool is interrupted while writing
+ Reword several notes for better readability
+ Use openat() when loading from a directory and when creating files in
a directory. Thus, iucode-tool will read/write to the same directory
even while racing another process that is trying to rename it while
iucode-tool is already running
-- Henrique de Moraes Holschuh <email address hidden> Sat, 14 Dec 2013 21:01:41 -0200
-
iucode-tool (1.0-1) unstable; urgency=low
* New upstream release
+ Add verbose title to manpage iucode_tool(8)
+ Add support to write an early initramfs archive for Linux v3.9
* install iucode-tool symlinks to iucode_tool (closes: #689128)
-- Henrique de Moraes Holschuh <email address hidden> Sat, 25 May 2013 13:40:57 -0300
