December 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1192429] Consider bringing newer LLVM to Leap 15.3
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1192429 https://bugzilla.suse.com/show_bug.cgi?id=1192429#c14 Michael Matz <matz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(matz(a)suse.com) | --- Comment #14 from Michael Matz <matz(a)suse.com> --- (In reply to Richard Biener from comment #13) > (In reply to Marcus Meissner from comment #12) > > would need a request via jira ... PM ticket. We can at most move it to > > legacy with 15-sp4 and announce we drop it later. But someone needs to open > > a PM ticket and convince PM. > > OK, Micha - can you ping whoever is appropriate to do this? I have now, but I want to note that deprecation of llvm7 in SLE is orthogonal to the eventual removal of the unversioned llvm package from SLE (to be replaced by one in Backports/Leap that tracks the "current" llvm version). Nevertheless I've asked Rado to create such ticket. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193276] yast2-services-manager: applying changes loses selection
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193276 https://bugzilla.suse.com/show_bug.cgi?id=1193276#c5 --- Comment #5 from Stefan Hundhammer <shundhammer(a)suse.com> --- Moving to our task queue for a future sprint. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193276] yast2-services-manager: applying changes loses selection
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193276 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED URL| |https://trello.com/c/K10dt3 | |MT Assignee|yast2-maintainers(a)suse.de |yast-internal(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193276] yast2-services-manager: applying changes loses selection
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193276 https://bugzilla.suse.com/show_bug.cgi?id=1193276#c4 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Service Manager: applying |yast2-services-manager: |loses selection |applying changes loses | |selection Flags|needinfo?(giecrilj(a)stegny.2 | |a.pl) | Severity|Normal |Minor --- Comment #4 from Stefan Hundhammer <shundhammer(a)suse.com> --- With a lot of guesswork I tried to reproduce this, and here is what I observed: After applying a change to the currently selected service, the table content is reloaded. The previously selected table item is no longer selected; it is now a different one, probably the (case-insenstive) alphabetically first one, "accounts-daemon". But that's not the first visible item in that table; that would be "Modem-Manager" which is the case-sensitive alphabetically first one. I am not sure how useful it would be to select the previously selected one again; we'll have to discuss that internally. But at the very least the behavior is inconsistent (case-sensitive vs. case-insensitive first item). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193284] New: Support should send txz files
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193284 Bug ID: 1193284 Summary: Support should send txz files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: giecrilj(a)stegny.2a.pl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- DESCRIPTION: Support creates txz files but sends only tgz or tbz files. REPRO: 1. Tell Support to send file /tmp/YaST2-14343-4xUbDd/scc_localhost.localdomain_211201_1319.txz! EXPECTED: Support should allow you to select the file. ACTUAL: The file is filtered out. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1193272] New: devel:libraries:c_c++/libffi causes fallout in Staging:A
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193272 Bug ID: 1193272 Summary: devel:libraries:c_c++/libffi causes fallout in Staging:A Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The libffi update causes build FAILs of gjs python-atspi:test python-dbus-python python-matplotlib:test python-python-dbusmock (and some more that look unrelated) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1193276] Service Manager: applying loses selection
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193276 https://bugzilla.suse.com/show_bug.cgi?id=1193276#c3 --- Comment #3 from Stefan Hundhammer <shundhammer(a)suse.com> --- Just repeating the first comment is not helpful at all. We already knew that. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193017] PAM authentication fails in OpenVPN
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193017 https://bugzilla.suse.com/show_bug.cgi?id=1193017#c7 --- Comment #7 from Matthias Adler <matthias.adler(a)cronic.de> --- Thank you very much for the explanation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192429] Consider bringing newer LLVM to Leap 15.3
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1192429 https://bugzilla.suse.com/show_bug.cgi?id=1192429#c13 Richard Biener <rguenther(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz(a)suse.com Flags| |needinfo?(matz(a)suse.com) --- Comment #13 from Richard Biener <rguenther(a)suse.com> --- (In reply to Marcus Meissner from comment #12) > would need a request via jira ... PM ticket. We can at most move it to > legacy with 15-sp4 and announce we drop it later. But someone needs to open > a PM ticket and convince PM. OK, Micha - can you ping whoever is appropriate to do this? > > For newer llvmxx in packagehub, we can build it internally in IBS (and ship > to packagehub) or externally in backports, depending on what is better. I think externally in backports works for me, if populating packagehub requires internal build in IBS then SLE customers might prefer that (guess we don't want it in both places - not sure about the interaction between SLE and Leap here). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192429] Consider bringing newer LLVM to Leap 15.3
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1192429 https://bugzilla.suse.com/show_bug.cgi?id=1192429#c12 --- Comment #12 from Marcus Meissner <meissner(a)suse.com> --- would need a request via jira ... PM ticket. We can at most move it to legacy with 15-sp4 and announce we drop it later. But someone needs to open a PM ticket and convince PM. For newer llvmxx in packagehub, we can build it internally in IBS (and ship to packagehub) or externally in backports, depending on what is better. -- You are receiving this mail because: You are on the CC list for the bug.

1 0