Engage. Your Community

Upgrade Korora 27 to Fedora 28 and Fedora 29

Update: can i upgrade this to fedora 29 5 months later?

The last days i am into updating all of my Korora AND Chapeau maschines. I am not here to blame anyone for discontinuing but to give an exit strategy.

I looked around and i think it IS possible to update from Korora to Fedora (but reinstallation might also be necessary).

After backing up all important data I upgraded my K26 instances to K27 (and one from K25) following the general upgrade guide

Then in the EOL post of Chapeau the developer left over a guide how to upgrade from C24 to F27:

right now i fired the following command (as root or sudo) to upgrade from K27 to F28:

dnf --refresh --allowerasing system-upgrade download --releasever=28 --disablerepo=korora

when all is downloaded i will do:

dnf system-upgrade reboot

gladly i dont have NVIDIA installed so i will skip that one from the Chapeau-guide

sudo dnf remove chapeau-nvidia* chapeau-bumble* *nvidia*
sudo dnf install xorg-x11-drv-nvidia akmod-nvidia

i hope that this post may help others to come to an positive EOL of Korora

cheers, Tom

back again after dnf system-upgrade reboot seems everything working!

Hurray!

I skipped the part with the repos because it looks as though that one is handled different in Korora and now i tried the following

[root@localhost ~]# dnf search korora
Copr repo for pidgin-lurch owned by treba           3.6 kB/s | 2.8 kB     00:00    
Fedora 28 - x86_64 - Updates                        299 kB/s | 5.5 MB     00:18    
Fedora 28 - x86_64                                  1.7 MB/s |  60 MB     00:36    
RPM Fusion for Fedora 28 - Free - Updates            20 kB/s |  21 kB     00:01    
RPM Fusion for Fedora 28 - Free                     118 kB/s | 754 kB     00:06    
RPM Fusion for Fedora 28 - Nonfree - Updates         49 kB/s | 3.6 kB     00:00    
RPM Fusion for Fedora 28 - Nonfree                  181 kB/s | 208 kB     00:01    
Letzte Prüfung auf abgelaufene Metadaten: vor 0:00:00 am So 06 Mai 2018 15:52:10 CEST.
====================== Name & Zusammenfassung Matched: korora ======================
korora-welcome.noarch : Korora welcome utility
plymouth-theme-korora.noarch : Plymouth Korora Theme
korora-settings-gnome.x86_64 : Korora configs for GNOME
anaconda-extras-korora.x86_64 : Korora customisation for the anaconda
korora-backgrounds-base.noarch : Base images for Korora 27 default background
korora-backgrounds-extras-base.noarch : Base images for Korora Extras Backrounds
korora-backgrounds-gnome.noarch : Korora 27 default wallpaper for Gnome and Cinnamon
korora-productimg-workstation.x86_64 : Installer branding and configuration for
                                     : Korora
korora-backgrounds-extras-gnome.noarch : Extra Korora Wallpapers for GNOME and
                                       : Cinnamon
=============================== Name Matched: korora ===============================
korora-logos.noarch : Icons and pictures
korora-logos-httpd.noarch : Fedora-related icons and pictures used by httpd

can there occure any issues when removing them?

i will try it later on a test machine and give feedback.

and:

dnf upgrade --refresh

worked without issues

You could replace the Korora packages with the equivalent Fedora ones. Those packages are the ones we modify to remove Fedora branding.

This is sad as I've been with Korora, upgraded on the same install, since version 21.

I'm determined to continue with the same install, by removing any korora repos (are there any?) and potentially breakable korora packages. For instance, I'll remove the korora welcome, but I suspect the korora backgrounds can be left alone on the system since they are only wallpapers.

I did the same for an Arch-based distro that was closed down, so that I'm now effectively running Arch.

I wish you a good rest and also good luck on your new endeavours. Hopefully you are free to answer a few migration questions in this space.

Yes it is sad - i wish the devs of chapeau and korora couldt do something toghether with half the effort or something.

But live goes on, things are coming and going - i also couldt imagine that Fedora rolls a "Consumer Edition" by adopting Korora to something official...

For me it was worth using Korora and i had stable Systems over the last year(s) - i want to contribute now here because i felt like i had to document that one because there was no other guide for it and others where starting to question

