Comment # 66 on bug 1182666 from B

(In reply to Stefan Dirsch from comment #64)
> (In reply to B from comment #57)
> > (In reply to Stefan Dirsch from comment #56)
> > > No, that's just a package update. First the files of the new package are
> > > installed, then the files of the old package which are not part
> > > of the new package are uninstalled. At last the %triggerpostun of
> > > nvidia-gfxG05-kmp-default is running. At that point there is
> > > kernel/ subdir. Check this out.
> > > 
> > > https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/
> > > #ordering
> > 
> > Yes, I read the link but I'm saying is that I observed it differently.
> > When you run zypper dup the summary for package updates usually says "The
> > following X packages are going to be upgraded: ..." but with the
> > kernel-default 5.11.4-1.2 -> 5.11.4.-1.3 it was:
> > "The following packages will be removed: kernel-default-5.11.4-1.2" 
> > "The following packages will be installed: kernel-default-5.11.4-1.3"
> > 
> > So in this specific situation that ordering doesn't apply, a package gets
> > removed, a new one installed and that's how those Nvidia modules in
> > /lib/modules/$kernel/updates/ get deleted.
> 
> Puh. If this is true, it would mean zypper would handle package updates
> different than RPM. I verified with rpm -vv that things are done in the
> right order during kernel-default Update and nvidia modules weren't removed
> afterwards when updating kernel-default 5.11.4-1.2 -> 5.11.4.-1.3.

I looked up that zypper also has extra flags for more verbosity

>-v, --verbose
>           Increase verbosity. For debugging output specify this option twice.

I'll try to do some installations/updates with zypper -vv, maybe it will show
what's happening more precisely.