Search results for

Re: Package fstrcmp is gone from TW 20231003 - on purpose?

by Manfred Hollstein

On Thu, 05 Oct 2023, 15:53:26 +0200, Jan Engelhardt wrote: > > On Thursday 2023-10-05 14:27, Manfred Hollstein wrote: > >On Thu, 05 Oct 2023, 13:59:45 +0200, Jan Engelhardt wrote: > >> On Thursday 2023-10-05 13:10, Andrei Borzenkov wrote: > >> >> > >> >> it looks like the last Tumbleweed snapshot 20231003 removed package > >> >> fstrcmp, i.e. libfstrcmp0 here; fwiw, openSUSE:Factory also doesn't > >> >> contain it anymore. > >> >> > >> >> This package is still needed by Kodi which now shows one orphaned > >> >> package. Was the removal on purpose? In that case we would have to > >> >> start building it for Tumbleweed on Packman. > >> > > >> > Descr: fails to build and is unused > >> > >> The buildfailure is easy to fix (already identified to require > >> groff-full), but the deletion crowd went chopping in the woods > >> quicker than anything else. > > > >Yeah, I stored the deleted files in the devel:libraries:c_c++ project > >and created a new package A_tw-fstrcmp in PMBS/Staging, which only > >builds for Tumbleweed and Slowroll. > > You can just bring it back for openSUSE:Factory. > If you set a maintainer on d:l:c/fstrcmp, you get reasonably-timed > build failure reports and there is less of a chance someone swings > the package axe. I just requested maintainership for d:l:c/fstrcmp. Once I get access rights, I'll resurrect the stuff in PMBS again. Thanks for pointing me in the right direction! Cheers. l8er manfred

1 year, 1 month

Re: Slowroll and amdgpu-pro and alternatives

by Peter McD

Am 30.11.23 um 01:22 schrieb Aaron Puchert: > Am 29.11.23 um 12:38 schrieb Peter McD: >> Am 29.11.23 um 08:15 schrieb Patrik Jakobsson: >>> Can you detect the card with clinfo? >> >> first the suggested link >> >> ln -s /usr/lib64/libOpenCL.so.1 /usr/lib64/libOpenCL.so > > Probably not needed, at least not for clinfo: > > > readelf --dynamic /usr/bin/clinfo | grep NEEDED > 0x0000000000000001 (NEEDED) Shared library: [libOpenCL.so.1] > 0x0000000000000001 (NEEDED) Shared library: [libc.so.6] > > The symlink should only be needed for development, and then you can find > it in ocl-icd-devel. > > The problem seems rather that the installation isn't being found. > Installations are dynamically loaded from those listed in > /usr/share/OpenCL/vendors and /etc/OpenCL/vendors. Unfortunately > existence of the latter precludes installations from the former > directory from being recognized with the loader from ocl-icd, if nothing > changed since 2020 > (https://bugzilla.opensuse.org/show_bug.cgi?id=1173005) Ideally you can > remove /etc/OpenCL/vendors entirely if all vendors are in /usr. If not, > symlink those from /usr that you want into /etc. > > The files in that directory are text files containing the name of a > library that should sit in /usr/lib64. Here with Mesa-libOpenCL: > > $ cat /usr/share/OpenCL/vendors/mesa.icd > libMesaOpenCL.so.1 > > So in this case the implementation is in /usr/lib64/libMesaOpenCL.so.1, > which will then be loaded via dlopen. > > If you have such a text file and the library exists, I'd suggest to run > clinfo under strace. You should see it find the file, then load the > library, then look up symbols. Check where it stops. > Thanks, I'll will lock at that later. cu Peter

11 months, 3 weeks

Re: Slowroll and amdgpu-pro and alternatives

by Peter McD

