Just been released: Fedora 27

Fedora fans all over the world have just excited for the release of the new version, Fedora 27. As usual, the the version brings several fixes and improvements as well as adds some new features.

Nevertheless, though, as for KDE spin, it’s likely there’s nothing really fresh in this new version of Fedora. From above screencast I found on youtube, we can see that the version of Plasma is 5.10.5, which is not the latest one: 5.11 that has new couple of brand new stuffs like the new Systemsettings UI design and Wayland support. But on the other hand, F27 KDE has the newest Qt version shipped, i.e 5.9.1 –nearly the newest one though.

As I wrote this post, I was in upgrading process. By the way, I started switching to Fedora since the version 23 back then. And I have successfully passed 3 times of upgrade processes, not by reinstalling a new ISO image. So, I feel so courageous to just upgrade it by DNF system-upgrade. Even though I need to download 2,4 GB of new packages!

Screenshot_20171115_155502
Upgrade process of Fedora 27

 

 

Screenshot_20171116_011020
Eventually… download finished, and then wait for the installation

Steps to upgrade

According to Fedora Magazine guide to upgrading Fedora 26 to 27, these are the DNF commands:

  1. sudo dnf upgrade --refresh
  2. sudo dnf install dnf-plugin-system-upgrade
  3. sudo dnf system-upgrade download --releasever=27
  4. sudo dnf system-upgrade reboot
Advertisements

RPM Packaging tutorial for Fedora

Hi again! You might be surprised for I post this in less than 24 hours after the previous one, so did I. 😁

Here will I share my first ever experience on packaging an RPM package in Fedora Linux. Umm, actually not the first time though, as I have been trying this before, but I didn’t record it in my mind. I mean I forget when or how it was going. 😁 Continue reading RPM Packaging tutorial for Fedora

Choosing the best version of Fedora app packages

Downgrading is something that looks scary. Come to think of it: come back to the past is something everyone afraid of, right? 😀 Nevertheless, sometimes downgrading is the option we want to choose when the current app is not working well, and there is no option to upgrade.

Recently I had VLC in Fedora that cannot stream from my Raspberry Pi DLNA server. The server is not listed on the UPNP playlist. While when I try VLC in Android, it could see the server. In the debug log message (CTRL+M), there were a couple of error messages, something like upnp services discovery: Initializing libupnp on '(null)'.

And actually, the workaround is simple: there is a feature of DNF to downgrade the working version of packages. In this case, the newest version of VLC that I installed from COPR repo cannot work with the latest libupnp version. Then I have to downgrade it to the previous version which fortunately still working.

sudo dnf downgrade libupnp

screenshot_20161227_214622