openSUSE Factory December 2016

factory@lists.opensuse.org

118 participants
95 discussions

[opensuse-factory] New Tumbleweed snapshot 20161216 released!
by Dominique Leuenberger 17 Dec '16

17 Dec '16

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&versio… 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: ModemManager MozillaFirefox (50.0.2 -> 50.1.0) apache2 bison dbus-1 dbus-1-x11 nghttp2 (1.16.1 -> 1.17.0) patterns-openSUSE pidgin pidgin-branding-openSUSE (42.1 -> 42.2) rtkit sbl sssd texlive texlive-specs-n (2016.112.2.004svn28119 -> 2016.113.2.004svn28119) transmission udisks2 (2.1.7 -> 2.1.8) zsh (5.2 -> 5.3) === Details === ==== ModemManager ==== Subpackages: ModemManager-bash-completion ModemManager-devel libmm-glib0 typelib-1_0-ModemManager-1_0 - Drop pkgconfig(libsystemd-login): Even though configure checks for it, pkgconfig(libsystemd) is actually enough to enable the needed features (resume support). libsystemd-login no longer exists with systemd v232. ==== MozillaFirefox ==== Version update (50.0.2 -> 50.1.0) Subpackages: MozillaFirefox-translations-common - update to Firefox 50.1.0 (boo#1015422) * MFSA 2016-94 CVE-2016-9894: Buffer overflow in SkiaGL (bmo#1306628) CVE-2016-9899: Use-after-free while manipulating DOM events and audio elements (bmo#1317409) CVE-2016-9895: CSP bypass using marquee tag (bmo#1312272) CVE-2016-9896: Use-after-free with WebVR (bmo#1315543) CVE-2016-9897: Memory corruption in libGLES (bmo#1301381) CVE-2016-9898: Use-after-free in Editor while manipulating DOM subtrees (bmo#1314442) CVE-2016-9900: Restricted external resources can be loaded by SVG images through data URLs (bmo#1319122) CVE-2016-9904: Cross-origin information leak in shared atoms (bmo#1317936) CVE-2016-9901: Data from Pocket server improperly sanitized before execution (bmo#1320057) CVE-2016-9902: Pocket extension does not validate the origin of events (bmo#1320039) CVE-2016-9903: XSS injection vulnerability in add-ons SDK (bmo#1315435) CVE-2016-9080: Memory safety bugs fixed in Firefox 50.1 CVE-2016-9893: Memory safety bugs fixed in Firefox 50.1 and Firefox ESR 45.6 - added patch mozilla-aarch64-startup-crash.patch (bsc#1011922) ==== apache2 ==== Subpackages: apache2-devel apache2-doc apache2-example-pages apache2-prefork apache2-utils - fix build with new systemd + amended httpd-2.4.3-mod_systemd.patch - Replace mixed indentation with predominant style. ==== bison ==== Subpackages: bison-lang - Update keyring file to not be 38 MB large... ==== dbus-1 ==== Subpackages: dbus-1-devel libdbus-1-3 libdbus-1-3-32bit - Requires systemd >= 209 and drop the compatibility pkg-config names that don't exist in newer systemd - Drop useless --with-pic which is only for static libs - Abort installation when user/group creation fails - Avoid calling %service_* more than once - Build the dbus-1 package without X in the dbus-1.spec - Move the dbus-launch.nox11 to the dbus-1 package and install it by default - Build devel-doc package in dbus-1.spec and don't build any documentation in dbus-1-x11 - Make dbus-1-x11 package contains only the X11-enabled dbus-launch - Fix some rpmlint warnings - Delete the dbus-1-x11.spec.in file, since maintaining it is more complicated then keeping in sync a dbus-1-x11.spec file of less then 120 lines - Create new subpackage: dbus-1-nox11 - contains dbus-launch without x11 support - Rename dbus-launch to dbus-launch.x11 - use update-alternatives to switch between dbus-launch with and without X11 - Solves [bnc#934214] ==== dbus-1-x11 ==== - Requires systemd >= 209 and drop the compatibility pkg-config names that don't exist in newer systemd - Drop useless --with-pic which is only for static libs - Abort installation when user/group creation fails - Avoid calling %service_* more than once - Build the dbus-1 package without X in the dbus-1.spec - Move the dbus-launch.nox11 to the dbus-1 package and install it by default - Build devel-doc package in dbus-1.spec and don't build any documentation in dbus-1-x11 - Make dbus-1-x11 package contains only the X11-enabled dbus-launch - Fix some rpmlint warnings - Delete the dbus-1-x11.spec.in file, since maintaining it is more complicated then keeping in sync a dbus-1-x11.spec file of less then 120 lines - Create new subpackage: dbus-1-nox11 - contains dbus-launch without x11 support - Rename dbus-launch to dbus-launch.x11 - use update-alternatives to switch between dbus-launch with and without X11 - Solves [bnc#934214] ==== nghttp2 ==== Version update (1.16.1 -> 1.17.0) - Update to version 1.17.0: * lib: Disallow content-length in 1xx, 204, or 200 to a CONNECT request (GH-722) * lib: Avoid memcpy against NULL src * build: MSVC version resource support (Patch from Remo E) (GH-718) * asio: server: Call on_close callback on connection close (GH-729) * nghttpx: Fix frequent crash with --backend-http-proxy-uri * nghttpx: Robust backend read timeout * nghttpx: Fix bug that mishandles response header from h1 backend * nghttpx: Fix bug that zero-length POST is not forwarded (GH-726) * nghttpx: Remove optional reason-phrase from SPDY :status * nghttpx: Header key and value must be string in mruby script * nghttpx: Strip content-length with 204 or 200 to CONNECT in mruby (GH-722) * nghttpx: Strict handling for Content-Length or Transfer-Encoding in h1 (GH-722) * nghttpx: Fix compilation with BoringSSL (Patch from dalf) (GH-717) * nghttpd, nghttpx, asio: Add missing mandatory SP after status code ==== patterns-openSUSE ==== Subpackages: patterns-openSUSE-apparmor patterns-openSUSE-apparmor_opt patterns-openSUSE-base patterns-openSUSE-books patterns-openSUSE-console patterns-openSUSE-devel_C_C++ patterns-openSUSE-devel_basis patterns-openSUSE-devel_ide patterns-openSUSE-devel_java patterns-openSUSE-devel_kde patterns-openSUSE-devel_kde_frameworks patterns-openSUSE-devel_kernel patterns-openSUSE-devel_osc_build patterns-openSUSE-devel_perl patterns-openSUSE-devel_python patterns-openSUSE-devel_qt5 patterns-openSUSE-devel_rpm_build patterns-openSUSE-devel_ruby patterns-openSUSE-devel_web patterns-openSUSE-dhcp_dns_server patterns-openSUSE-directory_server patterns-openSUSE-enhanced_base patterns-openSUSE-enhanced_base_opt patterns-openSUSE-file_server patterns-openSUSE-fonts patterns-openSUSE-fonts_opt patterns-openSUSE-games patterns-openSUSE-gateway_server patterns-openSUSE-generic_server patterns-openSUSE-gnome patterns-openSUSE-gnome_admin patterns-openSUSE-gnome_basis patterns-openSUSE-gnome_basis_opt patterns-openSUSE-gnome_games patterns-openSUSE-gnome_ide patterns-openSUSE-gnome_imaging patterns-openSUSE-gnome_imaging_opt patterns-openSUSE-gnome_internet patterns-openSUSE-gnome_laptop patterns-openSUSE-gnome_multimedia patterns-openSUSE-gnome_multimedia_opt patterns-openSUSE-gnome_office patterns-openSUSE-gnome_office_opt patterns-openSUSE-gnome_utilities patterns-openSUSE-gnome_yast patterns-openSUSE-imaging patterns-openSUSE-imaging_opt patterns-openSUSE-kde patterns-openSUSE-kde_edutainment patterns-openSUSE-kde_games patterns-openSUSE-kde_ide patterns-openSUSE-kde_imaging patterns-openSUSE-kde_internet patterns-openSUSE-kde_multimedia patterns-openSUSE-kde_office patterns-openSUSE-kde_plasma patterns-openSUSE-kde_telepathy patterns-openSUSE-kde_utilities patterns-openSUSE-kde_utilities_opt patterns-openSUSE-kde_yast patterns-openSUSE-kvm_server patterns-openSUSE-lamp_server patterns-openSUSE-laptop patterns-openSUSE-lxde patterns-openSUSE-lxde_laptop patterns-openSUSE-lxd e_office patterns-openSUSE-mail_server patterns-openSUSE-minimal_base patterns-openSUSE-minimal_base-conflicts patterns-openSUSE-misc_server patterns-openSUSE-multimedia patterns-openSUSE-multimedia_opt patterns-openSUSE-network_admin patterns-openSUSE-non_oss patterns-openSUSE-non_oss_opt patterns-openSUSE-office patterns-openSUSE-office_opt patterns-openSUSE-print_server patterns-openSUSE-remote_desktop patterns-openSUSE-rest_dvd patterns-openSUSE-sw_management patterns-openSUSE-sw_management_gnome patterns-openSUSE-sw_management_kde patterns-openSUSE-tabletpc patterns-openSUSE-technical_writing patterns-openSUSE-x11 patterns-openSUSE-x11_opt patterns-openSUSE-x11_yast patterns-openSUSE-xen_server patterns-openSUSE-xfce patterns-openSUSE-xfce_basis patterns-openSUSE-xfce_laptop patterns-openSUSE-xfce_office patterns-openSUSE-yast2_basis patterns-openSUSE-yast2_install_wf - Major cosmetic cleanup, No functional changes. Changes found by running zypper --whatprovides on each name listed in the pattern then fixing the differences. * Update packages that have been renamed * Drop packages that have been absorbed into other packages ==== pidgin ==== Subpackages: libpurple libpurple-tcl - Make libpurple require libpurple-branding. - Correctly remove *.so files for plugins (fixes devel-file-in-non-devel-package). - Rename libpurple-meanwhile to libpurple-plugin-sametime. - Remove generation of a plugin list to package, simply add it all in %files with exclusions. - Build with GStreamer 1.x on SLE 12 SP2. - Apply pidgin-use-default-alsa.patch for SLE 12+ only properly. - Provide libpurple-branding-upstream for SLE 11 as well. ==== pidgin-branding-openSUSE ==== Version update (42.1 -> 42.2) - Bump version to 42.2. - Spec cleanup. - Don't provide pidgin-branding with libpurple-branding-openSUSE, but still provide pidgin-branding-openSUSE. ==== rtkit ==== - Drop BR on libsystemd-daemon as rtkit uses a fancy way to reuse systemd code :) ==== sbl ==== - Drop (build) requirement on libsystemd-daemon There's no usage of systemd libraries in this package however build require the systemd rpm macros instead as they're used in the spec file. ==== sssd ==== Subpackages: libnfsidmap-sss libsss_idmap0 libsss_nss_idmap0 libsss_simpleifp0 sssd-32bit sssd-krb5-common sssd-ldap - BuildRequire pkgconfig(libsystemd) instead of pkgconfig(libsystemd-login): the latter has been deprecated since systemd 209 and finally removed with systemd 230. ==== texlive ==== - We want perl(Unicode::Collate) >= 1.14 for biblatex-biber 2.5 ==== texlive-specs-n ==== Version update (2016.112.2.004svn28119 -> 2016.113.2.004svn28119) - Add patch latexdiff_perl.dif which includes the upstream commits cfe445c and a83d9c to fix boo#1013904 ==== transmission ==== Subpackages: transmission-common transmission-gtk - Add transmission-systemd.patch: Look for libsystemd instead of libsystemd-daemon. The modules have been merged since systemd�209. ==== udisks2 ==== Version update (2.1.7 -> 2.1.8) Subpackages: libudisks2-0 - Update to version 2.1.8: + Allow NTFS mount option "big_writes". + Don't coldplug uninitilized udev devices. + Detect old (non-Pro) MemoryStick cards. + Lock the partition table while creating a new partition. + exfat: Drop umask=0077 default. + udisks2.service: Add KillSignal=SIGINT. + btrfs: Add support for changing label. + Updated translations. - Replace pkgconfig(libsystemd-login) BuildRequires with pkgconfig(libsystemd): the two have been merged since systemd 209. - Drop udisks2-Reread-partition-table-before-wiping.patch: fixed upstream. ==== zsh ==== Version update (5.2 -> 5.3) - Update to zsh 5.3 * Unicode9 support, this needs support from your terminal to work correctly. * The new word modifier ':P' computes the physical path of the argument. * The output of "typeset -p" uses "export" commands or the "-g" option for parameters that are not local to the current scope. * vi-repeat-change can repeat user-defined widgets if the widget calls zle -f vichange. * The parameter $registers now makes the contents of vi register buffers available to user-defined widgets. * New vi-up-case and vi-down-case builtin widgets bound to gU/gu (or U/u in visual mode) for doing case conversion. * A new select-word-match function provides vim-style text objects with configurable word boundaries using the existing match-words-by-style mechanism. * Support for the conditional expression [[ -v var ]] to test if a variable is set for compatibility with other shells. * The print and printf builtins have a new option -v to assign the output to a variable. * New x: syntax in completion match specifications make it possible to disable match specifications hardcoded in completion functions. - Re-add custom zshrc and zshenv to unbreak compatibility with old usage (boo#998858). - Add fix-printf.patch to fix a regression in printf. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] is this fix in upcoming leap? Could it be "backported" to older supported distro-releases (13.2?)?
by L A Walsh 17 Dec '16

17 Dec '16

Just ran into a bug in the "ld.gold" linker in binutils. When trying to compile the 4.9 vanilla kernel (as downloaded from kernel.org), I got: ld: internal error in target, at ../../gold/parameters.h:105 scripts/Makefile.build:498: recipe for target 'lib/lib-ksyms.o' failed make[1]: *** [lib/lib-ksyms.o] Error 1 Makefile:988: recipe for target 'lib' failed make: *** [lib] Error 2 It's caused by a bug in the gold linker (but is not present in the "ld.bfd" version of the linker). Apparently it's been patch in the trunk version of binutils as of 2016-11-21. Since it affect anyone compiling the kernel (and who's alternatives point "ld" to the ld.gold linker), it might be nice to backport. If not backported, then users can only work around the problem by overriding the "alternatives" dir and not using the gold linker -- which I though had various other benefits/features -- i.e. might cause other random compatibility issues if switched (I don't know how likely this is, but it makes me nervous to switch "ld" just for the kernel compiles and have it affect all other products that use "ld". -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Packaging of Rust compiler.
by Luke Jones 16 Dec '16

16 Dec '16

Hi all, I was recently added to the maintainer role for the rust compiler devel project; as rust is something I use daily, I feel I am a good fit for the task. I would now like to raise some discussion about the current state of packaging for Rust. At present the build process is relying on the previous version of Rust being packaged with a naming scheme of 'rustc-1_11' for example, which is used for building the next version of Rust. The issue I have with this is that we will end up with a large amount of previous versions at some point, along with a long list of obsoletes/provides in the spec files. The way I would like to counter this is by; 1. including the bootstrap tarball (for each arch) with the src rpm. 2. use the bootstrap tarballs to build the current compiler version 3. use spec file functionality to choose which tarball arch to use based on the cpu arch being built for. At this point I feel this is the best course of action to prevent future issues, it also has the benefit of the source rpm providing all the needed sources to build that version of Rust, rather than relying on a previously packaged version. It's a little extra work, but would be worth doing. I will get a trial package up in the next few days to see how it goes, then if all is okay and other agree with it, I'll switch over the official rpm build to that. Regards, Luke. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 11

[opensuse-factory] openSUSE Tumbleweed – Review of the Week 2016/50
by Dominique Leuenberger / DimStar 16 Dec '16

16 Dec '16

Dear Tumbleweed users and hackers, Even though the year is not yet completely over, this will be the last review for this year: starting from today on, I will be on annual leave until January 9th 2017, when I will resume all activities. Tumbleweed of course will not stop rolling at this time: it is YOU that makes it rolling after all. Nevertheless, you should not be surprised if the pace goes a bit down as many people will be busy with other things during this period. So, back to the review of Tumbleweed – let’s see what we got in the last week. Namely there were 7 snapshots again and I will cover {1209..1215}. Noteworthy updates in those snapshots: * GStreamer 1.10.2 * shim: the ms-signed uefi loader is now binary-shared with Leap * Linux kernel 4.8.13 * Wine is closing in to 2.0 with rc1 released * pitivi 0.9.8 fixes a lot of bugs Many of the things we had on the incoming list last week are still there: * systemd 232: x.org needed some packaging adjustments, but there is already an update hanging which causes issues in openQA. systemd will thus have to stay in line * X.org 1.19: as mentioned, this causes issues in openQA, where the screen apparently freezes (keyboard input / command execution seems to be handled though * KDE Applications 16.12.0: We had big hopes to get this into the 1216 snapshot, but some minor packaging issues with regards to ppc64le made this slip. But it can’t be that long anymore until we can ship it * Linux kernel 4.8.14 * KDE Frameworks 5.29.0 will be shipped in the same snapshot as the KDE Applications update * Qt 5.7.1 With this, I want to wish those that celebrate christmas a happy festive season. Everybody else, simply have a great time ahead. Cheers, Dominique

1 0

[opensuse-factory] Missing package /home:/namtrac: freetype2-devel-2.7-134.5.x86_64.rpm
by Marco Calistri 16 Dec '16

16 Dec '16

Hello, Anybody could suggest me another repository or even inform me if the missing package will become available next: File './x86_64/freetype2-devel-2.7-134.5.x86_64.rpm' non trovato sul supporto 'http://download.opensuse.org/repositories/home:/namtrac:/subpixel/openSUSE_…' Thanks and regards, -- Marco Calistri Opensuse Tumbleweed 64 bit Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 Intel® Sandybridge Mobile

2 1

[opensuse-factory] pidgin plays no sound anymore
by Olaf Hering 15 Dec '16

15 Dec '16

Since a few days (perhaps weeks?) pidgin does not seem to play sounds anymore when a new message arrives. I'm sure it used to do that. According to the settings sounds are enabled. If I click on "Preview.." for a given event there is some pulseaudio activity going on according to strace. But in the end nothing is heard. The control-center audio thing does play sound ("front left", "front right"), so I think parts of the sound system do work properly. Any idea why pidgin is silent? List of packages that may be involved in the issue: alsa-1.1.2-1.3.x86_64 alsa-oss-1.0.28-3.8.x86_64 alsa-oss-32bit-1.0.28-3.8.x86_64 alsa-plugins-1.1.1-1.5.x86_64 alsa-plugins-pulse-1.1.1-1.5.x86_64 alsa-plugins-pulse-32bit-1.1.1-1.5.x86_64 alsa-utils-1.1.2-1.3.x86_64 libtelepathy-glib0-0.24.1-2.3.x86_64 libtelepathy-glib0-debuginfo-0.24.1-2.3.x86_64 libtelepathy-logger3-0.8.2-2.1.x86_64 pulseaudio-9.0-2.2.x86_64 pulseaudio-bash-completion-9.0-2.2.x86_64 pulseaudio-module-bluetooth-9.0-2.2.x86_64 pulseaudio-module-gconf-9.0-2.2.x86_64 pulseaudio-module-lirc-9.0-2.2.x86_64 pulseaudio-module-x11-9.0-2.2.x86_64 pulseaudio-module-zeroconf-9.0-2.2.x86_64 pulseaudio-utils-32bit-9.0-2.2.x86_64 pulseaudio-utils-9.0-2.2.x86_64 speech-dispatcher-0.8.4-2.1.x86_64 speech-dispatcher-module-espeak-0.8.4-2.1.x86_64 telepathy-gabble-0.18.3-1.10.x86_64 telepathy-haze-0.8.0-5.5.x86_64 telepathy-idle-0.2.0-3.8.x86_64 telepathy-logger-0.8.2-2.1.x86_64 telepathy-mission-control-5.16.3-1.11.x86_64 telepathy-mission-control-plugin-goa-3.12.12-3.1.x86_64 telepathy-rakia-0.8.0-3.8.x86_64 telepathy-salut-0.8.1-7.9.x86_64 Olaf

3 3

[opensuse-factory] New Tumbleweed snapshot 20161214 released!
by Dominique Leuenberger 15 Dec '16

15 Dec '16

1 0

[opensuse-factory] New Tumbleweed snapshot 20161213 released!
by Dominique Leuenberger 14 Dec '16

14 Dec '16

1 0

[opensuse-factory] New Tumbleweed snapshot 20161212 released!
by Dominique Leuenberger 13 Dec '16

13 Dec '16

1 0

[opensuse-factory] nodejs renamed to nodejs6 on Tumbleweed
by Karl Cheng 12 Dec '16

12 Dec '16

Hi everyone, With the update to Node.js 6.9.2, users will need to install the nodejs6 package to receive this update as the nodejs package has been removed. This is to keep in line with the naming scheme for Leap, as well as the Web & Scripting Module in SLE. Node.js 7.x has not been submitted to Factory yet as an odd bug remains[1] that arguably should not be present in a post-testing release. [1]: https://github.com/nodejs/node/issues/9419 - Karl Cheng (Qantas94Heavy) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory December 2016