Am 30.11.23 um 01:22 schrieb Aaron Puchert: > Am 29.11.23 um 12:38 schrieb Peter McD: >> Am 29.11.23 um 08:15 schrieb Patrik Jakobsson: >>> Can you detect the card with clinfo? >> >> first the suggested link >> >> ln -s /usr/lib64/libOpenCL.so.1 /usr/lib64/libOpenCL.so > > Probably not needed, at least not for clinfo: > > > readelf --dynamic /usr/bin/clinfo | grep NEEDED > 0x0000000000000001 (NEEDED) Shared library: [libOpenCL.so.1] > 0x0000000000000001 (NEEDED) Shared library: [libc.so.6] > > The symlink should only be needed for development, and then you can find > it in ocl-icd-devel. > > The problem seems rather that the installation isn't being found. > Installations are dynamically loaded from those listed in > /usr/share/OpenCL/vendors and /etc/OpenCL/vendors. Unfortunately > existence of the latter precludes installations from the former > directory from being recognized with the loader from ocl-icd, if nothing > changed since 2020 > (https://bugzilla.opensuse.org/show_bug.cgi?id=1173005) Ideally you can > remove /etc/OpenCL/vendors entirely if all vendors are in /usr. If not, > symlink those from /usr that you want into /etc. I have now a fresh installation of Tumbleweed, added Patrik's repo and installed amd-opencl. clinfo shows: Number of platforms 0 ICD loader properties ICD loader Name OpenCL ICD Loader ICD loader Vendor OCL Icd free software ICD loader Version 2.3.1 ICD loader Profile OpenCL 3.0 ls -l /usr/share or ls -l /etc/ Neither in /usr/share/ nor in /etc/ is a direktory OpenCL, and so no directory "vendors" What else do I have to install? cu Peter

11 months, 2 weeks

Re: Is it possible for Slowroll to officially support the integrity of NVidia and VMWare modules?

by Xu Zhao

Hi Bernhard, Thanks for your response! See my comments below: On Tue, Dec 19, 2023, at 3:24 AM, Bernhard M. Wiedemann via openSUSE Factory wrote: > On 19/12/2023 05.25, Xu Zhao wrote: >> Currently I am blocked by using Qemu kvm to kick of specific tumbleweed >> snapshot image and test nvidia driver compile (sth like open build >> system). If anyone knows how to do that, or simply give code pointers on >> how OBS runs Qemu KVM, that would be very much appreciated. > > > https://github.com/nektos/act says > > GitHub Actions are running in fully virtualized machines > > so you probably cannot get KVM working there. But chroot or containers > should be an option. Chroot or plain containers will not work because NVIDIA driver will not build when the host kernel gcc version is incompatible with the container kernel header. https://forums.developer.nvidia.com/t/conftest-failed-error-while-trying-to… Conftest will fail when I was trying to cross-compile from a different kernel header files than the host kernel. I was about to try https://github.com/docker/setup-qemu-action, since Docker claims that they could run QEMU on GitHub Action runners. However, I am not sure how to proceed (e.g., should I use tumbleweed:latest docker image or tumbleweed ISO). > > OBS workers OTOH run on bare metal and thus have access to hardware > needed for KVM. Still, I am interested in what openSUSE Tumbleweed image is used in KVM. In the worst case, I could run self-hosted GitHub runner on my own bare-metal workstation, and run openSUSE Tumbleweed KVM images on it with GitHub actions. > > Attachments: > * OpenPGP_signature.asc Best, Xu

11 months

Re: VirtualBox 7.1 is out and Leap has not gotten 7.0.20 yet.

by Axel Braun

