In Tumbleweeb huge updates are usual and sometime a conflict can happen. Waiting for a solution of the conflict it would be useful to update all packages excluding that (or these) in conflict.
But in Tumbleweed I can’t find an effective way to partial update.
In Discover when deselect few packages (or select part of the packages) and press “update selected” all packages are updated. This is a bug, quite old and still unsolved.
Command line seems not having a solution for this.
You may (temporarily?) lock some packages to avoid them being upgraded, but sooner or later that might cause unresolvable conflicts and you may be forced to remove the lock.
You can lock a package in YaST Software by highlighting the package and hitting * or by zypper:
zypper addlock <name of package>
See
zypper al --help
for details.
zypper install the-single-package-you-want-to-update
Use YaST instead of Discover.
I agree.
But if you lock a package for come time you could forget it. Is there a way to list all locked package?
This is very useful. Easy to search for the package in GUI and lock it.
Tried this metod that can work only to update few packages.
In Tumbleweed YaST doesn’t show packages to update.
@Giorgio_os yes, zypper locks or zypper ll
YaST Software also shows available updates under Tumbleweed. Packages (version numbers) are marked blue when updates are available…
1 Like
Thanks, what I needed to have a complete list of locked packages.
Interesting. But what I would need is the possibility to deselect few packages (for example packages suspected braking system) and update all selected packages (that can be hundreds).
TW has no routine concept of update[1] as does Leap. When you see available new packages or packages with a newer version available, they normally comprise a component of a newer TW release version, coming from (main) OSS repo, not Updates repo.
[1] TW does have an updates repo. It’s use is uncommon, used almost exclusively for expediting high priority security fixes that bypass the normal TW QA routine. When used, it’s usually one package or one small group of related packages with interdependencies that cannot be installed partially.
If you believe that some of the packages in a new Tumbleweed snapshot will break your system you better wait for the next snapshot (and do a complete upgrade with that snapshot).
Every Tumbleweed snapshot is a standalone release (like Leap 15.5 or Leap 15.6). To install only some packages of a Tumbleweed snapshot would be exactly the same as installing only some of the Leap 15.6 packages when upgrading your Leap 15.5 system to Leap 15.6. The risk to break your system by this is high.
Upgrading from one Tumbleweed snapshot to another can result in many packages (e.g. > 2.000) being replaced. If this is a problem to you (e.g. due to limited download capacity) then you should not use Tumbleweed but Leap.
Not clear to me how to recognise a snapshot. Sometime upgrade include few tenth of packages, sometime several hundreds.
OK. Usually I update all packages available, only this time my system is broken.
Now in Discover only selected packages are updated then it seems that bug is solved.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.