November 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1064061] Virtualization/xen: Bug tracking multiple Xen CVEs
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1064061 http://bugzilla.suse.com/show_bug.cgi?id=1064061#c3 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(carnold(a)suse.com) | --- Comment #3 from Charles Arnold <carnold(a)suse.com> --- (In reply to pgnd _ from comment #2) > Great. Just to understand the 'link' ... Link in this case is an expression saying that when I push fixes into sles12sp3 they will automatically get pushed to os42.3. This is because the official channel for both contains Xen 4.9 and that version will not change through the life of both products (we do change the dot version, 4.9.0 -> 4.9.1). > > For example, for one CVE @ SuSE > > https://www.suse.com/security/cve/CVE-2017-15594 > > it references the fix in > > openSUSE Leap 42.3 xen >= 4.9.0_14-10.1 > > That openSUSE fix *is* targeted at > > http://download.opensuse.org/repositories/Virtualization/openSUSE_Leap_42.3 > > ? (which happens, atm, to have xen-4.10.0_01-537.1.x86_64.rpm) > > Not some other openSUSE repo, correct? The Virtualization/xen repo contains the most recent Xen version being worked on for the next SLES/openSUSE release - in this case xen 4.10. The repo has build targets for the older versions of openSUSE (eg, 42.2 and 42.3) for those interested in running it there but it is not the supported version of Xen for those older distros. Only the version that initially shipped with the distro will be officially supported with updates from the update channel. So for openSUSE 42.2, only Xen 4.7.x is supported with updates and for 42.3, only Xen 4.9.x. Xen 4.10 might run fine on 42.3 but it isn't specifically being tested there so your mileage may vary. Upstream Xen 4.10 is still in the 'rc' phase of development so expect some churn. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1065847] kvirc in KDE:Unstable:Extra requires libesd0 which has been dropped
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1065847 http://bugzilla.suse.com/show_bug.cgi?id=1065847#c5 --- Comment #5 from Wolfgang Bauer <wbauer(a)tmo.at> --- Btw: (In reply to Mircea Kitsune from comment #3) > That's because the official version is extremely old (4.2.0) whereas that > provides a much newer version (4.9.2): 4.2.0 is the last official upstream release: http://www.kvirc.net/?id=releases&platform=source The package in KDE:Unstable (4.9.2) is actually a current git snapshot, similar to the "nightly builds". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1064061] Virtualization/xen: Bug tracking multiple Xen CVEs
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1064061 http://bugzilla.suse.com/show_bug.cgi?id=1064061#c2 pgnd _ <pgnet.dev(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carnold(a)suse.com Flags| |needinfo?(carnold(a)suse.com) --- Comment #2 from pgnd _ <pgnet.dev(a)gmail.com> --- Great. Just to understand the 'link' ... For example, for one CVE @ SuSE https://www.suse.com/security/cve/CVE-2017-15594 it references the fix in openSUSE Leap 42.3 xen >= 4.9.0_14-10.1 That openSUSE fix *is* targeted at http://download.opensuse.org/repositories/Virtualization/openSUSE_Leap_42.3 ? (which happens, atm, to have xen-4.10.0_01-537.1.x86_64.rpm) Not some other openSUSE repo, correct? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1065847] kvirc in KDE:Unstable:Extra requires libesd0 which has been dropped
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1065847 Wolfgang Bauer <wbauer(a)tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|libesd0 missing from |kvirc in KDE:Unstable:Extra |openSUSE Tumbleweed |requires libesd0 which has |software repository |been dropped -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1065847] libesd0 missing from openSUSE Tumbleweed software repository
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1065847 http://bugzilla.suse.com/show_bug.cgi?id=1065847#c4 Wolfgang Bauer <wbauer(a)tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(sonichedgehog_hyp | |erblast00(a)yahoo.com) | --- Comment #4 from Wolfgang Bauer <wbauer(a)tmo.at> --- (In reply to Mircea Kitsune from comment #3) > My version of KVirc is installed from obs://build.opensuse.org/KDE:Unstable Ok, this one was indeed built with ESD support. Should be fixed by now, so just update to the latest version: https://build.opensuse.org/request/show/538182 The package in the distribution was built without ESD since ever. Note that the packages in KDE:Unstable are basically unsupported though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1064061] Virtualization/xen: Bug tracking multiple Xen CVEs
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1064061 http://bugzilla.suse.com/show_bug.cgi?id=1064061#c1 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Charles Arnold <carnold(a)suse.com> --- openSUSE 42.x and SLE12 SPx are now closely linked. When security fixes go out for SLE12, they are automatically rolled over to openSUSE so we don't need to track them. The fixes you have noted here have all gone out without any extra effort on my part :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1062590] Virtualization/virt-manager: Proposal insufficient for CaaS Platform
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1062590 http://bugzilla.suse.com/show_bug.cgi?id=1062590#c1 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Charles Arnold <carnold(a)suse.com> --- This should be fixed in the latest Tumbleweed versions of virt-manager and osinfo-db Maintenance updates for SLE12 SP2/SP3 have also been submitted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1065847] libesd0 missing from openSUSE Tumbleweed software repository
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=1065847 http://bugzilla.suse.com/show_bug.cgi?id=1065847#c3 --- Comment #3 from Mircea Kitsune <sonichedgehog_hyperblast00(a)yahoo.com> --- (In reply to Wolfgang Bauer from comment #2) My version of KVirc is installed from obs://build.opensuse.org/KDE:Unstable That's because the official version is extremely old (4.2.0) whereas that provides a much newer version (4.9.2): https://software.opensuse.org/package/kvirc I get the following error when running KVirc without this library: kvirc: error while loading shared libraries: libesd.so.0: cannot open shared object file: No such file or directory I do not know how to check the phonon backend. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1032385] New: Submit MongoDB to Factory/Tumbleweed and add additional Btrfs subvolume
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1032385 Bug ID: 1032385 Summary: Submit MongoDB to Factory/Tumbleweed and add additional Btrfs subvolume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guoyunhebrave(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- MongoDB is getting popular these years and considered as a reliable database widely used. So I suggest to submit mongodb package to openSUSE Factory/Tumbleweed. https://build.opensuse.org/request/show/485713 Like other database, MongoDB requires a subvolume in /var/lib/mongodb. This means we need to make changes in the installer. Currently, we have the latest stable version of MongoDB in server:database repository. Newer version MongoDB only supports x64 systems, so i586 build will fail. Configuration file in /etc/mongodb.conf is okay but more available configuration options should be added in future package updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1065961] New: Project config sets build flag that no available compiler supports
by bugzilla_noreply＠novell.com 01 Nov '17

01 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1065961 Bug ID: 1065961 Summary: Project config sets build flag that no available compiler supports Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: aloisio(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Both openSUSE:Leap:42.2:Update and openSUSE:Leap:42.3:Update add "-fstack-clash-protection" to %optflags, but neither gcc6 in the former nor gcc7 in the latter can understand. g++-6: error: unrecognized command line option '-fstack-clash-protection'; did you mean '-fstack-protector'? g++-7: error: unrecognized command line option '-fstack-clash-protection'; did you mean '-fstack-protector'? See https://build.opensuse.org/package/show/home:alois:branches:multimedia:apps… as example. -- You are receiving this mail because: You are on the CC list for the bug.

1 2