[opensuse-factory] (How did I get) packages installed in multiple versions?
Running "zypper up" right now, I get the following, and I recall that
I have seen similarly for some other packages over the last few weeks:
The following packages are going to be REMOVED:
gdb 7.1-2.3
gdb 7.1-2.4
gdb 7.1-3.2
gdb 7.1-3.3
gdb 7.1-3.4
gdb 7.1-3.5
gdb 7.1-3.6
gdb 7.1-3.7
gdb 7.1-3.8
gdb 7.1-3.10
gdb 7.1-6.2
gdb 7.1-6.3
So, after running the update I investigated a bit:
# rpm -qa --qf "%{NAME}\n" | sort | uniq -c | grep -v " 1 "
9 bluez
9 dbus-1-32bit
13 flex
9 gawk
14 gdb
6 gpg-pubkey
(Note how gdb is still in this list and some packages are there more
than once. Scary.)
# rpm -qa bluez dbus-1-32bit flex gawk | sort
bluez-4.64-1.1.x86_64
bluez-4.64-1.1.x86_64
bluez-4.64-2.1.x86_64
bluez-4.64-2.2.x86_64
bluez-4.64-2.3.x86_64
bluez-4.64-2.4.x86_64
bluez-4.64-2.5.x86_64
bluez-4.64-2.6.x86_64
bluez-4.69-1.3.x86_64
dbus-1-32bit-1.2.24-1.11.x86_64
dbus-1-32bit-1.2.24-1.11.x86_64
dbus-1-32bit-1.2.24-1.12.x86_64
dbus-1-32bit-1.2.24-1.13.x86_64
dbus-1-32bit-1.2.24-1.14.x86_64
dbus-1-32bit-1.2.24-1.15.x86_64
dbus-1-32bit-1.3.2-1.3.x86_64
dbus-1-32bit-1.3.2-2.1.x86_64
dbus-1-32bit-1.3.2-2.2.x86_64
flex-2.5.35-50.12.x86_64
flex-2.5.35-50.12.x86_64
flex-2.5.35-50.13.x86_64
flex-2.5.35-50.15.x86_64
flex-2.5.35-50.16.x86_64
flex-2.5.35-50.17.x86_64
flex-2.5.35-50.18.x86_64
flex-2.5.35-50.19.x86_64
flex-2.5.35-50.21.x86_64
flex-2.5.35-50.23.x86_64
flex-2.5.35-50.25.x86_64
flex-2.5.35-53.6.x86_64
flex-2.5.35-53.7.x86_64
gawk-3.1.6-30.10.x86_64
gawk-3.1.6-30.11.x86_64
gawk-3.1.6-30.13.x86_64
gawk-3.1.6-30.14.x86_64
gawk-3.1.6-30.7.x86_64
gawk-3.1.6-30.7.x86_64
gawk-3.1.6-30.8.x86_64
gawk-3.1.6-30.9.x86_64
gawk-3.1.6-34.7.x86_64
Am I the only one seeing this?
And what to do about it, not just for me, but possibly in getting
this addressed?
One instance I tried to resolve manually:
# zypper rm flex
The following packages are going to be REMOVED:
flex-2.5.35-50.11 flex-2.5.35-50.12 flex-2.5.35-50.13 flex-2.5.35-50.15
flex-2.5.35-50.16 flex-2.5.35-50.17 flex-2.5.35-50.18 flex-2.5.35-50.19
flex-2.5.35-50.21 flex-2.5.35-50.23 flex-2.5.35-50.25 flex-2.5.35-53.6
flex-2.5.35-53.7
13 packages to remove.
After the operation, 9.0 MiB will be freed.
Continue? [y/n/?] (y): y
Removing flex-2.5.35-50.11 [error]
Removal of (15714)flex-2.5.35-50.11.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: error: package
flex-2.5.35-50.11.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i
Removing flex-2.5.35-50.12 [done]
Removing flex-2.5.35-50.13 [done]
Removing flex-2.5.35-50.15 [done]
Removing flex-2.5.35-50.16 [done]
Removing flex-2.5.35-50.17 [done]
Removing flex-2.5.35-50.18 [done]
Removing flex-2.5.35-50.19 [done]
Removing flex-2.5.35-50.21 [done]
Removing flex-2.5.35-50.23 [done]
Removing flex-2.5.35-50.25 [done]
Removing flex-2.5.35-53.6 [done]
Removing flex-2.5.35-53.7 [done]
Still:
# rpm -qa flex
flex-2.5.35-50.12.x86_64
Looks like our update stack could need a bit more resilience. ;-)
Gerald
--
Dr. Gerald Pfeifer
On 08/11/2010 11:22 AM, Gerald Pfeifer pecked at the keyboard and wrote:
Running "zypper up" right now, I get the following, and I recall that I have seen similarly for some other packages over the last few weeks:
The following packages are going to be REMOVED: gdb 7.1-2.3 gdb 7.1-2.4 gdb 7.1-3.2 gdb 7.1-3.3 gdb 7.1-3.4 gdb 7.1-3.5 gdb 7.1-3.6 gdb 7.1-3.7 gdb 7.1-3.8 gdb 7.1-3.10 gdb 7.1-6.2 gdb 7.1-6.3
So, after running the update I investigated a bit:
# rpm -qa --qf "%{NAME}\n" | sort | uniq -c | grep -v " 1 " 9 bluez 9 dbus-1-32bit 13 flex 9 gawk 14 gdb 6 gpg-pubkey
(Note how gdb is still in this list and some packages are there more than once. Scary.)
# rpm -qa bluez dbus-1-32bit flex gawk | sort bluez-4.64-1.1.x86_64 bluez-4.64-1.1.x86_64 bluez-4.64-2.1.x86_64 bluez-4.64-2.2.x86_64 bluez-4.64-2.3.x86_64 bluez-4.64-2.4.x86_64 bluez-4.64-2.5.x86_64 bluez-4.64-2.6.x86_64 bluez-4.69-1.3.x86_64 dbus-1-32bit-1.2.24-1.11.x86_64 dbus-1-32bit-1.2.24-1.11.x86_64 dbus-1-32bit-1.2.24-1.12.x86_64 dbus-1-32bit-1.2.24-1.13.x86_64 dbus-1-32bit-1.2.24-1.14.x86_64 dbus-1-32bit-1.2.24-1.15.x86_64 dbus-1-32bit-1.3.2-1.3.x86_64 dbus-1-32bit-1.3.2-2.1.x86_64 dbus-1-32bit-1.3.2-2.2.x86_64 flex-2.5.35-50.12.x86_64 flex-2.5.35-50.12.x86_64 flex-2.5.35-50.13.x86_64 flex-2.5.35-50.15.x86_64 flex-2.5.35-50.16.x86_64 flex-2.5.35-50.17.x86_64 flex-2.5.35-50.18.x86_64 flex-2.5.35-50.19.x86_64 flex-2.5.35-50.21.x86_64 flex-2.5.35-50.23.x86_64 flex-2.5.35-50.25.x86_64 flex-2.5.35-53.6.x86_64 flex-2.5.35-53.7.x86_64 gawk-3.1.6-30.10.x86_64 gawk-3.1.6-30.11.x86_64 gawk-3.1.6-30.13.x86_64 gawk-3.1.6-30.14.x86_64 gawk-3.1.6-30.7.x86_64 gawk-3.1.6-30.7.x86_64 gawk-3.1.6-30.8.x86_64 gawk-3.1.6-30.9.x86_64 gawk-3.1.6-34.7.x86_64
Am I the only one seeing this?
And what to do about it, not just for me, but possibly in getting this addressed?
One instance I tried to resolve manually:
# zypper rm flex The following packages are going to be REMOVED: flex-2.5.35-50.11 flex-2.5.35-50.12 flex-2.5.35-50.13 flex-2.5.35-50.15 flex-2.5.35-50.16 flex-2.5.35-50.17 flex-2.5.35-50.18 flex-2.5.35-50.19 flex-2.5.35-50.21 flex-2.5.35-50.23 flex-2.5.35-50.25 flex-2.5.35-53.6 flex-2.5.35-53.7
13 packages to remove. After the operation, 9.0 MiB will be freed. Continue? [y/n/?] (y): y Removing flex-2.5.35-50.11 [error] Removal of (15714)flex-2.5.35-50.11.x86_64(@System) failed: Error: Subprocess failed. Error: RPM failed: error: package flex-2.5.35-50.11.x86_64 is not installed
Abort, retry, ignore? [a/r/i] (a): i Removing flex-2.5.35-50.12 [done] Removing flex-2.5.35-50.13 [done] Removing flex-2.5.35-50.15 [done] Removing flex-2.5.35-50.16 [done] Removing flex-2.5.35-50.17 [done] Removing flex-2.5.35-50.18 [done] Removing flex-2.5.35-50.19 [done] Removing flex-2.5.35-50.21 [done] Removing flex-2.5.35-50.23 [done] Removing flex-2.5.35-50.25 [done] Removing flex-2.5.35-53.6 [done] Removing flex-2.5.35-53.7 [done]
Still:
# rpm -qa flex flex-2.5.35-50.12.x86_64
Looks like our update stack could need a bit more resilience. ;-)
Gerald
Try rebuilding your RPM database rpm --rebuilddb -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, 11 Aug 2010, Ken Schneider - Factory wrote:
Try rebuilding your RPM database
rpm --rebuilddb
Of course I should have done this. Thanks for the hint, Kent.
That said, I ran this now, and no change.
Gerald
--
Dr. Gerald Pfeifer
On Wed, 11 Aug 2010 17:22:32 +0200 (CEST)
Gerald Pfeifer
Am I the only one seeing this?
At least I don't see this, and I'm running a pretty hardcore FACTORY installation: susi:~ # zypper lr # | Alias | Name | Enabled | Refresh ---+--------------------+-----------------------+---------+-------- 1 | KKFD | KKFD | Yes | Yes 2 | KOTD | KOTD | Yes | Yes 3 | X11:Xorg | X11:Xorg | Yes | Yes 4 | factory-debug | factory-debug | Yes | No 5 | factory-non-oss | factory-non-oss | Yes | Yes 6 | factory-oss | factory-oss | Yes | Yes 7 | home:seife:testing | home:seife:testing | Yes | Yes 8 | packman | packman | Yes | Yes So it does not seem to be a general problem but (hopefully ;) isolated on your installation. Good luck ;) -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
El 11/08/10 11:22, Gerald Pfeifer escribió:
Running "zypper up" right now, I get the following, and I recall that I have seen similarly for some other packages over the last few weeks:
This seems to be a bug, but in some package pre/post/preun. etc scripts or somehow your rpm database went belly up. zypper installs packages with --force , one by one and not in a transaction, hence you can effectively end with that many versions. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Aug 11, 2010 at 05:22:32PM +0200, Gerald Pfeifer wrote:
And what to do about it, not just for me, but possibly in getting this addressed?
'zypper verify' should 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: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/24/2010 01:15 PM, Michael Schroeder wrote:
On Wed, Aug 11, 2010 at 05:22:32PM +0200, Gerald Pfeifer wrote:
And what to do about it, not just for me, but possibly in getting this addressed? 'zypper verify' should fix this.
Cheers, Michael.
Watch Out! It will deselected/deinstall RPMs you installed without any way to replace them. Such as printer related RPMs. I am not sure about other locked "zypper al" file.rpm -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb@comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb@arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2010-08-24 T 16:23 -0500 Donn Washburn wrote:
On 08/24/2010 01:15 PM, Michael Schroeder wrote:
On Wed, Aug 11, 2010 at 05:22:32PM +0200, Gerald Pfeifer wrote:
And what to do about it, not just for me, but possibly in getting this addressed? 'zypper verify' should fix this.
Watch Out! It will deselected/deinstall RPMs you installed without any way to replace them. Such as printer related RPMs. I am not sure about other locked "zypper al" file.rpm
Does this apply to all types of RPMs or only those, which have _not_ been presented to ZYPP in a repository? In other words: it is good practice to have all RPMs (also your home built stuff) provided to ZYPP in a repository, thus ZYPP can handle dependencies appropriately and not intermix "rpm -Uvh ..." with "zypper in ...". In addition, "zypper verify --dry-run" certainly is a good idea, before running "zypper verify":-) so long - MgE -- Matthias G. Eckermann Senior Product Manager - SUSE® Linux Enterprise - Server Product Line SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Aug 24, 2010 at 04:23:07PM -0500, Donn Washburn wrote:
On 08/24/2010 01:15 PM, Michael Schroeder wrote:
On Wed, Aug 11, 2010 at 05:22:32PM +0200, Gerald Pfeifer wrote:
And what to do about it, not just for me, but possibly in getting this addressed? 'zypper verify' should fix this.
Cheers, Michael.
Watch Out! It will deselected/deinstall RPMs you installed without any way to replace them.
Are you confusing it with 'zypper dup'? 'zypper verify' will print a problem report for every package that it has to deinstall (except for the multiple version case). 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: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (7)
-
Cristian Rodríguez -
Donn Washburn -
Gerald Pfeifer -
Ken Schneider - Factory -
Matthias G. Eckermann -
Michael Schroeder -
Stefan Seyfried