April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222933] New: python-gear fails to build on Leap 15.6 - ssl.SSLError: [SSL: EE_KEY_TOO_SMALL]
by bugzilla_noreply＠suse.com 06 May '24

06 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222933 Bug ID: 1222933 Summary: python-gear fails to build on Leap 15.6 - ssl.SSLError: [SSL: EE_KEY_TOO_SMALL] Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello package python-gear fails to build on Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… [ 145s] 2024-04-15 10:21:37,509 gear.Connection.b'client' DEBUG Using SSL [ 145s] 2024-04-15 10:21:37,510 gear.Worker.b'worker' ERROR Exception while connecting to <gear.Connection 0x7fe38112fa20 host: 127.0.0.1 port: 35231> [ 145s] Traceback (most recent call last): [ 145s] File "/home/abuild/rpmbuild/BUILD/gear-0.14.0/gear/__init__.py", line 782, in _connectLoop [ 145s] conn.reconnect() [ 145s] File "/home/abuild/rpmbuild/BUILD/gear-0.14.0/gear/__init__.py", line 252, in reconnect [ 145s] self.connect() [ 145s] File "/home/abuild/rpmbuild/BUILD/gear-0.14.0/gear/__init__.py", line 211, in connect [ 145s] context.load_cert_chain(self.ssl_cert, self.ssl_key) [ 145s] ssl.SSLError: [SSL: EE_KEY_TOO_SMALL] ee key too small (_ssl.c:3503) [ 145s] 2024-04-15 10:21:37,510 gear.Client.b'client' ERROR Exception while connecting to <gear.Connection 0x7fe38112f9e8 host: 127.0.0.1 port: 35231> [ 145s] Traceback (most recent call last): [ 145s] File "/home/abuild/rpmbuild/BUILD/gear-0.14.0/gear/__init__.py", line 782, in _connectLoop [ 145s] conn.reconnect() [ 145s] File "/home/abuild/rpmbuild/BUILD/gear-0.14.0/gear/__i Could you please have a look? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1221433] New: [python-jirafs] Missing dependency PIL
by bugzilla_noreply＠suse.com 06 May '24

06 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221433 Bug ID: 1221433 Summary: [python-jirafs] Missing dependency PIL Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- tumbleweed-pkg~$ jirafs --help Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/jirafs/cmdline.py", line 16, in <module> from jira.utils import JIRAError File "/usr/lib/python3.11/site-packages/jira/__init__.py", line 11, in <module> from jira.client import ( File "/usr/lib/python3.11/site-packages/jira/client.py", line 44, in <module> from PIL import Image ModuleNotFoundError: No module named 'PIL' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/jirafs", line 5, in <module> from jirafs.cmdline import main File "/usr/lib/python3.11/site-packages/jirafs/cmdline.py", line 18, in <module> from jira.exceptions import JIRAError File "/usr/lib/python3.11/site-packages/jira/__init__.py", line 11, in <module> from jira.client import ( File "/usr/lib/python3.11/site-packages/jira/client.py", line 44, in <module> from PIL import Image ModuleNotFoundError: No module named 'PIL' tumbleweed-pkg~$ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221017] New: GCC 14: python-ruamel.yaml.clib package fails
by bugzilla_noreply＠suse.com 06 May '24

06 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221017 Bug ID: 1221017 Summary: GCC 14: python-ruamel.yaml.clib package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building python-ruamel.yaml.clib with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): _ruamel_yaml.c: In function ‘__pyx_pf_6ruamel_4yaml_4clib_12_ruamel_yaml_7CParser___init__’: _ruamel_yaml.c:5929:52: error: passing argument 2 of ‘yaml_parser_set_input’ from incompatible pointer type [-Wincompatible-pointer-types] 5929 | yaml_parser_set_input((&__pyx_v_self->parser), __pyx_f_6ruamel_4yaml_4clib_12_ruamel_yaml_input_handler, ((void *)__pyx_v_self)); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | | int (*)(void *, char *, int, int *) In file included from _ruamel_yaml.h:2: yaml.h:1370:30: note: expected ‘int (*)(void *, unsigned char *, size_t, size_t *)’ {aka ‘int (*)(void *, unsigned char *, long unsigned int, long unsigned int *)’} but argument is of type ‘int (*)(void *, char *, int, int *)’ 1370 | yaml_read_handler_t *handler, void *data); | ~~~~~~~~~~~~~~~~~~~~~^~~~~~~ In file included from /usr/include/python3.9/bytesobject.h:75, from /usr/include/python3.9/Python.h:92, from _ruamel_yaml.c:16: _ruamel_yaml.c: In function ‘__pyx_pf_6ruamel_4yaml_4clib_12_ruamel_yaml_8CEmitter___init__’: _ruamel_yaml.c:16882:53: error: passing argument 2 of ‘yaml_emitter_set_output’ from incompatible pointer type [-Wincompatible-pointer-types] 16882 | yaml_emitter_set_output((&__pyx_v_self->emitter), __pyx_f_6ruamel_4yaml_4clib_12_ruamel_yaml_output_handler, ((void *)__pyx_v_self)); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | | int (*)(void *, char *, int) yaml.h:1837:31: note: expected ‘int (*)(void *, unsigned char *, size_t)’ {aka ‘int (*)(void *, unsigned char *, long unsigned int)’} but argument is of type ‘int (*)(void *, char *, int)’ 1837 | yaml_write_handler_t *handler, void *data); | ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~ error: command '/usr/bin/gcc' failed with exit code 1 See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223148] New: NVIDIA Jetson AGX Orin/IGX Orin: Graphical desktop and Linux console not available after boot
by bugzilla_noreply＠suse.com 06 May '24

