I updated via pamac, unchecked updating to the NEW pamac and updated kernel, yay, ect… everything went fine or so i thought lol. I now get this
[christopher67@EndeavourOS ~]$ yay
yay: error while loading shared libraries: libalpm.so.15: cannot open shared object file: No such file or directory
[christopher67@EndeavourOS ~]$
Or when i try this
[christopher67@EndeavourOS ~]$ sudo pacman -Syu yay
[sudo] password for christopher67:
:: Synchronizing package databases...
endeavouros is up to date
core is up to date
extra is up to date
multilib is up to date
warning: yay-12.3.5-2 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing pacman (7.0.0.r3.g7736133-1) breaks dependency 'pacman<6.2' required by libpamac-git
this is my pacman.conf:
Make sure to not forget step 4!
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives
#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/
HoldPkg = pacman glibc dracut kernel-install-for-dracut eos-dracut
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
Color
ILoveCandy
#NoProgressBar
CheckSpace
VerbosePkgLists
ParallelDownloads = 5
DownloadUser = alpm
#DisableSandbox
# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required
# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.
#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
[endeavouros]
SigLevel = PackageRequired
Include = /etc/pacman.d/endeavouros-mirrorlist
#[core-testing]
#Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
#[extra-testing]
#Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist
[multilib]
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
Thanks for helping with the pacnew-files. I have overwritten the original files and just restored the latest Timeshift snapshot from yesterday before I updated the system. Now I used the pacdiff tool from the Welcome app and compared / merged the files.
updating now with the pacdiff tool of welcome, I read the thread but something I can’t find the answer yet.
on the makepkg file, Yannick says that
“makepkg ⇒ remove references to rust (merge), but keep compression level.”
but I have another change there.
pacnew: OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge debug lto)
current: OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug !lto !autodeps)
can someone help me understand if I should keep or merge the new?
See this comment on Reddit from an “Arch Linux Support Staff”:
This is only relevant if you create a custom repository (e.g. you have your own server that you want to serve your own packages to other installations from) If nothing that’s discussed in this link https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#Custom_local_repository ring a bell for you, then there’s no need for you to do anything.
A good read about the details is: man makepkg.conf
What to merge depends on what you want to build.
With makepkg.conf you’d typically go with the defaults provided by the .pacnew. But I’d recommend removing adding the exclamation mark (!) in front of debug unless you really want to create debug builds too.
Edit: fixed the recommendation about the exclamation mark.
It is the other way around: ! infront of debug disables the option.
And by removing the exclamation mark (!) in front of debug they will create debug builds as well.
There’s a pkgbuild that was posted on the paru GitHub issues that will compile a compatible build under the paru name so once a new stable build does come out it would automatically update. It’s been working well for me so this could be another option for people who don’t want to manually switch between paru and paru-git once the issue gets resolved.
I have to admit that I don’t understand this thread. When I noticed after installation of pacman 7 that yay didn’t work any longer I thought: ok, let’s wait for a day or two and then yay will be working again. That’s exactly what happened with the update of yay.
