On Thu, 3 Sep 2009 11:13:31 David C. Rankin wrote:
Listmates,
I have been using zypper from the command line to update exclusively for quite a while. However, recently zypper has been acting pretty sick concerning respecting locks on packages and in fact refusing to set locks. So tonight, the zypper up showed the following updates:
17:28 alchemy:~> zu Loading repository data... Reading installed packages...
The following package is going to be upgraded: opera
The following NEW package is going to be installed: compiz-plugins-extra
Overall download size: 10.4 MiB. After the operation, additional 8.4 MiB will be used. Continue? [_yes_/no]: no
The update was canceled because I don't want the compiz 8.2 packages, and in fact I have specifically locked compiz (each individual package) with:
# zypper al <package name>
All zypper shows as far as locks go is:
[20:26 alchemy:/usr/src/packages/RPMS/x86_64] # zypper ll # | Name | Type | Repository --+-------------+---------+----------- 1 | compiz | package | (any) 2 | kdiff3-lang | package | (any)
I have added way more locks than 2, but yet all zypper shows as locked are the two above? Example, locking the madwifi package does nothing:
[20:27 alchemy:/usr/src/packages/RPMS/x86_64] # zypper al madwifi [20:37 alchemy:/usr/src/packages/RPMS/x86_64] # zypper ll # | Name | Type | Repository --+-------------+---------+----------- 1 | compiz | package | (any) 2 | kdiff3-lang | package | (any)
Regardless, faced with zypper's lack of respect of prior locks, I fired up yast-> software management and found:
44 packages to update:
1251930897 (Wed 02 Sep 2009 05:34:57 PM CDT) madwifi-devel 1251930902 (Wed 02 Sep 2009 05:35:02 PM CDT) madwifi 1251930983 (Wed 02 Sep 2009 05:36:23 PM CDT) opera 1251931001 (Wed 02 Sep 2009 05:36:41 PM CDT) libdvdnav4 1251931010 (Wed 02 Sep 2009 05:36:50 PM CDT) mp3blaster 1251931017 (Wed 02 Sep 2009 05:36:57 PM CDT) alsaplayer 1251931024 (Wed 02 Sep 2009 05:37:04 PM CDT) libtheoraenc1 1251931028 (Wed 02 Sep 2009 05:37:08 PM CDT) libtheoradec1 1251931031 (Wed 02 Sep 2009 05:37:11 PM CDT) libfaad2 1251931038 (Wed 02 Sep 2009 05:37:18 PM CDT) yasm 1251931046 (Wed 02 Sep 2009 05:37:26 PM CDT) libtheora0 1251931050 (Wed 02 Sep 2009 05:37:30 PM CDT) liboil-0_3-0 1251931054 (Wed 02 Sep 2009 05:37:34 PM CDT) libavutil49 1251931059 (Wed 02 Sep 2009 05:37:39 PM CDT) libamrnb3 1251931064 (Wed 02 Sep 2009 05:37:44 PM CDT) libcaca0 1251931068 (Wed 02 Sep 2009 05:37:48 PM CDT) xvid4conf 1251931072 (Wed 02 Sep 2009 05:37:52 PM CDT) libamrwb3 1251931076 (Wed 02 Sep 2009 05:37:56 PM CDT) libspeex1 1251931090 (Wed 02 Sep 2009 05:38:10 PM CDT) mjpegtools 1251931106 (Wed 02 Sep 2009 05:38:26 PM CDT) perl-libintl-perl 1251931128 (Wed 02 Sep 2009 05:38:48 PM CDT) rar 1251931132 (Wed 02 Sep 2009 05:38:52 PM CDT) python-kdebase4 1251931139 (Wed 02 Sep 2009 05:38:59 PM CDT) kde4-webkitpart 1251931145 (Wed 02 Sep 2009 05:39:05 PM CDT) silc-toolkit 1251931177 (Wed 02 Sep 2009 05:39:37 PM CDT) binutils 1251931183 (Wed 02 Sep 2009 05:39:43 PM CDT) libdvdnav-devel 1251931187 (Wed 02 Sep 2009 05:39:47 PM CDT) libschroedinger-1_0-0 1251931191 (Wed 02 Sep 2009 05:39:51 PM CDT) xmms-faad2 1251931197 (Wed 02 Sep 2009 05:39:57 PM CDT) yasm-devel 1251931200 (Wed 02 Sep 2009 05:40:00 PM CDT) libswscale0 1251931203 (Wed 02 Sep 2009 05:40:03 PM CDT) libpostproc51 1251931205 (Wed 02 Sep 2009 05:40:05 PM CDT) amrwb 1251931208 (Wed 02 Sep 2009 05:40:08 PM CDT) faad2 1251931211 (Wed 02 Sep 2009 05:40:11 PM CDT) speex 1251931215 (Wed 02 Sep 2009 05:40:15 PM CDT) libsilcclient-1_1-3 1251931224 (Wed 02 Sep 2009 05:40:24 PM CDT) libsilc-1_1-2 1251931260 (Wed 02 Sep 2009 05:41:00 PM CDT) binutils-devel 1251931273 (Wed 02 Sep 2009 05:41:13 PM CDT) libavcodec52 1251931317 (Wed 02 Sep 2009 05:41:57 PM CDT) libpurple 1251931328 (Wed 02 Sep 2009 05:42:08 PM CDT) libavformat52 1251931332 (Wed 02 Sep 2009 05:42:12 PM CDT) k3b-codecs 1251931352 (Wed 02 Sep 2009 05:42:32 PM CDT) transcode 1251931361 (Wed 02 Sep 2009 05:42:41 PM CDT) libavdevice52 1251931365 (Wed 02 Sep 2009 05:42:45 PM CDT) libffmpeg0
WTF? Why wasn't zypper showing these packages as available for update?? I used to have complete confidence in zypper's ability to manage updates, but I'm seriously questioning that at this point. What gives?
I can't think of anything I can be screwing up. I mean you either issue:
# zypper up
from the command line, or use yast software management and choose:
Packages -> All Packages -> Update if Newer Version Available
both should do the same thing right??
David, What version of zypper? I had this problem a version or two back but one of the recent upgrades from factory fixed it (or at least appeared to). -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org