" the pacman-key tool, crucial for security in package signing, now correctly handles permission checks for operations performed without root access, an essential update for maintaining security in multi-user environments."
I like this. And this:
" brings numerous fixes and enhancements that bolster the robustness and reliability of the package manager. Notably, it ensures that both database updates and signatures are retrieved from the same location, streamlining the update process and addressing issues previously noted with XferCommand."
but this?ā" introduces the DisableSandbox option alongside a --disable-sandbox flag. This feature allows download write restrictions to be disabled, which is useful in scenarios where users operate within a secured or customized environment."
The reason you would download/install (pacman) something from the repo with its write restrictions disabled is to build or fork it, right? Had no idea repo packages came with write-restrictions I guess I never looked.
Whoa! Pacman 7.0? Thank You @swh I need to look at that a bit. 
Dear Sir,
i still have pacman version 6.1.0 on my endeavouros system, will pacman v7 be available soon through updates ?
Kind regards,
JP
We all have 6.1.0-3.
Watch your updates. As soon as 7.0 is in the repos, you will receive it.
Welcome to the 
-Forum 
Pacman7 is now in core repo
āÆ yay
[sudo] Passwort fĆ¼r swh:
:: Paketdatenbanken werden synchronisiert ā¦
endeavouros ist aktuell
core 117,6 KiB 1176 KiB/s 00:00 [--------------------------------------------------------------------] 100%
extra 7,4 MiB 5,55 MiB/s 00:01 [--------------------------------------------------------------------] 100%
multilib ist aktuell
:: Durchsuche AUR nach Updates...
:: Durchsuche Datenbanken nach Updates...
-> Pakete nicht im AUR: knotes
-> Verwaiste (nicht gepflegte) AUR-Pakete: aeskulap
-> Als nicht aktuell markierte AUR-Pakete: otf-ibm-plex
:: 18 Pakete zu upgraden/installieren.
18 core/pacman 6.1.0-3 -> 7.0.0.r3.g7736133-1
17 extra/android-tools 35.0.2-3 -> 35.0.2-4
16 extra/expac 10-10 -> 10-11
15 extra/kosmindoormap 24.08.1-2 -> 24.08.1-3
14 extra/libopenshot 0.3.3-5 -> 0.3.3-6
13 extra/libpackagekit-glib 1.2.8-8 -> 1.3.0-1
12 extra/libphonenumber 1:8.13.45-1 -> 1:8.13.45-2
11 extra/marble-common 24.08.1-2 -> 24.08.1-3
10 extra/marble-maps 24.08.1-2 -> 24.08.1-3
9 extra/marble-qt 24.08.1-2 -> 24.08.1-3
8 extra/opencv 4.10.0-7 -> 4.10.0-9
7 extra/packagekit 1.2.8-8 -> 1.3.0-1
6 extra/pacman-contrib 1.10.6-1 -> 1.10.6-2
5 extra/pacutils 0.14.0-1 -> 0.14.0-2
4 extra/protobuf 28.0-2 -> 28.1-1
3 extra/protobuf-c 1.5.0-5 -> 1.5.0-6
2 extra/strawberry 1.1.2-1 -> 1.1.2-2
1 extra/vlc 3.0.21-3 -> 3.0.21-4
==> Pakete zum AusschlieĆen: (z.B. "1 2 3", "1-3", "^4" oder Repo-Name)
-> Das AusschlieĆen von Paketen kann zu teilweisen Aktualisierungen fĆ¼hren und Systeme beschƤdigen.
==>
After the update and restart, yay no longer works:
[darius@eos-pc ~]$ yay
yay: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory
Yes, same here. And pacseek didnt even work. We need a new topic to be able to correct the error
I got this error and fixed it in probably a fairly inelegant way - simply reinstalling yay by rebuilding from git fixed it 
For error take a look here
Yea, looks to be a matter of Yay needing to get the latest libalpm.so.
https://archlinux.org/news/manual-intervention-for-pacman-700-and-local-repositories-required/
Manual intervention for pacman 7.0.0 and local repositories required
Sept. 14, 2024 - Morten Linderud
With the release of version 7.0.0 pacman has added support for downloading packages as a separate user with dropped privileges.
For users with local repos however this might imply that the download user does not have access to the files in question, which can be fixed by assigning the files and folder to the alpm group and ensuring the executable bit (+x) is set on the folders in question.
$ chown :alpm -R /path/to/local/repo
Remember to merge the .pacnew files to apply the new default.
Pacman also introduced a change to improve checksum stability for git repos that utilize .gitattributes files. This might require a one-time checksum change for PKGBUILDs that use git sources.
Hereās the Arch Newsfeed release on itā¦
With the release of version 7.0.0 pacman has added support for downloading packages as a separate user with dropped privileges.
For users with local repos however this might imply that the download user does not have access to the files in question, which can be fixed by assigning the files and folder to the alpm group and ensuring the executable bit (+x) is set on the folders in question.
$ chown :alpm -R /path/to/local/repo
Remember to merge the .pacnew files to apply the new default.
Pacman also introduced a change to improve checksum stability for git repos that utilize .gitattributes files. This might require a one-time checksum change for PKGBUILDs that use git sources.
Ok, Iām not quite up to speed with it yet, so what does this mean for us as EOS users? As far as I can see, we donāt have any local repos active, do we?
You most likely have to do nothing, except if you have packages that depend on pacman, like yay, paru, pacseek, etc.
For example I am using paru and it doesnāt work right now.
Is it helpful to rebuild paru?
No idea. Iāll just wait for the bin version to update and reinstall that manually.
Edit: Rebuild does not work according to a comment inside the paru repo. creating a symlink does, though.
No, the current version of paru supports libalpm v14, not v15.
this version of alpm.rs does not support libalpm v15.0.0 only v14.x.x is supported
stack backtrace:
0: 0x557c58267205 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hd736fd5964392270
...
...
warning: build failed, waiting for other jobs to finish...
Is this related to the error I just received using PARU this morning?
[mark@mark-optiplex9020 ~]$ paru
[sudo] password for mark:
:: Synchronizing package databasesā¦
endeavouros is up to date
core is up to date
extra is up to date
multilib is up to date
:: 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 ālibalpm.so=14ā required by libpamac-aur
:: installing pacman (7.0.0.r3.g7736133-1) breaks dependency āpacman<6.2ā required by libpamac-aur
[mark@mark-optiplex9020 ~]$
Another issue with Pacman 7:
It cannot access my own Pacman repository in my local.
$ sudo pacman -Syu
:: Synchronizing package databases...
zesko_repo.db failed to download
core is up to date
extra is up to date
error: failed retrieving file 'zesko_repo.db' from disk : Couldn't open file /media/share/zesko_pacman_repo/zesko_repo.db
error: failed to synchronize all databases (failed to retrieve some files)
My pacman config
[zesko_repo]
Server = file:///media/share/zesko_pacman_repo
But rolling back to Pacman 6 works without any issues.
Edit:
I fixed the issue by disabling a new feature
DownloadUser = alpmor changing it to a user dependent permission.