As mentioned in my previous post, the plan for the jump project is to be able to take some packages directly from SLE to build the next Leap version. Since that post, an updated version has been release. It is Build76.2, released 4 days ago. So I downloaded this release, and installed to a virtual machine for testing.
Again, I installed only the KDE desktop. And KDE does not come from SLE, though other basic packages do.
Here are some of things I have seen change in the latest release:
- When installed, this is now called “Jump 15.2.1” instead of Leap 15.2.
- It now has its own repos. Previously, if you installed Jump and then updated it, you would have a standard Leap. Now if you install Jump 15.2.1 and update it, you still have Jump. This is a necessary step, in moving toward 15.3.
Yesterday, I took a look at the Jump 15.2 download site.
Well, more accurately, I looked to see if I could find a download site. And it was there, with an iso ready for test.
For future reference, follow this link to the DOWNLOAD SITE
So what is Jump 15.2? It is really Leap 15.2, but being rebuilt in a different way. It is a test for how 15.3 will be built.
The Jump project
With the Leap series thus far, openSUSE is using some software sources from SLE and some that came from Tumbleweed. Those sources are then builts at OBS (the Open Build System) to produce the software release.
With the Jump project, the idea is to reduce some of the redundant operations. So the Jump release is supposed to use rpm binary packages that were built for SLE where available, and separately build the binary packages where the source does not come directly from SLE.
Yes, Leap 15.2 is still in Beta testing. However, I have now switched over to 15.2 on my main desktop.
I installed 15.2 some time ago, and have been periodically updating it since then. My plan was to switch to 15.2 shortly before the release date, because I can test more thoroughly when it is the system that I use for normal computing activity.
The original plan was for Leap 15.2 to be released in May, which is this month. However, there has been some slippage in that date:
Final release of Leap 15.2 is now expected to be in early July. In spite of that delay, I decided to go ahead with my planned switchover to using 15.2.
There’s a new plan afoot to more closely link Leap with SLE (the Enterprise SUSE release). This is the “Jump” project, mentioned that factory mailing list message, an that is the reason for the slippage. We will probably see that change for Leap 15.3, but there are some preparations being made now. The idea is that for packages that come from SLE, we will use them directly without have to rebuild. That should save effort. Leap packages that do not come from SLE will continue to be handled as they are now.
My main desktop is also an NFS and Samba server for the home network. I had already setup both NFS and Samba on the 15.2 install, a month or two ago.
I have been testing and blogging about the Alpha release for a while. But now 15.2 has reached the Beta phase. This suggests that it is closer to the final release version. As I understand it, once it reaches the beta level there are more restrictions on what software changes will be permitted.
Okay, I’m a few days late reporting this. The announcement was actually on Feb 20th:
At the time of the announcement, the software was still not available. But that showed up a few hours later:
So I have been busy over the last few days. I downloaded the DVD installer iso, and wrote that to an 8G USB drive. I used “dd_rescue” to write to the device. And then it was off to install and do some preliminary testing.
I have installed on 4 machines thus far. Two use traditional BIOS booting, and two use UEFI booting. I have secure-boot enabled on one of the two UEFI machines.
There was another update to openSUSE Leap 15.2 last week. I updated my installs at that time. I currently have it installed in two KVM virtual machines and on an external USB drive. I’ll note that 15.2 is still at the Alpha testing phase.
The most recent update brought Gnome to version 3.34.2. This will probably be close the final release version. It seems to be working pretty well. OpenSUSE Tumbleweed went to Gnome 3.34.2 some time ago. But, judging by bug reports, there were some problems in preparing this Gnome version for SLE 15 and for Leap 15.2. Apparently, those problems have been mostly resolved. Read More…
I noticed a new release of Leap 15.2Alpha. And, surprisingly, it comes with a 5.3 kernel — specifically kernel 5.3.0-rc5. There’s a mailing list discussion of this on the factory mailing list.
It turns out that this was seen as a good way of testing some of the new features of the 5.3 kernel. When Leap 15.2 is released (tentatively planned for May 2020), it is hard to guess whether it will have a 5.3 kernel or an older kernel.
For now, as a volunteer tester of Leap 15.2, I have not run into any problems with the new kernel.
This seemed like a good time for another install of Leap 15.2Alpha. This time I installed into a KVM virtual machine with an existing encrypted LVM, and using UEFI booting.
To use the existing LVM, I provided the encryption key when prompted by the installer. Then, at the partitioning stage, I chose to use the expert partitioner, starting with existing partitions (rather than with the proposed partitions).
At this point there was an option to import mount points. I used that, so that I was using the same partition that I had previously used with Leap 15.1 on that virtual machine.
The install went well. The installed system seems to be running well. So there’s not actually much to say, except for the use of the 5.3 kernel.
I recently checked what I expect to be the download page for Leap 15.2. I used the url http://download.opensuse.org/distribution/leap/15.2/iso/ which is almost the same as the url for the 15.1 download page — I just changed the “15.1” to “15.2”. And it turned out that there was an iso there waiting to be downloaded and tested.
I have been noticing occasional messages on the email lists about preparations for 15.2, and that’s why I checked. The iso has a date of July 29th, but the sha256 checksum file has a more recent date of Aug 09.
I used “wget” to download the “.sha256” checksum file. And then I used “aria2c” to download the iso itself. I then verified the gpg signature on the checksum file, with
gpg --verify *6
after which I verified the checksum with
sha256sum -c *6
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.