on my leap 15.5 using KDE I was updating and many packets ask me this:
YaST2 conflicts list - generated 2024-07-16 17:56:00
nothing provides ‘libc.so.6(GLIBC_2.38)(64bit)’ needed by the to be installed gstreamer-plugin-pipewire-1.2.0-lp155.217.1.x86_64
[ ] break gstreamer-plugin-pipewire-1.2.0-lp155.217.1.x86_64 by ignoring some of its dependencies
[x] do not install gstreamer-plugin-pipewire-1.2.0-lp155.217.1.x86_64
YaST2 conflicts list END
where can I found ‘libc.so.6(GLIBC_2.38)(64bit)’ and install it?
I would call this system corrupted and unsafe to the core. So much untested and incompatible home and devel repos at once…
Such a repo list calls for package conflicts and an unstable system.
yes but I need some software that plasmaregator has, so, I downgraded all the software that was asking ‘libc.so.6(GLIBC_2.38)(64bit)’ coming from plasmaregator but the last ones need this, I found in this repo: https://download.opensuse.org/repositories/home:videoregataos/15.5
is it possible to install more versions of ‘libc.so.6(GLIBC_2.38)(64bit)’ or I have to install version 2.38 upgrading all glibc??
Only one version of glibc is possible due to conflicts.
If you want to screw your system finaly with the regataos packages, you may switch glibc packages to the regataos version. You can do this via YaST software. Search for glibc and switch under the version tab to regataos.
I personaly, would stay far, far, far away from everything what is provided by regataos. See this thread.
Be aware that if you choose to go down this rabbit hole, that you probably won’t get security fixes from this user/repo…
With all the different non-standard repos you have configured, what you may be best off doing is getting rid of all of them, then creating your own home and having BS build what you need from source. How do you manage to need so much software that isn’t among the wealth of software in standard openSUSE repos?
I actually spent a portion of my day building my first package in OBS, actually a patched version of nautilus. (openSUSE Build Service == OBS ???). Getting it built was far easier than I anticipated.
On the rare occasions that I have needed or wanted a software package that is not in one of the standard trusted repos (e.g. the “official” suse repos, packman, videolan, nvidia), I have downloaded the source rpms and/or code and compiled locally using rpmbuild, and occasionally, old the old fashioned way (.configure/make/make install) in /usr/local.
If you have never compiled code before, I image the prospect of doing so is intimidating. Fortunately, It sounds MUCH harder than it actually is …
Well written and well designed code is almost always easy to build.
If you encounter all kinds of crazy problems building the binaries, that should be your first hint that you probably don’t want that code running on your box!
Oh! And I forgot to mention another approach. Find sane pre-compiled binaries of the software you need. They come is several flavors, but the easiest to use on openSUSE would probably come from flatpack.
openSUSE Leap used to have a package called FSLint. It is a tool that helps you find duplicate files, among other aspects of wasted disc space caused by redundancy. At some point, the FSLint developers stopped maintaining, a rather common occurrence in the open source world, and it could no longer be built or run on Leap because it required obsolete versions of python everything!
A couple of years back, some gung-ho Eastern European hackers re-created FSLint, or at least the basic design of the ui, but written completely in Rust. They call the program czkawka, which I believe is the Polish equivalent to the English “ooops!”.
When I first found czkawka, the only way to get it on Leap was to compile it yourself. As I was desperate an considered FSLint essential, I learned how to compile Rust programs.
Today, you can download a pre-compile universal gnu/linux binary from the the github project. Works GREAT with openSUSE. You can also install a flatpack: Install Czkawka on Linux | Flathub
For a number of reasons I won’t mention here, I don’t like flatpaks. My misgivings aside:
they generally do work well
they can be automatically updated (“flatpak update” from cli, don’t know if gnome-software / pkcon does this yet or not, but I suspect NOT)
you don’t need to learn anything about building software! A very good choice for the lazy at heart
And before someone hits me with a politically correct correction, in computer speak, LAZY == GOOD. To quote Larry Wall from the introduction to the computer science masterpiece “Progamming Perl”:
We will encourage you to develop the three great virtues of a programmer: *laziness* , *impatience* , and *hubris* .
manythanks for the suggestions
there isn’t a so big quantity of software to use the /home repos, but each software has its /home repo, for example I use sirikali and the last version of gparted and they require two or three /home repos, kde-servicemenu-kim another and so on.
I’m not used to use discover and flatpack but Iwill try, for now I used with zapzap, brave software, caprine and telegramdesktop, with 15.6 seems to be better than 15.5
