Planet openSUSE Planet openSUSE Dominique Leuenberger openSUSE Tumbleweed – Review of the week 2021/18 Fri, 07 May 2021 14:40:06 +0000 <p>Dear Tumbleweed users and hackers,</p> <p>Week 18 was a regular one with almost daily snapshots being published. A total of six snapshots went out to the users (0429, 0430, 0502, 0503, 0504, and 0506).</p> <p>The main changes in those snapshots included:</p> <ul> <li>GTK+ 3.24.29</li> <li>TeXLive 2021</li> <li>PHP 7.4.18</li> <li>Python 3.8.9</li> <li>We switched from openMPI2 to openMPI4</li> </ul> <p>Changes currently being prepared in the staging areas:</p> <ul> <li>GNOME 40.1</li> <li>KDE Plasma 5.21.5</li> <li>icu 69.1: for the ring packages, nodejs15 seems to be the last blocker</li> <li>Switch from go 1.15 to go 1.16: most packages fixed, the last failure in Staging:M is cilium</li> <li>GCC 11 as default compiler: Move from special-purpose Staging:Gcc7 to Staging:O (incl. openQA test coverage). There are a few more build failures to be addressed.</li> <li>UsrMerge: The current state is that we checked in all changes and are planning on actually doing the switch somewhen in the not too far future, likely together with the planned distro-rebuild for GCC 11</li> </ul> Martin de Boer Trying out Phosh shell on PinePhone and openSUSE Tumbleweed Tue, 04 May 2021 21:49:59 +0000 <p>During my time with Phosh on PinePhone and openSUSE Tumbleweed, I have stumbled on a couple of issues that made clear that the experience still needed some polish. This is not a critic against the Phosh or the GNOME project. I don’t envy the developers that need to ensure that their app works across many form factors. </p> <p>However, I can see that the additional time that the KDE project has spend on polishing their experience has paid off. In this article, I will describe the issues that I encountered and how you can fix them. I like everyone to try out this GNOME based mobile experience. It’s awesome to see FOSS beyond the PC / Laptop. </p> <h2>Where is my keyboard?</h2> <p>Unlocking your phone and then your SIM card are the number 1 and 2 things to do when you boot up a smartphone. However, its hard to unlock your SIM card without a virtual keyboard. And that was exactly what I encountered. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3054"></figure> <p>How do you progress? Click on Cancel and go to the Settings. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3055"></figure> <p>There is a category for Accessibility and under Typing you find a toggle for the (on) Screen Keyboard. Hit the switch!</p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3056"></figure> <p>You will find a keyboard icon at the bottom of the phone. Touching this keyboard button automatically opens and closes the virtual keyboard. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3057"></figure> <p>Now it is time to unlock that Simcard. Go to the Mobile category and click on Unlock.</p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3058"></figure> <p>Enter your Pincode and now you can make phone calls. The sound quality is excellent. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3060"></figure> <h2>The GNOME experience, but mobile</h2> <p>Phosh is GNOME. And that becomes very apparent when you go from the full-screen experience to the windowed experience. (Yes, you can do that.) Just drag the title-bar down and your windows are in plain sight. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3065"></figure> <p>In many ways you can see that most apps are plain desktop apps (up-scaled by 200%) on a mobile device screen. Take GNOME Software for instance, which is clearly not designed as a Mobile First app. However, it does everything that it needs to do. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3066"></figure> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3067"></figure> <p>The most funny example is when you open LibreOffice. (Yes, you can do that.) It is amazing that you can do this at all. I do recommend that you switch to a Dock and a FullHD monitor to work on your LibreOffice files. You won’t get very far on the PinePhone screen. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3068"></figure> <h2>Phosh looks good!</h2> <p>The parts that are developed for Phosh are designed to be Mobile First. You can see that the experience is optimized for those parts. Scrolling is relatively smooth (the PinePhone is not the fastest device and hardware acceleration is not working). The general design direction is clean and functional. The Lock screen is a good example of that design esthetic. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3062"></figure> <p>When you unlock Phosh, you are greeted by the App grid. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3063"></figure> <p>The Phone app is clearly designed to be a Mobile First experience.</p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3069"></figure> <p>When you swipe up, you go back to the Overview, where your open windows (Yes, it does multitasking) are shown above the App grid. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3064"></figure> <p>GNOME already featured a very clean and functional look for its apps. That translates quite well to a mobile form factor. GNOME Maps for instance looks quite good. The buttons could be a bit bigger, but it works fine on the PinePhone.</p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3070"></figure> <p>GNOME Weather works as you expect. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3071"></figure> <p>And GNOME Web (or Epiphany) works very well as a mobile browser. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3073"></figure> <p>The Smartphone app is called Megapixels. That app is still a work in progress. In contrast to opening this app on KDE Plasma Mobile, I can now see colors. The user interface of Megapixels is easy to understand. But there are very few features to work with. </p> <figure class="wp-block-image size-large"><img width="819" height="1024" src="//" alt="" class="wp-image-3074"></figure> <p>GNOME Clocks could also do better. Everything is very small and there is a lot of unused screen estate. Which is weird, because on my desktop PC the interface looks more mobile friendly. However, there is a minimum width for the window on my desktop PC. Maybe this is what happens, when you make the window even smaller. </p> <figure class="wp-block-image size-large"><img width="1024" height="1024" src="//" alt="" class="wp-image-3072"></figure> <h2>Conclusion</h2> <p>I liked exploring Phosh on openSUSE Tumbleweed. I am not in love with the experience, but I do like the way it operates. It’s a very functional experience. For some people, that is all it needs to be. With some love and development from the GNOME community, I am certain that it will reach the same level as polish that the KDE community has. </p> <p>What I really like about the PinePhone is that I can install any OS to the phone that I like to explore. It is a bit similar to using Virtualbox to explore the various Linux distributions and the various Desktop Environments. You can just wipe your phone and flash another Operating System on it and try it out. Every experience is unique. Although not every experience is right for me, it is fun poking around. And that is what FOSS is all about (for me). </p> <p><strong>Published on: 4 May 2021</strong></p> 3bb8ab65-05eb-463c-ad10-a3830cca5502:1baeb576-aa1e-46d7-8bbb-42108b857411 Peter Czanik Rocky Linux, AlmaLinux, CentOS &amp; syslog-ng Tue, 04 May 2021 11:42:20 +0000 <p>Last year, the CentOS project announced a <a href="">major shift</a> in strategy. Until recently, CentOS Linux has been a rebuild of Red Hat Enterprise Linux (RHEL) sources, each RHEL release was quickly followed by a corresponding CentOS Linux release. While CentOS 7 keeps working this way, CentOS 8 will reach its end of life by the end of this year. The CentOS project is focusing on CentOS Stream. It is a continuous stream of bug fixes and new features.</p> <p>Some of the users were not happy about the change, that is how Rocky Linux and AlmaLinux were born.</p> <p>As about 80% of syslog-ng Open Source Edition (OSE) installations run on CentOS and RHEL (<a href="/community/b/blog/posts/embedded-syslog-ng-bmw-i3-all-electric-car">if we do not count Kindle devices…</a>), support for CentOS Stream and CentOS Linux alternatives is a returning question. From this blog, you can learn about CentOS Stream and CentOS Linux alternatives and how the situation is affecting syslog-ng OSE users.</p> <h2 class="western">CentOS Linux vs. CentOS Stream</h2> <p>CentOS Linux was a recompilation of RHEL source packages. Of course, it is not this simple, there is a re-branding as well. But from the users’ point of view, it was RHEL for free with a slight delay.</p> <p>CentOS Stream does not have releases in a traditional sense. New features and bug fixes are integrated continuously. At and Red Hat Summit, various Red Hat managers described CentOS Stream as a development version of RHEL where new technologies are tested, and people can try new technologies before they enter RHEL. However, CentOS and Fedora developers consider CentOS Stream a stable and production-ready operating system. As you will see, most likely both sides are right.</p> <p>Talking to many syslog-ng and CentOS Linux users, the attitude towards CentOS Stream can be very different based on company size and job function as well. It is true for every generalization that it is not valid for everybody, still, I see three major trends:</p> <ul> <li> <p>Large companies with dedicated OS teams love CentOS Stream. They receive new features as soon as they are available, there is no need to wait for the next release. Inside their companies they can do their own operating system releases based on CentOS Stream. A good talk about it was <a href="">given by Facebook at</a>, but I had similar impressions in private discussions as well.</p> </li> <li> <p>Developers too like CentOS Stream: instead of larger jumps, they receive changes as they appear in much smaller dozes.</p> </li> <li> <p>The rest of the users, mostly smaller and mid-sized companies are not too enthusiastic about the change. Some already switched to something completely different, others are waiting for CentOS Linux alternatives. They do not have resources to tailor their infrastructure to an ever-changing CentOS Stream, traditional releases and occasional jumps suit their needs better.</p> </li> </ul> <h2 class="western">CentOS Linux alternatives</h2> <p>Red Hat says that if you want to use traditional releases, the best alternative to CentOS Linux is to use RHEL. Of course, it costs money, but if you are a small business, you can get free RHEL licenses for up to 16 hosts.</p> <p>From those who already did the jump to another distribution, many switched to Ubuntu LTS. Others changed to openSUSE Leap, which is the closest nonRed Hat OS to CentOS in many ways. But I even talked to CentOS Linux users who ended up running FreeBSD. And – while many syslog-ng users consider Oracle Linux almost as controversial as CentOS Stream – quite a few switched to this RHEL clone.</p> <p>Many CentOS Linux users are still waiting. The reason is, that there are two more CentOS Linux replacements under way.</p> <ul> <li> <p><a href="">AlmaLinux</a> was made by the same team who created CloudLinux OS. It is in release candidate phase, and it has been available for months. Some people use it already in production.</p> </li> <li> <p><a href="">Rocky Linux</a> was created from scratch by a large community of developers led by Gregory Kurtzer, who was also part of the original CentOS Linux effort. Their first release candidate arrived on 1st May.</p> </li> </ul> <h2 class="western">And what about syslog-ng support?</h2> <p>I maintain syslog-ng in the official EPEL repository and also maintain some unofficial syslog-ng repositories. So, no wonder that I was a bit nervous when I learned that instead of CentOS Linux and RHEL we will have RHEL, CentOS Stream, AlmaLinux, Rocky Linux, and even Oracle Linux.</p> <p>The good news is that after initial testing, it does not seem to create any extra work for me. Of course, I could not test all the syslog-ng features on all platforms, but anything I tested worked fine regardlessof the distribution I used. Both the EPEL packages and my unofficial packages work perfectly. I even test CentOS Stream regularly, and while I ran into minor problems and inconveniences, none of those affected syslog-ng in any way until now.</p> <h2 class="western">What is next?</h2> <p>I do not have a recommendation here for the OS. CentOS Linux 8 is going to reach its end of life at the end of the year. Make sure that you switch to CentOS Stream or one of its alternatives during the summer or early autumn. No matter what you choose, syslog-ng will work just fine on the OS of your choice. If you report a problem, I will be able to test it on RHEL, CentOS Stream, Alma Linux, Rocky Linux, and even on Oracle Linux. But based on my current experiences, I do not expect any differences between these platforms.</p> <p><br> </p> <p>If you have questions or comments related to syslog-ng, do not hesitate to contact us. You can reach us by email or even chat with us. For a list of possibilities, check our GitHub page under the “Community” section at <a href=""></a>. On Twitter, I am available as <a href="">@Pczanik</a>.</p> <div style="clear:both;"></div>'ve-already-commited-to-git? Santiago Zarate How to edit stuff that you've already commited to git? (And squash as a bonus) Tue, 04 May 2021 00:00:00 +0000've-already-commited-to-git.html <p>So, you’re in the middle of a review, and have couple of commits but one of the comments is asking you to modify a line that belongs to second to last, or even the first commit in your list, and you’re not willing to do:</p> <p><code class="language-plaintext highlighter-rouge">git commit -m "Add fixes from the review" $file</code></p> <p>Or you simply don’t know, and have no idea what <code class="language-plaintext highlighter-rouge">squash</code> or <code class="language-plaintext highlighter-rouge">rebase</code> means?, well I won’t explain rebase today, but I will explain <code class="language-plaintext highlighter-rouge">rebase</code></p> <p><img src="//" alt="DON'T PANIC"></p> <p>See how I do it, and also how do I screw up!</p> <p><a href=""><img src="//" alt="asciicast"></a></p> <p>It all boils down to making sure that you <strong>trust</strong> git, and hope that things are small enough so that if you lose the stash, you can always rewrite it.</p> <p>So in the end, for me it was:</p> <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>git fetch origin git rebase -i origin/master # if your branch is not clean, git will complain and stop git stash # because my branch was not clean, and my desired change was already done git rebase -i origin/master # now, let's do a rebase # edit desired commits, for this add the edit (or an e) before the commit # save and quit vim ([esc]+[:][x] or [esc]+[:][w][q], or your editor, if you're using something else git stash pop # because I already had my change $HACK # if you get conflicts or if you want to modify more # be careful here, if you rewrite history too much # you will end up in Back to the Future II # Luckly you can do git rebase --abort git commit --amend $files #(alternatively, git add $files first then git commit --amend git rebase --continue git push -f # I think you will need to add remote+branch, git will remind you # go on with your life </code></pre></div></div> <p>(Note: A squash is gonna put all of the commits together, just make sure that there’s an order:</p> <ul> <li>pick COMMIT1</li> <li>pick COMMIT2</li> <li>squash COMMIT3 # (Git will combine this commit, with the one above iir, so COMMIT2+COMMIT3 and git will ask you for a new commit message)</li> </ul> YaST Team Digest of YaST Development Sprint 122 Mon, 03 May 2021 06:00:00 +0000 <p>If something is not broken, do not fix it. Following that principle, the YaST Team spent almost no time on the latest sprint working on SUSE Linux Enterprise 15 SP3 or openSUSE Leap 15.3. But that doesn’t mean we remained idle. Quite the opposite, we invested our time reorganizing some of the YaST internals. An effort that hopefully will pay off in the mid term and that affects topics like:</p> <ul> <li>Management of local users, specially during installation.</li> <li>Unification of the code for configuring the network.</li> <li>Error handling and reporting.</li> <li>Reorganization of our UI toolkit.</li> </ul> <p>So let’s take a closer look to all that.</p> <p>In our previous blog post we already announced we were considering to refactor the YaST Users modules to improve the management of local users and to reduce the risk associated to the current complexity of the module. We can now say we are making good progress in that front. We are working on a separate branch of the development repository that is not submitted to Tumbleweed or any other available distribution, which means we still have nothing concrete our users can test. But we hope to have the creation of users during installation completely rewritten by the end of next sprint, while still remaining compatible with all other YaST components that rely on user management.</p> <p>Another milestone we reached on the latest sprint regarding YaST internal organization was the removal of the legacy network component known as <code class="language-plaintext highlighter-rouge">LanItems</code>. Everything started with the report of <a href="">bug#1180085</a> that was produced because the installer, which uses the new <code class="language-plaintext highlighter-rouge">Y2Network</code> (a.k.a. network-ng) infrastructure for most tasks, was still relying on that legacy component for proposing the installation of the <code class="language-plaintext highlighter-rouge">wpa_supplicant</code> package. So we took the opportunity to seek and destroy all usage of the old component all along YaST, replacing the calls to it with the equivalent ones in the new infrastructure. Less code to maintain in parallel, less room for bugs.</p> <p>That was not the only occasion during this sprint in which we turned a bug into an opportunity to improve YaST internals. It was also reported that using an invalid value for the <code class="language-plaintext highlighter-rouge">bootmode</code> or <code class="language-plaintext highlighter-rouge">startmode</code> fields of a network configuration file could produce a crash in YaST. In addition to fixing that problem, we took the opportunity to <a href="">introduce a whole new general mechanism</a> to handle errors in YaST and report them to the user in a structured and centralized way. Apart from the YaST Network module, that new internal infrastructure will be adopted by several parts of YaST during subsequent sprints. In fact, it’s already being used in the rewritten management of local users mentioned at the beginning of this post.</p> <p>Last but not least, we would like to mention that we keep working to improve the new unified <a href="">repository of LibYUI</a>. Apart from revamping the README file that serves as landing page, we created new scripts for a more pleasant and flexible building process, we are improving the compatibility with the Gtk backend and with libyui-mga (the extra components developed and maintained by Mageia) and we published the <a href="">API documentation</a> in a central location that is now automatically updated on every change of the repository.</p> <p>Of course, during the process of implementing all the mentioned improvements, we fixed several other bugs for SLE-15-SP3 and openSUSE Leap 15.3 and also for older releases and Tumbleweed. But, who wants to write about boring bug fixes? We prefer to go back to work and prepare more exciting news for our next report in two weeks from now. See you then!</p> Dominique Leuenberger openSUSE Tumbleweed – Review of the week 2021/17 Fri, 30 Apr 2021 14:05:40 +0000 <p>Dear Tumbleweed users and hackers,</p> <p>This week seemed rather calm except for a minor glitch with the Linux kernel 5.11.16, which, due to a build failure, was out of sync between the various kernel sub-packages for one snapshot. The pace of the snapshots was averaged at 5 snapshots (0423, 0425, 0426, 0427, and 0428).</p> <p>The changes included things like:</p> <ul> <li>Linux kernel 5.11.16 &amp; 5.12.0</li> <li>KDE Gear 21.04.0 (formerly KDE Applications)</li> <li>Mozilla Firefox 88.0</li> <li>NetworkManager 1.30.4</li> <li>Virtualbox 6.1.20: some services were renamed; e.g. vboxautostart.service” is replaced by “vboxautostart-service.service</li> </ul> <p>The plan for the upcoming snapshots currently includes:</p> <ul> <li>TeXLive 2021</li> <li>Move openmpi default from openmpi2 to openmpi4</li> <li>GNOME 40.1</li> <li>icu 69.1: for the ring packages, nodejs15 seems to be the last blocker</li> <li>Switch from go 1.15 to go 1.16: most packages fixed, the last failure in Staging:M is cilium</li> <li>GCC 11 as default compiler: Move from special-purpose Staging:Gcc7 to Staging:O (incl. openQA test coverage). There are a few more build failures to be addressed.</li> <li>UsrMerge: The current state is that we checked in all changes and are planning on actually doing the switch somewhen in the not too far future, likely together with the planned distro-rebuild for GCC 11</li> </ul> /2021/04/30/llvm-kde-gear-gnome-update-in-tw/ openSUSE News LLVM, KDE Gear, GNOME Update in Tumbleweed Fri, 30 Apr 2021 00:00:00 +0000 <p>Six <a href="">openSUSE</a> <a href="">Tumbleweed</a> were released this week.</p> <p>The snapshots delivered updated versions of <a href="">curl</a>, <a href="">KDE Gear</a>, <a href="">LLVM</a>, <a href="">GNOME 40</a>, Mozilla’s <a href="">Firefox</a> and <a href="">Thunderbird</a> and much more.</p> <p>The <a href="">20210428</a> snapshot updated the <a href="">Linux Kernel</a> to version 5.12 and text editor <a href="">vim</a> to version 8.2.2800. The <a href="">virtualbox</a> update to 6.1.20 took care of a hang for guest operating systems under circumstances where <a href="">Hyper-V</a> is used and the VM packaged added support for kernel versions 5.11 and 5.12. Domaine name cacher <a href="">dnsmasq</a> 2.85 added <code class="language-plaintext highlighter-rouge">--dynamic-host</code> options and debugger <a href="">strace </a> 5.12.0 made improvements and implemented an option to display SELinux contexts.</p> <p>Daniel Stenberg detailed the patch release of <a href="">curl 7.76.1</a> in a video on April 14, which made it into snapshot <a href="">20210427</a>. No new features were made with the curl release, but Stenberg acknowledged contributions in the video and highlighted the selection of HTTP/2 over HTTPS. Open-source file pager <a href="">less</a> updated to version 581, which fixed some crashes and added several new options in the release. Utility probing package <a href="">os-prober</a> updated to version 1.78 and firmware package <a href="">shim-leap</a> updated to version 15.4.</p> <p>Snapshot <a href="">20210426</a> updated about 15 packages, which included the 5.11.16 <a href="">Linux Kernel</a> and an updated version of <a href="">java-11-openjdk</a>, which had a very large update and addressed two <a href="">Common Vulnerabilities and Exposures</a>. A fix for container runtime binary labels were made in the update of <a href="">container-selinux</a> 2.160.1. A major version of <a href="">ncompress</a> 5.0 cleaned up some code and fixed the recursive mode. General purpose cryptographic library <a href="">libgcrypt</a> provided some accelerated implementations for <a href="">x86_64</a> in the 1.9.3 update. Other packages to update in the snapshot are <a href="">pipewire</a> 0.3.26, <a href="">rubygem-nokogiri</a> 1.11.3, <a href="">python-pydot</a> 1.4.2 and more.</p> <p><a href="">KDE Gear 21.04.0</a>, which is the new name for KDE apps, arrived in snapshot <a href="">20210425</a>. A new menu option was added in the file archiver <a href="">Ark</a> to show the about dialog for <a href="">kpart</a>. File manager <a href="">Dolphin</a> removed some input methods and fixed the alignment of the location bar during the first startup. KDE’s text editor <a href="">Kate</a> fixed a memory leak and some compiler warnings. Video editor <a href="">Kdenlive</a> fixed a few crashes and the keyframe limit on imports from the clipboard. <a href="">GNOME 40</a> had multiple updates. Translations were made with <a href="">gedit</a> 40.1, Document viewer <a href="">evince</a> 40.1 added three patches to remove more <a href="">SyncTeX</a>, and <a href="">gnome-tweaks</a> 40.0 made a fix bumping up from the beta version, which failed to recognize when GNOME Shell was running in the release candidate version. Both <a href="">gtk3</a> and <a href="">gtk4</a> were updated to 3.24.28 and 4.2.0 respectively. <a href="">GTK4</a> brought some event matching fixes for missed layouts for <a href="">Wayland</a>. Other packages updated in the snapshot were <a href="">NetworkManager</a> 1.30.4, <a href="">glib2</a> 2.68.1, <a href="">pango</a> 1.48.4, <a href="">rsyslog</a> 8.2104.0 and <a href="">wireshark</a> 3.4.5, which fixed the printing of GeoIP information.</p> <p>Snapshot <a href="">20210423</a> updated Mozilla’s <a href="">Firefox</a> to version 88.0 and <a href="">Thunderbird</a> to version 78.10.0. The browser has a new feature with PDF forms now supporting JavaScript embedded in PDF files. The open-source browser also made a change to the microphone and camera prompts reducing the number of times a prompt asks to grant device access on a website. Nine CVEs were fixed with the <a href="">Thunderbird</a> email client; one of which could have executed an arbitrary FTP command on FTP servers using an encoded URL. Regressions were fixed with <a href="">redis</a> 6.2.2 and a <a href="">Xen</a> update restored a change that was silently removed almost two years ago. <a href="">YaST</a> had multiple packages updated and many of those entailed some spec file cleanups.</p> <p>The week’s opening snapshot, <a href="">20210422</a>, gave audio users an update with <a href="">Audacity</a> 3.0.2; the audio software added some new preferences for output and improved diagnostics reporting. The major version of <a href="">llvm12 12.0.0</a> arrived and the compiler brought in a ton of changes. There were changes for architecture targets, the <a href="">WebAssembly</a> target, <a href="">go</a> bindings, C <a href="">Application Programming Interfaces</a> and much more. <a href="">AppStream</a> made some parsing improvements and improved a text wrap for when words could be excessively long. Text shaping package <a href="">harfbuzz</a>, developed by everyone’s favorite font expert <a href="">Behdad Esfahbod</a>, improved some shape joining scripts and provided documentation improvements. Other packages updated in the snapshot were <a href=""> hwinfo</a> 21.73, <a href="">sqlite</a> 3.35.5, <a href="">sudo</a> 1.9.6 and more.</p> /blog/k8s-121 Kubic Project Kubic with Kubernetes 1.21.0 released Wed, 28 Apr 2021 14:50:00 +0000 /blog/2021-04-28-k8s-121/ <h2 id="announcement">Announcement</h2> <p>The Kubic Project is proud to announce that Snapshot 20210426 has been released containing Kubernetes 1.21.0.</p> <p>Release Notes are avaialble <a href="">HERE</a>.</p> <h2 id="upgrade-steps">Upgrade Steps</h2> <p>All newly deployed Kubic clusters will automatically be Kubernetes 1.21.0 from this point.</p> <p>For existing clusters, please follow our new documentation our wiki <a href="">HERE</a></p> <p>Thanks and have a lot of fun!</p> <p><strong>The Kubic Team</strong></p> /blog/k8s-121 Kubic Project Kubic with Kubernetes 1.20.0 released Wed, 28 Apr 2021 14:50:00 +0000 /blog/2021-04-28-k8s-121/ <h2 id="announcement">Announcement</h2> <p>The Kubic Project is proud to announce that Snapshot 20210426 has been released containing Kubernetes 1.21.0.</p> <p>Release Notes are avaialble <a href="">HERE</a>.</p> <h2 id="upgrade-steps">Upgrade Steps</h2> <p>All newly deployed Kubic clusters will automatically be Kubernetes 1.21.0 from this point.</p> <p>For existing clusters, please follow our new documentation our wiki <a href="">HERE</a></p> <p>Thanks and have a lot of fun!</p> <p><strong>The Kubic Team</strong></p> /2021/04/28/opensuse-leap-153-enters-rc-phase/ openSUSE News openSUSE Leap 15.3 Enters Release Candidate Phase Wed, 28 Apr 2021 00:00:00 +0000 <p>The <a href="">openSUSE Project</a> and its community, contributors and release engineers have entered the Release Candidate phase for the upcoming <a href="">openSUSE Leap 15.3</a> version today after a snapshot was released, which transitions the release to a new phase.</p> <p>The RC signals the package freeze for software that will make it into the distribution, which is used on server, workstation, desktop and for virtualization and container use.</p> <p>openSUSE Leap offers a clear advantage for servers by providing at least 18 months of updates for each release. There is a projection as of April 2021 that Leap 15 will extend to Leap 15.5. Leap Major Release (15.x) extends maintenance and support until a successor. At present, a successor has not been declared; Leap 15’s lifecycle fully aligns with <a href="">SUSE Linux Enterprise</a> and uses the source code and Leap is built with the exact same binary packages..</p> <p>Desktop environments for the release include KDE’s Long-Term-Support version of Plasma 5.18, GNOME 3.34 and Xfce 4.16. Packages for artificial Intelligence and Machine Learning are available for data scientists who use the release. A list of some of the packages in openSUSE Leap 15.3 can be found on the <a href="">Wiki</a>.</p> <p>Leap release manager Lubos Kocman recommends Beta and RC testers use the “zypper dup” command in the terminal when upgrading to the General Availability (GA) once it’s released.</p> <p>During the development stage of Leap versions, contributors, packagers and the release team use a rolling development method that are categorized into phases rather than a single milestone release; snapshots are released with minor version software updates once passing automated testing until the final release of the Gold Master (GM). At that point, the GM becomes available to the public (GA expected on June 2) and the distribution shifts from a rolling development method into a supported release where it receives updates until its End of Life (EOL).</p> <p>Kocman listed the following important dates related to the release:</p> <ul> <li>May 14 - Translation deadline</li> <li>May 21 - Gold Master</li> <li>June 2 - Public Availability of the Release (5 to 10 days after GM)</li> <li>June 2 - Start of Release retrospective survey</li> <li>June 16 - Collect feedback from the retrospective</li> </ul> <p>Users upgrading to openSUSE Leap 15.3 need to be aware that upgrading directly from versions before openSUSE Leap 15.2 is not recommended. Due to the upgrade path, it is highly recommended to upgrade to Leap 15.2 before upgrading to Leap 15.3.</p> <p>The community is supportive and engages with people who use older versions of Leap through community channels like the <a href="">mailing lists</a>, <a href="">Matrix</a>, <a href="">Discord</a>, <a href="">Telegram</a>, and <a href="">Facebook</a>.</p>