Am 22.02.23 um 01:45 schrieb Aaron Puchert:
But maybe this isn't about Factory itself but rather third-party repositories? (In which case others on the thread mentioned a flag that might help.)
yes, often the packages i want to update are coming from extra repositories.
i have, for example, extra repos configured for Xorg, libreoffice, KDE, kernel, extra kernel-modules (wlan, vbox) That sounds like a lot. Are these all devel repos? What is the reason for that? Having even newer versions than Tumbleweed or having software
Am 22.02.23 um 11:50 schrieb Rainer Klier: that's not in Tumbleweed at all? In the former case I think you're essentially setting yourself up for trouble, especially with so many repositories. In the latter case I'd recommend giving these repos higher priority (numerically, which means a lower priority), so that packages from these repos are only used if the software isn't in Tumbleweed.
most of the time updating packages from those repos don't produce problems.
but there are also sometimes packages listed in those tumbleweed snapshot emails, which are only existing in the main tumbleweed repos, or for which i don't have an extra repo. Well, shouldn't this be the general case? Or are you not actually running Tumbleweed but a union of development repositories? and i don't want to update the whole tumbleweed system, only because for example yast2-fonts is released in a new version. that's the main reason for using that approach.
What do you mean with "update the whole tumbleweed system"? If only yast2-fonts has been released in a new version, you should generally only get an update for that if you do "zypper dup". Unless of course you're using development repositories, which rebuild whenever any dependency changes. For what it's worth, I'm very sympathetic to keeping updates small. But you should be able to get that with "zypper dup" and not have to manually select packages. Aaron