From: Robert Nichols on
In article <01644013-6f58-4076-bb81-d2447b1dc34f(a)k4g2000yqb.googlegroups.com>,
Bob <jeep(a)rahul.net> wrote:
:
:> How did you update? Did you use the installation media and tell it
:> "update", or did you change your upstream repository to the new
:> repository and do it one component at a time, or what? And do you have
:> any reason not to jump to Fedora 12 now?
:
:I updated with the Fed 11 DVD, I chose the
:'install or upgrade option' and upgraded from older
:version of fedora. I didnt change any of the repos.
:Whatever it did it did on its own.
:
:About Fedora 12, yes, im avoiding it. I tried updating
:my other machine from 11 to 12 and it had video issues.
:It didnt recognize my 512Mbyte AGP card (fed 11 works
:fine), and even in text mode after upgrading (init level 3),
:the cursor was stuck up at the upper left corner. After
:1 page of text I couldnt see anything anymore, it was
:very strange.
:
:I have a perfectly running server that Id hate to have
:to re-install things on because it would take me 3
:days to set it back up with everything.
:
:On a side note, is there some reason why older fc rpm
:packages are left on an upgrade? ie I have some fc10
:rpms and not fc11 ones after the upgrade which I suspect
:might be causing this? Seems to me fedora should take
:care of it for me during upgrade somehow.

That can happen when you wait to do the upgrade until a long time after
the release. Problem is that updates to F-10 during that interval have
installed packages with version numbers that make them "newer" than what
is on the F-11 disk. Does the installation disk allow you to specify
additional repos during an upgrade? If so, you could try the upgrade
again and add an F-11 "updates" repo to the mix. That will hopefully
bring in the correct version of those packages. The only other thing I
can suggest is manually running rpm with the "--oldpackage" option to
force installation of any of the "older" F-11 packages that look like
they are needed, but you are likely to find yourself going through
Dependency Hell with that approach.

--
Bob Nichols AT comcast.net I am "RNichols42"
From: Nico Kadel-Garcia on
On Dec 1, 8:33 pm, Robert Nichols
<SEE_SIGNAT...(a)localhost.localdomain.invalid> wrote:
> In article <01644013-6f58-4076-bb81-d2447b1dc...(a)k4g2000yqb.googlegroups.com>,Bob  <j...(a)rahul.net> wrote:

> :On a side note, is there some reason why older fc rpm
> :packages are left on an upgrade?  ie I have some fc10
> :rpms and not fc11 ones after the upgrade which I suspect
> :might be causing this?  Seems to me fedora should take
> :care of it for me during upgrade somehow.
>
> That can happen when you wait to do the upgrade until a long time after
> the release.  Problem is that updates to F-10 during that interval have
> installed packages with version numbers that make them "newer" than what
> is on the F-11 disk.  Does the installation disk allow you to specify
> additional repos during an upgrade?  If so, you could try the upgrade
> again and add an F-11 "updates" repo to the mix.  That will hopefully
> bring in the correct version of those packages.  The only other thing I
> can suggest is manually running rpm with the "--oldpackage" option to
> force installation of any of the "older" F-11 packages that look like
> they are needed, but you are likely to find yourself going through
> Dependency Hell with that approach.

As near as I can tell, unless the package is discarded as part of the
new release, this older/newer package desynchronization only occurs
when there is a published update for both the older and newer OS, and
you've failed to run "yum update" for the new OS. "yum update" can
suck up one hell of a lot of bandwidth if packages like kde language
or OpenOffice packages have updated, and take quite a long time to
run, but they're worth doing.
From: Bob on

> As near as I can tell, unless the package is discarded as part of the
> new release, this older/newer package desynchronization only occurs
> when there is a published update for both the older and newer OS, and
> you've failed to run "yum update" for the new OS. "yum update" can
> suck up one hell of a lot of bandwidth if packages like kde language
> or OpenOffice packages have updated, and take quite a long time to
> run, but they're worth doing.

I dont mind taking the time or the bandwidth if needed, but when
things dont work...or at least the software doesnt figure out a way
to make it all work properly after an upgrade, that irks me. Being
a software engineer, I hate when my code is broken and do my best
to fix it properly. I realize an entire upgrade is a lot of smaller
pieces,
but still, this problem is unacceptable.

So it sounds like Ill have to do fresh installs on both machines.

Thanks for trying to help, I do appreciate it.
From: Robert Nichols on
In article <1e07cabb-b448-4f45-8030-1180ff340911(a)p35g2000yqh.googlegroups.com>,
Nico Kadel-Garcia <nkadel(a)gmail.com> wrote:
:On Dec 1, 8:33=A0pm, Robert Nichols
:<SEE_SIGNAT...(a)localhost.localdomain.invalid> wrote:
:> In article <01644013-6f58-4076-bb81-d2447b1dc...(a)k4g2000yqb.googlegroups.=
:com>,Bob =A0<j...(a)rahul.net> wrote:
:
:> :On a side note, is there some reason why older fc rpm
:> :packages are left on an upgrade? =A0ie I have some fc10
:> :rpms and not fc11 ones after the upgrade which I suspect
:> :might be causing this? =A0Seems to me fedora should take
:> :care of it for me during upgrade somehow.
:>
:> That can happen when you wait to do the upgrade until a long time after
:> the release. =A0Problem is that updates to F-10 during that interval have
:> installed packages with version numbers that make them "newer" than what
:> is on the F-11 disk. =A0Does the installation disk allow you to specify
:> additional repos during an upgrade? =A0If so, you could try the upgrade
:> again and add an F-11 "updates" repo to the mix. =A0That will hopefully
:> bring in the correct version of those packages. =A0The only other thing I
:> can suggest is manually running rpm with the "--oldpackage" option to
:> force installation of any of the "older" F-11 packages that look like
:> they are needed, but you are likely to find yourself going through
:> Dependency Hell with that approach.
:
:As near as I can tell, unless the package is discarded as part of the
:new release, this older/newer package desynchronization only occurs
:when there is a published update for both the older and newer OS, and
:you've failed to run "yum update" for the new OS.

That's exactly the situation you'll find yourself in if you take a fully
updated F-10 installation and try to upgrade it with the F-11
installation disk (now more than 6 months out of date) without also
including an F-11 "updates" repository in your upgrade process. You
stand a good chance of ending up with a system that is too broken to be
able to do any further updates on its own.

"yum update" can
:suck up one hell of a lot of bandwidth if packages like kde language
:or OpenOffice packages have updated, and take quite a long time to
:run, but they're worth doing.

Amen. When I upgraded from F-11 to F-12 with an F-12 "os" release repo
available locally, there were already 300MB of F-12 updates that got
pulled in from the net, and this was within a week of the F-12 release.
That's pretty hard to avoid when using a distro that changes as rapidly
as does Fedora.

--
Bob Nichols AT comcast.net I am "RNichols42"
From: Bible Trivia on
Ok I think I solved it, believe it or not, relatively
painlessly. I installed something called 'smart'
http://labix.org/smart

I removed yum-utils via the smart tool,
then downloaded (seperately) the yum package rpm,
installed it, and wallah, it worked!