VB_devel_project and VB_Packages are *placeholders* for the project resp. the package. Viele Grüße Axel -- Diese Nachricht wurde von meinem Android-Tablet mit K-9 Mail gesendet. Am 13. September 2024 14:56:32 OESZ schrieb Larry Len Rainey <llrainey15(a)gmail.com>: >That did not work > >Larry > >user@LLR3:~> osc mr -m 'update to Virtualbox' VB_devel_project VB_Packages openSUSE:Backports:SLE-15-SP6:Update > Using target project 'openSUSE:Maintenance'. (release in 'openSUSE:Backports:SLE-15-SP6:Update') > Server returned an error: HTTP Error 404: Not Found > Project not found: VB_devel_project > user@LLR3:~> > >On 9/13/24 04:35, Axel Braun wrote: > >Am Donnerstag, 12. September 2024, 19:23:19 MESZ schrieb Javier Llorente: > >Hi Larry! El jueves, 12 de septiembre de 2024 16:39:45 (CEST), Larry Len Rainey escribió: > >Can someone get VirtualBox 7.0.20 out for Leap. It had no changes for user code - just a lot of CVE fixes. I did remove all the 41 42 15.0 15.1 15.2 15.3 specific patches that did nothing that Larry Finger had in the spec file. It has been in Tumbleweed and Slowroll for a month. > > In order to push it to Leap, you have to create a maintenance request for each release (15.5, 15.6) . The following example is for Leap 15.6 (SP6): osc branch openSUSE:Backports:SLE-15-SP6:Update virtualbox osc co home:username:branches:openSUSE:Backports:SLE-15-SP6:Update/virtualbox > > I dont think a local branch is needed. Submit it from the devel-project to Backports: osc mr -m 'update to Virtualbox' VB_devel_project VB_Packages openSUSE:Backports:SLE-15-SP6:Update Note - of course it should build properly in the devel project. Cheers Axel

2 months, 1 week

Re: slowroll is broken

by Adrian Schröter

On Mittwoch, 28. Februar 2024, 17:32:21 CET Andreas Schwab wrote: > On Feb 28 2024, Adrian Schröter wrote: > > > On Donnerstag, 15. Februar 2024, 17:13:13 CET Bernhard M. Wiedemann via openSUSE Factory wrote: > >> > >> On 15/02/2024 14.31, Larry Len Rainey wrote: > >> > Getting this today (repo list at bottom) > >> > > >> > zypper dup > >> > > >> > >> > 'apparmor-docs-3.1.7-1.1.noarch.rpm' > >> > [/var/tmp/AP_0xi8dYFp/noarch/apparmor-docs-3.1.7-1.1.noarch.rpm] > >> > > >> > expected > >> > afe4d69e9749e1798412c520c01b266856af22bf8a9f3342c33368dd224e1b0b9f3b24f5c330de85290e2db31b8ab083466fe6363a06e8bf0aa519f13884feae > >> > but got > >> > 33c05a3a7c0232392229d52abdd78d7d1106fb4eb312e820731f67747b9e2d89253ec3a941bf7169b6ec29fe92d64355b10296b94a9b7f26ee1760dfa1baa7cf > >> > >> This is fallout from the version bump when packages got replaced with a > >> different version under the same name. > >> It is still a ToDo to get OBS to create proper numbering > >> e.g. fix https://github.com/openSUSE/open-build-service/issues/15079 > > > > erm, even when you always have the same revision number for the checkin counter, > > you should still have a different build counter. > > > > Are you sure that this is not a different issue here? > > It can also happen when a noarch (sub-)package is republished, but from > a build by a different architecture. yes, but the publisher is usually taking care of this and does not switch it. -- Adrian Schroeter <adrian(a)suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev

8 months, 3 weeks

openSUSE Release Engineering meeting 30.10.2024

by Lubos Kocman

