Please format the posted text for better readability.
Highlight the text and press Ctrl-E.
1 Like
The single package (xed) did not update because you probably entered a number when yay prompted you “Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)” – and that number corresponed to the package xed.
yay is telling you that if you want to exclude a package from being updated, you need to enter the number of the package (from the numbered list of packages to upgrade). Indeed, yay even warns you that excluding packages from upgrading is a bad idea, as partial updates can break your system.
Normally you do not want to exclude any packages from being updated, so you should not enter a number. In fact the default response is to not enter a number, so just press the ENTER key when it asks if you want to exclude a package from updating. Don’t enter a number.
The issue isn’t with yay, but your pacman configuration is from before the Arch migration that happened three weeks ago.
Just read the following post carefully and compare @joekamprad’s config with yours, line by line. Then apply the changes.
While the pacman.conf will become an issue in the future, the specific problems referenced in this thread are likely caused by a lack of understanding of yay’s “exclude packages” option.
and
However:
1 Like
The package in the latest post that is ignored is in Arch Extra and not an AUR package, so the configuration definitely plays a part in this.
I even doubt if the OP performed the manual intervention in the first place.
OP did not perform the manual intervention, but that is not the issue here. The Community repo is still working, but it’s empty. Eventually it will be nuked, and when that happens, anyone who still has it in theor pacman.conf will have problems, but for now it still wotks.
Look, if I add the Community repo back to my pacman.conf, everything still works, and the xed package will be installed, too:
seems indeed like OP is not accepting any suggestions in the thread.
Looks more like ignoring all of them and instead documenting what OP tried on them self…
1 Like
Okay, thnx for that extra info.
I update my machine 4/5 times a day and I use Yay without any hitches. So, there must be something wrong with the config, right?
(Besides the fact @pavlar refused to use the handouts given earlier in the thread)
1 Like
No, it’s not a config issue, the user is inputting a number when yay gives the option to exclude a package from updating.
That’s why it is a different package on different occasions.
2 Likes
Eh, by habit I used pacman directly instead of yay in that last screenshot, but it doesn’t make any differenence. Here’s the output from yay -Syu xed, it also works fine (as xed is not an AUR package).
output
staggerlee>>yay -Syu xed
[sudo] password for staggerlee:
:: Synchronizing package databases...
endeavouros is up to date
core is up to date
extra is up to date
community is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
-> Packages not in AUR: libsidplay
-> sevi-icon-theme-blue-dark: local (r195.ae31a48-1) is newer than AUR (r194.959a351-1)
:: 39 packages to upgrade/install.
39 core/kbd 2.5.1-2 -> 2.6.0-1
38 core/util-linux 2.39-8 -> 2.39-9
37 core/util-linux-libs 2.39-8 -> 2.39-9
36 extra/duktape 2.7.0-5 -> 2.7.0-6
35 extra/electron 22.3.3-1 -> 22.3.13-1
34 extra/fwupd 1.9.2-1 -> 1.9.2-2
33 extra/fzf 0.41.1-1 -> 0.42.0-1
32 extra/glslang 12.1.0-2 -> 12.2.0-1
31 extra/gst-libav 1.22.3-5 -> 1.22.3-6
30 extra/gst-plugins-bad 1.22.3-5 -> 1.22.3-6
29 extra/gst-plugins-bad-libs 1.22.3-5 -> 1.22.3-6
28 extra/gst-plugins-base 1.22.3-5 -> 1.22.3-6
27 extra/gst-plugins-base-libs 1.22.3-5 -> 1.22.3-6
26 extra/gst-plugins-ugly 1.22.3-5 -> 1.22.3-6
25 extra/gstreamer 1.22.3-5 -> 1.22.3-6
24 extra/kio 5.107.0-1 -> 5.107.0-2
23 extra/kwin 5.27.5-2 -> 5.27.5-3
22 extra/libcups 1:2.4.4-1 -> 1:2.4.5-1
21 extra/libde265 1.0.11-2 -> 1.0.12-1
20 extra/libjxl 0.8.1-2 -> 0.8.2-1
19 extra/qt5-base 5.15.9+kde+r155-1 -> 5.15.10+kde+r129-1
18 extra/qt5-declarative 5.15.9+kde+r26-1 -> 5.15.10+kde+r26-1
17 extra/qt5-graphicaleffects 5.15.9-1 -> 5.15.10-1
16 extra/qt5-location 5.15.9+kde+r4-1 -> 5.15.10+kde+r4-1
15 extra/qt5-multimedia 5.15.9+kde+r3-1 -> 5.15.10+kde+r3-1
14 extra/qt5-quickcontrols 5.15.9-1 -> 5.15.10-1
13 extra/qt5-quickcontrols2 5.15.9+kde+r6-1 -> 5.15.10+kde+r6-1
12 extra/qt5-sensors 5.15.9-1 -> 5.15.10-1
11 extra/qt5-speech 5.15.9+kde+r1-1 -> 5.15.10+kde+r1-1
10 extra/qt5-svg 5.15.9+kde+r8-1 -> 5.15.10+kde+r8-1
9 extra/qt5-tools 5.15.9+kde+r1-1 -> 5.15.10+kde+r3-1
8 extra/qt5-translations 5.15.9-1 -> 5.15.10-1
7 extra/qt5-wayland 5.15.9+kde+r55-1 -> 5.15.10+kde+r51-1
6 extra/qt5-webchannel 5.15.9+kde+r3-1 -> 5.15.10+kde+r3-1
5 extra/qt5-webengine 5.15.14-1 -> 5.15.14-2
4 extra/qt5-x11extras 5.15.9-1 -> 5.15.10-1
3 extra/xed -> 3.4.1-1
2 extra/xkeyboard-config 2.38-1 -> 2.39-1
1 aur/google-chrome 114.0.5735.106-1 -> 114.0.5735.133-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
-> Excluding packages may cause partial upgrades and break systems
==>
But I am prompted to make a choice to exclude packages 1,2, or 3. If you do not choose, then the update does not go any further. And if 4 is interrupted
Just hit the ENTER key without inputting a number. You don’t want to exclude any packages.
Whether you believe me or not, I promise you, the specific issue you are having with a random package here and there not updating via yay but updating via pacman have been caused by you entering a number. Just leave it blank and hit ENTER and you won’t have that problem.
2 Likes
Then why even this suggestion of excluding packages?
Occasionally there are packages that can be problematic, due to a bug in the package or an incompatibility with other packages. In that specific case, a user might choose to not upgrade a package (or several packages) until the bugs or incompatibilities are corrected upstream. This is not common, but it can happen.
For this reason, the option is given to exclude one or more packages from an update, but unless you have a very good reason to do so plus you know what you are doing, you should never exclude a package from an update. Partial updates can break your system. So don’t do it.
4 Likes
Thanks
1 Like
It wouldn’t hurt to perform that manual intervention I was talking about earlier. Just to avoid future issues. 
I tried ENTER Everything is fine. Why not write on the command line something like "To continue without exception, press ENTER?Or ENTER is it a divine word and must itself fly down from heaven?
We didn’t design and develop yay, working with a terminal user interface does mean careful reading.
A part from your topic, there has been an upstream infrastructure change by Arch. Since we are Arch-based, it is necessary to perform those steps described in the “Arch is moving to GIT packaging” article.
You only have to perform those steps once, after that your system is ready for the change Arch has made.
yay -S upgrade
2 Likes
no such package … may you are searching for rolling?
–closing–
2 Likes