This is not an issue here it’s actually a protection put in place to avoid update surprises. What yum is telling you is that it found a new eos-xrootd version that it can update to namely (4.12.1) but the currently installed eos-client (for example) has an explicit dependency on eos-xrootd-4.11.3 - therefore this update will not go through. Which is exactly what we want.
You can/should exclude “eos-*” from the automatic yum updates as you hardly ever want this to happen without your knowledge.
Hi! I see… there is no automatic updating service, myself is enough for the entire datacenter
I prefer to be always on the latest version, as any bugs encountered on the latest versions are the most likely to get the most attention from the developers