How to join the meeting? https://calendar.opensuse.org/teams/release/events/opensuse-release-enginee… https://meet.opensuse.org/meeting All meeting minutes can be found here: https://etherpad.opensuse.org/p/ReleaseEngineering-meeting ## Attendees: ddemaio, DimStar, GuillaumeG, lkocman, adamm, maxlin, rfrohl, wengel, bmwiedemann, Marcus, ## Leap SUSE Czech Open House 2024 on 13th of November in Prague. Everybody is welcome to come! I'll be having Leap 16 install workshop there! We'll get bunch of Laptops from SUSE IT and will have bunch of USB install sticks. Details at https://more.suse.com/openhousecz Reduced YaST-stack for Leap 16 https://code.opensuse.org/leap/features/issue/173 I'd love to see the yast software management center, and perhaps a few other standalone components. We have to respect YaST's resources. So far I was told that keeping the software center should be okay. We will likely need a new yast-less migration tool from Leap to SLES. I suggest using something minimalistic with jeos-firstboot style dialog cmd, swapping releases, calling suseconnect and zy^pper dup. This could also support migration in between, Leap 15 -> 16, Leap -> TW, Leap -> Slowroll, Leap -> SLES. I might be looking into this over hackweek. But I need decent SCC setup for both SLES 16 and Leap 16 first. I'm really happy to see that our SLES 16 SRs from code-o-o features are being accepted in reasonable time (within a week from submit). KDE branding focus, we need to have a dark theme. I received the first set of complaints. Micro 6.1 is still in progress. ## openSUSE Tumbleweed (DimStar) openSUSE:Factory build fail stats: 237 failed 34 unresolvable (last week 54 failed, 4 unresolvable) - main increase due to some sync between :Rebuild and :Factory (to wake up maintainers) https://tinyurl.com/ysy4nnnz ( https://build.opensuse.org/project/show/openSUSE:Factory:Rebuild shows the results when we'd use rebuild=transitive, i.e 400 failed packages) 662 requests accepted in the last week (data source: https://build.opensuse.org/projects/openSUSE:Factory/pulse) Most relevant changes: GNOME 47.1 Kernel 6.11.5 KDE Plasma 6.2.2 Pam 1.7.0 Branding update (wallpaper and Logo) Blocked / on-going: Enabling python 3.13 modules (python313-*); python 3.11 stays the default for now icu 76.1 rc, 9 packages ftbfs https://bugzilla.opensuse.org/show_bug.cgi?id=1232061 LLVM 19 / Mesa 24.2.x blocked on https://gitlab.freedesktop.org/mesa/mesa/-/issues/11840 swig 4.3.0, 4 packages failing to build ldns https://bugzilla.opensuse.org/show_bug.cgi?id=1231584 libftdi1 https://bugzilla.opensuse.org/show_bug.cgi?id=1231585 python-M2Crypto https://bugzilla.opensuse.org/show_bug.cgi?id=1231589 subversion https://bugzilla.opensuse.org/show_bug.cgi?id=1231590 health-checker https://bugzilla.suse.com/show_bug.cgi?id=1231127 ## Richard (Aeon+botmaster) Not avialable ## Max Leap 16.0 * Regarding gcc build variant package problem from SLFO https://bugzilla.suse.com/show_bug.cgi?id=1230628 the corresponding package were rebuilt in SLFO, will verify it in the next Leap 16.0 product rebuilding(leap_16 snapshot got refreshed today) * Plasma 6 update is blocked by kinfocenter6 https://build.opensuse.org/package/live_build_log/openSUSE:Leap:16.0:Stagin… , need to whitelsit it in polkit-default-privs * Processing pending new package submissions to Leap 16.0, merged ~900 package already lkocman: Licensedigger addition is planned. ## Guillaume - Arm Tumbleweed: * Rolling * Missing non-oss source repo for aarch64 - https://bugzilla.suse.com/show_bug.cgi?id=1226763 - Adrian will look into it. Leap 15.5: * RPi3: Boot Network issue poped in openQA (broken kernel backport) - Fix on the way - https://bugzilla.opensuse.org/show_bug.cgi?id=1232342 Leap 15.6: * Problems on RPi4 with very long boot and keyboard unrecognized with latest rapsberrypi-eeprom update (update taken from TW) - https://bugzilla.opensuse.org/show_bug.cgi?id=1230104 Leap 16.0: * no blocker ## Sarah - s390x * not available ## Doug * openSUSE.Asia Summit happening this weekend * Giving talks on Leap & Geeko Foundation * Leap, TW branding article published * Monthly TW article released * New rsync.net Support for openSUSE Devs - https://lists.opensuse.org/archives/list/project@lists.opensuse.org/thread/… * Did TSPs for GSoC Summit * Working on FrOSCon sponsorship * GNOME Extensions workshop https://www.youtube.com/live/_v0INEp6gNU?si=r31FqI0yrGlnIooC * FOSDEM * Emails coming out about dev rooms CfPs * Bus Set * Community in Nuremberg should connect ddemaio(a)opensuse.org to reserve a seat * Early Adopter Tech Summit 14.03.25 to 15.03.25 (what's the location?) * CfP is open ## Dirk Working on adding python 3.13 modules in Factory - Staging:I, full drama in devel:languages:python:backports * 197 failed, 295 unresolvable lkocman: There was a communication of "default" python in SLES16 to python mailing list. Is that all confirmed information? Dirk: The current plan is to have a 3.11 in SLFO, but it will not stay like that forever, it can be updated to 3.13, respective 3.15 later on. ## Maintenance (Marcus, Robert) All is working nicely. We're still having problem with Xfce/branding package. ## Wolfgang (Package Hub), Scott Bahling, Nathan Cutler * Still fixing missing dependencies for SP7 (and some of them also for SP6) * Scheduling a meeting regarding workflow (staging etc.) for Package Hub for SLE-16/Leap 16.0 (Adam, Adrian, Lubos, Max, Dirk, Stephan, Wolfgang) This will directly effect hot changes are submitted to Leap 16.0. ## Adrian - OBS No update, processing backlog. ## Bernhard - Slowroll kernels updated snapshot planned around 2024-11-03 and version bump around 2024-11-09 to keep the monthly cadence ## Bernhard - reproducible builds preparing monthly report for Factory ML ## Adam - Git Workflow No updates ## Open Floor

