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=20160602 Packages changed: adwaita-icon-theme bluez (5.39 -> 5.40) calligra desktop-file-utils device-mapper (1.02.115 -> 1.02.124) evince gdb gdm ghex gnome-backgrounds gnome-terminal gnome-weather kernel-firmware (20160503 -> 20160516) ktouch (15.12.3 -> 16.04.1) libgit2-glib libimobiledevice libstorage (2.26.2 -> 2.26.3) libusbmuxd libvirt lilo lvm2 (2.02.141 -> 2.02.152) meld mutt nfs-utils pcsc-lite (1.8.16 -> 1.8.17) phonon-backend-vlc postfix (2.11.7 -> 3.1.1) powertop rubygem-cfa (0.3.0 -> 0.3.1) tigervnc valgrind vte2 wicked (0.6.34 -> 0.6.35) xorg-x11-driver-input yast2 (3.1.189 -> 3.1.191) yast2-bootloader (3.1.187 -> 3.1.192) yast2-firewall (3.1.4 -> 3.1.5) yast2-installation (3.1.187 -> 3.1.191) yast2-mail (3.1.7 -> 3.1.8) yast2-network (3.1.151 -> 3.1.152) yast2-ruby-bindings (3.1.46 -> 3.1.48) === Details === ==== adwaita-icon-theme ==== - Actually apply adwaita-symbolic-fixes.patch. ==== bluez ==== Version update (5.39 -> 5.40) Subpackages: bluez-cups bluez-devel libbluetooth3 - update to version 5.40: This is mostly a bug fix release fixing issues with GATT, paired devices and connection handling (particularly for accepting connections through the Profile D-Bus interface). One new feature is the ability to use btmon for reading HCI logs from a TTY device. Right now the creation of this kind of logs is available with Zephyr https://www.zephyrproject.org/ in the form of a special console logging mode (more information available here https://www.zephyrproject.org/doc/board/arduino_101_ble.html#getting-hci-traces>). The format of the protocol is a slight modification of what btmon normally receives from the kernel monitor sockets, and is documented in doc/btsnoop.txt). ==== calligra ==== Subpackages: calligra-extras-dolphin calligra-extras-okular calligra-stage calligra-words-common - Re-enable building against Vc-devel-static, it builds fine again - Remove some unnecessary part from the specfile ==== desktop-file-utils ==== - Fix suse-update-mime-defaults: Ensure the directory structure to write the cache info to is in place (boo#976973). ==== device-mapper ==== Version update (1.02.115 -> 1.02.124) - Add compat symlinks for binaries to /sbin/ to avoid errors on hardcoded systems, obsolete them with leap 43 - Add conflicts on unsplit packages to allow smooth upgrade path Also do the conflict properly in baselibs.conf - Add dependencies to the devel pacakge in baselibs.conf - Update patch use-mirrortype-asdefault-whenclvmdrunning.patch to match up the patches/pvmove_support_clustered_vg.diff and not use the define declared only when building clvm codebase; it is still broken if someone changes the PID location, but at least it now does not depend on clvm code - Regenerate_initrd in post of the lvm2 main pkg - Update baselibs to point to split-out devicemapper libraries - Keep in sync the common configuration options that are shared among all the variants dm/lvm2/clvm - Provide symlinks to 1.02 versions of dm and dm-event libs * this should sort out binary packages without the need of double rebuilding - Update to 2.02.152 release, read WHATS_NEW for detailed log. - Refresh patches: * 10-dm.rules-Reset-state-variable-for-spurious-events.patch * device-mapper-gcc-warnings.patch * device-mapper-link.patch * udev-Check-for-DM_NR_VALID_PATHS.patch - Slightly tweak btrfs patch as the code changed for the detection: * fsadm-add-support-for-btrfs.patch - Build and install properly cluster files - Remove csm-converter.tar.gz as the evms was last present on sle10 and thus migration is bit out of scope today - Add pre_checkin.sh to allow syncing of patches between packages: workflow = add everything to lvm2.spec and run pre_checkin.sh - Refresh patch use-mirrortype-asdefault-whenclvmdrunning.patch to work without clvm code enabled - Regenerate lvm2 tmpfiles after install so they won't populate just after the reboot - Split out lvm2 libraries to separate subpkgs per standards - Rename versioning of plugins patch: * version-plugins-in-libdir -> version-plugins-in-libdir.patch - Remove evms provides/obsoletes, last seen on sle10 - Mark configs as such - Ghost the during-run created dirs - Install rcbla compat service symlinks - Sync with device-mapper.spec, build only lvm and wipe devicemapper binaries - Install in /usr there is no technical reason to keep this out of /usr - Split out device-mapper and clvm to separate spec files * No factual changes just deletion in the spec to keep it out of interacting with those parts - Do not explicitely require expat it is only used by thin_provisioning - There is no factual reason to keep the device mapper out of /usr so just match everything else - Remove device-mapper-static.patch as there should be no need to have static library here and it can be reenabled with some explanation if needed - Rename device-mapper-link to device-mapper-link.patch ==== evince ==== Subpackages: evince-browser-plugin evince-plugin-comicsdocument evince-plugin-djvudocument evince-plugin-dvidocument evince-plugin-pdfdocument evince-plugin-psdocument evince-plugin-tiffdocument evince-plugin-xpsdocument libevdocument3-4 libevview3-3 nautilus-evince typelib-1_0-EvinceDocument-3_0 typelib-1_0-EvinceView-3_0 - Change Group in devel sub-package to Development/Languages/C and C++: Silence rpmlint. - Drop old Provides and Obsoletes that do not make any sense keeping around anymore. Silence even more rpmlint warnings. + Provides: ggv, gpdf, evince-doc. + Obsoletes: ggv, gpdf, evince-doc. ==== gdb ==== - Add gdb-gcc6-Wparentheses-warning.patch to fix Werrors reported by GCC6. ==== gdm ==== Subpackages: gdmflexiserver libgdm1 typelib-1_0-Gdm-1_0 - Disable gdm-workaround-boo971852.patch. ==== ghex ==== Subpackages: ghex-lang libgtkhex-3-0 - Update to GNOME 3.20.2 Fate#318572 ==== gnome-backgrounds ==== Subpackages: gnome-backgrounds-lang - Update to GNOME 3.20 Fate#318572 ==== gnome-terminal ==== Subpackages: gnome-shell-search-provider-gnome-terminal nautilus-extension-terminal - Remove gnome-core obsoletes; it is from 2002 or so and not relevant now. ==== gnome-weather ==== Subpackages: gnome-shell-search-provider-gnome-weather - Update to GNOME 3.20.2 FATE#318572 ==== kernel-firmware ==== Version update (20160503 -> 20160516) Subpackages: ucode-amd - Update to version 20160516: * linux-firmware: intel: Update Skylake audio firmware * linux-firmware: update rt2860.bin, rt2800pci driver * linux-firmware: update rt2870.bin, rt2800usb driver * amdgpu: update firmware ==== ktouch ==== Version update (15.12.3 -> 16.04.1) - Update to KDE Applications 16.04.1 * KDE Applications 16.04.1 * https://www.kde.org/announcements/announce-applications-16.04.1.php - Update to KDE Applications 16.04.0 * KDE Applications 16.04.0 * https://www.kde.org/announcements/announce-applications-16.04.0.php - Update to KDE Applications 16.03.90 * KDE Applications 16.04.0 RC * https://www.kde.org/announcements/announce-applications-16.04-rc.php ==== libgit2-glib ==== - Add to the SDK. Fate#319349 ==== libimobiledevice ==== Subpackages: libimobiledevice-devel libimobiledevice6 - Add libimobiledevice-CVE-2016-5104.patch: Make sure sockets only listen locally (CVE-2016-5104, boo#982014). ==== libstorage ==== Version update (2.26.2 -> 2.26.3) Subpackages: libstorage-ruby libstorage7 - call parted with --wipesignatures when creating partitions to avoid auto-assembly of old MD RAIDs (fate#319893, bsc#943623) - 2.26.3 ==== libusbmuxd ==== Subpackages: libusbmuxd-devel libusbmuxd4 - Add libusbmuxd-CVE-2016-5104.patch: Make sure sockets only listen locally (CVE-2016-5104, boo#982014). ==== libvirt ==== Subpackages: libvirt-client libvirt-daemon libvirt-daemon-config-network libvirt-daemon-config-nwfilter libvirt-daemon-driver-interface libvirt-daemon-driver-libxl libvirt-daemon-driver-lxc libvirt-daemon-driver-network libvirt-daemon-driver-nodedev libvirt-daemon-driver-nwfilter libvirt-daemon-driver-qemu libvirt-daemon-driver-secret libvirt-daemon-driver-storage libvirt-daemon-driver-uml libvirt-daemon-driver-vbox libvirt-daemon-lxc libvirt-daemon-qemu libvirt-daemon-xen - Avoid suppressing errors during useradd/groupadd ==== lilo ==== - Do not buildrequire device-mapper-32bit: this package contains the libraries needed by device-mapper-devel-32bit and as such it is the -devel package's responsibility, to bring the libs in. ==== lvm2 ==== Version update (2.02.141 -> 2.02.152) - Add compat symlinks for binaries to /sbin/ to avoid errors on hardcoded systems, obsolete them with leap 43 - Add conflicts on unsplit packages to allow smooth upgrade path Also do the conflict properly in baselibs.conf - Add dependencies to the devel pacakge in baselibs.conf - Update patch use-mirrortype-asdefault-whenclvmdrunning.patch to match up the patches/pvmove_support_clustered_vg.diff and not use the define declared only when building clvm codebase; it is still broken if someone changes the PID location, but at least it now does not depend on clvm code - Regenerate_initrd in post of the lvm2 main pkg - Update baselibs to point to split-out devicemapper libraries - Keep in sync the common configuration options that are shared among all the variants dm/lvm2/clvm - Provide symlinks to 1.02 versions of dm and dm-event libs * this should sort out binary packages without the need of double rebuilding - Update to 2.02.152 release, read WHATS_NEW for detailed log. - Refresh patches: * 10-dm.rules-Reset-state-variable-for-spurious-events.patch * device-mapper-gcc-warnings.patch * device-mapper-link.patch * udev-Check-for-DM_NR_VALID_PATHS.patch - Slightly tweak btrfs patch as the code changed for the detection: * fsadm-add-support-for-btrfs.patch - Build and install properly cluster files - Remove csm-converter.tar.gz as the evms was last present on sle10 and thus migration is bit out of scope today - Add pre_checkin.sh to allow syncing of patches between packages: workflow = add everything to lvm2.spec and run pre_checkin.sh - Refresh patch use-mirrortype-asdefault-whenclvmdrunning.patch to work without clvm code enabled - Regenerate lvm2 tmpfiles after install so they won't populate just after the reboot - Split out lvm2 libraries to separate subpkgs per standards - Rename versioning of plugins patch: * version-plugins-in-libdir -> version-plugins-in-libdir.patch - Remove evms provides/obsoletes, last seen on sle10 - Mark configs as such - Ghost the during-run created dirs - Install rcbla compat service symlinks - Sync with device-mapper.spec, build only lvm and wipe devicemapper binaries - Install in /usr there is no technical reason to keep this out of /usr - Split out device-mapper and clvm to separate spec files * No factual changes just deletion in the spec to keep it out of interacting with those parts - Do not explicitely require expat it is only used by thin_provisioning - There is no factual reason to keep the device mapper out of /usr so just match everything else - Remove device-mapper-static.patch as there should be no need to have static library here and it can be reenabled with some explanation if needed - Rename device-mapper-link to device-mapper-link.patch ==== meld ==== Subpackages: meld-lang - Update to GNOME 3.20.2 (Fate#318572) ==== mutt ==== - Fix crash due keywords.patch which stumble over not existing standard mailbox - Update to neomutt 20160530 - Avoid sidebar patch from bother other users (boo#982129) - Remove patch patch-1.6.1.rr.compressed.bz2 as now part of neumutt ==== nfs-utils ==== Subpackages: nfs-client nfs-doc nfs-kernel-server - 0001-systemd-Decouple-the-starting-and-stopping-of-rpcbin.patch 0002-systemd-unit-files-fix-up-dependencies-on-rpcbind.patch Fix systemd dependencies to ensure rpcbind is started when needed. (bsc#975265) ==== pcsc-lite ==== Version update (1.8.16 -> 1.8.17) Subpackages: libpcsclite1 - Updated to version 1.8.17 * Fix SCardEndTransaction() issue with a SCARD_SHARE_EXCLUSIVE connection * Fix an issue when used with systemd (problem in signal handler) * SCardGetAttrib(): set pcbAttrLen when buffer is too small * Some other minor improvements ==== phonon-backend-vlc ==== - Require VLC 2.1.0 at least for building, support for 2.0.x has been removed upstream ==== postfix ==== Version update (2.11.7 -> 3.1.1) Subpackages: postfix-doc - fix Changelog cause of Factory decline - Fix typo in config.postfix - bnc#981097 config.postfix creates broken main.cf for tls client configuration - bnc#981099 /etc/sysconfig/postfix: POSTFIX_SMTP_TLS_CLIENT incomplete - update to 3.1.1: - The new address_verify_pending_request_limit parameter introduces a safety limit for the number of address verification probes in the active queue. The default limit is 1/4 of the active queue maximum size. The queue manager enforces the limit by tempfailing probe messages that exceed the limit. This design avoids dependencies on global counters that get out of sync after a process or system crash. - Machine-readable, JSON-formatted queue listing with "postqueue -j" (no "mailq" equivalent). - The milter_macro_defaults feature provides an optional list of macro name=value pairs. These specify default values for Milter macros when no value is available from the SMTP session context. - Support to enforce a destination-independent delay between email deliveries. The following example inserts 20 seconds of delay between all deliveries with the SMTP transport, limiting the delivery rate to at most three messages per minute. smtp_transport_rate_delay = 20s - Historically, the default setting "postscreen_dnsbl_ttl = 1h" assumes that a "not found" result from a DNSBL server will be valid for one hour. This may have been adequate five years ago when postscreen was first implemented, but nowadays, that one hour can result in missed opportunities to block new spambots. To address this, postscreen now respects the TTL of DNSBL "not found" replies, as well as the TTL of DNSWL replies (both "found" and "not found"). The TTL for a "not found" reply is determined according to RFC 2308 (the TTL of an SOA record in the reply). Support for DNSBL or DNSWL reply TTL values is controlled by two configuration parameters: postscreen_dnsbl_min_ttl (default: 60 seconds). postscreen_dnsbl_max_ttl (default: $postscreen_dnsbl_ttl or 1 hour) The postscreen_dnsbl_ttl parameter is now obsolete, and has become the default value for the new postscreen_dnsbl_max_ttl parameter. - New "smtpd_client_auth_rate_limit" feature, to enforce an optional rate limit on AUTH commands per SMTP client IP address. Similar to other smtpd_client_*_rate_limit features, this enforces a limit on the number of requests per $anvil_rate_time_unit. - New SMTPD policy service attribute "policy_context", with a corresponding "smtpd_policy_service_policy_context" configuration parameter. Originally, this was implemented to share the same SMTPD policy service endpoint among multiple check_policy_service clients. - A new "postfix tls" command to quickly enable opportunistic TLS in the Postfix SMTP client or server, and to manage SMTP server keys and certificates, including certificate signing requests and TLSA DNS records for DANE. - build with working support for SMTPUTF8 - fix build on sle11 by pointing _libexecdir to /usr/lib all the time. - some distros did not pull pkgconfig indirectly. pull it directly. - fix building the dynamic maps: the old build had postgresql e.g. with missing symbols. - convert to AUXLIBS_* instead of plain AUXLIBS which is needed for proper dynamic maps. - reordered the CCARGS and AUXLIBS* lines to group by feature - use pkgconfig or *_config tools where possible - picked up signed char from fedora spec file - enable lmdb support: new BR lmdb-devel, new subpackage postfix-lmdb. - don't delete vmail user/groups - update to 3.1.0 - Since version 3.0 postfix supports dynamic loading of cdb:, ldap:, lmdb:, mysql:, pcre:, pgsql:, sdbm:, and sqlite: database clients. Thats why the patches dynamic_maps.patch and dynamic_maps_pie.patch could be removed. - Adapting all the patches to postfix 3.1.0 - remove obsolete patches * add_missed_library.patch * postfix-opensslconfig.patch - update vda patch * remove postfix-vda-v13-2.10.0.patch * add postfix-vda-v13-3.10.0.patch - The patch postfix-db6.diff is not more neccessary - Backwards-compatibility safety net. With NEW Postfix installs, you MUST install a main.cf file with the setting "compatibility_level = 2". See conf/main.cf for an example. With UPGRADES of existing Postfix systems, you MUST NOT change the main.cf compatibility_level setting, nor add this setting if it does not exist. Several Postfix default settings have changed with Postfix 3.0. To avoid massive frustration with existing Postfix installations, Postfix 3.0 comes with a safety net that forces Postfix to keep running with backwards-compatible main.cf and master.cf default settings. This safety net depends on the main.cf compatibility_level setting (default: 0). Details are in COMPATIBILITY_README. - Major changes - tls * [Feature 20160207] A new "postfix tls" command to quickly enable opportunistic TLS in the Postfix SMTP client or server, and to manage SMTP server keys and certificates, including certificate signing requests and TLSA DNS records for DANE. * As of the middle of 2015, all supported Postfix releases no longer nable "export" grade ciphers for opportunistic TLS, and no longer use the deprecated SSLv2 and SSLv3 protocols for mandatory or opportunistic TLS. * [Incompat 20150719] The default Diffie-Hellman non-export prime was updated from 1024 to 2048 bits, because SMTP clients are starting to reject TLS handshakes with primes smaller than 2048 bits. * [Feature 20160103] The Postfix SMTP client by default enables DANE policies when an MX host has a (DNSSEC) secure TLSA DNS record, even if the MX DNS record was obtained with insecure lookups. The existence of a secure TLSA record implies that the host wants to talk TLS and not plaintext. For details see the smtp_tls_dane_insecure_mx_policy configuration parameter. - Major changes - default settings [Incompat 20141009] The default settings have changed for relay_domains (new: empty, old: $mydestination) and mynetworks_style (new: host, old: subnet). However the backwards-compatibility safety net will prevent these changes from taking effect, giving the system administrator the option to make an old default setting permanent in main.cf or to adopt the new default setting, before turning off backwards compatibility. See COMPATIBILITY_README for details. [Incompat 20141001] A new backwards-compatibility safety net forces Postfix to run with backwards-compatible main.cf and master.cf default settings after an upgrade to a newer but incompatible Postfix version. See COMPATIBILITY_README for details. While the backwards-compatible default settings are in effect, Postfix logs what services or what email would be affected by the incompatible change. Based on this the administrator can make some backwards-compatibility settings permanent in main.cf or master.cf, before turning off backwards compatibility. - Major changes - address verification safety [Feature 20151227] The new address_verify_pending_request_limit parameter introduces a safety limit for the number of address verification probes in the active queue. The default limit is 1/4 of the active queue maximum size. The queue manager enforces the limit by tempfailing probe messages that exceed the limit. This design avoids dependencies on global counters that get out of sync after a process or system crash. Tempfailing verify requests is not as bad as one might think. The Postfix verify cache proactively updates active addresses weeks before they expire. The address_verify_pending_request_limit affects only unknown addresses, and inactive addresses that have expired from the address verify cache (by default, after 31 days). - Major changes - json support [Feature 20151129] Machine-readable, JSON-formatted queue listing with "postqueue -j" (no "mailq" equivalent). The output is a stream of JSON objects, one per queue file. To simplify parsing, each JSON object is formatted as one text line followed by one newline character. See the postqueue(1) manpage for a detailed description of the output format. - Major changes - milter support [Feature 20150523] The milter_macro_defaults feature provides an optional list of macro name=value pairs. These specify default values for Milter macros when no value is available from the SMTP session context. For example, with "milter_macro_defaults = auth_type=TLS", the Postfix SMTP server will send an auth_type of "TLS" to a Milter, unless the remote client authenticates with SASL. This feature was originally implemented for a submission service that may authenticate clients with a TLS certificate, without having to make changes to the code that implements TLS support. - Major changes - output rate control [Feature 20150710] Destination-independent delivery rate delay Support to enforce a destination-independent delay between email deliveries. The following example inserts 20 seconds of delay between all deliveries with the SMTP transport, limiting the delivery rate to at most three messages per minute. /etc/postfix/main.cf: smtp_transport_rate_delay = 20s For details, see the description of default_transport_rate_delay and transport_transport_rate_delay in the postconf(5) manpage. - Major changes - postscreen dnsbl [Feature 20150710] postscreen support for the TTL of DNSBL and DNSWL lookup results Historically, the default setting "postscreen_dnsbl_ttl = 1h" assumes that a "not found" result from a DNSBL server will be valid for one hour. This may have been adequate five years ago when postscreen was first implemented, but nowadays, that one hour can result in missed opportunities to block new spambots. To address this, postscreen now respects the TTL of DNSBL "not found" replies, as well as the TTL of DNSWL replies (both "found" and "not found"). The TTL for a "not found" reply is determined according to RFC 2308 (the TTL of an SOA record in the reply). Support for DNSBL or DNSWL reply TTL values is controlled by two configuration parameters: postscreen_dnsbl_min_ttl (default: 60 seconds). This parameter specifies a minimum for the amount of time that a DNSBL or DNSWL result will be cached in the postscreen_cache_map. This prevents an excessive number of postscreen cache updates when a DNSBL or DNSWL server specifies a very small reply TTL. postscreen_dnsbl_max_ttl (default: $postscreen_dnsbl_ttl or 1 hour) This parameter specifies a maximum for the amount of time that a DNSBL or DNSWL result will be cached in the postscreen_cache_map. This prevents cache pollution when a DNSBL or DNSWL server specifies a very large reply TTL. The postscreen_dnsbl_ttl parameter is now obsolete, and has become the default value for the new postscreen_dnsbl_max_ttl parameter. - Major changes - sasl auth safety [Feature 20151031] New "smtpd_client_auth_rate_limit" feature, to enforce an optional rate limit on AUTH commands per SMTP client IP address. Similar to other smtpd_client_*_rate_limit features, this enforces a limit on the number of requests per $anvil_rate_time_unit. - Major changes - smtpd policy [Feature 20150913] New SMTPD policy service attribute "policy_context", with a corresponding "smtpd_policy_service_policy_context" configuration parameter. Originally, this was implemented to share the same SMTPD policy service endpoint among multiple check_policy_service clients. ==== powertop ==== Subpackages: powertop-lang - Don't requires xterm-bin but xterm if Leap, boo#981780 ==== rubygem-cfa ==== Version update (0.3.0 -> 0.3.1) - better inspecting of BooleanValue objects (helps with debugging various bncs, like bnc#980108 or bnc#940465) - 0.3.1 ==== tigervnc ==== Subpackages: libXvnc1 xorg-x11-Xvnc - Add /etc/pam.d/vnc configuration and add vnc user to shadow group. (bnc#980326) - Add dependency on fltk-devel version >= 1.3.3. ==== valgrind ==== - add vex-r3197.diff (bsc#981447) ==== vte2 ==== Subpackages: libvte9 vte2-lang - Update to GNOME 3.20.2 FATE#318572 - Fixes bsc#979317 ==== wicked ==== Version update (0.6.34 -> 0.6.35) Subpackages: libwicked-0-6 wicked-service - version 0.6.35 - spec: removed ppp service template macro calls (fate#317976) - bonding: support for new v3.7.1 netlink options in 4.4 kernel - linux: update included headers to 4.4, add if_addr.h ==== xorg-x11-driver-input ==== - No longer require xf86-input-synaptics on systems later than Leap 42.1. Instead require xf86-input-libinput. People who will need the synaptics driver may install it by hand. (boo#981750). ==== yast2 ==== Version update (3.1.189 -> 3.1.191) Subpackages: yast2-devel-doc - Split SuSEFirewall and SuSEFirewallServices classes to separate files as recommended by the Yast coding style (fate#318356, gh#yast/yast-yast2#471) - 3.1.191 - Refactor SuSEFirewall backend code to support FirewallD. This allows yast2 modules to be firewall agnostic and handle firewall services in either SuSEFirewall2 or FirewallD (fate#318356, gh#yast/yast-yast2#457) * Do a bit of code cleanup. * Add FirewallD tests. - 3.1.190 ==== yast2-bootloader ==== Version update (3.1.187 -> 3.1.192) - Drop yast2-bootloader-devel-doc package (fate#320356) - 3.1.192 - fix unknown method error ( caused by fix for bnc#980529) - 3.1.191 - use proper device to setup pmbr for grub2efi (bnc#981997) - 3.1.190 - do not try to install grub2 on lvm on partition-less disk (bnc#980529) - 3.1.189 - run mkinitrd at the end of installation to ensure proper initrd even for image based installation or live install (bnc#977656,bnc#979719) - 3.1.188 ==== yast2-firewall ==== Version update (3.1.4 -> 3.1.5) - Add support for firewalld (fate#318356) * Bump yast2 dependency to 3.1.191 which is the first version to support the firewalld backend. - 3.1.5 ==== yast2-installation ==== Version update (3.1.187 -> 3.1.191) - When importing SSH keys/configuration, only regular files will be considered (bsc#982522) - Force YaST2-Firstboot.service to run after YaST2-Second-Stage.service (bsc#980365) - 3.1.191 - Move the debugger invocation code to yast2-ruby-bindings package to use the same implementation at run time (FATE#318421) - 3.1.190 - System Role: centered dialog (ncurses). - More visual improvements in the SSH keys importing proposal summary based on blog entry feedback. (Fate#319624) - 3.1.189 - Start the Ruby debugger at the beginning of installation when Y2DEBUGGER is set (FATE#318421) - 3.1.188 ==== yast2-mail ==== Version update (3.1.7 -> 3.1.8) - bnc#981103 - yast2 mail uses always brackets for relayhost - bnc#981101 - yast2 mail adds POSTFIX_NODAEMON to /etc/sysconfig/postfix - 3.1.8 ==== yast2-network ==== Version update (3.1.151 -> 3.1.152) - fate#319319 - implemented support for vncmanager in Remote module. Thanks to msrb@suse.cz. - 3.1.152 ==== yast2-ruby-bindings ==== Version update (3.1.46 -> 3.1.48) - Improve the debugger support - use the same code also at run time, allow using `Y2DEBUGGER` also in installed system (FATE#318421) - 3.1.48 - Added support for running the Ruby debugger (FATE#318421) - Allow running the Ruby debugger from the generic crash handler if the debugger is installed - 3.1.47 - update code according to updated yast ruby style guide -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org