This worked flawlessly. For those wishing to keep their Korroa system this method is the way to go. I have several laptops for family members with Korora installed so not having to do a fresh Fedora install is great. Thanks for the controbution netzgestaltung!

I haven't upgraded yet to Fedora 28 as I usually do it in August/Sep, a few months before the next release of Fedora is announced. However, I'm having some weird issues with the Oracle Virtualbox repo not showing the latest Virtual updates after 5.2.8 (I think 5.2.10 and 5.2. 12). I'm guessing that it's not recognising Korora as a Fedora release. Am I right? Does that mean that if I want the VB updates now (ie, prior to the switch to Fedora 28), I have to swap all the fedora-release packages from the korora repo to the ones from the official Fedora 27 repos?

Finally upgraded to Fedora 28 (disabling the korora repos at the same time as advised by the OP), and the old korora distro and os-release information files were automatically replaced by the Fedora ones. RPM-Fusion repos were also automatically set to Fedora 28.

No issues with the upgrade. I deleted most of the korora packages/files left on the system except for the korora logos, which I decided to keep in place of the standard Fedora ones to remind me of the origin of this long-running installation of mine. It's also a nicer logo. :-)

However, Virtualbox continues to have the problem it had in K27, which was it hangs my whole PC when I open it. Not sure why, but I'm removing it and the Oracle repo for now.

I now try to upgrade this installation to fedora 29. I startet with the command line as described in fedoramagazine

Disclaimer working or not reflects only my specific installation. i can not guarantee that it will work for you the same way.

this is what i get from dnf system-upgrade download --releasever=29:

