Bug 668588

What do you mean by "patterns sometimes deliberately didn't select some packages"? Packages deselected by a user ought to be in the SoftLocks file.

Well, did you run sw_single after an installation? Fact is zypper in doesn't try to install unrelated packages but calling sw_single immediately results in some packages marked for install.

So this would be something for yast to fix (if desired). Don't know whether it is set globally in the pkg-bindings, or specific to the sw_single modules.

Fixed in yast2-pkg-bindings-2.21.7 - ignoreAlreadyRecommended is set by default to true.

Users can revert to the previous behavior by a new option in the package manager UI ("Ignore Packages for Already Installed Packages" check box in the options menu).

Added in yast2-ncurses-pkg-2.21.1, yast2-gtk-2.22.1, yast2-qt-pkg-2.21.5.

*** Bug 704738 has been marked as a duplicate of this bug. ***

The fix here is too simple and raised bnc#599224.

So let's reopen this one and not pollute 599224 further.
Important comment from ma in 599224#c16:

> For the solver fs-dependencies supplement the always 'installed' system
> package. 
> So in case the solverflags 'ignorealreadyrecommended' (or 'onlyrequires') are
> set, those packages won't be selected.
> 
> - IMO YaST should turn on 'ignorealreadyrecommended' when doing installations
> in unattended modes (i.e. config modules installing packages or yast -i). Those
> acttions should not attract unrelated packages.
> 
> 
> - During system installation/update it should be turned off to resolve this
> bug.
>   (@Ladislav: pls. check whether SLE11SP is affected by this too)
> 
> - Interactive and in the running system a toggle, as it seems to be introduced
> by bnc#668588, is probably OK. 
> 
> A more user friendly solution could be to have an initial solver run (with
> 'ignorealreadyrecommended' off) without any package being selected. If the 
> solver now selects outstanding recommendations, collect them in a list and
> present them to the user. Say 'These are package recommended by your system.
> Decide which of them should be installed and which not.' If the user deselects
> some packages from the list and later commits, they will be weak-locked so they
> won't show up in the list the next time. Also add a 'I'll think about this
> later' button, and if pressed continue with 'ignorealreadyrecommended' turned
> on.

*** Bug 360689 has been marked as a duplicate of this bug. ***

Fixed in yast2-packager-2.21.14 (Factory/12.1) 

(After selecting "Use Btrfs as default Filesystem" option btrfsprogs package is selected to install.)

This is an autogenerated message for OBS integration:
This bug (668588) was mentioned in
https://build.opensuse.org/request/show/82114 Factory / yast2-packager

This is an autogenerated message for OBS integration:
This bug (668588) was mentioned in
https://build.opensuse.org/request/show/82125 Factory / yast2-packager

Reopening (instead of bug#360689) - I'm installing Factory with NET ISO i586-build0298, jfsutils is still not auto-selected for installation.

I just tried with DVD-x86_64-Build0298 and it added the right thing to package list for both btrfs and jfs.

Are you sure that you gave the Factory repo instead of the default 12.1 one?

You can try pressing ctrl-alt-shift-x
and run
grep yast2-packager /.packages.root
it said 2.21.15 for me (which contains the fix) - even on NET+Factory

You're right, this was in fact Milestone 5, not Factory. (I thought a fresh NET iso would default to Factory). I'm closing this again, sorry about the noise.

*** Bug 716639 has been marked as a duplicate of this bug. ***