openSUSE Bugs October 2019

bugs@lists.opensuse.org

1 participants
4129 discussions

[Bug 1152771] New: [/usr/etc] installation-images needs to follow pam changes
by bugzilla_noreply＠novell.com 02 Oct '19

02 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1152771 Bug ID: 1152771 Summary: [/usr/etc] installation-images needs to follow pam changes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- PAM is moving the system default configuration from /etc to /usr/etc (allowing the admin to override directly in /etc) This currently causes installation-images to fail, as it no longer finds the templates in /etc [ 845s] adding package pam [1.3.1+git20190923.ea78d67-169.3.i586] {prein,postin} [ 845s] cp: cannot stat 'tmp/rescue//etc/pam.d/common-auth': No such file or directory [ 845s] unable to access /etc/pam.d/common-auth at lib/AddFiles.pm line 791. [ 845s] make: *** [Makefile:169: rescue] Error 1 [ 845s] error: Bad exit status from /var/tmp/rpm-tmp.cUK8uI (%build) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1151518] AUDIT-TRACKER: bluez: new D-Bus service /etc/dbus-1/system.d/bluetooth-mesh.conf
by bugzilla_noreply＠novell.com 02 Oct '19

02 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1151518 http://bugzilla.suse.com/show_bug.cgi?id=1151518#c5 --- Comment #5 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- (In reply to seife(a)novell.slipkontur.de from comment #4) > For now I suddest to disable the mesh dbus-config, maybe ship it as an > example with a README in the package docs. If you want to take this route then it is fine from my side. Then we (security team) have nothing to do. By not installing the mesh dbus-config the rpmlint error will go away. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1150338] New: Drop Ghostscript apparmor profile as it is useless
by bugzilla_noreply＠novell.com 02 Oct '19

02 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1150338 Bug ID: 1150338 Summary: Drop Ghostscript apparmor profile as it is useless Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All URL: https://rudin.suse.de:8894/request/show/701304 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jsegitz(a)suse.com, jsmeix(a)suse.com, meissner(a)suse.com, opensuse(a)dstoecker.de, suse-beta(a)cboltz.de, werner(a)suse.com Depends on: 1134327 Found By: Community User Blocker: --- +++ This bug was initially created as a clone of Bug #1134327 +++ -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1134327] New: Enhance Ghostscript apparmor profile for ps2epsi
by bugzilla_noreply＠novell.com 02 Oct '19

02 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1134327 Bug ID: 1134327 Summary: Enhance Ghostscript apparmor profile for ps2epsi Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Enhancement Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: jsmeix(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- See https://build.opensuse.org/request/show/701304 Basically this are the intended changes: +++ ghostscript.changes @@ -1,0 +2,5 @@ +Tue May 7 11:57:21 UTC 2019 - Dirk Stoecker <opensuse(a)dstoecker.de> + +- Fix apparmor profile for ps2epsi + +------------------------------------------------------------------- other changes: -------------- ++++++ apparmor_ghostscript --- apparmor_ghostscript +++ apparmor_ghostscript @@ -45,4 +45,13 @@ #include <abstractions/base> /usr/bin/dirname mr, } + + # ps2epsi + /usr/bin/gawk mrix, + /usr/bin/cat mrix, + /usr/bin/ls mrix, + /usr/bin/mktemp mrix, + /usr/bin/rm mrix, + /usr/bin/sed mrix, + /usr/bin/which mrix, } -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1149761] python-kiwi must be updated to support aarch64 live images
by bugzilla_noreply＠novell.com 02 Oct '19

02 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1149761 http://bugzilla.suse.com/show_bug.cgi?id=1149761#c1 Marcus Schaefer <ms(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|ms(a)suse.com |dominic.vieira(a)suse.com --- Comment #1 from Marcus Schaefer <ms(a)suse.com> --- I'm assigning this to Dominic, since he is coordinating together with Alex which ECO is needed to get that done Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1152748] New: Configured network not detected
by bugzilla_noreply＠novell.com 02 Oct '19

02 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1152748 Bug ID: 1152748 Summary: Configured network not detected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: igonzalezsosa(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- YaST2 does not detect correctly whether the network is configured or not during installation. See https://openqa.opensuse.org/tests/1045828. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1152006] dracut update breaks kiwi oem image pxe installation
by bugzilla_noreply＠novell.com 02 Oct '19

02 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1152006 http://bugzilla.suse.com/show_bug.cgi?id=1152006#c9 --- Comment #9 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Stefan Seyfried from comment #4) > See - no root device needed ;-) Understood. The problem is that that dracut's primary objective is still booting computers, and it's easy to forget about the other use cases. > I guess that initrd-root-device.target is intended simply as an ordering > helper target in systemd In principle, this is modeled via the dependencies of "initrd.target". By default, these include "initrd-root-fs.target initrd-root-device.target initrd-fs.target". That supports my point - if the root device and FS are present, there's no point in waiting any further, whether or not "$netroot" is set. [Note to self: By default, "initrd-parse-etc.service", pulled in by "initrd.target", execs systemctl daemon-reload ("Reload Configuration from the Real Root") and then starts "initrd-cleanup.service", which has "After" deps on initrd-root-fs.target initrd-fs.target initrd.target and isolates "initrd-switch-root.target". See also bootup(7).] The Right Solution (TM) for dracut's alternate use cases such as Kiwi (and also, for the default case) would be to create a proper model for the dependencies for initrd.target. In your case, the dependency list of initrd-root-device.target is empty, and thus nothing to wait for. BUT you need to wait for the network to be up, and that should be properly modeled by a systemd dependency. Also, you don't need initrd-switch-root.target, obviously (how is that avoided today?). Unfortunately, there's no such thing as "initrd-network.target", currently. Instead, there's dracut's legacy "initqueue" concept. At least the "finished" initqueue is not much else than a "poor man's systemd" trying to model service dependencies in a simplistic manner. This was the point of my patch - the initqueue dumbly waits for the network device even though it's redundant and the root disk has long be found. Doing this right for all use cases (or at least: figuring out a framework that can be extended to work for all use cases) is non-trivial, prone to cause regressions, and would require intensive upstream discussion. Comments welcome. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1151518] AUDIT-TRACKER: bluez: new D-Bus service /etc/dbus-1/system.d/bluetooth-mesh.conf
by bugzilla_noreply＠novell.com 02 Oct '19

02 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1151518 http://bugzilla.suse.com/show_bug.cgi?id=1151518#c4 --- Comment #4 from Stefan Seyfried <seife(a)novell.slipkontur.de> --- I agree with the assessment that this is a niche feature right now, I do not even know how to use it at all ;-) For now I suddest to disable the mesh dbus-config, maybe ship it as an example with a README in the package docs. Regarding a special group that gives access to the feature: as the feature is very special, probably a dedicated group for it would be justified, but I'd go this way once there are users for the feature and a real demand for it, if it is still necessary then. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1149131] transaction server shell does not mount /etc
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1149131 http://bugzilla.opensuse.org/show_bug.cgi?id=1149131#c3 --- Comment #3 from William Brown <william.brown(a)suse.com> --- I tried to use pip install and it was unable to access the ca from /etc if I recall? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136184] python-botocore needs to support urllib 1.25 for CVE-2019-9947
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1136184 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:11175:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs October 2019