Re: Apparently Incomplete Fedup 18->19

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07/28/2013 10:37 AM, Sam Varshavchik wrote:
Tim Evans writes:

Nearly everything seems to suggest that my fedup upgrade from F18 only
partially F19 succeeded.

$ cat /etc/fedora-release
Fedora release 19 (Schrödinger’s Cat)

$ head /var/log/boot.log
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Basic System.

Welcome to Fedora 19 (Schrödinger’s Cat)!

But, the blue progress bar during bootup shows "Fedora 18."

Kernel appears to be F18, though:

$ uname -a
Linux harrier.xxx.com 3.9.11-200.fc18.i686.PAE #1 SMP Mon Jul 22
21:19:06 UTC 2013 i686 i686 i386 GNU/Linux

By way of additional info, after running fedup with no errors, I
rebooted, picking the "Fedora Upgrade" option.  Then went to dinner.
When I returned, the system was *powered completely down*.  Booting it
revealed the F18 message on the progress bar.

yum update shows a string of "some-package.fc19 is a duplicate of
same-package.fc18

I don't see anything untoward in /var/log/fedup.log.  Seems whatever
has happened occurred after the reboot into the upgrade.

If a kernel update wasn't done as part of the upgrade, the boot message
will still report F18, until the first F19 kernel update gets installed.

Running package-cleanup --cleandupes should remove the F18 package if an
F19 package is already installed. Do that, then as long as the
fedora-release package was updated to F19, you should be able to run
'yum update', and complete the upgrade.



It would appear the key part of my experience was finding the system powered down with no indication as to why. Long story short: it looks like I have a hardware power issue and that almost nothing of F19 was actually upgraded on the first round. I was able to re-run 'fedup' successfully, reboot, get the FedUp option again, and a couple of thousand upgrades got done. A half hour after completion however, I again ran into power issues--neither AC nor battery power seems to work now, so it appears the problem was external to 'fedup' and that I really need a Lenovo repair shop, here in Baltimore. :=(

--
Tim Evans			|   5 Chestnut Court
UNIX System Admin Consulting	|   Owings Mills, MD 21117
http://www.tkevans.com/		|   443-394-3864
				|   tkevans@xxxxxxxxxxx
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org




[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux