[Bug 1004977] New: suse-filelist-forbidden-sysconfig (Badness: 10000) /etc/sysconfig/corosync-qdevice is not allowed in SUSE
http://bugzilla.suse.com/show_bug.cgi?id=1004977 Bug ID: 1004977 Summary: suse-filelist-forbidden-sysconfig (Badness: 10000) /etc/sysconfig/corosync-qdevice is not allowed in SUSE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team@suse.de Reporter: bliu@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- When I commit corosync-2.4.1 to obs(both Leap 42.1 and Tumbleweed) At the end, obs reports some errors: [ 169s] corosync-qdevice.i586: E: suse-filelist-forbidden-sysconfig (Badness: 10000) /etc/sysconfig/corosync-qdevice is not allowed in SUSE [ 169s] corosync-qnetd.i586: E: suse-filelist-forbidden-sysconfig (Badness: 10000) /etc/sysconfig/corosync-qnetd is not allowed in SUSE [ 169s] corosync.i586: E: suse-filelist-forbidden-sysconfig (Badness: 10000) /etc/sysconfig/corosync is not allowed in SUSE [ 169s] Please use /var/adm/fillup-templates/sysconfig.<pkgname> [ 169s] and call %fillup_and_insserv for new sysconfig files. [ 169s] [ 169s] corosync.i586: E: suse-dbus-unauthorized-service (Badness: 10000) /etc/dbus-1/system.d/corosync-signals.conf Can we allow the operation by adding some rules? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1004977 http://bugzilla.suse.com/show_bug.cgi?id=1004977#c2 Bin Liu <bliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwang@suse.com --- Comment #2 from Bin Liu <bliu@suse.com> --- (In reply to Andreas Stieger from comment #1)
Follow the instructions given in the message. Do not package the file in /etc/sysconfig. Instead ..
(In reply to Bin Liu from comment #0)
[ 169s] Please use /var/adm/fillup-templates/sysconfig.<pkgname> [ 169s] and call %fillup_and_insserv for new sysconfig files.
https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#. 25fillup_and_insserv
I tried the method, take corosync-qdevice as an example: %post -n corosync-qdevice %{fillup_and_insserv corosync-qdevice} It fails to fillup if file "/etc/sysconfig/corosync-qdevice" does not exist. And when I use touch to create an empty file "/etc/sysconfig/corosync-qdevice", fillup operation can success. I think there is something wrong with either %fillup_and_insserv or fillup binary. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1004977 Bin Liu <bliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Security |Basesystem Assignee|security-team@suse.de |bnc-team-screening@forge.pr | |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1004977 http://bugzilla.suse.com/show_bug.cgi?id=1004977#c3 Bin Liu <bliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #3 from Bin Liu <bliu@suse.com> --- reopen this bug to let bug owner know the issue, please feel free to close if this is not a bug. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1004977 http://bugzilla.suse.com/show_bug.cgi?id=1004977#c4 Bin Liu <bliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Bin Liu <bliu@suse.com> --- close the bug as invalid as this because the file name has "-", without "-n", it will fetch the part before "-". -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com