3 weeks, 4 days

Re: slowroll will not install correctly from either network iso or DVD image

by Felix Miata

Joe Salmeri composed on 2023-09-19 13:06 (UTC-0400): > One other thing, if I ping cdn.opensuse.org I get > localhost:~ # ping cdn.opensuse.org > PING dualstack.n.sni.global.fastly.net (151.101.45.91) 56(84) bytes of data. > 64 bytes from 151.101.45.91 (151.101.45.91): icmp_seq=1 ttl=60 time=17.9 ms > 64 bytes from 151.101.45.91 (151.101.45.91): icmp_seq=2 ttl=60 time=20.1 ms > 64 bytes from 151.101.45.91 (151.101.45.91): icmp_seq=3 ttl=60 time=22.4 ms > Do you get the same server or a different one ? That's what I get in FL: > ping -c4 cdn.opensuse.org PING dualstack.n.sni.global.fastly.net (151.101.1.91) 56(84) bytes of data. 64 bytes from 151.101.1.91 (151.101.1.91): icmp_seq=1 ttl=60 time=34.9 ms 64 bytes from 151.101.1.91 (151.101.1.91): icmp_seq=2 ttl=60 time=33.9 ms 64 bytes from 151.101.1.91 (151.101.1.91): icmp_seq=3 ttl=60 time=43.3 ms 64 bytes from 151.101.1.91 (151.101.1.91): icmp_seq=4 ttl=60 time=36.7 ms > > ping -c3 download.opensuse.org PING download.opensuse.org (195.135.221.134) 56(84) bytes of data. 64 bytes from download.opensuse.org (195.135.221.134): icmp_seq=1 ttl=50 time=174 ms 64 bytes from download.opensuse.org (195.135.221.134): icmp_seq=2 ttl=50 time=140 ms 64 bytes from download.opensuse.org (195.135.221.134): icmp_seq=3 ttl=50 time=135 ms > > ping -c3 provo-mirror.opensuse.org PING provo-mirror.opensuse.org (91.193.113.70) 56(84) bytes of data. 64 bytes from provo-mirror.opensuse.org (91.193.113.70): icmp_seq=1 ttl=47 time=142 ms 64 bytes from provo-mirror.opensuse.org (91.193.113.70): icmp_seq=2 ttl=47 time=105 ms 64 bytes from provo-mirror.opensuse.org (91.193.113.70): icmp_seq=3 ttl=47 time=157 ms > -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

