Monthly Archives: February 2017

Next release plans

We are planning™ to release a full set of siduction images with all flavours before going to CLT (Chemnitzer Linux-Tage) next month. There are at least three reasons for that:

  • We can boast about it at the conference
  • We will have a new installer for you to try
  • We promised to do so

And here are the gory details: Six years ago we thought it would be a cool idea to have our installer running in a browser with the help of a tiny http server. Today for some reasons we do not think it is quite that cool. One of the reasons for that being the fact, that the guy who initialy wrote the installer is not available anymore.

Then, about three years ago someone by the name of Teo Mrnjavac had a marvelous idea, that will, similar to systemd, unify linux in a in my humble opinion positive way. I am talking about the Calamares Installer Framework. As you can see at the bottom of their webpage, your favorite distro is listed there already. It is used more and more by distributions and every one of them makes the code better. Sharing one installer eases a lot of problems for smaller distributions. The partitioning is done by KDE’s partition manager. What it does not do yet is LVM and RAID, but those are in the pipeline. Also, Calamares will make it’s way into Debian soon.

So for the past weeks that is what we have been working on. Calamares is C++, Qt 5 for the user interface and python modules to pick what you need and configure to your liking. Then apply a branding and you are done. Of course this was the fast-forward-mode, but we managed to get it up and running in less than two weeks. We are doing more testing to make sure it lives up to it’s reputation with siduction as well.

It also works fine with BIOS and UEFI, which kills another problem for us: The integration of UEFI in the old installer was far from perfect and included manual setup work before starting the installer. Given that we do not run into any blockers with the installer, we are confident that the freeze for Debian GNU/Linux 9 »Stretch« will allow us a release of all flavours without too many problems.

We also plan to make this next release our first release with 64-bit only. Yep, we think the time is right to drop the 32-bit plattform without making too many users unhappy. Should you be one of those not happy with our plan, please let us know your reasons on our forum. If you have a good reason to still run 32-bit, you might even be able to talk us into a custom build. But overall, dropping this architecture saves us a lot of time that can be better spent elsewhere.

Flatpak with siduction

Yesterday I wrote about how to install and use Snap to install the latest LibreOffice 5.3. I promised to do the same with Fedora/GNOME’s alternative package format Flatpak. Needless to say this also applies for pure Debian Unstable and Debian Testing installs. For Debian Jessie you would need backports enabled. For yesterdays post on Snap, the same goes for Unstable and Testing, whereas Jessie is left out in the rain for now.

Even though there is no flatpak for the latest version 5.3 of LibreOffice yet, we will install LO 5.2.5, which then can be updated to 5.3 in a few hours or days. Setting the base framework for flatpak is a little more work as you have to install the basic runtime (at least on a KDE system, maybe it comes automaticaly with a GNOME install. OK, lets get started withthe package itself:
# apt install flatpak
Now we need to get the runtime:
$ wget
$ flatpak remote-add --user --gpg-import=gnome-sdk.gpg gnome
$ flatpak install --user gnome org.gnome.Platform 3.20

Now you can download the flatpak package for Libreoffice from the Flatpak-Apps page. Move to the directory where the download landed and install it:
$ flatpak install --user --bundle LibreOffice.flatpak
When that is done, you can start LO from the same directory by running:
$ flatpak run org.libreoffice.LibreOffice

Updates can be performed by running:
$ flatpak update --user org.libreoffice.LibreOffice

These alternate packaging formats are ideal for installing software that is not (yet) available in your distribution or versions not yet available, like LO 5.3 in our example. Developers can install different versions of a software that do not interfer with each other for testing. Which one of the new self-contained package formats (there is also Appimage) you prefer is totaly up to you. They offer a sandboxing model that is supposed the keep them separated from the environment. In the case of Flatpak they can talk to each other by means of Flatpak Portals.

Snaps with siduction

I am sure, everyone has heard about Ubuntu’s new package format snap by now. Today I wanted to try the brand new and still hot off the press LibreOffice 5.3 for a review. So I found that the Document Foundation had a snap ready for deployment. The prerequisites for siduction are not many:
# apt update && apt install snapd
After that, you can check, which snaps are avaialable for LibreOffice with:
$ snap info libreoffice
As you can see, the new version 5.3 is in the edge-channel. That is all you need to know to install it with:
# snap install libreoffice --channel=edge
Afterwards a repeated
$ snap info libreoffice
will reflect the installed packages. As you might have a version of LibreOffice already installed through your package manager, you will need to start the snap, using the full path:
$ /snap/bin/libreoffice &
Later on you can refresh them with
$ snap refresh libreoffice

Just a day or two ago, the first snaps of KDE apps turned up in the KDE-Store Tomorrow I will give flatpak, the alternative new package format by Fedora a try with libreoffice. You can read the results here tomorrow