[opensuse-factory] New Tumbleweed snapshot 20160828 released!
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20160828 When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem. Packages changed: PackageKit cryptsetup (1.7.0 -> 1.7.2) gnome-maps (3.20.2 -> 3.20.3) gvfs kernel-firmware (20160804 -> 20160824) mutter === Details === ==== PackageKit ==== Subpackages: PackageKit-backend-zypp PackageKit-gstreamer-plugin PackageKit-gtk3-module libpackagekit-glib2-18 typelib-1_0-PackageKitGlib-1_0 - Drop PackageKit-1.0.1-fix-bashisms.patch: this patch has been submitted upstream for discussion (gh#hughsie/PackageKit#162). If accepted, we'll inherit with a future update, if declined, it is not important enough to carry around. The code it touches is only used by the internal test suite. - Drop PackageKit-fix-offline-trigger.patch: in line with upstreams expectation we package /var/cache/PackageKit. With this present the symlink produced for offline update can correctly symlink to an existing directory. ==== cryptsetup ==== Version update (1.7.0 -> 1.7.2) Subpackages: libcryptsetup4 libcryptsetup4-32bit - Update to version 1.7.2: * Update LUKS documentation format. Clarify fixed sector size and keyslots alignment. * Support activation options for error handling modes in Linux kernel dm-verity module: - -ignore-corruption - dm-verity just logs detected corruption - -restart-on-corruption - dm-verity restarts the kernel if corruption is detected If the options above are not specified, default behavior for dm-verity remains. Default is that I/O operation fails with I/O error if corrupted block is detected. - -ignore-zero-blocks - Instructs dm-verity to not verify blocks that are expected to contain zeroes and always return zeroes directly instead. NOTE that these options could have security or functional impacts, do not use them without assessing the risks! * Fix help text for cipher benchmark specification (mention --cipher option). * Fix off-by-one error in maximum keyfile size. Allow keyfiles up to compiled-in default and not that value minus one. * Support resume of interrupted decryption in cryptsetup-reencrypt utility. To resume decryption, LUKS device UUID (--uuid option) option must be used. * Do not use direct-io for LUKS header with unaligned keyslots. Such headers were used only by the first cryptsetup-luks-1.0.0 release (2005). * Fix device block size detection to properly work on particular file-based containers over underlying devices with 4k sectors. - Update to version 1.7.1: * Code now uses kernel crypto API backend according to new changes introduced in mainline kernel While mainline kernel should contain backward compatible changes, some stable series kernels do not contain fully backported compatibility patches. Without these patches most of cryptsetup operations (like unlocking device) fail. This change in cryptsetup ensures that all operations using kernel crypto API works even on these kernels. * The cryptsetup-reencrypt utility now properly detects removal of underlying link to block device and does not remove ongoing re-encryption log. This allows proper recovery (resume) of reencrypt operation later. NOTE: Never use /dev/disk/by-uuid/ path for reencryption utility, this link disappears once the device metadata is temporarily removed from device. * Cryptsetup now allows special "-" (standard input) keyfile handling even for TCRYPT (TrueCrypt and VeraCrypt compatible) devices. * Cryptsetup now fails if there are more keyfiles specified for non-TCRYPT device. * The luksKillSlot command now does not suppress provided password in batch mode (if password is wrong slot is not destroyed). Note that not providing password in batch mode means that keyslot is destroyed unconditionally. ==== gnome-maps ==== Version update (3.20.2 -> 3.20.3) - Update to version 3.20.3 (boo#995112): + Download a service.json file to get tile server URI among other things. + Use GtkClutter for the attribution logo, to get transparency. ==== gvfs ==== Subpackages: gvfs-backend-afc gvfs-backend-samba gvfs-backends gvfs-fuse - Drop gvfs-support-nop-ftruncate.patch (bnc#466794, bgo#573837), gvfs-no-useless-x-flags.patch (bnc#538069), gvfs-monitor-proxy-debug.patch (bnc#903858): Fixed upstream. ==== kernel-firmware ==== Version update (20160804 -> 20160824) Subpackages: ucode-amd - Update to version 20160824: * linux-firmware/i915: Restore DMC 1.23 * linux-firmware: intel: Update Kabylake audio firmware * linux-firmware: intel: Update Broxton audio firmware * linux-firmware: rockchip: update dptx firmware to v2.9 * usb: host: xhci-rcar: update firmware for R-Car H3 and M3-W * qed: Add firmware 8.10.10.0 * ath10k: QCA4019 hw1.0: add firmware and board files * ath10k: QCA9887 hw1.0: add firmware and board files * ath10k: QCA9888 hw2.0: add firmware and board files * ath10k: QCA9984 hw1.0: add firmware and board files * ath10k: QCA988X hw2.0: update firmware to 10.2.4.70.54 * ath10k: QCA6174: update board files ==== mutter ==== Subpackages: libmutter0 mutter-data typelib-1_0-Meta-3_0 - Add mutter-bsc984738-grab-display.patch (bsc#984738, bgo#769387). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
==== kernel-firmware ==== Version update (20160804 -> 20160824) Subpackages: ucode-amd
- Update to version 20160824: * linux-firmware/i915: Restore DMC 1.23 What does linux-firmware/i915: Restore DMC 1.23 is please?
Thanks. Cheers, Marco -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2016-08-30 at 10:48 -0300, Marco Calistri wrote:
==== kernel-firmware ==== Version update (20160804 -> 20160824) Subpackages: ucode-amd
- Update to version 20160824: * linux-firmware/i915: Restore DMC 1.23 What does linux-firmware/i915: Restore DMC 1.23 is please?
https://01.org/linuxgraphics/downloads/skylake-dmc-1.23 Cheers, Dominique
On 08/30/2016 08:48 AM, Marco Calistri wrote:
==== kernel-firmware ==== Version update (20160804 -> 20160824) Subpackages: ucode-amd
- Update to version 20160824: * linux-firmware/i915: Restore DMC 1.23 What does linux-firmware/i915: Restore DMC 1.23 is please?
Thanks.
Cheers,
The commit message to linux-firmware is as follows: commit 3d1020bb4006e21c4eeca368044f16c9c206394e Author: Rodrigo Vivi <rodrigo.vivi@intel.com> Date: Tue Aug 9 22:22:21 2016 -0700 linux-firmware/i915: Restore DMC 1.23 1.26 is the stable and recommended firmware for Skylake. However one conflict in i915 accidentally restored 1.23 making that the default in some kernel out there. So, let's restore this 1.23 here. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97182 Cc: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Unfortunately, that does not make it much clearer, thus I Cc'd the patch author. Perhaps he will be able to help. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Dienstag, 30. August 2016 09:02:45 CEST Larry Finger wrote:
On 08/30/2016 08:48 AM, Marco Calistri wrote:
==== kernel-firmware ==== Version update (20160804 -> 20160824) Subpackages: ucode-amd
- Update to version 20160824: * linux-firmware/i915: Restore DMC 1.23
What does linux-firmware/i915: Restore DMC 1.23 is please?
Thanks.
Cheers,
The commit message to linux-firmware is as follows:
commit 3d1020bb4006e21c4eeca368044f16c9c206394e Author: Rodrigo Vivi <rodrigo.vivi@intel.com> Date: Tue Aug 9 22:22:21 2016 -0700
linux-firmware/i915: Restore DMC 1.23
1.26 is the stable and recommended firmware for Skylake. However one conflict in i915 accidentally restored 1.23 making that the default in some kernel out there.
So, let's restore this 1.23 here.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97182 Cc: Jani Nikula <jani.nikula@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Unfortunately, that does not make it much clearer, thus I Cc'd the patch author. Perhaps he will be able to help.
Larry
current kernel-firmware: $> rpm -ql kernel-firmware | grep dmc /lib/firmware/i915/bxt_dmc_ver1.bin /lib/firmware/i915/bxt_dmc_ver1_07.bin /lib/firmware/i915/kbl_dmc_ver1.bin /lib/firmware/i915/kbl_dmc_ver1_01.bin /lib/firmware/i915/skl_dmc_ver1.bin /lib/firmware/i915/skl_dmc_ver1_23.bin /lib/firmware/i915/skl_dmc_ver1_26.bin The package now contains both Skylake DMC firmware 1.23 and 1.26, as some kernels in the wild require 1.23, others 1.26. skl_dmc_ver1.bin is a symlink to skl_dmc_ver1_26.bin Restore != replace Kind regards, Stefan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Brüns, Stefan
-
Dominique Leuenberger
-
Dominique Leuenberger / DimStar
-
Larry Finger
-
Marco Calistri