Upgrade From Fedora Nineteen To Twenty Using Fedup

The recommended upgrade method for Fedora is to job the fedup tool. Below is my sense inwards next the fedup procedure to upgrade from Fedora nineteen to 20. The upgrade was done over the Internet ("network upgrade") instead of from a local DVD media.

1. Back upwards all of import information inwards the system.
2. Verify that the difficult disk has sufficient disk space.

   Fedup starting fourth dimension downloads the version xx packages spell the organization is notwithstanding running version 19. Therefore, the difficult drive must bring plenty disk infinite to concord packages of both versions during the upgrade process. For my system, storing the version xx packages requires most 2 GB.

3. Perform a sum organization update nether Fedora 19, in addition to reboot to ensure that the organization has the latest core changes.

    $ sudo yum update $ sudo reboot 

4. Install fedup client.

   The fedup customer downloads over the Internet the kick ikon required to run the upgrade every bit good every bit the packages to survive upgraded. It sets upwards the organization to run the upgrade at the adjacent boot.

    $  sudo yum install fedup 

5. Run fedup client.

    $ sudo fedup --network xx 

   The higher upwards dominance downloads over the Internet (from the Fedora mirror system) all needed packages to upgrade to Fedora 20. It took almost an hr for my organization to download everything. You should e'er verify that the install was successful yesteryear checking the fedup log file, /var/log/fedup.log.

   My starting fourth dimension upgrade elbow grease appeared stalled towards the goal of the download. So, I terminated the programme amongst a Control-C. The fedup log file revealed a job amongst downloading gnupg.

    [  4130.971] (II) fedup.cli:start_meter() download gnupg-1.4.18-1.fc20.i686.rpm [  4131.107] (II) fedup.yum:log_grab_failure() http://www.muug.mb.ca/pub/fedora/linux/updates/20/i386/gnupg-1.4.18-1.fc20.i686.rpm: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable 

   I reran the command, in addition to it went farther than earlier simply notwithstanding failed amongst the mistake message Downloading failed: Didn't install whatever keys.

   The log file revealed that the offending cardinal was RPM-GPG-KEY-rpmfusion-nonfree-fedora-20.

    [   122.225] (--) fedup.yum:_retrievePublicKey() Retrieving cardinal from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-20 [   122.266] (II) fedup.yum:_GPGKeyCheck() repo 'rpmfusion-nonfree' wants to import cardinal /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-20 [   122.267] (II) fedup.yum:check_keyfile() checking keyfile /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-20 [   122.268] (DD) fedup.yum:check_keyfile() keyfile owned yesteryear packet rpmfusion-nonfree-release-0:19-1 [   122.271] (DD) fedup.yum:check_keyfile() packet was signed amongst cardinal cd30c86b [   122.272] (II) fedup.yum:check_keyfile() REJECTED: cardinal cd30c86b is non trusted yesteryear rpm [   122.273] (II) fedup.yum:_GPGKeyCheck() no automatic trust for cardinal %s [   122.273] (II) fedup:message() Downloading failed: Didn't install whatever keys [   122.274] (DD) fedup:<module<() Traceback (for debugging purposes): 

   To solve the cardinal problem, I manually imported the cardinal using the next command:

    $ sudo rpmkeys --import /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-20 

   Then, I ran the fedup dominance for the 3rd time.

    $ fedup --network xx setting upwards repos... No upgrade available for the next repos: fedora-chromium-stable getting kick images... .treeinfo.signed                                         | 2.1 kB     00:00      setting upwards update... finding updates 100% [=========================================================] verify local files 100% [======================================================] testing upgrade transaction rpm transaction 100% [=========================================================] rpm install 100% [=============================================================] setting upwards organization for upgrade Finished. Reboot to start upgrade. Packages without updates: .... NOTE: Some repos could non survive contacted: fedora-chromium-stable If y'all start the upgrade now, packages from these repos volition non survive installed. 

   The dominance completed amongst an informational message No upgrade available for the next repos: fedora-chromium-stable. The motility of the message is that Fedora xx does non include Chromium inwards its official repository. I decided to ignore the message, in addition to continued amongst the upgrade. As a result, Chromium volition non survive automatically upgraded. However, afterward the upgrade is finished, I tin manually upgrade Chromium from an unofficial repository or install Google Chrome instead.

6. Reboot the system.

    $ sudo reboot 

   Note that a novel entry, System Upgrade, is added to the GRUB menu. This is the default entry, in addition to volition survive automatically selected. The actual upgrade took most 1 hr for my system.

   After the upgrade is complete, the organization automatically reboots into Fedora 20.

7. Login.

   Now that Fedora xx is running, login in addition to run the next dominance to display the version information.

    $ lsb_release -a LSB Version: :core-4.1-ia32:core-4.1-noarch Distributor ID: Fedora Description: Fedora issue xx (Heisenbug) Release: xx Codename: Heisenbug 

8. Install Chrome.

   Instead of upgrading Chromium from an unofficial Fedora repository, I decided to switch to Chrome. Chrome is the costless Google browser that is derived from the upstream Chromium project.

   To install Chrome:

   • Browse to the Google Chrome download site.
   • Select to download the appropriate 32 or 64-bit Fedora rpm.
   • Install the rpm

     I starting fourth dimension used the rpm dominance to install the package. It failed because of a dependency problem.

      $ sudo rpm -i google-chrome-stable_current_i386.rpm  warning: google-chrome-stable_current_i386.rpm: Header V4 DSA/SHA1 Signature, cardinal ID 7fac5991: NOKEY error: Failed dependencies:  lsb >= 4.0 is needed yesteryear google-chrome-stable-37.0.2062.120-1.i386 

     To resolve the dependency automatically, I used the yum dominance every bit follows:

      $ sudo yum localinstall google-chrome-stable_current_i386.rpm 

What was your sense inwards upgrading Fedora? Let us know yesteryear entering a comment.

Share this post