October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1230673] perl: y2038: 32-bit builds use 4-byte time_t
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230673 https://bugzilla.suse.com/show_bug.cgi?id=1230673#c9 --- Comment #9 from Michael Schröder <mls(a)suse.com> --- Hey, what's with the 0002-Remove-CPAN-rpaths.patch patch? It seems like with this patch, the shared objects are not linked against the pcp lib and thus no library dependency is recorded. Meaning, trying to use the perl Modules will return with undefined symbol errors as the library is not loaded by the linker. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231244] Installing udev in a chroot or non booted container is not creating the system users it provides
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231244 https://bugzilla.suse.com/show_bug.cgi?id=1231244#c3 --- Comment #3 from Franck Bui <fbui(a)suse.com> --- I don't think you clearly answer to my previous question so let me ask again: did you face any concrete issues with delaying the creation of sytemd-timesync system user or not ? Again the final initialization of a stateless system is supposed to happen on the first boot process. So I'd like to understand why this couldn't be achieved or whether it's currently "only" some inconsistencies you're seeing between some systemd-user-* packages and systemd/udev. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231338] New: [Build 40.1] ppc64le fails to boot
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231338 Bug ID: 1231338 Summary: [Build 40.1] ppc64le fails to boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: Other URL: https://openqa.opensuse.org/tests/4539694/modules/agam a/steps/2 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Leap 16.0 fails to boot on ppc64le. I suppose this will be lack of boot options, as I've seen working agama installation on https://openqa.opensuse.org/group_overview/116 openQA test in scenario opensuse-16.0-agama-installer-Leap-ppc64le-gnome-agama@ppc64le fails in [agama](https://openqa.opensuse.org/tests/4539694/modules/agama/steps/2) ## Test suite description Agama based GNOME installation for Leap 16, lkocman 20240730 ## Reproducible Fails since (at least) Build [36.53](https://openqa.opensuse.org/tests/4493796) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1230262] GCC14 internal compiler error: Segmentation fault during LTO
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230262 https://bugzilla.suse.com/show_bug.cgi?id=1230262#c8 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rguenther(a)suse.co | |m) Status|NEW |IN_PROGRESS --- Comment #8 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Andreas Färber from comment #7) > (In reply to Guillaume GARDET from comment #6) > > (In reply to Andreas Färber from comment #5) > > > Should we in the meantime switch to either gcc13 or non-LTO builds? > > > > Not all builds fail, so I would stick to gcc14 and LTO builds for Tumbleweed > > in general. > > If some packages are key packages, we can disable LTO until this bug is > > fixed. > > I was thinking of openvino in particular; not sure where libaom is used. > It already took a month for the upstream GCC bug to get assigned, so leaving > it failing in Factory does not strike me as a good strategy, given that > there is an upstream reproducer. Patch is on list already: https://gcc.gnu.org/pipermail/gcc-patches/2024-October/664319.html So, if @Richard Biener agrees, we could add this patch on our gcc14 package? Otherwise, I will disable LTO for openvino and also for libaom because of the number of packages depending on it: osc whatdependson openSUSE:Factory:ARM libaom standard aarch64 |wc -l returns 506! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231058] podofo package contains no actual binaries?
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231058 https://bugzilla.suse.com/show_bug.cgi?id=1231058#c3 --- Comment #3 from Marcus Rückert <mrueckert(a)suse.com> --- then dont ship the podofo main rpm then? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231065] I think we can learn the way Fedora packages Chromium.
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231065 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |ro(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231289] libbullet may be built both with double precision and without
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231289 https://bugzilla.suse.com/show_bug.cgi?id=1231289#c5 --- Comment #5 from Dirk Stoecker <opensuse(a)dstoecker.de> --- Is there really a reason to provide a single precision version of the library nowadays? There may be individual uses (which can fork the package or build manual), but as a package I don't see a need for that. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230262] GCC14 internal compiler error: Segmentation fault during LTO
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230262 https://bugzilla.suse.com/show_bug.cgi?id=1230262#c6 --- Comment #6 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Andreas Färber from comment #5) > Should we in the meantime switch to either gcc13 or non-LTO builds? Not all builds fail, so I would stick to gcc14 and LTO builds for Tumbleweed in general. If some packages are key packages, we can disable LTO until this bug is fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231319] New: [Build 20241004] jing: JAVA_HOME not set
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231319 Bug ID: 1231319 Summary: [Build 20241004] jing: JAVA_HOME not set Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other URL: https://openqa.opensuse.org/tests/4535542/modules/yast 2_clone_system/steps/22 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: java-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation /usr/bin/jing: JAVA_HOME is not set and default java installation was not found. JAVA_HOME for system applications can be set in java.conf in /etc/java j3GQc-1- openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-clone_system@64bit fails in [yast2_clone_system](https://openqa.opensuse.org/tests/4535542/modules/yast2… ## Test suite description Maintainer: QE Yast Clone the system into an autoyast profile to be used by downstream jobs, e.g. to test reinstall from that profile. ## Reproducible Fails since (at least) Build [20241004](https://openqa.opensuse.org/tests/4534583) ## Expected result Last good: [20241003](https://openqa.opensuse.org/tests/4532972) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1230577] tailscale + selinux: MagicDNS mislabels /etc/resolv.conf leading to NetworkManager unlink access errors
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230577 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(suse+accounts@fin | |nes.dev) CC| |suse+accounts(a)finnes.dev -- You are receiving this mail because: You are on the CC list for the bug.

1 0