slarm64This forum is for the discussion of slarm64.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
All your extra packages seem to be built on Current. That's not good for a guy like me who tried to stay on 15.0, because this sort of thing happens:
Code:
dec@SparrowFart:~/Downloads$ ldd /usr/lib64/chromium/chromium |grep found
/usr/lib64/chromium/chromium: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by /usr/lib64/chromium/chromium)
/usr/lib64/chromium/chromium: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /usr/lib64/chromium/chromium)
/usr/lib64/chromium/chromium: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib64/chromium/chromium)
libavcodec.so.59 => not found
libavformat.so.59 => not found
libavutil.so.57 => not found
libFLAC.so.12 => not found
Incidentally, ffmpeg & libFLAC are requirements for Chromium.
If you're not doing packages for 15.0, I'd probably be better updating to Current fairly often, wouldn't I? I have a stable release, but no extra packages.
Yes, additional packages are updated for current, I don't use 15.0 on my boards (except aarch32).
I'll leave it until the 6.2.x kernels come along with their enhanced graphics. Please wait for at least 6.2.0.1 because those sort of things always seem to give out their bugs once the masses get their hands on them.
I'll evidently have to start keeping an eye on the ChangeLog too, as packages are dropped and new ones stuck in. Alien Bob had me kind of spoiled because his x86_64 repo has 15.0 & current.
EDIT: [Looking at ChangeLog] All I need is a smart line with sed to delete every entry in the ChangeLog with "Upgraded" or "Rebuilt" in them, and I'm left with the ones you added or dropped. Alternatively I could just grep for 'Added' or 'Dropped' which is probably lazier.
Last edited by business_kid; 12-03-2022 at 11:17 AM.
It's on Alien Bob's blog (or blurb) that chromium-107 was a quick fix to patch something being used in the wild. But in closing one door, it opened another. I'm posting this from x86_64 on Ungoogled-Chromium-108.0.5359.94, which patches the new fault introduced on 107.<whatever>. It might be good to get that one instead.
What glibc is that compiled against? I'm on 2.33 here. I just dread all the work changing things over and my neat little shortcuts that I had worked out to update.
What glibc is that compiled against? I'm on 2.33 here. I just dread all the work changing things over and my neat little shortcuts that I had worked out to update.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