06 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223148 Bug ID: 1223148 Summary: NVIDIA Jetson AGX Orin/IGX Orin: Graphical desktop and Linux console not available after boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- On NVIDIA Jetson AGX Orin/IGX Orin platforms display remains black after boot. Linux console is not available either. Workaround: Login via serial console or ssh. Run these commands: $ sudo rmmod tegra_drm $ sudo modprobe tegra_drm $ sudo rcxdm restart With that the graphical destkop should be running and display lightening up as expected. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1217828] New: podman not using netavark as default
by bugzilla_noreply＠suse.com 06 May '24

06 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217828 Bug ID: 1217828 Summary: podman not using netavark as default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Tumbleweed, despite being on podman 4.8.0 we are still using CNI instead of netavark as the default network backend https://openqa.opensuse.org/tests/3781263#step/podman/48 This issue was detected while extending the podman tests on Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221905] New: named crashes on startup: mem.c:736: fatal error: malloc failed: Cannot allocate memory
by bugzilla_noreply＠suse.com 05 May '24

05 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221905 Bug ID: 1221905 Summary: named crashes on startup: mem.c:736: fatal error: malloc failed: Cannot allocate memory Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873759 --> https://bugzilla.suse.com/attachment.cgi?id=873759&action=edit strace Hi, BIND from the update repositories works on our virtual machines, but does not start on a physical one: ``` Mar 24 17:20:07 stonehat systemd[1]: Starting Berkeley Internet Name Domain (DNS)... Mar 24 17:20:07 stonehat named[49737]: starting BIND 9.16.48 (Extended Support Version) <id:0dab57e> Mar 24 17:20:07 stonehat named[49737]: running on Linux x86_64 5.14.21-150500.55.52-default #1 SMP PREEMPT_DYNAMIC Tue Mar 5 16:53:41 UTC 2024 (a62851f) Mar 24 17:20:07 stonehat named[49737]: built with '--host=x86_64-suse-linux-gnu' '--build=x86_64-suse-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/et> Mar 24 17:20:07 stonehat named[49737]: running as: named -u named Mar 24 17:20:07 stonehat named[49737]: compiled by GCC 7.5.0 Mar 24 17:20:07 stonehat named[49737]: compiled with OpenSSL version: OpenSSL 1.1.1l-fips 24 Aug 2021 SUSE release SUSE_OPENSSL_RELEASE Mar 24 17:20:07 stonehat named[49737]: linked to OpenSSL version: OpenSSL 1.1.1l-fips 24 Aug 2021 SUSE release 150500.17.25.1 Mar 24 17:20:07 stonehat named[49737]: compiled with libuv version: 1.44.2 Mar 24 17:20:07 stonehat named[49737]: linked to libuv version: 1.44.2 Mar 24 17:20:07 stonehat named[49737]: compiled with libxml2 version: 2.10.3 Mar 24 17:20:07 stonehat named[49737]: linked to libxml2 version: 21003 Mar 24 17:20:07 stonehat named[49737]: compiled with json-c version: 0.13 Mar 24 17:20:07 stonehat named[49737]: linked to json-c version: 0.13 Mar 24 17:20:07 stonehat named[49737]: compiled with zlib version: 1.2.13 Mar 24 17:20:07 stonehat named[49737]: linked to zlib version: 1.2.13 Mar 24 17:20:07 stonehat named[49737]: ---------------------------------------------------- Mar 24 17:20:07 stonehat named[49737]: BIND 9 is maintained by Internet Systems Consortium, Mar 24 17:20:07 stonehat named[49737]: Inc. (ISC), a non-profit 501(c)(3) public-benefit Mar 24 17:20:07 stonehat named[49737]: corporation. Support and training for BIND 9 are Mar 24 17:20:07 stonehat named[49737]: available at https://www.isc.org/support Mar 24 17:20:07 stonehat named[49737]: ---------------------------------------------------- Mar 24 17:20:07 stonehat named[49737]: adjusted limit on open files from 524288 to 1048576 Mar 24 17:20:07 stonehat named[49737]: found 64 CPUs, using 64 worker threads Mar 24 17:20:07 stonehat named[49737]: using 64 UDP listeners per interface Mar 24 17:20:07 stonehat named[49737]: using up to 21000 sockets Mar 24 17:20:07 stonehat named[49737]: DNSSEC algorithms: RSASHA1 NSEC3RSASHA1 RSASHA256 RSASHA512 ECDSAP256SHA256 ECDSAP384SHA384 ED25519 ED448 Mar 24 17:20:07 stonehat named[49737]: DS algorithms: SHA-1 SHA-256 SHA-384 Mar 24 17:20:07 stonehat named[49737]: HMAC algorithms: HMAC-MD5 HMAC-SHA1 HMAC-SHA224 HMAC-SHA256 HMAC-SHA384 HMAC-SHA512 Mar 24 17:20:07 stonehat named[49737]: TKEY mode 2 support (Diffie-Hellman): yes Mar 24 17:20:07 stonehat named[49737]: TKEY mode 3 support (GSS-API): yes Mar 24 17:20:07 stonehat named[49737]: loading configuration from '/etc/named.conf' Mar 24 17:20:07 stonehat named[49737]: reading built-in trust anchors from file '/etc/bind.keys' Mar 24 17:20:07 stonehat named[49737]: looking for GeoIP2 databases in '/usr/share/GeoIP' Mar 24 17:20:07 stonehat named[49737]: using default UDP/IPv4 port range: [32768, 60999] Mar 24 17:20:07 stonehat named[49737]: using default UDP/IPv6 port range: [32768, 60999] Mar 24 17:20:07 stonehat named[49737]: listening on IPv4 interface lo, 127.0.0.1#53 Mar 24 17:20:07 stonehat named[49737]: listening on IPv4 interface prg2_asgard1, 172.16.201.6#53 Mar 24 17:20:07 stonehat named[49737]: listening on IPv4 interface prg2_asgard2, 172.16.202.6#53 Mar 24 17:20:07 stonehat named[49737]: listening on IPv4 interface private, 192.168.87.1#53 Mar 24 17:20:07 stonehat named[49737]: generating session key for dynamic DNS Mar 24 17:20:07 stonehat named[49737]: sizing zone task pool based on 18 zones Mar 24 17:20:08 stonehat named[49737]: obtaining root key for view _default from '/etc/bind.keys' Mar 24 17:20:08 stonehat named[49737]: set up managed keys zone for view _default, file '/var/lib/named/dyn//managed-keys.bind' Mar 24 17:20:08 stonehat named[49737]: mem.c:736: fatal error: Mar 24 17:20:08 stonehat named[49737]: malloc failed: Cannot allocate memory Mar 24 17:20:08 stonehat named[49737]: exiting (due to fatal error in library) Mar 24 17:20:08 stonehat systemd[1]: named.service: Control process exited, code=exited, status=1/FAILURE Mar 24 17:20:08 stonehat systemd[1]: named.service: Failed with result 'exit-code'. Mar 24 17:20:08 stonehat systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). ``` With the bind-9.16.38-150400.5.20.2 package from the GA repository, named starts fine. We don't know which update introduced the problem. I tried disabling "zone-statistics", but that did not help. Strace output while running named in foreground is attached. No related kernel log entries are observed, but dmesg is attached as well. Cheers, Georg -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1223548] New: Renoir/Cezanne Crashing on 3D Game/Project Usage Randomly but Frequently - NOT PRESENT ON OTHER OS
by bugzilla_noreply＠suse.com 04 May '24

