January 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1178080] systemd-resolved linked against gnutls
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1178080 https://bugzilla.suse.com/show_bug.cgi?id=1178080#c1 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |fbui(a)suse.com --- Comment #1 from Franck Bui <fbui(a)suse.com> --- (In reply to Ludwig Nussel from comment #0) > Would it be possible to build systemd-resolved with openssl instead? That should be possible since https://github.com/systemd/systemd/pull/9734. However I'm not sure it would be a good idea since: - gnutls supports "TLS False Start" whereas openssl doesn't - gnutls backend is the default and used by all major distros That would leave TW the only distro using openssl here hence hitting tricky/security bugs that no other distro has faced before... So I'm wondering whether it is really worth avoiding to pull libgnutls in in a minimal system... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179423] ArmNN is not installable (and is unresolvable in OBS)
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179423 https://bugzilla.suse.com/show_bug.cgi?id=1179423#c4 --- Comment #4 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Egbert Eich from comment #3) > @Guillaume: any reason to not make this a duplicate of boo#1178287? Same root cause, but the same problem. > > Also, please remove the tag from the openQA test! These constant 'reminders' > are annoying! No, I will keep the tag in openQA as it ignores automatically the failure. Which annoying "reminders"? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180070] Make bootloader automatically pass encryption key to kernel during boot
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180070 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180493] MultiOS Flatpak Installation
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180493 https://bugzilla.suse.com/show_bug.cgi?id=1180493#c4 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka(a)suse.com Whiteboard| |Internal hint: | |JSC#SLE-16650 --- Comment #4 from Lukas Ocilka <locilka(a)suse.com> --- The idea of keeping just one instance of Flatpak apps is interesting, especially as they use quite some space. The (not only) only problem is, that there is no Flatpak-specific partition on the system at all. At least not in openSUSE. Flatpak apps are deployed into /var/lib/flatpak directory. By default, openSUSE uses btrfs for most of the system parts and /var or /var/lib might be subvolumes. Such setup does not seem to be compatible with other distributions or even with other versions/instance of openSUSE when used within the same computer. What you are (?) asking for seems to be a new partition or LVM volume with some kind of identifier $THIS_IS_FLATPAK_DIR - and this would be obviously working only for system apps. In contrast to user-specific apps that are installed into user's home. This could be possibly addressed by extending the concept of discoverable partitions https://systemd.io/DISCOVERABLE_PARTITIONS/ -- which is not (yet) supported by [open]SUSE as it seems to bring more problems than benefits. Keep in mind, that partition created just for Flatpak would occupy space that could be used for something else. The problem seems to be smaller when using LVM and space can be easily extended (more or less). Anyway, it's hard to predict how big the partition should be. Slawek, maybe I understood it in a different way, so could you PLS elaborate a bit more about your ideas or expectations? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179522] netcdf from opensuse repo linked to different version of hdf5 header
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179522 https://bugzilla.suse.com/show_bug.cgi?id=1179522#c1 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Egbert Eich <eich(a)suse.com> --- This has been fixed with: Wed Dec 9 08:29:38 UTC 2020 - Egbert Eich <eich(a)suse.com> ------------------------------------------------------------------- - Change 'Requires:' to hdf5 to %requires_eq to match the exact version of hdf5 in the dependency. This should take care of HPC packages ignoring proper ABI versioning (boo#1179521). already. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180491] "Panic on CPU 0: IO-APIC + timer doesn't work!"
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180491 https://bugzilla.suse.com/show_bug.cgi?id=1180491#c1 Jan Beulich <jbeulich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Jan Beulich <jbeulich(a)suse.com> --- See https://lists.xen.org/archives/html/xen-devel/2020-12/msg01793.html for the most recent upstream report of this. As per the reply there, a fix is in the works. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179423] ArmNN is not installable (and is unresolvable in OBS)
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179423 https://bugzilla.suse.com/show_bug.cgi?id=1179423#c3 --- Comment #3 from Egbert Eich <eich(a)suse.com> --- @Guillaume: any reason to not make this a duplicate of boo#1178287? Also, please remove the tag from the openQA test! These constant 'reminders' are annoying! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180437] VBoxAdditions.iso is missing in VirtualBox 6.1
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180437 https://bugzilla.suse.com/show_bug.cgi?id=1180437#c1 Larry Finger <Larry.Finger(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Larry Finger <Larry.Finger(a)gmail.com> --- VboxAdditions.iso and the appropriate .extpak files have never been, nor will they ever be, part of the openSUSE distributions. They are licensed with the PUEL licence; however, the "open" part of openSUSE demands a GPLv2 or MIT licence. You need to download those files from Oracle. For the .iso, the GUI will offer you the option of downloading the file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179816] zypper(8) man page document non existing option -y
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179816 https://bugzilla.suse.com/show_bug.cgi?id=1179816#c1 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Michael Andres <ma(a)suse.com> --- > zypper [--global-opts] command [--command-opts] [command-arguments] As a global-option zypper accepts "-n, --non-interactive" together with any command (recommended): zypper -n COMMAND ... Only some commands accept a (legacy) "-y, --no-confirm" as command-option (passed after the command name): zypper in -y ... It seems to work as expected, but I rephrased the man page tying to point out the difference more clearly: -y, --no-confirm Don��t require user interaction. It��s recommended to use the --non-interactive global option instead. Global options are passed before the command (zypper --non-interactive COMMAND ...). Unlike the no-confirm command option, the global option can be used together with any zypper command. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180491] "Panic on CPU 0: IO-APIC + timer doesn't work!"
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180491 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|xen-bugs(a)suse.de |jbeulich(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0