When I recently updated my Leap 15.1 systems, the “Beta” disappeared from the version information in “/etc/os-release”. That indicates that we are now seeing release candidates rather than beta versions. The final release is expected to be in late May.
After noticing this, I download the DVD installer iso so that I could try a clean install. As usual, I used “aria2c” for the download. And I also downloaded the sha256 checksum file. The gpg signature on the checksum file validated that download, and then the checksum validated the iso download.
The install itself went well. I mostly took the defaults. I selected the KDE desktop (there isn’t a default choice there). And this install was on a UEFI virtual machine (under KVM).
As indicated, I took the defaults for most choices. And, as a result, the installer used “btrfs”. I have normally avoided “btrfs”, and will probably revert to using “ext4”.
OpenSUSE 15.1 is moving along steadily. I have been testing most releases. Sometimes I download the DVD installer for testing an install. And, at other times, I just update my already installed systems.
During the alpha testing phase, I was mostly doing this in two differently configured KVM virtual machines.
The first Beta release was Build414.1, which was available Thursday last week. I downloaded DVD installer for that, and wrote that to a USB drive. I then installed on a virtual machine. And later that same day, I installed on a real computer (a laptop).
Since that time, there have been two more releases — Build416.2 was available around two days ago. And, today, Build417.2 came out.
My update procedure, at present, is to use
I’ve been testing Leap 15.0 for some time. I have not always posted about that. As long as it is working, a post would not be very interesting. However, it is time to sum up the current status.
We now have a release date for the finalized Leap 15.0. The plan is to release on May 25, at 12:00 UTC. See the announcement for more details:
I’m expecting further test releases before that date. They will mostly be release candidates. My own plans are to update my current installs for each release candidate. I probably won’t do another full install on a real machine, but I will install some of the release candidates on a KVM virtual machine.
My current usage
At present I am still using Leap 42.3 on my main desktop. Sometime within the next week or so, I plan to switch to full time use of Leap 15.0, and mostly retire 42.3.
Since my last post on Leap 15.0, Build 139.1 was released. It was time for a new install, so I downloaded the iso. And then I installed to a virtual machine.
I ran into some interesting bugs.
It told me that my EFI partition (at 33M) was too small. Well, I agree that’s small. But it is what an earlier build of 15.0 had created. It looks as if they have adjusted to a more reasonable size.
I told the installer to go ahead, in spite of the small EFI partition size. And I then ran into an additional bug. The installer said that some devices (the ones to which I was installing) did not exist. See bug 1082143 for details.
The installer allowed me to continue in spite of those errors. And the install was successful. So the errors were bogus.
A Tumbleweed install
Back to Tumbleweed. Actually, that Leap 15.0 is part of the background. I decided to try installing Tumbleweed into the same virtual machine where I had just installed Leap 15.0. However, this time I would allow it to delete everything on disk and make a fresh start.
Since my last post on 15.0, there have been several new beta releases. We have seen Build115.1, Build 124.1, Build 127.1, Build 128.1 and Build 129.1.
With that many builds, I have not been downloading them all. I have been updating my 15.0 systems. I am updating them in the same way that I update openSUSE Tumbleweed. That is, I am using
to update from the repos. My most recent install attempts have been with Build127.1, though most of my systems are now updated to the latest version.
Things are mostly going well with 15.0. The final release is still planned for May. But if you want to take a look at pre-release versions, then now is a good time to try.
What I have tested is mainly working well. There are still a few bugs in the partitioner, as used for install. Some of those bugs have already been fixed in the latest updates.
Build 109.3 of Leap 15.0 was announced on Friday. So I download and installed. With build 109.3, it is now announcing itself as a Beta release. Previous releases that I tested have indicated that they were Alpha releases.
I followed my usual practice of downloading with “aria2c”. I am using the download site download.opensuse.org/distribution/leap/15.0/iso/. I first used “wget” to download “openSUSE-Leap-15.0-DVD-x86_64-Build109.3-Media.iso.sha256” (the checksum file). I then verified its gpg signature. Next, I downloaded the iso itself. And I used “sha256sum” to verify the sha256 checksum. And, following that, I wrote the iso to an 8G USB flash drive. Read More…
I notice, on Thursday Jan 4th, that Build 84.1 was available at the download site. So I download, and did some testing.
As is my usual practice, I used “aria2c” to download the iso, and I used “wget” to download the checksum file. I then verified the “gpg” signature on the checksum file, after which I used the checksum to verify the downloaded iso file.
My first test was to update an existing 15.0 system. For that, I wrote the iso to a USB flash drive. I then configured that flash drive as a repo. And, following that, I used “zypper dup” to bring the existing 15.0 system up to date. When I do this, I can see that most of the updated software comes from the local USB that I configured as a repo. Some updated software comes from the online repos. The “zypper” command seems to recognize that the repo on the local USB is to be preferred to the online repo, when the software is available in both places.
The next Leap version, 15.0, is still showing as an alpha release. Still, I was happy to see the install iso for Build 79.1 show up at the download site last Wednesday. At around the same time, there was an update message on the factory mailing list, reporting the current status of Leap 15.0.
According to that update message, the current aim is for a final release in May of 2018. That seems more realistic than the earlier (Feb/March) suggestion.
When I noticed that the iso was available, I of course downloaded it. I followed my usual practice for this:
wget http://download.opensuse.org/distribution/leap/15.0/iso/openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso.sha256 aria2c -V -R http://download.opensuse.org/distribution/leap/15.0/iso/openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso gpg --verify openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso.sha256 sha256sum -c openSUSE-Leap-15.0-DVD-x86_64-Build79.1-Media.iso.sha256
In turn, those commands download the sha256 checksum and the iso itself. Then they verify the gpg signature on the checksum file, and the checksum of the downloaded iso file.
I did another install of 42.3 on Thursday. I guess I’m a tad slow reporting that. This install was for Build 0283. I installed it on my main desktop. At the moment, I am still running 42.2 on that computer. I installed 42.3 on a separate area of the disk.
I do plan to soon switch to running 42.3 full time. That’s the best way of testing this beta release. The final release is due in about one month.
Downloading and installing
I followed my usual procedure. I used “aria2c” to download the iso for the DVD installer. I used “wget” to download the sha256 checksum file. Then I verified the gpg signature on the checksum file, and verified that the checksum matched the downloaded iso.
The next step was to write the iso file to a USB flash drive. I used “dd_rescue” for that. Then I booted the USB, and installed 42.3
Installation itself went well. Everything worked about as expected. Following the install, I booted into 42.3, and did a little final tweaking. And I also added additional software that is not on the install media but is in the repos.
Release candidate 2 (or RC2) is now out. It was announced earlier today:
As you might expect, I downloaded the iso for the DVD installer, and “burned” that to a USB flash drive. I then did an install using it.
The install went quite well. I followed the same general method as in my install for RC1.
I noticed one change. Early in the install, I was told about “Mesa-dri-nouveau”. This is a new package, broken out from mesa. The notification asked me whether I wanted to accept this package. If I did not accept, then 3D would be emulated in software.
I accepted the package. I cannot test it otherwise.
Unfortunately, it does not work well enough with my nvidia card.