Hi, there!
I’m running oenSuse 13.2. After fresh install, I removed some applications like Amarok, KRDC and so on.
But, every time I want to install a new application by mean Yast Software Management, it add those applications as “Automatic changes”.
Mark the packages you don’t want to have installed as “Taboo - Never install”.
Or even better, enable the option “Ignore recommended packages for already installed packages” in YaST’s “Options” menu.
Otherwise they will be marked for automatic installation again and again, as they are recommended by the KDE patterns.
(you could of course uninstall the patterns as well…)
On 2014-11-24 17:46, gogalthorp wrote:
>
> Mark the package not to be installed
In 13.2 it is not enough, you have to taboo them, because it wants to
install “reccomends” for already installed packages, not only new
packages. It does not remember that you removed them.
Apparently, this is a removed feature in 13.2. Or a new feature, if you
prefer, kind of intentional…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Well, this is actually not new, it was the same behaviour in 13.1 and earlier.
The default was to also install recommended packages for already installed packages there already.
That’s why you got a lot of packages marked for installation when you first entered YaST, especially when you installed from the LiveCD (which contains fewer packages than the full DVD, so not all recommended packages can be installed during the initial installation).
But, as you say, in earlier versions it remembered packages you uninstalled and never installed them automatically again (unless required).
On 2014-11-25 00:36, wolfi323 wrote:
>
> robin_listas;2678727 Wrote:
>> In 13.2 it is not enough, you have to taboo them, because it wants to
>> install “reccomends” for already installed packages, not only new
>> packages.
> Well, this is actually not new, it was the same behaviour in 13.1 and
> earlier.
Huh, no, I’m on 13.1 and I don’t have that problem.
> But, as you say, in earlier versions it remembered packages you
> uninstalled and never installed them automatically again (unless
> required).
Exactly, that’s why 13.1 doesn’t have that problem
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
But it caused other problems. Any time you uninstalled something it wanted to stay uninstalled or caused weird problems. I had problem with the NVIDIA drive because I experimented and uninstalled GO2 then installed GO3 when I changed video cards. This caused a default kernel and and default NVIDIA drivers to be installed at next update. It is much better to have the user black list a package if they don’t want it. I caught the problem but other did not and several had a bit of trouble with default kernels being dragged in. Another option might be a special check mark if the package is black listed buy the system because it was removed allowing you to remove it from the not install list. But I still would rather mark it myself to not reinstall. Always give the user the choice.
Of course you have.
But only for packages that you did not uninstall yet.
So, let’s say you installed from the LiveCD (the full DVD should already install all recommended packages in the first place).
When you enter YaST the first time, a lot of recommended packages get selected to be installed.
If you just deselect them, they’ll get selected again the next time you enter YaST.
Or try to remove the SoftLocks file (/var/lib/zypp/SoftLocks), and all those recommended packages will get automatically selected for installation again. Unless you disabled “Ignore recommended packages for already installed packages” or the installation of recommended packages altogether of course.
Or if you remove recommended packages with “rpm -e”, YaST will want to install them again as well, as they don’t get soft-locked then (this is a feature of libzypp, which is circumvented in this case).
> But, as you say, in earlier versions it remembered packages you
> uninstalled and never installed them automatically again (unless
> required).
Exactly, that’s why 13.1 doesn’t have that problem
The SoftLocks feature was removed, which existed upto 13.1, yes.
But my point was that recommended packages (recommended by already installed packages) that you never explicitely uninstalled will still get installed automatically, even on 13.1 (with the default settings). That feature is not at all new in 13.2.
So, again, just deselecting them won’t help much (not on 13.2 and not on 13.1 either), as you would have to do this over and over again, also on 13.1.
> On 2014-11-25 00:36, wolfi323 wrote:
> >
> > robin_listas;2678727 Wrote:
> >> In 13.2 it is not enough, you have to taboo them, because it wants
> >> to install “reccomends” for already installed packages, not only
> >> new packages.
> > Well, this is actually not new, it was the same behaviour in 13.1
> > and earlier.
>
> Huh, no, I’m on 13.1 and I don’t have that problem.
>
> > But, as you say, in earlier versions it remembered packages you
> > uninstalled and never installed them automatically again (unless
> > required).
>
> Exactly, that’s why 13.1 doesn’t have that problem
>
Funnily enough, 13.1 did have that problem during the development phase,
at least it did with one set of apps. For every new install, each time
I deleted packagekit apps and apper, I had to taboo a couple of them to
prevent automatic re-installation. However, the final release - and
perhaps the RC? - had this “feature” removed.
This all happened again with 13.2 testing and I naturally assumed it
would go away again but, unfortunately, it didn’t.
–
Graham Davis [Retired Fortran programmer - now a mere computer user]
openSUSE Tumbleweed (64-bit); KDE 4.14.3; AMD Phenom II X2 550
Processor; Kernel: 3.17.2; Video: nVidia GeForce 210 (using nVidia
driver); Sound: ATI SBx00 Azalia (Intel HDA)
Yes. The “SoftLocks” feature was removed on purpose because it caused unexpected behaviour/problems especially (but not only) with KMP packages, as mentioned already.
AIUI, “Ignore recommended packages for already installed packages” should actually be enabled by default, but isn’t because of a bug: http://bugzilla.opensuse.org/show_bug.cgi?id=902394