October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1232517] FTBFS: kicad
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232517 https://bugzilla.suse.com/show_bug.cgi?id=1232517#c7 --- Comment #7 from Boehmer <joergboe44(a)googlemail.com> --- Apparently a test failed and the repository was brought into an inconsistent state. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231795] python3-config contains some garbage flags
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231795 https://bugzilla.suse.com/show_bug.cgi?id=1231795#c1 Daniel Garcia <daniel.garcia(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.garcia(a)suse.com --- Comment #1 from Daniel Garcia <daniel.garcia(a)suse.com> --- I can think about a simple solution to just remove the -IVendor from the final python3-config after install like: sed -i 's/-IVendor\///' %{buildroot}%{_bindir}/python%{python_abi}-config And related to this, checking the result of "python3-config --cflags", I can also see duplicated options there, we've right now: export OPT="%{optflags} -DOPENSSL_LOAD_CONF -fwrapv $(pkg-config --cflags-only-I libffi) -fno-semantic-interposition" export CFLAGS="%{optflags} -IVendor/" I'm not sure about how the %configure macro expands, but maybe it's not needed to have "%{optflags}". In any case, the duplicate options shouldn't be a problem, so we just need need to remove the "-IVendor/". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232517] FTBFS: kicad
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232517 https://bugzilla.suse.com/show_bug.cgi?id=1232517#c6 --- Comment #6 from Stefan Brüns <stefan.bruens(a)rwth-aachen.de> --- When the update was submitted, all components built sucessfully. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232517] FTBFS: kicad
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232517 https://bugzilla.suse.com/show_bug.cgi?id=1232517#c5 --- Comment #5 from Boehmer <joergboe44(a)googlemail.com> --- Ultimately, when delivering the package, the delivery team/tool must decide whether all required packages are error-free. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232230] nodejs22: fails to build with openssl 3.1.7
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232230 https://bugzilla.suse.com/show_bug.cgi?id=1232230#c1 Adam Majer <amajer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Adam Majer <amajer(a)suse.com> --- fix submitted to factory as part of nodejs22 version update to 22.10.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231323] core dump (Segmentation fault) when ending repository management
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231323 https://bugzilla.suse.com/show_bug.cgi?id=1231323#c34 --- Comment #34 from Stefan Hundhammer <shundhammer(a)suse.com> --- When I simply don't delete the PkgModule singleton with the YRepo vector and its MediaSetAccess objects and just let it all leak, I still get a segfault: >> yast2 repositories >> /sbin/yast2: line 468: 11482 Segmentation fault (core dumped) >> $ybindir/y2start $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS >> tail -n 8 y2log >> >> 2024-10-29 [Interpreter] bin/y2start:68 Called YaST client returned. >> 2024-10-29 [qt-ui] YQUI.cc(uiThreadDestructor):320 Destroying UI thread >> 2024-10-29 [qt-ui] YQUI.cc(~YQUI):302 Closing down Qt UI. >> 2024-10-29 [Pkg] YRepo.cc(~YRepo):68 Deleting YRepo #1 for <default CTOR> >> 2024-10-29 [Pkg] YRepo.cc(~YRepo):86 DONE ~YRepo #1 for <default CTOR> >> 2024-10-29 [Pkg] PkgModule.cc(unregisterZyppLogger):119 Closing down ZYPP logger >> 2024-10-29 [Pkg] PkgModule.cc(unregisterZyppLogger):124 ZYPP logger closed down. >> 2024-10-29 [Pkg] PkgModule.cc(destroy):96 NOT deleting PkgModule object... >> cd /var/lib/systemd/coredump >> gdb /usr/bin/ruby.ruby3.3 core.Zypp-main.0.63f5cc4... >> >> (gdb) bt >> #0 0x00007fda70056078 in ??? () at /lib64/libruby3.3.so.3.3 >> #1 0x00007fda7005633f in ??? () at /lib64/libruby3.3.so.3.3 >> #2 0x00007fda70056379 in ??? () at /lib64/libruby3.3.so.3.3 >> #3 0x00007fda6febf21d in ??? () at /lib64/libruby3.3.so.3.3 >> #4 0x00007fda6ffd347d in ??? () at /lib64/libruby3.3.so.3.3 >> #5 0x00007fda6fa41580 in <signal handler called> () at /lib64/libc.so.6 >> #6 0x00007fda6fa9ea76 in pthread_rwlock_wrlock(a)GLIBC_2.2.5 () at /lib64/libc.so.6 >> #7 0x00007fda43c19399 in CRYPTO_THREAD_write_lock () at /lib64/libcrypto.so.3 >> #8 0x00007fda43c470f3 in RAND_get_rand_method () at /lib64/libcrypto.so.3 >> #9 0x00007fda43c48536 in RAND_status () at /lib64/libcrypto.so.3 >> #10 0x00007fda4a17d7dc in rand_enough () at vtls/openssl.c:1018 >> #11 ossl_seed (data=0x563b954e0940) at vtls/openssl.c:1027 >> #12 ossl_random (data=0x563b954e0940, entropy=0x7ffe8e9ff6e0 ":17", length=4) at vtls/openssl.c:5278 >> #13 0x00007fda4a1182fd in Curl_ssl_random (length=4, data=<optimized out>, entropy=0x7ffe8e9ff6e0 ":17") at vtls/vtls.c:932 >> #14 randit (data=<optimized out>, rnd=0x7ffe8e9ff6e0, env_override=true) at /usr/src/debug/curl-8.10.1/lib/rand.c:187 >> #15 Curl_rand_alnum (data=0x563b954e0940, rnd=0x7ffe8e9ff790 "p\370\237\216\376\177", num=<optimized out>) at /usr/src/debug/curl-8.10.1/lib/rand.c:293 >> #16 Curl_fopen (data=0x563b954e0940, filename=0x563b90167420 "/var/lib/YaST2/cookies", fh=0x7ffe8e9ff838, tempname=0x7ffe8e9ff840) at /usr/src/debug/curl-8.10.1/lib/fopen.c:114 >> #17 0x00007fda4a114f4f in cookie_output (data=0x563b954e0940, c=0x563b954dfea0, filename=<optimized out>) at /usr/src/debug/curl-8.10.1/lib/cookie.c:1640 >> #18 Curl_flush_cookies (data=0x563b954e0940, cleanup=true) at /usr/src/debug/curl-8.10.1/lib/cookie.c:1761 >> #19 0x00007fda4a18ca5e in Curl_close.isra.0 (datap=datap@entry=0x7ffe8e9ff9c8) at /usr/src/debug/curl-8.10.1/lib/url.c:279 >> #20 0x00007fda4a116934 in curl_easy_cleanup (data=<optimized out>) at /usr/src/debug/curl-8.10.1/lib/easy.c:838 >> #21 0x00007fda48397b31 in zypp::media::MediaCurl::disconnectFrom (this=0x563b955350d0) at /usr/src/debug/libzypp-17.35.12/zypp/media/MediaCurl.cc:725 >> #22 0x00007fda48378fcf in zypp::media::MediaHandler::disconnect (this=0x563b955350d0) at /usr/src/debug/libzypp-17.35.12/zypp/media/MediaHandler.cc:692 >> #23 0x00007fda4837c420 in zypp::media::MediaHandler::release (this=0x563b955350d0, ejectDev="") at /usr/src/debug/libzypp-17.35.12/zypp/media/MediaHandler.cc:723 >> #24 0x00007fda483a7b1f in zypp::media::(anonymous namespace)::ManagedMedia::close (this=0x563b95541618) at /usr/src/debug/libzypp-17.35.12/zypp/media/MediaManager.cc:108 >> #25 0x00007fda483a7cb0 in zypp::media::(anonymous namespace)::ManagedMedia::~ManagedMedia (this=0x563b95541618, this=<optimized out>) >> at /usr/src/debug/libzypp-17.35.12/zypp/media/MediaManager.cc:52 >> #26 0x00007fda483b05c2 in std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia>::~pair (this=0x563b95541610, this=<optimized out>) >> at /usr/include/c++/14/bits/stl_pair.h:284 >> #27 std::__new_allocator<std::_Rb_tree_node<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> > >::destroy<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> > (this=0x563b90e83058, __p=0x563b95541610) at /usr/include/c++/14/bits/new_allocator.h:198 >> #28 std::allocator_traits<std::allocator<std::_Rb_tree_node<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> > > >::destroy<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> > (__a=..., __p=0x563b95541610) at /usr/include/c++/14/bits/alloc_traits.h:591 >> #29 std::_Rb_tree<unsigned int, std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia>, std::_Select1st<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> >, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> > >::_M_destroy_node >> (this=0x563b90e83058, __p=0x563b955415f0) at /usr/include/c++/14/bits/stl_tree.h:621 >> #30 std::_Rb_tree<unsigned int, std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia>, std::_Select1st<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> >, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> > >::_M_drop_node >> (this=0x563b90e83058, __p=0x563b955415f0) at /usr/include/c++/14/bits/stl_tree.h:629 >> #31 std::_Rb_tree<unsigned int, std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia>, std::_Select1st<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> >, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> > >::_M_erase (this=0x563b90e83058, __x=0x563b955415f0) >> at /usr/include/c++/14/bits/stl_tree.h:1934 >> #32 std::_Rb_tree<unsigned int, std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia>, std::_Select1st<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> >, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> > >::clear (this=0x563b90e83058) >> at /usr/include/c++/14/bits/stl_tree.h:1251 >> #33 std::map<unsigned int, zypp::media::(anonymous namespace)::ManagedMedia, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, zypp::media::(anonymous namespace)::ManagedMedia> > >::clear (this=0x563b90e83058) at /usr/include/c++/14/bits/stl_map.h:1183 >> #34 zypp::media::MediaManager_Impl::~MediaManager_Impl (this=<optimized out>, this=<optimized out>) at /usr/src/debug/libzypp-17.35.12/zypp/media/MediaManager.cc:249 >> #35 boost::checked_delete<zypp::media::MediaManager_Impl> (x=<optimized out>) at /usr/include/boost/core/checked_delete.hpp:44 >> #36 boost::checked_delete<zypp::media::MediaManager_Impl> (x=0x563b90e83050) at /usr/include/boost/core/checked_delete.hpp:31 >> #37 boost::detail::sp_counted_impl_p<zypp::media::MediaManager_Impl>::dispose (this=<optimized out>) at /usr/include/boost/smart_ptr/detail/sp_counted_impl.hpp:89 >> #38 0x00007fda483b041a in boost::detail::sp_counted_base::release (this=0x563b90e85830) at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_atomic.hpp:120 >> #39 boost::detail::sp_counted_base::release (this=0x563b90e85830) at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_atomic.hpp:116 >> #40 boost::detail::shared_count::~shared_count (this=<optimized out>, this=<optimized out>) at /usr/include/boost/smart_ptr/detail/shared_count.hpp:432 >> #41 boost::shared_ptr<zypp::OnMediaLocation::Impl>::~shared_ptr (this=<optimized out>, this=<optimized out>) at /usr/include/boost/smart_ptr/shared_ptr.hpp:336 >> #42 0x00007fda6fa43f31 in __run_exit_handlers () at /lib64/libc.so.6 >> #43 0x00007fda6fa44000 in exit () at /lib64/libc.so.6 >> #44 0x00007fda6fa2a2b5 in __libc_start_call_main () at /lib64/libc.so.6 >> #45 0x00007fda6fa2a379 in __libc_start_main_impl () at /lib64/libc.so.6 >> #46 0x0000563b72d3f155 in _start () -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232517] FTBFS: kicad
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232517 https://bugzilla.suse.com/show_bug.cgi?id=1232517#c3 --- Comment #3 from Boehmer <joergboe44(a)googlemail.com> --- I think the delivery of a package should be prevented if a required package does not make it through the tool chain. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202053] Nokogiri was built against LibXML version 2.9.12, but has dynamically loaded 2.9.14
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1202053 https://bugzilla.suse.com/show_bug.cgi?id=1202053#c32 Steven Baker <steven.baker(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #32 from Steven Baker <steven.baker(a)suse.com> --- Duplicate. Fixed awaiting approval. *** This bug has been marked as a duplicate of bug 1228355 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228355] New: Package rubygem-nokogiri does not build with gcc 14 because of new errors (that were previously warnings)
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228355 Bug ID: 1228355 Summary: Package rubygem-nokogiri does not build with gcc 14 because of new errors (that were previously warnings) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mrueckert(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Package rubygem-nokogiri fails to build with GCC 14 because of various C99 violations which previously just generated warning s but which cause errors with GCC 14 by default. For more information see https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571. BuildService failures are available online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… The build with GCC 14 can now be tried locally with: osc build --clean --alternative-project home:rguenther:nextgcc The (first) error that stops the build is: [ 17s] html4_document.c: In function ‘rb_html_document_s_read_io’: [ 17s] html4_document.c:49:52: error: passing argument 2 of ‘xmlSetStructuredErrorFunc’ from incompatible pointer type [-Wincompatible-pointer-types] [ 17s] 49 | xmlSetStructuredErrorFunc((void *)rb_error_list, Nokogiri_error_array_pusher); [ 17s] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 17s] | | [ 17s] | void (*)(void *, xmlError *) {aka void (*)(void *, struct _xmlError *)} [ 17s] In file included from /usr/include/libxml/valid.h:15, [ 17s] from /usr/include/libxml/parser.h:19, [ 17s] from ./nokogiri.h:35, [ 17s] from html4_document.c:1: [ 17s] /usr/include/libxml/xmlerror.h:898:57: note: expected ‘xmlStructuredErrorFunc’ {aka ‘void (*)(void *, const struct _xmlError *)’} but argument is of type ‘void (*)(void *, xmlError *)’ {aka ‘void (*)(void *, struct _xmlError *)’} [ 17s] 898 | xmlStructuredErrorFunc handler); [ 17s] | ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~ [ 17s] html4_document.c: In function ‘rb_html_document_s_read_memory’: [ 17s] html4_document.c:109:52: error: passing argument 2 of ‘xmlSetStructuredErrorFunc’ from incompatible pointer type [-Wincompatible-pointer-types] [ 17s] 109 | xmlSetStructuredErrorFunc((void *)rb_error_list, Nokogiri_error_array_pusher); [ 17s] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 17s] | | [ 17s] | void (*)(void *, xmlError *) {aka void (*)(void *, struct _xmlError *)} [ 17s] /usr/include/libxml/xmlerror.h:898:57: note: expected ‘xmlStructuredErrorFunc’ {aka ‘void (*)(void *, const struct _xmlError *)’} but argument is of type ‘void (*)(void *, xmlError *)’ {aka ‘void (*)(void *, struct _xmlError *)’} [ 17s] 898 | xmlStructuredErrorFunc handler); [ 17s] | ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1231674] New: U-Boot 2024.10 broken on VisionFive2
by bugzilla_noreply＠suse.com 29 Oct '24

29 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231674 Bug ID: 1231674 Summary: U-Boot 2024.10 broken on VisionFive2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: mbrugger(a)suse.com Reporter: schwab(a)suse.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- 2024.10 fails to boot from flash on VisionFive2: U-Boot SPL 2024.10 (Oct 08 2024 - 07:10:55 +0000) DDR version: dc2e84f0. Trying to boot from SPI SPI probe failed. SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### This is broken by 0017-riscv-dts-jh7110-Update-qspi-node-w.patch. It also breaks SPI flashing in U-Boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 7