-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jay Mistry wrote:
On Mon, Mar 30, 2009 at 5:56 PM, Jan Kupec
wrote: # rpmdb --rebuilddb # zypper refresh -b # zypper up
Doing the above, after su to root from init 3, gives a totally different set of packages (which are correct, going by the version numbers), than what YaST (GUI : YAST --> Software Management) shows. How did you try to update via YaST?
As mentioned, (at that time) I had logged into Yast (as root) & then -> Software Management.
OK, this preselects a few packages for update automatically, if available (the same which 'zypper inr' would install). But what did you do then? Did you choose "Upgrade all packages to newer version if available" (that should be roughly equivalent to 'zypper up', but i'm not exactly sure) or something like that?
Presently, I generally do updates (via Yast GUI, and only when major new releases are brought in) after filtering 'By Repository' or 'By Package Group'; I find this gives me much greater control over what and how many packages to update - eg, for the KDE 4 Factory Repo [1];
Yes, that is a good approach for your case. Although you can do this with zypper as well ('zypper lu', 'zypper up package1 package2 ...'), it is more convenient to this in yast GUI in this case.
I avoid updating bandwidth-consuming packages that are unnecessary to be updated- such as 'oxygen-icon-theme', 'kdebase4-wallpapers', games, etc. Doing 'zypper -up' gives the whole gamut of updates for that repository- including many packages that I do not need.
The only way that we could make this more convenient on command line would be to allow the user to feed zypper with a list of package names s/he wants to get updated from a file (that would be handy for a GUI as well). Alternatively, package locks (Taboo/Protected in YaST, 'zypper *lock*' commands) can be used to avoid updates of specific packages.
..... Search showed me the yast2 Repair Tool at http://packages.opensuse-community.org/packageinfo.jsp?checksum=b508b5f52d3fb7f50e083e94580093e919dbc794&distro=openSUSE_111 . Any idea what this does ? how I can repair YaST GUI to accurately show updates and packages ?
Can you shed any light on this (Yast2 Repair Tool) ? I have not been able to get any information on what it is supposed to do (in an installed openSUSE system) ?
The Repair module is described here: http://en.opensuse.org/SDB:YaST_System_Repair - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknR+icACgkQgEhGpmN+6QHueACfakSUN66NKgeMbippbDGFGrXn U3YAnRoAQAr+PwAtTQgrsUiYYUQ22X+K =OIpf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org