Incredible F8 updates -- followup : anticlimax, I hope
 

On Sun, 02 Dec 2007 20:38:16 +0000, I (Beartooth) wrote:
[...]
> Then the main one hit some snag with curl-devel dependencies. So
> I told yum to remove that, and carefully kept a list of things it took
> with it, so as to put them back shortly.
>
> Then I told it you update again.
>
> It's in process of downloading 523 -- no typo : five hundred
> twenty three -- 523 items.
>
> What in the blue blazes have I done? Is the whole shebang about
> to implode before my eyes??

Well, it downloaded them all -- including several things that I
always UNinstall if I ever get it -- and then fizzled :

[....]
(521/523): libacl-2.2.45- 100% |=========================| 20 kB
00:00
(522/523): cyrus-sasl-dev 100% |=========================| 351 kB
00:03
(523/523): gtk-nodoka-eng 100% |=========================| 47 kB
00:00
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
file /etc/gre.d/gre.conf conflicts between attempted installs of
xulrunner-1.9-0.beta1.3.fc9.i386 and firefox-2.0.0.10-1.fc9.i386

Error Summary
-------------

[root@localhost ~]#


So I don't know whether to go put back the stuff that went with
curl-devel and then update again, or ....

--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Incredible F8 updates -- followup : anticlimax, I hope
 

On Sun, 2007-12-02 at 22:01 +0000, Beartooth wrote:
> Well, it downloaded them all -- including several things that I
> always UNinstall if I ever get it -- and then fizzled :
>
> [....]
> (521/523): libacl-2.2.45- 100% |=========================| 20 kB
> 00:00
> (522/523): cyrus-sasl-dev 100% |=========================| 351 kB
> 00:03
> (523/523): gtk-nodoka-eng 100% |=========================| 47 kB
> 00:00
> Running rpm_check_debug
> Running Transaction Test
> Finished Transaction Test
>
>
> Transaction Check Error:
> file /etc/gre.d/gre.conf conflicts between attempted installs of
> xulrunner-1.9-0.beta1.3.fc9.i386 and firefox-2.0.0.10-1.fc9.i386
>
> Error Summary
> -------------
>
> [root@localhost ~]#
>
>
> So I don't know whether to go put back the stuff that went with
> curl-devel and then update again, or ....

It sounds to me like you've enabled the development repos. Was that
intentional?

If not, I would edit /etc/yum.repos.d/fedora-development.repo and make
sure all stanzas have "enabled=0" in them. If they DO have "enabled=1",
change it back to 0 (everywhere it's listed!). Then do a "yum clean all"
and try your yum installation again.

- Ben

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Incredible F8 updates -- followup : anticlimax, I hope
 

On Sun, 02 Dec 2007 15:10:34 -0700, Ben Brown wrote:

> It sounds to me like you've enabled the development repos. Was that
> intentional?

Bless you, SIR! It was most certainly NOT intentional; I do at
least know better than that ...

But I had indeed, somehow. I discovered that much last night, and
futzed with it -- the wrong way, of course : commenting things out rather
than changing enablements.

> If not, I would edit /etc/yum.repos.d/fedora-development.repo and make
> sure all stanzas have "enabled=0" in them. If they DO have "enabled=1",
> change it back to 0 (everywhere it's listed!). Then do a "yum clean all"
> and try your yum installation again.

Any guidance on what should or should not be commented out?

There's another problem with that machine, which I don't *think*
is inherently related, but it affects things.

Even though I pulled the KVM switch out of the situation, and did
the latest new OS-install (i.e., F8) with the peripherals connected
directly to the machine; even though Fedora 8 (at last, bless it!) knew
about the Acer AL1916 monitor and recognized it; it *still* does what F7
and F6 did -- fails to recognize the monitor on boot when back behind the
KVM switch, and gives me a display saying only something not supported.

I fix that as I did before, by hitting Ctrl-Alt-Backspace, and
then it does recognize it.

But now I get no GUI. (I normally run Gnome.) It comes up with
CLI only, and startx fails, both as user and as root.

I can do stuff like "nano -w /etc/yum.repos.d" to change the
enablings, and undo extraneous comments-out (once I establish which they
are). But I'm no technoid, and I need my Gnome just to find things I have
to tweak.

Anyhow, I zeroed out the enables, and did yum clean all. Then I
did my usual routine, adding rpm --rebuilddb and updatedb. I hope that
was right.

Then I rebooted it, without yet doing yum update.

I should probably add that grub now gives me a choice of two
kernels -- one that looks normal, and above it a strange one that I
certainly shouldn't have, with an fc9 (yes, nine) at the end. I'll try to
transcribe it : 2.6.24-0.62.rc3.git5.fc9 -- and it doesn't boot at all,
but hangs up looking for something. At least the fc8 kernel does get me
all the way to a prompt. But startx, even with the .fc8 kernel, still
fails.

--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list