[root@localhost ~]# dnf system-upgrade download --releasever=29
Before you continue ensure that your system is fully upgraded by running "dnf --refresh upgrade". Do you want to continue [y/N]: y
Copr repo for gcolor3 owned by fnux             3.1 kB/s | 2.4 kB     00:00    
Copr repo for pidgin-lurch owned by treba       4.2 kB/s | 3.3 kB     00:00    
Fedora 29 - x86_64 - Updates                    920 kB/s | 5.2 MB     00:05    
Fedora 29 - x86_64                              8.7 MB/s |  62 MB     00:07    
created by dnf config-manager from http://ftp.g 7.4 MB/s | 9.1 MB     00:01    
Google Chrome                                    13 kB/s | 3.9 kB     00:00    
Photivo - photo processor (Fedora_26)           1.7 kB/s | 9.5 kB     00:05    
RPM Fusion for Fedora 29 - Free - Updates       1.8 kB/s | 9.1 kB     00:05    
RPM Fusion for Fedora 29 - Free                 155 kB/s | 759 kB     00:04    
RPM Fusion for Fedora 29 - Nonfree - Updates     36 kB/s | 3.3 kB     00:00    
RPM Fusion for Fedora 29 - Nonfree              147 kB/s | 222 kB     00:01    
TeamViewer - x86_64                             1.4 kB/s | 7.7 kB     00:05    
Letzte Prüfung auf abgelaufene Metadaten: vor 0:00:00 am Do 01 Nov 2018 07:36:58 CET.
Fehler: 
 Problem 1: package anaconda-extras-korora-0.2-1.fc27.x86_64 requires python(abi) = 3.6, but none of the providers can be installed
  - python3-3.6.6-1.fc28.x86_64 does not belong to a distupgrade repository
  - problem with installed package anaconda-extras-korora-0.2-1.fc27.x86_64
 Problem 2: package python3-3.6.6-1.fc28.x86_64 requires python3-libs(x86-64) = 3.6.6-1.fc28, but none of the providers can be installed
  - package canvas-0.5.6-1.fc27.x86_64 requires python(abi) = 3.6, but none of the providers can be installed
  - python3-libs-3.6.6-1.fc28.x86_64 does not belong to a distupgrade repository
  - problem with installed package canvas-0.5.6-1.fc27.x86_64
 Problem 3: package python3-numpy-f2py-1:1.15.1-1.fc29.x86_64 requires python3-devel, but none of the providers can be installed
  - package python3-devel-3.7.1-1.fc29.i686 conflicts with python3 < 3.7.1-1.fc29 provided by python3-3.6.6-1.fc28.x86_64
  - package python3-devel-3.7.1-1.fc29.x86_64 conflicts with python3 < 3.7.1-1.fc29 provided by python3-3.6.6-1.fc28.x86_64
  - package python3-devel-3.7.0-9.fc29.i686 conflicts with python3 < 3.7.0-9.fc29 provided by python3-3.6.6-1.fc28.x86_64
  - package python3-devel-3.7.0-9.fc29.x86_64 conflicts with python3 < 3.7.0-9.fc29 provided by python3-3.6.6-1.fc28.x86_64
  - problem with installed package python3-numpy-f2py-1:1.14.5-1.fc28.x86_64
  - package korora-productimg-workstation-24-1.fc27.x86_64 requires python(abi) = 3.6, but none of the providers can be installed
  - python3-numpy-f2py-1:1.14.5-1.fc28.x86_64 does not belong to a distupgrade repository
  - python3-devel-3.6.6-1.fc28.x86_64 does not belong to a distupgrade repository
  - problem with installed package korora-productimg-workstation-24-1.fc27.x86_64
 Problem 4: package python3-productmd-1.17-1.fc29.noarch requires python(abi) = 3.7, but none of the providers can be installed
  - python3-3.7.1-1.fc29.i686 has inferior architecture
  - python3-3.7.0-9.fc29.i686 has inferior architecture
  - package anaconda-core-29.24.7-1.fc29.x86_64 requires python3-productmd, but none of the providers can be installed
  - cannot install both python3-3.7.1-1.fc29.x86_64 and python3-3.6.6-1.fc28.x86_64
  - cannot install both python3-3.7.0-9.fc29.x86_64 and python3-3.6.6-1.fc28.x86_64
  - problem with installed package anaconda-core-28.22.11-1.fc28.x86_64
  - package python3-lens-0.15.2-1.fc27.x86_64 requires python(abi) = 3.6, but none of the providers can be installed
  - anaconda-core-28.22.11-1.fc28.x86_64 does not belong to a distupgrade repository
  - problem with installed package python3-lens-0.15.2-1.fc27.x86_64
 Problem 5: package python3-libdnf-0.22.0-6.fc29.x86_64 requires libpython3.7m.so.1.0()(64bit), but none of the providers can be installed
  - cannot install both python3-libs-3.7.1-1.fc29.x86_64 and python3-libs-3.6.6-1.fc28.x86_64
  - cannot install both python3-libs-3.7.0-9.fc29.x86_64 and python3-libs-3.6.6-1.fc28.x86_64
  - package python3-dnf-4.0.4-1.fc29.noarch requires python3-libdnf, but none of the providers can be installed
  - package python3-3.6.6-1.fc28.x86_64 requires python3-libs(x86-64) = 3.6.6-1.fc28, but none of the providers can be installed
  - package korora-welcome-26.2-1.fc27.noarch requires python3-dnf, but none of the providers can be installed
  - package python3-lens-gtk-0.15.2-1.fc27.x86_64 requires python(abi) = 3.6, but none of the providers can be installed
  - python3-dnf-2.7.5-12.fc28.noarch does not belong to a distupgrade repository
  - problem with installed package python3-lens-gtk-0.15.2-1.fc27.x86_64
  - problem with installed package korora-welcome-26.2-1.fc27.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)

i now think about --allowerasing as option or uninstalling the korora packages. to keep contents (logo, etc) a backup of the files would be possible i think

after researching i found other peoples programs have similar problems with python 3.6 and in question was what of the list bad to break with --allowerasing.

i decided that i am feeling lucky today(and willing to do a fresh installation if it fails):

[root@localhost ~]# dnf system-upgrade download --releasever=29 --allowerasing
... list of a lot packages
Transaktionsübersicht
========================================================================================================================
Installieren     74 Pakete
Aktualisieren  2473 Pakete
Entfernen        12 Pakete
Zurücksetzen     17 Pakete

Gesamte Downloadgröße: 3.8 G
DNF will only download packages, install gpg keys, and check the transaction.
Ist dies in Ordnung? [j/N]:j
Pakete werden heruntergeladen:
... download list of 2565 packages
Gesamt                                                                                  7.4 MB/s | 3.8 GB     08:40
... list of GPG keys to import and confirm
Schlüssel erfolgreich importiert
Transaktionsüberprüfung wird ausgeführt
Transaktionsprüfung war erfolgreich.
Transaktion wird getestet
Transaktionstest war erfolgreich.
Transaktion wird ausgeführt
  Vorbereitung läuft    :                                                                                           1/1 