04 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223548 Bug ID: 1223548 Summary: Renoir/Cezanne Crashing on 3D Game/Project Usage Randomly but Frequently - NOT PRESENT ON OTHER OS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: padreadamo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874573 --> https://bugzilla.suse.com/attachment.cgi?id=874573&action=edit PDF from post on Freedesktop Renoir/Cezanne Crashing on 3D Game/Project Usage Randomly but Frequently - NOT PRESENT ON OTHER OS I posted this to AMD Issues on Freedesktop: https://gitlab.freedesktop.org/drm/amd/-/issues/3335 The issue was closed but I thought it a good idea to post it here. Major issues using Tumbleweed with this APU. Games/3D crashes (hard crashes) every few minutes. Can only obtain crash data via SSH unfortunately I'm not well versed in that. I have been using OpenSUSE Tumbleweed for about 10 years. Hoping to raise awareness by posting this. Essentially, all issues went away when I switched to POP OS as a test. I believe they use an LTS kernel? ------------- I use OpenSUSE Tumebleweed (Plasma). I have tried numerous Kernel Parameters, Wayland vs Xorg, power profiles, CoreCTRL. I can't produce the issue at will it just happens rather regularly. Essentially, any game sometimes after a few minutes sometimes within an hour will lock up and I am forced to reboot. I have never reported a bug here so I apologize if I'm missing something or not doing something correctly. I just don't know else to do, I'm at a loss. Operating System: openSUSE Tumbleweed 20240419 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 81YM System Version: IdeaPad 5 14ARE05 I wiped the laptop and installed Windows 10 from my Lenovo recovery. I had to do this to update my bios. I updated my bios. Installed OpenSUSE Tumbleweed alongside Windows and the issue persists. Running the following command allows me to at least kill the game running before it locks up the laptop: amdgpu.runpm=0 POP OS DOES NOT HAVE THIS ISSUE. SWITCHING AND I HAVE HAD ZERO CRASHES. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222180] New: openssh: rewrite systemd notification without linking systemd
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222180 Bug ID: 1222180 Summary: openssh: rewrite systemd notification without linking systemd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- openssh carries this patch: https://build.opensuse.org/projects/openSUSE:Factory/packages/openssh/files… which is linking libsystemd, just for notifying systemd. given the large dependency tree of systemd, this increases the attack surface of openssh, as can be seen via https://www.suse.com/security/cve/CVE-2024-3094.html we should split out sd_notify() into a separate standalone library (or maybe it exists already?) and link that one instead -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1223378] New: rstudio fails to build against boost 1.85
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223378 Bug ID: 1223378 Summary: rstudio fails to build against boost 1.85 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: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- rstudio failed to build in openSUSE:Factory after boost had been updated to version 1.85, see https://build.opensuse.org/package/live_build_log/openSUSE:Factory/rstudio/… -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1213297] New: No clang-tools package needed by clang >=13 from PackageHub repo
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213297 Bug ID: 1213297 Summary: No clang-tools package needed by clang >=13 from PackageHub repo Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: oleksandr.shchirskyi(a)intel.com QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: No There is an issues with LLVM versions >=13 on SLES15 SP5. None of the Package Hub versions can be installed because the Clang-tool dependency is missing. For example, LLVM for SLES15 SP4 includes Clang-tool, but for SP5 it doesn't: https://packagehub.suse.com/packages/llvm13/ The same issue applies to LLVM 14. Here's a brief log example: # grep PRETTY /etc/os-release PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5" # zypper install clang14-devel Refreshing service 'Basesystem_Module_15_SP5_x86_64'. Refreshing service 'Desktop_Applications_Module_15_SP5_x86_64'. Refreshing service 'Development_Tools_Module_15_SP5_x86_64'. Refreshing service 'Legacy_Module_15_SP5_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Server_15_SP5_x86_64'. Refreshing service 'SUSE_Package_Hub_15_SP5_x86_64'. Refreshing service 'Server_Applications_Module_15_SP5_x86_64'. Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'clang-tools >= 14.0.6' needed by the to be installed clang14-devel-14.0.6-bp155.4.10.x86_64 Solution 1: do not install clang14-devel-14.0.6-bp155.4.10.x86_64 Solution 2: break clang14-devel-14.0.6-bp155.4.10.x86_64 by ignoring some of its dependencies # zypper info clang14-devel Refreshing service 'Basesystem_Module_15_SP5_x86_64'. Refreshing service 'Desktop_Applications_Module_15_SP5_x86_64'. Refreshing service 'Development_Tools_Module_15_SP5_x86_64'. Refreshing service 'Legacy_Module_15_SP5_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Server_15_SP5_x86_64'. Refreshing service 'SUSE_Package_Hub_15_SP5_x86_64'. Refreshing service 'Server_Applications_Module_15_SP5_x86_64'. Loading repository data... Reading installed packages... Information for package clang14-devel: -------------------------------------- Repository : SUSE-PackageHub-15-SP5-Backports-Pool Name : clang14-devel Version : 14.0.6-bp155.4.10 Arch : x86_64 Vendor : openSUSE Support Level : unknown Installed Size : 17.3 MiB Installed : No Status : not installed Source package : llvm14-14.0.6-bp155.4.10.src Upstream URL : https://www.llvm.org/ Summary : CLANG frontend for LLVM (devel package) Description : This package contains the clang (C language) frontend for LLVM. (development files) # zypper search clang | grep tools # At the same moment it's possible to install LLVM >=13 from OpenSUSE repos, for example, adding this to repos config "http://download.opensuse.org/distribution/leap/15.5/repo/oss/" -- You are receiving this mail because: You are on the CC list for the bug.

1 2