1 year, 2 months

Re: [TW][Slowroll] latest opi wants to install build system tools and more (29 new)

by Andrei Borzenkov

On 19.01.2024 21:53, Felix Miata wrote: > Should I report a bug? If yes, against TW? SR isn't apparent there. > To update opi: > # time zypper -v dup > ... > Computing upgrade... > ... > The following package is going to be upgraded: > opi 3.5.0-1.1 -> 4.3.0-1.1 > > The following 29 NEW packages are going to be installed: > binutils 2.41-1.2 > debugedit 5.0-5.6 > dwz 0.15-2.6 > gcc 13-1.6 > gcc13 13.2.1+git8109-1.1 > gettext-runtime 0.21.1-2.4 > gettext-tools 0.21.1-2.4 > glibc-devel 2.38-7.1 > libasan8 13.2.1+git8109-1.1 > libatomic1 13.2.1+git8109-1.1 > libctf-nobfd0 2.41-1.2 > libctf0 2.41-1.2 > libhwasan0 13.2.1+git8109-1.1 > libitm1 13.2.1+git8109-1.1 > liblsan0 13.2.1+git8109-1.1 > liblzo2-2 2.10-8.4 > libtextstyle0 0.21.1-2.4 > libtsan2 13.2.1+git8109-1.1 > libubsan1 13.2.1+git8109-1.1 > libxcrypt-devel 4.4.36-1.4 > linux-glibc-devel 6.6-1.1 > make 4.4.1-2.5 > patch 2.7.6-6.9 > python-rpm-macros 20231010.0a1f0d9-1.1 > python-rpm-packaging 20210526+a18ca48-1.9 > python311-packaging 23.2-1.1 > rpm-build 4.18.0-6.2 > rpm-build-perl 4.18.0-6.2 > squashfs 4.6.1-2.2 > > 1 package to upgrade, 29 new. > Overall download size: 1.3 MiB. Already cached: 48.7 MiB. After the operation, additional 188.3 MiB will be used. > Continue? [y/n/v/...? shows all options] (y): n > # > > Why are all these construction packages required in order to do opi package > searches? Is this really intended? # for rpm building and snap extracting Requires: rpm-build

10 months

Re: NFS Server mount issues since some days

by Ulf

Thanks Bernhard and Jose :-) can be the case, that Jose is right with his link to the resume and that nfs-client.target is stopped. Anyhow I don't use them, I will check it next time if my <mountpoint>.mount can be restarted at the client. At least the <mountpoint>.automount fails. About the Kernal I was looking as well Bernhard. Thanks for hint. I was thinking if the new scheduler have an impact as well. Ulf Am Dienstag, 30. Januar 2024, 10:02:25 CET schrieb Jose Iván Lopez: > Hi! > > I am not sure if it is related, but there is an open bug for NFS automount > after resuming the system, see > https://bugzilla.suse.com/show_bug.cgi?id=1217176. > > > On Tue, Jan 30, 2024 at 8:11 AM Bernhard M. Wiedemann via openSUSE Factory < > factory(a)lists.opensuse.org> wrote: > > On 29/01/2024 20.19, Ulf via openSUSE Factory wrote: > > > Since some days, my Tumbleweed with running NFS-server, blocks from time > > > > to > > > > > time the possibility to login. At systemctrl status and journalctl, I > > > > can't > > > > > find any hint. The login request will be displayed but the NFS-client > > > > timed > > > > > out. > > > > > > Can't find a update of NFS or bind in the last days. > > > > > > Any idea how to debug this issue? > > > > Kernel 6.7.1 came to Factory 3 days ago, so you could try to boot into a > > 6.6.x kernel to see if that helps. > > > > If it was already uninstalled, you can find it at > > > > https://download.opensuse.org/update/slowroll/repo/oss/x86_64/kernel-defau > > lt-6.6.11-1.1.x86_64.rpm

9 months, 3 weeks

openSUSE Factory search results for query "Slowroll"