libalpm.so.11 29 May 2018, 03:15:41 Hello again everyone, I've just updated my Artix systems & have hit a snag, libalpm.so.11 is missing & so expac isn't working, thankfully pacman still works though, when expac stops working the AUR packages all want to update for some reason... all of them by the looks of it want to update! This is reproducable on my second PC too. Creating a symlink from the current libalpm.so.10 to libalpm.so.11 will make everything malfunction - networkmanager, xdm, basically everything from what I can tell.
Re: libalpm.so.11 Reply #1 – 29 May 2018, 08:40:17 I think expac should be on the title and not libpalm Here is a quick sloppy fix till it is really fixed:Code: [Select]sudo ln -s /usr/lib/libalpm.so.10 /usr/lib/libalpm.so.11remember to remove this link before you update libalpm Last Edit: 29 May 2018, 12:12:39 by fungalnet
Re: libalpm.so.11 Reply #2 – 29 May 2018, 15:24:14 Fungalnet did you even read what I wrote? I said creating a symlink from the current libalpm to libalpm.so.11 will make everything malfunction, XDM will even fail to restart. I don't mean to sound rude but I really dislike it when people tell me to do something I've already stated that I've tried...and, when libalpm gets updated, wouldn't I only need to add --force to pacman to overwrite that symlink? Last Edit: 29 May 2018, 15:35:36 by kenny_w
Re: libalpm.so.11 Reply #3 – 29 May 2018, 16:12:46 Are you sure don't just have to rebuild your AUR helper? Admittedly, I haven't had time to update and test this yet, but that's what it sounds like to me.
Re: libalpm.so.11 Reply #4 – 29 May 2018, 16:14:15 Quote from: Dudemanguy – on 29 May 2018, 16:12:46Are you sure don't just have to rebuild your AUR helper? Admittedly, I haven't had time to update and test this yet, but that's what it sounds like to me.I don't believe that will help. The pacman API changed in 5.1.0 which means any software that uses those libraries will need to be updated to use the new API. A symlink won't fix that, and neither will a rebuild.expat will most likely need to be changed to use the new API, until that happens, expat won't work. Last Edit: 29 May 2018, 16:15:49 by Chris Cromer
Re: libalpm.so.11 Reply #5 – 29 May 2018, 16:34:45 Ah, for AUR helpers that rely on package-query (like yaourt), updating package-query from AUR works. Also, the latest trizen from AUR works. Both packages are behind a release version in galaxy.
Re: libalpm.so.11 Reply #6 – 29 May 2018, 16:38:33 Quote from: Dudemanguy – on 29 May 2018, 16:34:45Ah, for AUR helpers that rely on package-query (like yaourt), updating package-query from AUR works. Also, the latest trizen from AUR works. Both packages are behind a release version in galaxy.That is different, AUR helpers are built around makepkg. Expac is built on pacmans libs. 2 totally different pieces of software.
Re: libalpm.so.11 Reply #7 – 29 May 2018, 16:41:48 Quote from: Chris Cromer – on 29 May 2018, 16:38:33That is different, AUR helpers are built around makepkg. Expac is built on pacmans libs. 2 totally different pieces of software.Pacaur actually depends on expac which is what I suspect kenny was using and what is causing his issues. Despite being abandoned for months it actually still worked until this update of course.
Re: libalpm.so.11 Reply #8 – 29 May 2018, 22:06:38 Quote from: kenny_w – on 29 May 2018, 15:24:14Fungalnet did you even read what I wrote? I did, but I thought you didn't make that symlink, because when I did there wasn't a problem. Yaourt worked fine and there was nothing to update. I am more worried of pacman not working right. After upgrading pacman pamac is no longer installable with new pacman.We'll just have to wait for something to catch up with everything else, that's what it seems like. Last Edit: 29 May 2018, 22:22:59 by fungalnet
Re: libalpm.so.11 Reply #9 – 01 June 2018, 15:53:35 Another update seemed to have fixed the problem, thanks though guys.
Re: libalpm.so.11 Reply #10 – 02 June 2018, 06:03:13 Hmm, so it turns out pacaur's author has released one final update for pacman 5.1. So you can still use it for a while.
Re: libalpm.so.11 Reply #11 – 02 June 2018, 17:09:53 One final update for 5.1? What do you mean by that? Is pacaur going to end up unmaintained? :< I like pacaur, its exactly like pacman but with AUR packages.
Re: libalpm.so.11 Reply #12 – 02 June 2018, 17:19:35 Quote from: kenny_w – on 02 June 2018, 17:09:53One final update for 5.1? What do you mean by that? Is pacaur going to end up unmaintained? :< I like pacaur, its exactly like pacman but with AUR packages.The author announced a few months ago that pacaur will be unmaintained. Apparently he already had most of the work done for the upcoming 5.1 pacman release already, so he just pushed those updates to the AUR package for this latest update. So yeah it still works for now, but at some point in the future it'll permanently break. The git repo is already read only and the author says that there's too many fundamental problems with pacaur and a full rewrite would be necessary (which he doesn't want to do).I also think it's a shame since pacaur was by far my favorite AUR helper and I used it for years.
Re: libalpm.so.11 Reply #13 – 03 June 2018, 11:02:21 Quote from: kenny_w – on 02 June 2018, 17:09:53One final update for 5.1? What do you mean by that? Is pacaur going to end up unmaintained? :< I like pacaur, its exactly like pacman but with AUR packages.trizen seems like a good replacement and alternative. I'm using it right now.
Re: libalpm.so.11 Reply #14 – 03 June 2018, 15:31:48 trizen is good but you know what I think after yesterday the latest "yay" is a even better solution it builds packages trizen spits out with errors, yay has come on leaps and bounds of late.
Topic: libalpm.so.11 (Read 4787 times)
previous topic - next topic
Topic: libalpm.so.11 (Read 4787 times)
previous topic - next topic