I already reported the answer to this question above. Read all my messages
Listen, if you can not answer, then do not fool me
No point in trying to help you if you are not going to cooperate. You did not share the output of that command.
Good like with your problem, I’m out.
You don’t need me for that, you’re doing fine yourself.
I’m not going to answer the same question ten times
Once would have been enough, but okay… 
If you want to have a constructive dialogue, take the time to read all the messages above
You’re acting as if you’re doing me a favour for letting me help you. 
You just take my time
You could have shared the output of that command 20 times by now, instead of whining about your time being precious…
Good luck getting help with that attitude, I’m out of here.
2 Likes
I will use pacman better - there are no such messages
==> Packages to exclude: (eg: “1 2 3”, “1-3”, “^4” or repo name)
→ Excluding packages may cause partial upgrades and break systemsIt is not clear to me why such a message appears and can it be removed from the update process?
Add to the YAY settings file
~/.config/yay/config.json
it is
{
"combinedupgrade": false
}
OR
use yay -Syu --nocombinedupgrade
https://github.com/Jguer/yay/issues/2078#issuecomment-1498949096
2 Likes
Maybe you should stick with windows. People here are willing to help those who actually listen and not argue.
5 Likes
@pavlar Everyone is trying to help you, the issue over here is that the particular package is on the ignore list of your pacman settings, just go to the wiki link I have sent you and read and perform the instructions on ignoring package updates.
2 Likes
pacman will only update packages from the package repositories not builds from AUR (Archlinux User Repository) what holds build instructions to build packages locally to install them… these are not official supported packages as you got over the package repositories… yay is an AUR helper and is tehre to manage thes ebuilds and managing the builded packages… indeed it can also handle packages from repositories…
This message you see is not any way a warning it odders an option to exclude builds from the update in case you need to ignore these… it is not saying anything about an issue or warns about issues with these packages it offers the option only by default:
==> Packages to exclude: (eg: “1 2 3”, “1-3”, “^4” or repo name) → Excluding packages may cause partial upgrades and break systems
the following info about partial upgrades is also only informative… and thats a fact on arch it does not support partial upgrades… this does not say it will always be the case that your systen break if you cause a partial update.
As @Vedun says over my post it is possible to disable this option to show up.
1 Like
check /etc/pacman.conf for this:
cat /etc/pacman.conf | grep zeromq
will show the line with IgnorePkg…
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
1 Like
No you didn’t
1 Like
This may be helpful for you.
community shouldn’t be in your pacman.conf any longer, or at least # out.
Today yay did not update this package: Starting full system upgrade…
warning: xed: ignoring package upgrade (3.4.0-1 => 3.4.1-1). So I updated it with pacman 
pacman.conf
# /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
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
Color
ILoveCandy
#NoProgressBar
#CheckSpace
VerbosePkgLists
DisableDownloadTimeout
ParallelDownloads = 5
# 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
#[testing]
#Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
#[community-testing]
#Include = /etc/pacman.d/mirrorlist
[community]
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
If yay has problem, then why automatically after the system boots up there is an obsessive suggestion to use it? https://ibb.co/wdgfnQT Wouldn’t it be better to write pacman instead of yay here?