September 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1194717] windows:mingw:win{32|64}:mingwxx-atkmm: Could not specify different version of a development dependency
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1194717 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fstrba(a)suse.com |ralf.habacker(a)freenet.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201119] windows:mingw:win{32|64}: obsolete build references in c++ based packages
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1201119 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fstrba(a)suse.com |ralf.habacker(a)freenet.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230114] New: non-oss source repo is not published for aarch64
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1230114 Bug ID: 1230114 Summary: non-oss source repo is not published for aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: tamara.zoe.schmitz(a)posteo.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For some reason there is no non-oss-source repo for aarch64 despite some packages such as nmap being built from a source code. And so, openSUSE-repos-Tumbleweed adds repo-non-oss-source with http://cdn.opensuse.org/ports/aarch64/source/tumbleweed/repo/non-oss which leads to a 404 and an error when activated. Could publishing for this repo be enabled in OBS, please? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1201112] WiFi not available on pinebook pro
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1201112 https://bugzilla.suse.com/show_bug.cgi?id=1201112#c13 --- Comment #13 from Jiri Slaby <jslaby(a)suse.com> --- Brought upstream: https://lore.kernel.org/all/9b5a5238-0e08-41e5-9cc0-346b446e0562@kernel.org/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201112] WiFi not available on pinebook pro
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1201112 https://bugzilla.suse.com/show_bug.cgi?id=1201112#c12 --- Comment #12 from Jiri Slaby <jslaby(a)suse.com> --- FTR, it seems that kernel-firmware-brcm's license: /usr/share/licenses/kernel-firmware-brcm/LICENCE.broadcom_bcm43xx (which we distribute) is the same as for brcmfmac43456-sdio.pine64,pinebook-pro.bin: https://github.com/bsdkurt/brcm-supplemental/blob/master/LICENSE in https://github.com/bsdkurt/brcm-supplemental -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1214004] Rebuilding MD-RAID brings system almost to a halt
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1214004 https://bugzilla.suse.com/show_bug.cgi?id=1214004#c5 --- Comment #5 from Coly Li <colyli(a)suse.com> --- (In reply to Ulrich Windl from comment #4) > (In reply to Hannes Reinecke from comment #3) > > According to the BIOS message on booting the RAID was is "verify mode", so > nothing actually needed writing or fixing unless there was a mismatch > detected. > However I don't know how MD-RAID actually handles that. > > What could be done? > > If it's possible to detect that kind of problem (read stalls obviously), the > default speed_limit_max could be reduced automatically until the situation > improves. Obviously such mechanism should be "located near MD-RAID > activation". > > Being practically unable to work with the system for hours cannot be the > solution (I'm aware that a "change bitmap" on the array would be the best > solution, but the hardware doesn't support that AFAIK) Recently it was reported that an upstream issue had similar behavior as you described. This issue was fixed in recent openSUSE Leap 15.6 kernel (leap 15.5 is on the way). Note: the fix comes after openSUSE Leap 15.6 released, please download the latest installation iso. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216121] New: rust1.7{1,2,3} fail to build with newest binutils
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1216121 Bug ID: 1216121 Summary: rust1.7{1,2,3} fail to build with newest binutils Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Keywords: build Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: burnus(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: william.brown(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I have no idea why rust1.7{1,2,3} fails, I just note that with the new binutils https://build.opensuse.org/request/show/1113885 as shown below. The current error message does not point to anything obvious with regards to binutils - but looks more like a generic Rust build issue. But it as it does compile on opensuse:Factory, it must have something to do with binutils. The fails is: [ 191s] Finished release [optimized] target(s) in 1m 54s [ 192s] Building LLD for x86_64-unknown-linux-gnu ... [ 192s] CMake Deprecation Warning at /home/abuild/rpmbuild/BUILD/rustc-1.73.0-src/src/llvm-project/cmake/Modules/CMakePolicy.cmake:6 (cmake_policy): [ 192s] The OLD behavior for policy CMP0114 will be removed from a future version [ 192s] of CMake. [ 192s] [ 192s] The cmake-policies(7) manual explains that the OLD behaviors of all [ 192s] policies are deprecated and that a policy should be set to OLD only under [ 192s] specific short-term circumstances. Projects should be ported to the NEW [ 192s] behavior and not rely on setting a policy to OLD. [ 192s] Call Stack (most recent call first): [ 192s] CMakeLists.txt:6 (include) [ 192s] [ 192s] [ 192s] -- The C compiler identification is GNU 13.2.1 [ 192s] -- The CXX compiler identification is GNU 13.2.1 [ 192s] -- Detecting C compiler ABI info [ 192s] -- Detecting C compiler ABI info - done ... [ 194s] -- Configuring done (2.2s) [ 194s] CMake Error at /usr/lib64/cmake/llvm/AddLLVM.cmake:714 (target_link_libraries): [ 194s] Target "lldELF" links to: [ 194s] [ 194s] zstd::libzstd_static [ 194s] [ 194s] but the target was not found. Possible reasons include: [ 194s] [ 194s] * There is a typo in the target name. [ 194s] * A find_package call is missing for an IMPORTED target. [ 194s] * An ALIAS target is missing. [ 194s] [ 194s] Call Stack (most recent call first): [ 194s] cmake/modules/AddLLD.cmake:13 (llvm_add_library) [ 194s] ELF/CMakeLists.txt:21 (add_lld_library) [ 194s] [ 194s] [ 194s] -- Generating done (0.0s) [ 194s] CMake Warning: [ 194s] Manually-specified variables were not used by the project: [ 194s] [ 194s] CMAKE_ASM_COMPILER [ 194s] [ 194s] [ 194s] CMake Generate step failed. Build files cannot be regenerated correctly. [ 194s] thread 'main' panicked at /home/abuild/rpmbuild/BUILD/rustc-1.73.0-src/vendor/cmake/src/lib.rs:975:5: [ 194s] [ 194s] command did not execute successfully, got: exit status: 1 [ 194s] [ 194s] build script failed, must exit now [ 194s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 194s] finished in 2.256 seconds [ 194s] Build completed unsuccessfully in 0:02:30 [ 194s] error: Bad exit status from /var/tmp/rpm-tmp.YhjGx1 (%build) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1229338] ffmpeg fails to build on 32bit arm
by bugzilla_noreply＠suse.com 04 Sep '24

04 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1229338 https://bugzilla.suse.com/show_bug.cgi?id=1229338#c6 --- Comment #6 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1229338) was mentioned in https://build.opensuse.org/request/show/1198597 Factory / ffmpeg-5 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1229997] mdadm monitoring broken in Leap 15.6 (list and scan cannot be combined)
by bugzilla_noreply＠suse.com 03 Sep '24

03 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1229997 https://bugzilla.suse.com/show_bug.cgi?id=1229997#c2 Neil Brown <nfbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #2 from Neil Brown <nfbrown(a)suse.com> --- I think the problem is that your /etc/sysconfig/mdadm has both "MDADM_RAIDDEVICES" set and also "MDADM_SCAN=yes". I don't think those two make sense together. This used to work prior to mdadm-4.3 but when we updated past that version the inconsistent setting are now reported as an error. We should probably improve the documentation in /etc/sysconfig/mdadm or maybe automatically resolve the inconsistency in /usr/libexec/mdadm/mdadm_env.sh -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219882] New: Adapt package dd_rescue to build with OpenSSL 3
by bugzilla_noreply＠suse.com 03 Sep '24

03 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1219882 Bug ID: 1219882 Summary: Adapt package dd_rescue to build with OpenSSL 3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: otto.hollmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Package dd_rescue requires openssl 1.1.1 that is EOL and we would like to remove it from Factory. > # Workaround for bsc#1193438 > BuildRequires: libopenssl-1_1-devel Please check tracker bug 1219879 for more details. -- You are receiving this mail because: You are on the CC list for the bug.

1 7