Reinstalliert:
  pidgin-lurch.x86_64 0.6.7-1                                                                                           

Entfernt:
  kernel.x86_64 4.18.7-200.fc28                        kernel-core.x86_64 4.18.7-200.fc28                               
  kernel-devel.x86_64 4.18.7-200.fc28                  kernel-modules.x86_64 4.18.7-200.fc28                            
  kernel-modules-extra.x86_64 4.18.7-200.fc28          anaconda-extras-korora.x86_64 0.2-1.fc27                         
  canvas.x86_64 0.5.6-1.fc27                           kmod-VirtualBox-4.18.7-200.fc28.x86_64.x86_64 5.2.18-3.fc28      
  korora-productimg-workstation.x86_64 24-1.fc27       korora-welcome.noarch 26.2-1.fc27                                
  python3-lens.x86_64 0.15.2-1.fc27                    python3-lens-gtk.x86_64 0.15.2-1.fc27 

... list of new installed packages
... list of updated packages

Zurückgesetzt:
  VirtualBox.x86_64 5.2.18-1.fc29                VirtualBox-kmodsrc.noarch 5.2.18-1.fc29                               
  VirtualBox-server.x86_64 5.2.18-1.fc29         akmod-VirtualBox.x86_64 5.2.18-3.fc29                                 
  clementine.x86_64 1.3.1-27.fc29                dtv-scan-tables-legacy.noarch 1-2.20171226git07b18ecef174.fc29        
  iio-sensor-proxy.x86_64 2.4-4.fc29             libreswan.x86_64 3.25-3.fc29.1                                        
  libxcrypt.x86_64 4.2.2-1.fc29                  libxcrypt-common.noarch 4.2.2-1.fc29                                  
  libxcrypt-devel.x86_64 4.2.2-1.fc29            live555.x86_64 2018.09.18-1.fc29                                      
  osinfo-db.noarch 20180920-1.fc29               unbound-libs.x86_64 1.7.3-9.fc29                                      
  vlc.x86_64 3.0.5-3.fc29                        vlc-core.x86_64 3.0.5-3.fc29                                          
  vlc-extras.x86_64 3.0.5-3.fc29                

Fertig.
Download complete! Use 'dnf system-upgrade reboot' to start the upgrade.
To remove cached metadata and transaction use 'dnf system-upgrade clean'
Die heruntergeladenen Pakete wurden bis zur nächsten erfolgreichen Transaktion im Zwischenspeicher abgelegt.
Sie können zwischengespeicherte Pakete mit dem Befehl »dnf clean packages« entfernen.

so next up is dnf system-upgrade reboot

back again - it worked

maybe i should have done better dnf system-upgrade reboot --allowerasing. The log mentioned that it skipped packages with bad dependencies. I have some minor tweaks to do for fuse and maybe a few others that are related to my specific configuration. Kernel Modules also beefed, maybe because of virtualbox...

Hey there, just wanted to thank you for your contribution regarding your solution to the Korora EOF predicament. Following your suggestion I successfully upgraded my machines from Korora to Fedora 28.

With the recent release of Fedora 29, however, it seems that I am unable to upgrade with the following errors.

On the Package Updater Gui "Could not depsolve transaction" with the following errors. Error: Problem 1: package kernel-modules-extra-4.17.12-200.fc28.x86_64 requires kernel-uname-r = 4.17.12-200.fc28.x86_64, but none of the providers can be installed

  • conflicting requests Problem 2: package kernel-4.17.12-200.fc28.x86_64 requires kernel-core-uname-r = 4.17.12-200.fc28.x86_64, but none of the providers can be installed
  • conflicting requests

Do you have any tips?

Anyway, thanks again for your suggestions above, it saved me time and it's been operating really well.

UPDATE: I actually managed to sort the issue out by editing the /etc/dnf/dnf.conf file and increasing the installonly_limit from 3 to 5. This is meant to relate to the number of installonly packages allowed to be installed concurrently. 3 is the default with 2 being the minimum. Values 0 or 1 will set this to unlimited. I'm still not sure why this restricted the upgrade though.

Please Log In to participate with the community.