Am Montag, 4. März 2019, 01:21:19 CET schrieb Patrick Shanahan:
* Maximilian Trummer <maximilian@trummer.xyz> [03-03-19 18:53]:
Am Sonntag, 3. März 2019, 18:32:07 CET schrieb Patrick Shanahan:
* Maximilian Trummer <maximilian@trummer.xyz> [03-03-19 11:52]:
I'm trying to do a 'zypper dup' on a headless server, but it wants to install a load of unnecessary packages. Many of them are gtk stuff, but also cryptsetup, mdadm, PackageKit and fuse.
you don't say, but suggest: zypper -v --no-r --no-allow-v dup
The upgrade would be from the currently running 20190222 to 20190301, which upgrades the schemes 'base', 'basesystem' and 'minimal_base'.
How can I find out what package is trying to pull in these new dependencies?> > try first the above and it may solve itself
if you still get unwanted pkgs, try adding specific locks
--no-recommends is just a temporary fix, those packages will still get --pulled in the next time or when using 'zypper install-new-recommends'.
I would add 'specific locks' if I actually knew what other package wants to install e.g. adwaita-icon-theme.
allow install of adwaita-icon-theme, then rpm -e adwaita-icon-theme rpm will advise you what it must erase to accomplish and you will have your answer.
is that the only unwanted app that remains when using --no-r ?
and you can set "--no-recommends" to be default in /etc/zypp/zypp.conf and use "--recommends" or --r to over-ride when needed. rpm -e $package just deletes the package because it's not a hard dependency.
I got another machine now that installed the chromium browser on 'zypper dup' for whatever reason. 'zypper se --recommends chromium' yields no results...