I wonder why during an upgrade from FC5 to FC6, yum is asking for i386 dependencies files?<br><br>I cleaned up my system of all i386 packages (some of them where confusing yum which bombed out with an error message asking for dependencies when both the x86_64 and the i386 package where installed).
<br clear="all"><br>After this small bit of sanitation I ran "yum upgrade" and was surprised to see on the list of dependencies to be installed some i386 packages. Here is the whole dependencies list.<br>=======================================================
<br>Installing for dependencies:<br> audit-libs i386 1.4-1.fc6 updates 57 k<br> cairomm x86_64 1.2.4-1.fc6 extras 40 k<br> cyrus-sasl-md5 x86_64
2.1.22-4 core 46 k<br> dbus i386 1.0.1-9.fc6 updates 471 k<br> dbus-glib i386 0.70-6.fc6 updates 152 k<br> dvd+rw-tools x86_64
7.0-0.fc6.4 updates 117 k<br> elfutils-libelf-devel-static x86_64 0.125-1.fc6 updates 57 k<br> expat i386 1.95.8-8.2.1 core 77 k<br> ffmpeg-libs x86_64
0.4.9-0.34.20070204.lvn6 livna 1.5 M<br> fftw x86_64 3.1.2-3.fc6 extras 1.0 M<br> glib2 i386 2.12.9-1.fc6 updates 698 k<br> gnome-python2-gconf x86_64
2.16.2-2.fc6 updates 34 k<br> gtk2-engines x86_64 2.8.0-1.fc6 core 350 k<br> hpijs x86_64 1:1.6.12-1.fc6 updates 289 k<br> imake x86_64
1.0.2-3 core 319 k<br> kpartx x86_64 0.4.7-5 core 408 k<br> libcap i386 1.10-25 core 22 k<br> libdca x86_64
0.0.2-3.lvn6 livna 103 k<br> libdvdnav x86_64 0.1.10-2.lvn6 livna 88 k<br> libfontenc-devel x86_64 1.0.2-2.1 core 8.6 k<br> libfreebob x86_64
1.0.0-3.fc6 extras 155 k<br> libiec61883 x86_64 1.1.0-1.fc6 updates 37 k<br> libnotify x86_64 0.4.2-5.fc6 updates 38 k<br> libofa x86_64
0.9.3-8.fc6 extras 63 k<br> libselinux i386 1.33.4-2.fc6 updates 94 k<br> libsepol i386 1.15.3-1.fc6 updates 129 k<br> libsepol-devel x86_64
1.15.3-1.fc6 updates 194 k<br> libsysfs x86_64 2.0.0-6 core 45 k<br> libtunepimp x86_64 0.5.3-1.fc6 extras 373 k<br> libvolume_id x86_64
095-17.fc6 updates 36 k<br> nash x86_64 5.1.19.0.2-1 updates 1.1 M<br> notification-daemon x86_64 0.3.6-1.fc6 updates 52 k<br> notify-python x86_64
0.1.0-3.fc6 core 13 k<br> paps x86_64 0.6.6-17.fc6 updates 32 k<br> poppler-qt x86_64 0.5.4-5.fc6 updates 29 k<br> pygobject2 x86_64
2.12.3-1.fc6 updates 102 k<br> twolame x86_64 0.3.9-1.fc6.rf dries 78 k<br> wavpack x86_64 4.40-1.1.fc6 extras 115 k<br> wxGTK x86_64
2.6.3-2.6.3.2.3.fc6 extras 3.5 M<br> x264 x86_64 0.0.0-0.3.20061214.fc6.rf dries 418 k<br> xorg-x11-drv-ast x86_64 0.81.0-3 core 24 k<br> xorg-x11-drv-cirrus x86_64
1.1.0-2.fc6 core 42 k<br> xorg-x11-drv-vmmouse x86_64 12.4.0-2.1 core 14 k<br> xorg-x11-resutils x86_64 7.1-2.fc6 core 63 k<br> xorg-x11-util-macros x86_64
1.0.2-4.fc6 core 8.2 k<br> yum-metadata-parser x86_64 1.0.3-1.fc6 updates 23 k<br><br>==========================================<br>Why are audit-libs, dbus, dbus-glib, glib2 libcap, libselinux and libsepol picking up the i386 version instead of the x86_64 version? Are they related somehow? I remember specifically deleting the dbus and the glib2 i386 stuff
<br><br>This is weird<br><br>So far, it looks like it is updating everything else properly, but I wonder if these i368 stuff may conflict with the x86_64 libs<br>-- <br>------------------------------<br> /\_/\ <br> |O O|
<a href="mailto:pepebuho@pananet.com">pepebuho@pananet.com</a><br> ~~~~ Javier Perez<br> ~~~~ While the night runs<br> ~~~~ toward the day...<br> m m Pepebuho watches <br> from his high perch.