YaST (Software Management) and zypper give different package update results

[Jay Mistry]

I find that YaST --> Software Management (YaST GUI) and zypper (#
zypper up, after # zypper refresh) give different results for Software
Package updates (particularly for the KDE 4.2 packages).

This was after I did the 1-click install of KDE 4.2 (upgrade from KDE
4.1.3), from this page - http://en.opensuse.org/KDE4. This persisted
even after I deleted the KDE 3.5.x and KDE 4.1.4 repos (as given on
this page: http://en.opensuse.org/KDE/Repositories).

Is this a bug ? If additional system data is required to troubleshoot,
pl let me know.

Jay

[Jay Mistry]

YaST does not show the same packages that zypper (through konsole,
after su -) does. This was after I updated to KDE 4.2; also have KDE
3.5 installed.

# 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.

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 ?

Thanks,

Jay

[Allen Zhu]

Post by Jay Mistry
YaST does not show the same packages that zypper (through konsole,
after su -) does. This was after I updated to KDE 4.2; also have KDE
3.5 installed.
# 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.
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 ?
Thanks,
Jay
--
http://www.smolts.org/client/show/?uuid=pub_b541a450-9bc1-45fd-beab-d46ee43a0108
--

Seems as if it replaces YaST modules based on the file contents of the
package...

Allen

[Jan Kupec]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Jay Mistry
YaST does not show the same packages that zypper (through konsole,
after su -) does. This was after I updated to KDE 4.2; also have KDE
3.5 installed.

The behavior of YaST does not depend on KDE or QT, the problem must be
somewhere else.

Post by Jay Mistry
# 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?

- --
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

iEYEARECAAYFAknQunoACgkQgEhGpmN+6QHLlgCdG644qSnq57+K1ET5zC6juu32
7O4An0rx7eRJ88fG7qvliNu2qO/DKC/5
=UhYX
-----END PGP SIGNATURE-----

[Jay Mistry]

Post by Jan Kupec
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Jay Mistry
YaST does not show the same packages that zypper (through konsole,
after su -) does. This was after I updated to KDE 4.2; also have KDE
3.5 installed.

The behavior of YaST does not depend on KDE or QT, the problem must be
somewhere else.

Post by Jay Mistry
   # 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.

_Note_
However, please note that this may have been en error on my part, as I
do not recall exactly what or how many packages were separately given
by Yast & zypper and what repositories I had in Yast- subsequently, I
changed these to get a working KDE 4.2.1 install. This was during the
time when KDE 4.2 was newly released and I was trying to update from
KDE 4.1.3 to KDE 4.2. There was some misunderstanding then about what
repo's to add for KDE 4.2 & Qt (Qt 4.4/ only Qt).
Now though, I have a relatively stable KDE 4.2.1 with Qt 4.5.

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];
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.

Post by Jan Kupec
..... 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) ?

Post by Jan Kupec
cheers,
jano
 Ján Kupec
 YaST team

Thanks,

Jay

[1] http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_11.1/

[Jan Kupec]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Jay Mistry

Post by Jan Kupec

Post by Jay Mistry
# 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?

Post by Jay Mistry
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.

Post by Jay Mistry
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.

Post by Jay Mistry

Post by Jan Kupec
..... 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-----

[Carlos E. R.]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Jay Mistry
YaST does not show the same packages that zypper (through konsole,
after su -) does. This was after I updated to KDE 4.2; also have KDE
3.5 installed.
# rpmdb --rebuilddb
# zypper refresh -b
# zypper up

If you are using 11.1, I believe that you should use instead "zypper
patch", which does the same as yast update (ie, a security update).
"Zypper up" updates to newer version if available.


- --------
NOT_nimrodel:~ # zypper help up
update (up) [options] ...

Update all or specified installed packages with newer versions, if possible.


...

NOT_nimrodel:~ # zypper help patch
patch [options]

Install all available needed patches.
- --------


Zypper patch in 11.1 is equivalent to zypper up in 11.0, I understand.


- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAknSBMIACgkQtTMYHG2NR9V/kgCcCvu0C8fffGDvg50KAuj0l9Uw
2g8AoIAUHKZ+e1i2c6UoZk4jyDI8Pcv5
=mK7z
-----END PGP SIGNATURE-----