Greetings;
I enabled the development repo long enough to pull in the new yum, which is
reported to have a 're-install' option. That also pulled in the following
list of deps:
Packages Installed:
pygpgme.i386 0.1-8.fc9
Packages Updated:
yum-updatesd.noarch 1:0.9-1.fc9
yumex.noarch 2.0.4-1.fc9
glib2.i386 2.16.3-3.fc9
yum.noarch 3.2.14-10.fc9
glib2-devel.i386 2.16.3-3.fc9
yum-metadata-parser.i386 1.1.2-8.fc9
glibc.i686 2.8-1
glibc-headers.i386 2.8-1
glibc-devel.i386 2.8-1
yum-utils.noarch 1.1.13-2.fc9
glibc-common.i386 2.8-1
2 problems, 1) my build system is hosed, everything fails at the 'make clean'
stage with an assertion error 134,
and 2) yum can't find a file its requested to re-install (& yumex hasn't been
informed of the new option which would be the ideal situation)
Since I don't seem to have a path to back this up to pure, uptodate f8, is it
safe right now to just let yum update the whole system to rawhide? That's
1300+ packages, including kde-4.03, which I understand from copying the mail
here, will hose kmail, and I have little use for t-bird until it grows some
ease of configuration like kmail has had for 5+ years.
Or should I cancel that, and see about getting the beta image here first?
Yumex is waiting. :)
Or should I cherry pick and see if newer gcc pieces might help?
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Above all things, reverence yourself.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
