FS#79323 - [vim] libperl.so: cannot open shared object file: No such file or directory

Attached to Project: Arch Linux
Opened by Luke Yeager (lukeyeager) - Monday, 07 August 2023, 15:58 GMT
Last edited by Robin Candau (Antiz) - Monday, 07 August 2023, 16:39 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

$ vim
vim: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory
$ pacman -Q vim
vim 9.0.1676-2
$ pacman -Q perl
perl 5.36.1-2
$ grep perl /var/log/pacman.log
[2023-08-07T10:05:36-0500] [ALPM-SCRIPTLET] WARNING: '/usr/lib/perl5/5.38' contains data from at least 22 packages which will NOT be used by the installed perl interpreter.
[2023-08-07T10:05:36-0500] [ALPM-SCRIPTLET] -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/5.38'

Looks like the same issue happened when perl was upgraded from 5.34 to 5.36: https://bbs.archlinux32.org/viewtopic.php?id=3245
This task depends upon

Closed by  Robin Candau (Antiz)
Monday, 07 August 2023, 16:39 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Partial update/inconsistent mirror issue: vim 9.0.1676-2 (rebuild against perl 5.38) but still perl 5.36.1-2 installed on the system.
Fixed by updating the system again.
Comment by Luke Yeager (lukeyeager) - Monday, 07 August 2023, 16:03 GMT
Temporarily solved by downgrading: pacman -U /var/cache/pacman/pkg/vim{,-runtime}-9.0.1676-1-x86_64.pkg.tar.zst
Comment by Robin Candau (Antiz) - Monday, 07 August 2023, 16:09 GMT
This is a partial update issue. Your perl package is outdated, the current one is v5.38.0-1.
Comment by Luke Yeager (lukeyeager) - Monday, 07 August 2023, 16:19 GMT
I agree. I ran '-Syu' again and now I see the 5.38 perl package. Upgraded and I'm good to go. Good to close.

You say "a partial update issue" as if this is a normal thing. Is it expected for the package lists to be in an inconsistent/dangerous state like this? I have used arch for a few years and, as far as I can remember, this is the first time I've had an update install inconsistent versions.
Comment by Robin Candau (Antiz) - Monday, 07 August 2023, 16:35 GMT
It is not expected, but I'm not saying it was necessarily your fault. You probably had a bad timing moment (updating your system while the packages were being moved after the perl 5.38 rebuild and your mirror was catching up)...

If such issues happens in the future, eventually make your sure your mirrors (and your system) are fully up to date :)

Loading...