zypper-1.14.70 will support a new option: 'dup --remove-orphaned' to remove all unneeded orphans.
...and not just the ones otherwise blocking the dup. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres (he/him/his), Engineering & Innovation, ma@suse.com +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH www.suse.com Frankenstr. 146, 90461 Nuernberg, Germany Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg) +------------------------------------------------------------------+
On 2024-03-25 14:31, Michael Andres via openSUSE Factory wrote:
...and not just the ones otherwise blocking the dup.
Could you not have reused the solver.upgradeRemoveDroppedPackages code path here and treat every snapshot as such an event? May I point out multiversion packages, specifically kernel-default, that may not see special handling here? Kernels in Tumbleweed would immediately be considered orphaned and removed before the new kernel is ever booted into successfully - this conflicts with the documented intent of multiversion.kernels and the cleanup job. Andreas
Hello Michael Am Montag, 25. März 2024, 14:31:50 CET schrieb Michael Andres via openSUSE Factory:
...and not just the ones otherwise blocking the dup.
an option dup --offline could as well be helpful if one has loaded the update beforehand (-d) and wants/needs to install without internet access. Or is there already a way to do this? Cheers Axel
On 2024-03-25 21:20, Axel Braun wrote:
Am Montag, 25. März 2024, 14:31:50 CET schrieb Michael Andres via openSUSE Factory:
...and not just the ones otherwise blocking the dup. an option dup --offline could as well be helpful if one has loaded the update beforehand (-d) and wants/needs to install without internet access. Or is there already a way to do this?
Implicitly, --no-refresh Andreas
Am Montag, 25. März 2024, 21:38:08 CET schrieb Andreas Stieger via openSUSE Factory:
On 2024-03-25 21:20, Axel Braun wrote: Am Montag, 25. März 2024, 14:31:50 CET schrieb Michael Andres via openSUSE Factory: ...and not just the ones otherwise blocking the dup. an option dup --offline could as well be helpful if one has loaded the update beforehand (-d) and wants/needs to install without internet access. Or is there already a way to do this?
Implicitly, --no-refresh
Thanks Andreas, Adam, Michael, was not aware that this triggers kinda offline handling! Axel
On Monday 25 March 2024 21:20:07 Axel Braun wrote:
Hello Michael
Am Montag, 25. März 2024, 14:31:50 CET schrieb Michael Andres via openSUSE Factory:
...and not just the ones otherwise blocking the dup.
an option dup --offline could as well be helpful if one has loaded the update beforehand (-d) and wants/needs to install without internet access. Or is there already a way to do this?
What about zypper dup --download-only zypper --no-refresh dup -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres (he/him/his), Engineering & Innovation, ma@suse.com +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH www.suse.com Frankenstr. 146, 90461 Nuernberg, Germany Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg) +------------------------------------------------------------------+
W dniu 25.03.2024 o 21:20, Axel Braun pisze:
an option dup --offline could as well be helpful if one has loaded the update beforehand (-d) and wants/needs to install without internet access. Or is there already a way to do this?
Cheers Axel
Yes, there is. download packages: zypper dup --download-only install them from local cache: zypper --no-refresh dup
On 03-25-2024 08:31AM, Michael Andres via openSUSE Factory wrote:
...and not just the ones otherwise blocking the dup.
Would passing the command then wipe out needed existing orphaned files? e.g. On the machine here there are important and needed printer and scanner packages.
On Monday 25 March 2024 22:30:26 -pj via openSUSE Factory wrote:
On 03-25-2024 08:31AM, Michael Andres via openSUSE Factory wrote:
...and not just the ones otherwise blocking the dup.
Would passing the command then wipe out needed existing orphaned files? e.g. On the machine here there are important and needed printer and scanner packages.
'Needed' is 'required by other packages', not 'important for user or functionality'. If you have important packages, you can kind of un-orphan them by putting them into a plaindir repo: mkdir /LocalRepo zypper ar -f /LocalRepo LocalRepo Put the .rpms into the directory and they will no longer be treated as an orphan. In case they somehoe block a later upgrade an conflict will be raised rather than removing them. Another option is to lock the important packages, so dup won't touch them. zypper al PKG.. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres (he/him/his), Engineering & Innovation, ma@suse.com +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH www.suse.com Frankenstr. 146, 90461 Nuernberg, Germany Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg) +------------------------------------------------------------------+
participants (5)
-
-pj -
Adam Mizerski -
Andreas Stieger -
Axel Braun -
Michael Andres