antonio montagnani wrote:
1) I went through yum.log and I cannot see what was set to be
erased.In yum.log I read:
Jul 21 00:29:16 Updated: cairo.i386 1.4.10-1.fc7
Jul 21 00:29:17 Updated: gnome-python2-extras.i386 2.14.3-4.fc7
Jul 21 00:29:25 Updated: autofs.i386 1:5.0.1-20
Jul 21 00:29:26 Updated: gnome-python2-gtkmozembed.i386 2.14.3-4.fc7
Jul 21 00:30:20 Updated: seamonkey.i386 1.1.3-1.fc7
Jul 21 00:30:26 Updated: gnome-python2-libegg.i386 2.14.3-4.fc7
Jul 21 00:32:41 Updated: thunderbird.i386 2.0.0.5-1.fc7
Jul 21 00:32:45 Updated: mdadm.i386 2.6.2-4.fc7
Jul 21 00:32:46 Updated: gnome-python2-gtkhtml2.i386 2.14.3-4.fc7
Jul 21 00:43:29 Installed: kernel-devel.i686 2.6.22.1-27.fc7
Jul 21 00:44:56 Installed: kernel.i686 2.6.22.1-27.fc7
Jul 21 00:45:18 Updated: kernel-headers.i386 2.6.22.1-27.fc7
I would have thought right there in yum.log, but you'll have to get a
developer to say for sure. If it doesn't, I'd file an RFE to get it to.
I know it shows when I explicitly erase a package with yum.
and in rpmpkgs:
kernel-2.6.21-1.3194.fc7.i686.rpm
kernel-2.6.21-1.3228.fc7.i686.rpm
kernel-devel-2.6.21-1.3194.fc7.i686.rpm
kernel-devel-2.6.21-1.3228.fc7.i686.rpm
kernel-headers-2.6.21-1.3228.fc7.i386.rpm
in rpmpkg.1
kernel-2.6.21-1.3194.fc7.i686.rpm
kernel-2.6.21-1.3228.fc7.i686.rpm
kernel-devel-2.6.21-1.3194.fc7.i686.rpm
kernel-devel-2.6.21-1.3228.fc7.i686.rpm
kernel-headers-2.6.21-1.3228.fc7.i386.rpm
Where do I read the full story (erased, updated, added)??
I'm not sure.
2) what is really funny, I cannot read the following files aslo as
root by clicking on them, but I can open by gedit!!!
yum.conf
[main]
cachedir=/var/cache/yum
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
metadata_expire=1800
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
yumex.conf
[yumex]
autorefresh = yes
filelists = no
recentdays = 14
autocleanup = yes
proxy =
exclude =
debug = no
mirrordetection = default
nofastestmirror = 0
:
/etc/yum/pluginconf.y/installony.conf
[main]
enabled=1
# this sets the number of package versions which are kept
tokeep=2
Can't tell you why. I always edit them with emacs from a command line.
3) The madwifi-0.9.3-2.fc7.i386.rpm from freshrpm doesn't build
the
module at start-up by dkms, so I don't have wireless card operating!!!
Shall I file a bug (for madwifi not o.k.) against Fedora or Freshrpms??
Sorry, I don't use dkms, I use Axel's kmdl's (and 1 kmod from livna).
But if you think its a dkms problem, file it against FreshRPMs.
They'll tell you if its Fedora's fault or not.
--
Kevin J. Cummings
kjchome(a)rcn.com
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (
http://counter.li.org)