
Am 23.02.23 um 00:49 schrieb Aaron Puchert:
Am 22.02.23 um 11:50 schrieb Rainer Klier:
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 that's not in Tumbleweed at all? In the former case I think you're essentially setting
some of them is for having newer versions of packages than Tumbleweed, some of them are because packages are not included in Tumbleweed.
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.
normally there is no problem in cherry picking for example latest version of thunderbird from thunderbird repo. if it doesn't work, i always can disable extra repo, and downgrade thunderbird to the version from Tumbleweed. and this approach works for nearly all those packages from extra repos. the only trouble i ever ran into was when packages from Tumbleweed repo became updated (for example, systemd and yast) and i manually cherry picked them in yast and updated, and then system wasn't booting into grafical runlevel or yast was not any more working, which both then produces the problem, that starting yast and fixing the system by additionally also updating some missed packages is then not possible.... and all those situations, where i ran into trouble was, because there were some packages, which i didn't know there were also needed to be updated, and package management didn't auto-select them. other from that, i never had problems when updating for example thunderbird, firefox, VLC, remmina, or other packages from extra repos.
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?
no. because i don't have an extra repo for yast, but i have one for firefox. but packages for both are exsiting in Tumbleweed repo.
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.
what i mean is, that if there is an update for yast2-fonts, i select this package in yast and update it, rather then running "zypper dup" which then maybe pulls also some updates for things which are not important for me, like for example some updated localization files.
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.
yeah, maybe i can achive what i want/need by using this "--from <alias>" to zypper dup only packages from original Tumbleweed repo. i have to try. -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development