June 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 757318] OCICLI - duplicating repos
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=757318 http://bugzilla.suse.com/show_bug.cgi?id=757318#c6 --- Comment #6 from Stefan Hundhammer <shundhammer(a)suse.com> --- (In reply to Nathan Cutler from comment #5) > (In reply to Stefan Hundhammer from comment #4) > > Since nothing whatsoever happened here within 7 years, I wouldn't get my > > hopes too high. > > The bug was originally opened against a stable openSUSE release, so once > that release went out of maintenance the bug was never looked at again. Now > that it's against Tumbleweed, the bug stays on the radar. All those years of inactivity speak against that theory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137056] Automatically add a custom generated key to initrd when installing to LVM/LUKS
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1137056 http://bugzilla.suse.com/show_bug.cgi?id=1137056#c4 --- Comment #4 from Steffen Winterfeldt <snwint(a)suse.com> --- I confess I use a setup similar to the proposed myself. The usability of the current default setup is less than optimal, to put it mildly. And that's not even counting the grub behavior on entering a wrong password. If there's any intention to encourage people to use encryption this seems counterproductive to me. I haven't seen any convincing argument as to why storing the password in an encrypted initrd is a security risk. As Arvin pointed out root can access the LUKS decryption keys anyway. And unless you have special crypto hardware that's by design. We've had fate#320901 open for the better part of 3 years without anything coming of it. Which is really a sad state. If anything we should at least give the user the *choice* to go for a user-friendly setup like the proposed. That the initrd gets inadvertently copied to a nonencrypted partition is indeed a risk and we should help the admin to prevent this, if possible. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1115997] New: Please convert SysV init scripts shipped by xrootd-server into native systemd services.
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1115997 Bug ID: 1115997 Summary: Please convert SysV init scripts shipped by xrootd-server into native systemd services. 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1116052] New: Please convert SysV init scripts by wondershaper into native systemd services
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1116052 Bug ID: 1116052 Summary: Please convert SysV init scripts by wondershaper into native systemd services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1116039] New: Please convert SysV init scripts by Supybot into native systemd services
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1116039 Bug ID: 1116039 Summary: Please convert SysV init scripts by Supybot into native systemd services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1116038] New: Please convert SysV init scripts by smbtad into native systemd services
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1116038 Bug ID: 1116038 Summary: Please convert SysV init scripts by smbtad into native systemd services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: fbui(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1116036] New: Please convert SysV init scripts by scsirastools into native systemd services
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1116036 Bug ID: 1116036 Summary: Please convert SysV init scripts by scsirastools into native systemd services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1116032] New: Please convert SysV init scripts by pen into native systemd services
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1116032 Bug ID: 1116032 Summary: Please convert SysV init scripts by pen into native systemd services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1116030] New: Please convert SysV init scripts by pdnsd into native systemd services
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1116030 Bug ID: 1116030 Summary: Please convert SysV init scripts by pdnsd into native systemd services Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1116025] New: Please convert SysV init scripts by nxtvepg into native systemd services
by bugzilla_noreply＠novell.com 03 Jun '19

03 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1116025 Bug ID: 1116025 Summary: Please convert SysV init scripts by nxtvepg into native systemd services 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 3