[zypp-devel] zypper odds
Hi, I have cleaned the rpm db (manually - since zypper did not let me do it) from any packages I do not want, and given that clean slate, let's begin there: beta1:/home/salestv # zypper in sensors Reading installed packages... The following NEW packages are going to be installed: yast2-trans-en_US yast2-registration suseRegister opensuse-manual_en bundle-lang-common-en bash-completion uuid-runtime sensors readline-doc perl-doc perl-TimeDate orbit2 openobex obex-data-server nss-mdns limal-ca-mgm-perl limal-ca-mgm libtasn1-3 libtasn1 libsoup-2_4-1 libsoup libsensors4 libgvfscommon0 libgphoto2 libgnutls26 libgio-2_0-0 libfuse2 libexif libavahi-glib1 libavahi-core5 libavahi-common3 libavahi-client3 libarchive2 gvfs-fuse gvfs-backends gvfs gtk2-branding-upstream gnome-keyring gconf2 fuse ft2demos checkmedia bluez-libs bash-doc avahi alsa-plugins alsa-oss PolicyKit-doc Overall download size: 29.1 M. After the operation, additional 61.5 M will be used. Continue? [YES/no]: No way does sensors need documentation. Why is this counterproductive setting enabled, and where can it be changed? -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Jan Engelhardt wrote:
Hi,
I have cleaned the rpm db (manually - since zypper did not let me do it)
What do mean by this, what didn't zypper let you do?
from any packages I do not want, and given that clean slate, let's begin there:
beta1:/home/salestv # zypper in sensors Reading installed packages...
The following NEW packages are going to be installed:
yast2-trans-en_US yast2-registration suseRegister opensuse-manual_en bundle-lang-common-en bash-completion uuid-runtime sensors readline-doc perl-doc perl-TimeDate orbit2 openobex obex-data-server nss-mdns limal-ca-mgm-perl limal-ca-mgm libtasn1-3 libtasn1 libsoup-2_4-1 libsoup libsensors4 libgvfscommon0 libgphoto2 libgnutls26 libgio-2_0-0 libfuse2 libexif libavahi-glib1 libavahi-core5 libavahi-common3 libavahi-client3 libarchive2 gvfs-fuse gvfs-backends gvfs gtk2-branding-upstream gnome-keyring gconf2 fuse ft2demos checkmedia bluez-libs bash-doc avahi alsa-plugins alsa-oss PolicyKit-doc
Overall download size: 29.1 M. After the operation, additional 61.5 M will be used. Continue? [YES/no]:
No way does sensors need documentation. Why is this counterproductive setting enabled, and where can it be changed?
No setting should do this, it's a bug. But maybe only packaging/dependencies problem. Just in case: retry with --no-recommends command option. Cheers, jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Thursday 2008-04-17 23:03, Jano Kupec wrote:
I have cleaned the rpm db (manually - since zypper did not let me do it)
What do mean by this, what didn't zypper let you do?
It did not let me "do" it because at the same time, it wants to install other things.
No way does sensors need documentation. Why is this counterproductive setting enabled, and where can it be changed?
No setting should do this, it's a bug. But maybe only packaging/dependencies problem. Just in case: retry with --no-recommends command option.
No change in behavior with --no-recommends. zypper *really* needs --explain. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Jan Engelhardt wrote:
Hi,
I have cleaned the rpm db (manually - since zypper did not let me do it) from any packages I do not want, and given that clean slate, let's begin there:
beta1:/home/salestv # zypper in sensors Reading installed packages...
The following NEW packages are going to be installed:
yast2-trans-en_US yast2-registration suseRegister opensuse-manual_en bundle-lang-common-en bash-completion uuid-runtime sensors readline-doc perl-doc perl-TimeDate orbit2 openobex obex-data-server nss-mdns limal-ca-mgm-perl limal-ca-mgm libtasn1-3 libtasn1 libsoup-2_4-1 libsoup libsensors4 libgvfscommon0 libgphoto2 libgnutls26 libgio-2_0-0 libfuse2 libexif libavahi-glib1 libavahi-core5 libavahi-common3 libavahi-client3 libarchive2 gvfs-fuse gvfs-backends gvfs gtk2-branding-upstream gnome-keyring gconf2 fuse ft2demos checkmedia bluez-libs bash-doc avahi alsa-plugins alsa-oss PolicyKit-doc
Overall download size: 29.1 M. After the operation, additional 61.5 M will be used. Continue? [YES/no]:
No way does sensors need documentation. Why is this counterproductive setting enabled, and where can it be changed?
it seems solver wants to install something even if zypper didn't tell it to install anything: $ zypper install foo Reading installed packages... 'foo' not found. The following NEW package is going to be installed: gdm-branding-openSUSE Overall download size: 111.0 K. After the operation, additional 608.0 K will be used. Continue? [YES/no]: n I get a lot more packages on my VBox machine. jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Thu, Apr 17, 2008 at 11:24:59PM +0200, Jano Kupec wrote:
it seems solver wants to install something even if zypper didn't tell it to install anything:
$ zypper install foo Reading installed packages... 'foo' not found.
The following NEW package is going to be installed: gdm-branding-openSUSE
That's probably a 'recommended' package. libzypp actually has the information if this is the case, maybe zypper should show it to the user. Regarding installing recommended packages, this is not a bug in the solver. You need to set a 'keep' lock on the packages you don't want, but persistent keep locks are not yet implemented in libzypp. BTW, deleting recommended packages with 'rpm -e' won't help, as there will be no 'keep' lock created. Thus libzypp will reinstall the packages in the next run. There really is no good way to fix this. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Fri, Apr 18, Michael Schroeder wrote:
Regarding installing recommended packages, this is not a bug in the solver. You need to set a 'keep' lock on the packages you don't want, but persistent keep locks are not yet implemented in libzypp.
for beta2 -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Michael Schroeder wrote:
On Thu, Apr 17, 2008 at 11:24:59PM +0200, Jano Kupec wrote:
it seems solver wants to install something even if zypper didn't tell it to install anything:
$ zypper install foo Reading installed packages... 'foo' not found.
The following NEW package is going to be installed: gdm-branding-openSUSE That's probably a 'recommended' package. libzypp actually has the information if this is the case, maybe zypper should show it to the user.
Indeed, --no-recommends got rid of that package. But my understanding of the dragging of the recommends in was that you only try to install recommends starting from the recommends of the package you _requested_. In this case, no available package was requested. Also, the other mail by Jan (Engelhardt) says that --no-recommends didn't help him.
Regarding installing recommended packages, this is not a bug in the solver. You need to set a 'keep' lock on the packages you don't want, but persistent keep locks are not yet implemented in libzypp.
When will these weak locks be added? Anytime the solver runs with 'no-recommends' and any recommends are found? Upon removal of previously installed recommended package?
BTW, deleting recommended packages with 'rpm -e' won't help, as there will be no 'keep' lock created. Thus libzypp will reinstall the packages in the next run. There really is no good way to fix this.
Of course. 'no-recommends' must be explicitly requested via zypp.conf or CLI parameter. jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Jan Kupec escribió:
But my understanding of the dragging of the recommends in was that you only try to install recommends starting from the recommends of the package you _requested_. In this case, no available package was requested.
I reported a similar misbehaviour in bug #378192 -- "Freedom of religion also means freedom **from** religion" - Anonymous Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
participants (6)
-
Cristian Rodríguez -
Jan Engelhardt -
Jan Kupec -
Jano Kupec
-
Michael Andres -
Michael Schroeder