From vmoutoussamy at suse.com Wed Mar 2 14:10:31 2022 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Wed, 2 Mar 2022 14:10:31 +0000 Subject: openSUSE 15.4 and SLE 15 SP4 developed together Message-ID: Hi beta testers! For your information openSUSE 15.4 also entered beta phase, please check out the following links for more information: * https://news.opensuse.org/2022/03/02/leap-reaches-beta-build-phase/ * https://news.opensuse.org/2022/03/01/test-leap-beta/ * openSUSE & SLE ? Developed together: https://www.suse.com/c/how-suse-builds-its-enterprise-linux-distribution-part-5/ Of course, if you have any questions regarding openSUSE or SLE, please feel free to ask here. Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program Manager JeOS Technical Project Manager SLE Container Module Project Manager Paris, France -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at suse.com Wed Mar 9 17:37:15 2022 From: beta-programs at suse.com (SUSE Beta Program) Date: Wed, 09 Mar 2022 18:37:15 +0100 Subject: [ANNOUNCE] SUSE Linux Enterprise 15 SP4 Online Updates (Snapshot-202203-1)! Message-ID: <6228e5cbe07a6_e00e2bc-28b@MacBouille-3.local.mail> We are happy to announce the first online updates for SUSE Linux Enterprise 15 Service Pack 4 labeled Snapshot-202203-1. Important notice SLE 15 SP4 Beta Registration Codes Please contact us at beta-programs at suse.com to request your Beta Registration Codes, in case you want to benefit from our Online Updates on your installed system or for testing online migration from SLE 15 SP3! Upgrading a PublicBeta-202202 installation to the latest Snapshot During the development of SLE 15 SP4 all packages are delivered via the Pool channel. These channels are updated with every new Release Milestone. To not override an existing installation, the Pool channel repositories on a Beta installation are set to not auto-refresh when zypper is called. If a beta tester wants to do an unsupported upgrade to a newer Release Milestone release, they either need to enable the auto-refresh of all Pool channels via sudo zypper -r repo-ID or call sudo zypper ref --force before every update. The repo-ID can be looked up via zypper lr. Just like with Tumbleweed the usage of sudo zypper dup is the recommended way of updating the system afterwards. Selection of package changes Added - clingo 5.5.0-150400.2.1 - containerized-data-importer-manifests 1.43.0-150400.1.13 - mpich-ofi 3.4.2-150400.1.6 - mpich-ofi-devel 3.4.2-150400.1.6 - nvme-stas 1.0~rc2-150400.1.1 - perl-Cairo-GObject 1.005-150400.1.1 - perl-Glib-Object-Introspection 0.049-150400.1.1 - perl-Gtk3 0.038-150400.1.1 - update-test-trivial 5.1-33.2 - gdm-schema 41.3-150400.1.1 Updated Kernel - kernel-source: 5.14.21-150400.9.1 => 5.14.21-150400.11.1 Updated - 389-ds: 2.0.11~git13.e14935725-150400.1.4 => 2.0.13~git1.72eb93ac9-150400.1.1 - apache2-mod_php7: 7.4.25-150400.1.4 => 7.4.25-150400.2.1 - apache2-mod_php8: 8.0.10-150400.1.6 => 8.0.10-150400.2.1 - apache2: 2.4.51-150400.2.1 => 2.4.51-150400.3.1 - autoyast2: 4.4.30-150400.1.1 => 4.4.32-150400.1.1 - avahi: 0.8-150400.4.4 => 0.8-150400.5.9 - blog: 2.20-2.1 => 2.26-150300.4.3.1 - bmake: 20181221-5.3.1 => 20200606-150400.1.1 - clamav: 0.103.4-3.32.1 => 0.103.5-3.35.1 - cloud-regionsrv-client: 9.3.1-6.57.1 => 10.0.0-6.62.1 - coccinelle: 1.0.8-1.37 => 1.1.0-150400.1.1 - containerd: 1.4.12-60.1 => 1.4.12-63.1 - cosign: 1.5.0-150400.1.2 => 1.5.2-150400.1.2 - cyrus-sasl: 2.1.27-2.2 => 2.1.27-150300.4.3.1 - duperemove: 0.11.beta4-1.26 => 0.11.3-3.3.1 - elfutils-debuginfod: 0.185-150400.2.69 => 0.185-150400.3.1 - elfutils: 0.185-150400.2.69 => 0.185-150400.3.1 - fetchmail: 6.4.22-20.23.1 => 6.4.22-20.26.1 - fontconfig: 2.12.6-4.3.1 => 2.13.1-150400.1.1 - gdm: 41.0-150400.1.6 => 41.3-150400.1.1 - gnome-documents: 3.34.0+26-150400.2.1 => 3.34.0+37-150400.1.1 - go1: 1.16.13-1.40.1 => 1.16.14-1.43.1 - grub2: 2.06-150400.5.10 => 2.06-150400.6.1 - ImageMagick: 7.1.0.9-150400.2.2 => 7.1.0.9-150400.3.1 - jython: 2.2.1-11.65 => 2.2.1-150400.18.2 - kbd: 2.4.0-150400.2.1 => 2.4.0-150400.3.1 - libqt5-qtwayland: 5.15.2+kde44-150400.2.1 => 5.15.2+kde54-150400.1.1 - libreoffice: 7.1.4.2-14.22.10.1 => 7.2.3.2-150300.14.22.15.3 - libzypp: 17.29.4-150400.1.2 => 17.29.5-150400.1.1 - MozillaFirefox: 91.5.0-152.12.1 => 91.6.0-152.15.1 - MozillaThunderbird: 91.5.0-8.51.1 => 91.6.1-8.54.1 - nvme-cli: 2.0~0-150400.2.1 => 2.0~5-150400.1.1 - ocaml-rpm-macros: 20200514-1.5 => 20211027-150400.1.1 - opae: 1.3.2-1.65 => 1.3.2-150400.8.1 - papi_6_0_0_1-hpc: 6.0.0.1-1.5 => 6.0.0.1-150400.6.1 - papi: 6.0.0.1-1.5 => 6.0.0.1-150400.6.1 - perl-Gtk2: 1.24993-150400.1.3 => 1.24993-150400.2.1 - php7-{fastcgi,fpm}: 7.4.25-150400.1.4 => 7.4.25-150400.2.1 - php7: 7.4.25-150400.1.7 => 7.4.25-150400.2.1 - php8-{embed,fastcgi,fpm,test}: 8.0.10-150400.1.4 => 8.0.10-150400.2.1 - php8: 8.0.10-150400.1.9 => 8.0.10-150400.2.1 - polkit: 0.116-3.6.1 => 0.116-3.9.1 - powerpc-utils: 1.3.9-150400.16.1 => 1.3.9-150400.17.1 - psmisc: 23.0-6.16.1 => 23.0-6.19.1 - raspberrypi-eeprom: 0.0~2020.09.03.75~g3129546-1.2 => 2021.04.29-150300.3.3.1 - rekor: 0.4.0-150400.1.12 => 0.4.0-150400.2.2 - rpm-config-SUSE: 1-150400.11.45 => 1-150400.12.3 - rpmlint: 1.10-7.35.1 => 1.10-7.38.1 - s390-tools: 2.19.0-150400.1.13 => 2.19.0-150400.2.4 - salt: 3004-150400.2.4 => 3004-150400.3.3 - sapwmp: 0.1+git.1635770861.0992962-150400.1.4 => 0.1+git.1645197740.6b06c5c-150400.1.1 - sg3_utils: 1.47+3.adb7276-150400.1.4 => 1.47+4.82fb156-150400.1.1 - spack: 0.16.1-5.3.1 => 0.17.1-150400.9.1 - strongswan: 5.8.2-11.21.1 => 5.8.2-11.24.1 - supportutils-plugin-suse-public-cloud: 1.0.5-3.6.1 => 1.0.6-3.9.1 - suseconnect-ng: 0.0.6~git0.77933db-150400.1.2 => 0.0.6~git9.33e5847-150400.1.2 - sysstat: 12.0.2-3.30.1 => 12.0.2-3.33.1 - systemd: 249.9-150400.1.5 => 249.10-150400.1.3 - tigervnc: 1.10.1-150400.3.1 => 1.10.1-150400.4.1 - tomcat: 9.0.36-13.1 => 9.0.36-16.1 - transactional-update: 3.2.2-1.1 => 3.6.2-150300.3.3.1 - ucode-intel: 20210525-7.1 => 20220207-10.1 - usbguard: 1.0.0-150400.1.7 => 1.1.0-150400.1.1 - vim: 8.0.1568-5.14.1 => 8.0.1568-5.17.1 - wireshark: 3.4.10-3.62.1 => 3.6.2-3.71.1 - wpa_supplicant: 2.9-4.29.1 => 2.9-4.33.1 - xerces-j2: 2.12.0-1.64 => 2.12.0-3.3.1 - yast2-firstboot: 4.4.7-150400.1.1 => 4.4.8-150400.1.1 - yast2-installation: 4.4.41-150400.1.1 => 4.4.45-150400.1.1 - yast2-network: 4.4.39-150400.1.1 => 4.4.42-150400.1.1 - yast2-nis-server: 4.4.1-150400.1.2 => 4.4.2-150400.1.1 - yast2-registration: 4.4.15-150400.1.1 => 4.4.17-150400.1.1 - yast2-s390: 4.4.4-150400.1.1 => 4.4.5-150400.1.1 - yast2-security: 4.4.11-150400.1.1 => 4.4.12-150400.1.1 - yast2-theme: 4.4.4-150400.1.3 => 4.4.6-150400.1.1 - zramcfg: 0.2-1.26 => 0.2-150400.12.1 - zsh: 5.6-5.17 => 5.6-7.5.1 - zypper: 1.14.51-150400.1.2 => 1.14.52-150400.1.1 Removed - fontconfig-32bit - libboost_mpi1_66_0 - libboost_mpi1_66_0-devel - libboost_python-py2_7-1_66_0 - libboost_python-py2_7-1_66_0-devel - libwireshark14 - libwiretap11 - libwsutil12 - nss_ldap-265 - nss_ldap-32bit-265 - pam_ldap-186 - pam_ldap-32bit-186 - python-dmidecode Downgraded - None Architecture changes - None One more thing We wish you an happy hacking and happy testing time and we wanted to share a bit of fun with you: new SUSE Music Parody: Personal Linux[1] More information Schedule[2] Changelog[3] Known issues[4] Questions? If you have any questions, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[5] [1]:https://youtu.be/WoGywmAaa50 [2]:https://suse.com/betaprogram/sle-beta/#releases [3]:https://suse.com/betaprogram/sle-beta/#changelogs [4]:https://suse.com/betaprogram/sle-beta/#knownissues [5]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from% 20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SLE %20Public%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: From suse at shedit.eu Fri Mar 11 09:40:24 2022 From: suse at shedit.eu (Syds Bearda) Date: Fri, 11 Mar 2022 10:40:24 +0100 Subject: Migration leap 15.4 beta to SLED 15 Sp4 beta registration error Message-ID: Hi, I installed openSUSE 15.4 beta with the plan to migrate to SLED 15 SP 4 beta and got a registration code for it. However registering doesn?t work for me. First of all SUSEConnect and yast2-registration can?t be installed together. yast2-registration install libsuseconnect instead. Second doing a migration with first registration gives the following error: ----- Registration failed. Connection to registration server failed. Details: HTTP error code: 422 The subscription with the provided Registration Code does not include the requested product 'openSUSE Leap 15.4 x86_64' ---- What can I do to fix this? Thanks, Syds From lubos.kocman at suse.com Fri Mar 11 10:10:27 2022 From: lubos.kocman at suse.com (Lubos Kocman) Date: Fri, 11 Mar 2022 10:10:27 +0000 Subject: Migration leap 15.4 beta to SLED 15 Sp4 beta registration error In-Reply-To: References: Message-ID: <8f7b5b116e64d050be499ecc4838179337618636.camel@suse.com> Hello Syds, I did validate the conflict and reported this bug https://bugzilla.opensuse.org/show_bug.cgi?id=1197006 I did already notify Yast2 team about this issue. **Regarding SLED being the migration target** SLED migration path is currently unsupported as we did not enable such migration path in SCC. So I think that yast2 migration would simply not work for you as it would not find matching migration target and would end up with registration error (unless you have also access to SLES subscription). **Could the migraton from SLES to SLED be supported in the future?** Tasks for me and Vincent would then be to return back to SUSE Product Management, that there seem to be an interest in this scenario, but we'd need more inforomation about your usecase. That doesn't mean that you can't migrate it manually (if you really want to). However, SUSE would not be able to provide support for the transition. Bugs in toolchain? could still be reported though.? Most of openSUSE side documentation is living here https://en.opensuse.org/SDB:System_upgrade everyone is welcome to extend it with some new findings. Hope it helps Thank you very much Lubos Kocman Syds Bearda p??e v P? 11. 03. 2022 v 10:40 +0100: > Hi, > > I installed openSUSE 15.4 beta with the plan to migrate to SLED 15 SP > 4 beta and got a registration code for it. > > However registering doesn?t work for me. > > First of all SUSEConnect and yast2-registration can?t be installed > together. yast2-registration install libsuseconnect instead. > > Second doing a migration with first registration gives the following > error: > > ----- > Registration failed. > > > > Connection to registration server failed. > > > > Details: HTTP error code: 422 > > The subscription with the provided Registration Code does not include > the requested product 'openSUSE Leap 15.4 x86_64' > > ---- > > What can I do to fix this? > > Thanks, > Syds > -- Best regards Lubos Kocman openSUSE Leap Release Manager From suse at shedit.eu Fri Mar 11 10:17:09 2022 From: suse at shedit.eu (Syds Bearda) Date: Fri, 11 Mar 2022 11:17:09 +0100 Subject: Migration leap 15.4 beta to SLED 15 Sp4 beta registration error In-Reply-To: <8f7b5b116e64d050be499ecc4838179337618636.camel@suse.com> References: <8f7b5b116e64d050be499ecc4838179337618636.camel@suse.com> Message-ID: <0eb86a0d-ac3c-428e-810d-2642999fda77@www.fastmail.com> On Fri, 11 Mar 2022, at 11:10, Lubos Kocman wrote: > Hello Syds, > > I did validate the conflict and reported this bug > https://bugzilla.opensuse.org/show_bug.cgi?id=1197006 > I did already notify Yast2 team about this issue. > > > **Regarding SLED being the migration target** > > SLED migration path is currently unsupported as we did not enable such > migration path in SCC. So I think that yast2 migration would simply not > work for you as it would not find matching migration target and would > end up with registration error (unless you have also access to SLES > subscription). > Hi Lubos, Thanks for your quick answer. I was trying it as it was mentioned in the sle-beta site [1] [1] https://www.suse.com/betaprogram/sle-beta/#faq-update5 > **Could the migraton from SLES to SLED be supported in the future?** > Tasks for me and Vincent would then be to return back to SUSE Product > Management, that there seem to be an interest in this scenario, but > we'd need more inforomation about your usecase. > > That doesn't mean that you can't migrate it manually (if you really > want to). However, SUSE would not be able to provide support for the > transition. Bugs in toolchain? > could still be reported though.? How does it work manually? With SLED DVD and do upgrade? > > Most of openSUSE side documentation is living here > https://en.opensuse.org/SDB:System_upgrade everyone is welcome to > extend it with some new findings. > > > Hope it helps > > Thank you very much > > Lubos Kocman > > > > Syds Bearda p??e v P? 11. 03. 2022 v 10:40 +0100: >> Hi, >> >> I installed openSUSE 15.4 beta with the plan to migrate to SLED 15 SP >> 4 beta and got a registration code for it. >> >> However registering doesn?t work for me. >> >> First of all SUSEConnect and yast2-registration can?t be installed >> together. yast2-registration install libsuseconnect instead. >> >> Second doing a migration with first registration gives the following >> error: >> >> ----- >> Registration failed. >> >> >> >> Connection to registration server failed. >> >> >> >> Details: HTTP error code: 422 >> >> The subscription with the provided Registration Code does not include >> the requested product 'openSUSE Leap 15.4 x86_64' >> >> ---- >> >> What can I do to fix this? >> >> Thanks, >> Syds >> > > -- > Best regards > > Lubos Kocman > openSUSE Leap Release Manager From lubos.kocman at suse.com Fri Mar 11 10:42:40 2022 From: lubos.kocman at suse.com (Lubos Kocman) Date: Fri, 11 Mar 2022 10:42:40 +0000 Subject: Migration leap 15.4 beta to SLED 15 Sp4 beta registration error In-Reply-To: <0eb86a0d-ac3c-428e-810d-2642999fda77@www.fastmail.com> References: <8f7b5b116e64d050be499ecc4838179337618636.camel@suse.com> <0eb86a0d-ac3c-428e-810d-2642999fda77@www.fastmail.com> Message-ID: <6435a25cb5b824bd2e68bb0885362c0ce8829094.camel@suse.com> Syds Bearda p??e v P? 11. 03. 2022 v 11:17 +0100: > > > On Fri, 11 Mar 2022, at 11:10, Lubos Kocman wrote: > > Hello Syds, > > > > I did validate the conflict and reported this bug > > https://bugzilla.opensuse.org/show_bug.cgi?id=1197006 > > I did already notify Yast2 team about this issue. > > Seems that I was wrong suseconnect-ng simply nowadays provides SUSEConnect command, here's a request to make it more explicit in our documentation https://bugzilla.suse.com/show_bug.cgi?id=1197009 > > > > **Regarding SLED being the migration target** > > > > SLED migration path is currently unsupported as we did not enable > > such > > migration path in SCC. So I think that yast2 migration would simply > > not > > work for you as it would not find matching migration target and > > would > > end up with registration error (unless you have also access to SLES > > subscription). > > > > Hi Lubos, > > Thanks for your quick answer. I was trying it as it was mentioned in > the sle-beta site [1] > > [1] https://www.suse.com/betaprogram/sle-beta/#faq-update5 > > > > **Could the migraton from SLES to SLED be supported in the > > future?** > > Tasks for me and Vincent would then be to return back to SUSE > > Product > > Management, that there seem to be an interest in this scenario, but > > we'd need more inforomation about your usecase. > > > > That doesn't mean that you can't migrate it manually (if you really > > want to). However, SUSE would not be able to provide support for > > the > > transition. Bugs in toolchain? > > could still be reported though.? > > How does it work manually? With SLED DVD and do upgrade? Again if you don't have a good reason for this, I'd not recommend to make it part of your workflow and simply ask SUSE to support the scenario. Otherwise, You'd have to skip yast2 migration or zypper migrate and SUSEConnect and zypper dup instead. Idea is the same, register system, enable repos, exchange openSUSE- release package for SLED release package, run upgrade (dup) and perhaps allow vendor change (nowadays SUSE and openSUSE keys should be already whitelisted by zypper). > > > > Most of openSUSE side documentation is living here > > https://en.opensuse.org/SDB:System_upgrade? everyone is welcome to > > extend it with some new findings. > > > > > > Hope it helps > > > > Thank you very much > > > > Lubos Kocman > > > > > > > > Syds Bearda p??e v P? 11. 03. 2022 v 10:40 +0100: > > > Hi, > > > > > > I installed openSUSE 15.4 beta with the plan to migrate to SLED > > > 15 SP > > > 4 beta and got a registration code for it. > > > > > > However registering doesn?t work for me. > > > > > > First of all SUSEConnect and yast2-registration can?t be > > > installed > > > together. yast2-registration install libsuseconnect instead. > > > > > > Second doing a migration with first registration gives the > > > following > > > error: > > > > > > ----- > > > Registration failed. > > > > > > > > > > > > Connection to registration server failed. > > > > > > > > > > > > Details: HTTP error code: 422 > > > > > > The subscription with the provided Registration Code does not > > > include > > > the requested product 'openSUSE Leap 15.4 x86_64' > > > > > > ---- > > > > > > What can I do to fix this? > > > > > > Thanks, > > > Syds > > > > > > > -- > > Best regards > > > > Lubos Kocman > > openSUSE Leap Release Manager > -- Best regards Lubos Kocman openSUSE Leap Release Manager From beta-programs at suse.com Wed Mar 16 15:01:42 2022 From: beta-programs at suse.com (SUSE Beta Program) Date: Wed, 16 Mar 2022 16:01:42 +0100 Subject: [ANNOUNCE] Userspace Live Patching Technology Preview! Message-ID: <6231fbd655d5e_110342bc-2d8@MacBouille-3.local.mail> As of now our SUSE Linux Enterprise Live Patching[1] allows you to apply patches to your Linux kernel without rebooting the system, but we are excited to announce that we are working on extending the coverage to Userspace packages as well! First and foremost, we are still in the development phase, so testing this new technology will not be for everyone, but it is very important for us that we develop in the open and that we allow our users and community to test early in the process! There is only 2 important pages that you should know about: - https://build.opensuse.org/package/show/home:ULP/ulp-demo This is where you can find everything you need to test ULP on your system. Please refer to the demo instructions[2] for more information. - https://github.com/SUSE/libpulp/ We are hosting Libpulp, the framework that enables Userspace Live Patching on github. This is where you can look under the hood if you are interested in further study of ULP. Note that there is a developer mailing list at ulp-devel at lists.opensuse.org if you want to contribute to ULP, but if you have any question, you can respond to this email. Finally, we are planning for having ULP to be officially released post-SLE 15 SP4! Please stay in touch. We wish you all a nice day, Questions? If you have any questions, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[3] [1]:https://www.suse.com/products/live-patching/ [2]:https://build.opensuse.org/package/view_file/home:ULP/ulp -demo/README.demo?expand=1 [3]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from% 20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SLE %20Public%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at suse.com Mon Mar 21 08:38:32 2022 From: beta-programs at suse.com (SUSE Beta Program) Date: Mon, 21 Mar 2022 09:38:32 +0100 Subject: [ANNOUNCE] SUSE Linux Enterprise 15 SP4 Online Updates (Snapshot-202203-2)! Message-ID: <62383988470b4_7d842bc-299@MacBouille-3.local.mail> We are happy to announce another online updates for SUSE Linux Enterprise 15 Service Pack 4 labeled Snapshot-202203-2. Important notice SLE 15 SP4 Beta Registration Codes Please contact us at beta-programs at suse.com to request your Beta Registration Codes, in case you want to benefit from our Online Updates on your installed system or for testing online migration from SLE 15 SP3! Upgrading a PublicBeta-202202 installation to the latest Snapshot During the development of SLE 15 SP4 all packages are delivered via the Pool channel. These channels are updated with every new Release Milestone. To not override an existing installation, the Pool channel repositories on a Beta installation are set to not auto-refresh when zypper is called. If a beta tester wants to do an unsupported upgrade to a newer Release Milestone release, they either need to enable the auto-refresh of all Pool channels via sudo zypper -r repo-ID or call sudo zypper ref --force before every update. The repo-ID can be looked up via zypper lr. Just like with Tumbleweed the usage of sudo zypper dup is the recommended way of updating the system afterwards. Selection of package changes Added - go1.17 1.17.7-1.20.1 - go1.17-doc 1.17.7-1.20.1 - go1.17-race 1.17.7-1.20.1 - go1.18 1.18beta2-1.3.1 - go1.18-doc 1.18beta2-1.3.1 - go1.18-race 1.18beta2-1.3.1 Updated Kernel - kernel-source: 5.14.21-150400.11.1 => 5.14.21-150400.12.2 Updated - 389-ds: 2.0.13~git1.72eb93ac9-150400.1.1 => 2.0.14~git12.d04ffd4b6-150400.1.1 - autoyast2: 4.4.32-150400.1.1 => 4.4.35-150400.1.1 - barrel: 0.1.0-150400.1.2 => 0.1.0-150400.2.1 - bluez: 5.62-150400.1.6 => 5.62-150400.2.1 - cryptsetup: 2.4.1-150400.1.165 => 2.4.3-150400.1.13 - cyrus-sasl-bdb: 2.1.27-150300.4.3.1 => 2.1.27-150300.4.6.1 - cyrus-sasl-saslauthd-bdb: 2.1.27-150300.4.3.1 => 2.1.27-150300.4.6.1 - cyrus-sasl-saslauthd: 2.1.27-150300.4.3.1 => 2.1.27-150300.4.6.1 - cyrus-sasl: 2.1.27-150300.4.3.1 => 2.1.27-150300.4.6.1 - dracut: 055+suse.238.gacab0df5-150400.1.5 => 055+suse.244.g2f624182-150400.1.1 - firewalld: 0.9.3-1.1 => 0.9.3-150400.6.1 - google-guest-configs: 20211116.00-1.16.1 => 20211116.00-150400.11.1 - grub2: 2.06-150400.6.1 => 2.06-150400.7.1 - icewm-theme-branding: 1.2.5-3.24 => 1.2.5-150300.5.3.1 - libzypp: 17.29.5-150400.1.1 => 17.29.6-150400.1.1 - lvm2: 2.03.05-150400.14.1 => 2.03.05-150400.15.1 - mdadm: 4.1-24.6.1 => 4.1-150300.24.9.1 - MozillaFirefox: 91.6.0-152.15.1 => 91.6.1-152.19.1 - MozillaThunderbird: 91.6.1-8.54.1 => 91.6.2-8.59.1 - ndctl: 71.1-3.3.1 => 71.1-150400.8.1 - nvme-cli: 2.0~5-150400.1.1 => 2.0~6-150400.1.1 - open-iscsi: 2.1.5-32.12.1 => 2.1.6-150400.36.1 - openvpn: 2.4.3-5.7.1 => 2.5.5-150400.1.1 - ovmf: 202111-150400.2.2 => 202202-150400.1.1 - pciutils: 3.5.6-11.45 => 3.5.6-150300.13.3.1 - permissions: 20181225-23.12.1 => 20201225-150400.1.1 - procps: 3.3.15-7.19.1 => 3.3.15-7.22.1 - python310-setuptools: 57.4.0-150400.1.4 => 57.4.0-150400.2.1 - raspberrypi-firmware-config: 2021.09.30-150400.1.2 => 2021.09.30-150400.2.1 - raspberrypi-firmware: 2021.09.30-150400.1.2 => 2021.09.30-150400.2.1 - rdma-core: 38.1-150400.2.1 => 38.1-150400.4.1 - rmt-server: 2.7.0-150400.1.3 => 2.7.1-150400.1.1 - s390-tools: 2.19.0-150400.2.4 => 2.19.0-150400.3.8 - scap-security-guide: 0.1.59-1.24.3 => 0.1.60-1.29.1 - suse-build-key: 12.0-8.16.1 => 12.0-8.19.1 - systemd: 249.10-150400.1.3 => 249.10-150400.3.7 - tcmu-runner: 1.5.2-3.3.1 => 1.5.4-150400.1.1 - update-alternatives: 1.19.0.4-2.48 => 1.19.0.4-4.3.1 - util-linux: 2.37.2-150400.4.19 => 2.37.2-150400.5.3 - util-linux-systemd: 2.37.2-150400.4.2 => 2.37.2-150400.5.1 - yast2-audit-laf: 4.4.1-150400.1.2 => 4.4.2-150400.1.1 - yast2-country: 4.4.11-150400.1.1 => 4.4.12-150400.1.1 - yast2-installation: 4.4.45-150400.1.1 => 4.4.48-150400.1.1 - yast2-network: 4.4.42-150400.1.1 => 4.4.45-150400.1.1 - yast2-packager: 4.4.23-150400.1.1 => 4.4.24-150400.1.1 - yast2-security: 4.4.12-150400.1.1 => 4.4.13-150400.1.1 - yast2: 4.4.45-150400.1.1 => 4.4.47-150400.1.1 - yast2-theme: 4.4.6-150400.1.1 => 4.4.7-150400.1.1 Removed - go1.14 - go1.14-doc - go1.16 - go1.16-doc - go1.16-race - python-xml - systemd-bash-completion-234 Downgraded - None Architecture changes - None More information Schedule[1] Changelog[2] Known issues[3] Questions? If you have any questions, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[4] [1]:https://suse.com/betaprogram/sle-beta/#releases [2]:https://suse.com/betaprogram/sle-beta/#changelogs [3]:https://suse.com/betaprogram/sle-beta/#knownissues [4]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from% 20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SLE %20Public%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Lehmann at csiro.au Wed Mar 23 00:05:05 2022 From: Greg.Lehmann at csiro.au (Lehmann, Greg (IM&T, Pullenvale)) Date: Wed, 23 Mar 2022 00:05:05 +0000 Subject: query on whether a kernel patch is backported Message-ID: Hi SuSE, This article references a nice code change that could help our Milan HPC cluster quite a bit, I think. Are there plans to have it included in SLES 15 SP4? https://www.phoronix.com/scan.php?page=article&item=linux-imbalance-epyc&num=1 Cheers, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Thu Mar 24 09:51:20 2022 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 24 Mar 2022 09:51:20 +0000 Subject: query on whether a kernel patch is backported In-Reply-To: References: Message-ID: Hi there, This patch looks too recent to me for being included in 15SP4, but I?m no expert. @Libor Pechacek we need your help, could you please comment? Thanks and have a nice day everyone, Regards, -- Vincent Moutoussamy SUSE Beta Program Manager JeOS Technical Project Manager SLE Container Module Project Manager Paris, France From: sle-beta on behalf of Lehmann, Greg (IM&T, Pullenvale) Date: Wednesday, 23 March 2022 at 01:05 To: sle-beta at lists.suse.com Subject: query on whether a kernel patch is backported Hi SuSE, This article references a nice code change that could help our Milan HPC cluster quite a bit, I think. Are there plans to have it included in SLES 15 SP4? https://www.phoronix.com/scan.php?page=article&item=linux-imbalance-epyc&num=1 Cheers, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Lehmann at csiro.au Thu Mar 24 23:04:04 2022 From: Greg.Lehmann at csiro.au (Lehmann, Greg (IM&T, Pullenvale)) Date: Thu, 24 Mar 2022 23:04:04 +0000 Subject: query on whether a kernel patch is backported In-Reply-To: References: Message-ID: Nice! Is there any chance of it being backported in SLES 15 SP3? Regards, Greg From: Libor Pechacek Sent: Friday, March 25, 2022 12:06 AM To: Vincent Moutoussamy ; Lehmann, Greg (IM&T, Pullenvale) ; sle-beta at lists.suse.com Cc: Michal Svec Subject: Re: query on whether a kernel patch is backported Hi Vincent, you are right that in this phase of the SLE development cycle we are strict about which changes enter the kernel codebase. So, such a patch might have to wait either post-release or for the next service pack. In this particular case, however, the situation is different. The fix was originally developed in SUSE and simultaneously ported to SLE and posted upstream. As a result, SLE 15 SP4 received the change earlier than the mainline kernel and the optimization has been part of the beta releases. Hope that helps. Libor -- Libor Pechacek SUSE Labs Remember to have fun... ________________________________ From: Vincent Moutoussamy > Sent: Thursday, March 24, 2022 10:51 AM To: Lehmann, Greg (IM&T, Pullenvale) >; sle-beta at lists.suse.com >; Libor Pechacek > Cc: Michal Svec > Subject: Re: query on whether a kernel patch is backported Hi there, This patch looks too recent to me for being included in 15SP4, but I'm no expert. @Libor Pechacek we need your help, could you please comment? Thanks and have a nice day everyone, Regards, -- Vincent Moutoussamy SUSE Beta Program Manager JeOS Technical Project Manager SLE Container Module Project Manager Paris, France From: sle-beta > on behalf of Lehmann, Greg (IM&T, Pullenvale) > Date: Wednesday, 23 March 2022 at 01:05 To: sle-beta at lists.suse.com > Subject: query on whether a kernel patch is backported Hi SuSE, This article references a nice code change that could help our Milan HPC cluster quite a bit, I think. Are there plans to have it included in SLES 15 SP4? https://www.phoronix.com/scan.php?page=article&item=linux-imbalance-epyc&num=1 Cheers, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From ddavis at suse.com Fri Mar 25 18:17:08 2022 From: ddavis at suse.com (Darren R. Davis) Date: Fri, 25 Mar 2022 12:17:08 -0600 Subject: query on whether a kernel patch is backported In-Reply-To: References: Message-ID: <5af7e3d2-8e3d-3f30-f751-ddd243c7c45d@suse.com> Hello, As a note, our kernel sources are publicly available, so you can check and see if patches are there or not: https://kernel.suse.com/ Cheers, Darren On 3/24/22 5:04 PM, Lehmann, Greg (IM&T, Pullenvale) wrote: > > Nice! Is there any chance of it being backported in SLES 15 SP3? > > Regards, > > Greg > > ** > > *From:*Libor Pechacek > *Sent:* Friday, March 25, 2022 12:06 AM > *To:* Vincent Moutoussamy ; Lehmann, Greg > (IM&T, Pullenvale) ; sle-beta at lists.suse.com > *Cc:* Michal Svec > *Subject:* Re: query on whether a kernel patch is backported > > Hi Vincent, > > you are right that in this phase of the SLE development cycle we are > strict about which changes enter the kernel codebase. So, such a patch > might have to wait either post-release or for the next service pack. > > In this particular case, however, the situation is different. The fix > was originally developed in SUSE and simultaneously ported to SLE > > and posted upstream. As a result, SLE 15 SP4 received the change > earlier than the mainline kernel and the optimization has been part of > the beta releases. > > Hope that helps. > > Libor > > -- > > Libor Pechacek > > SUSE Labs ? ? ? ? ? ? ? ? ? ?Remember to have fun... > > ------------------------------------------------------------------------ > > *From:*Vincent Moutoussamy > *Sent:* Thursday, March 24, 2022 10:51 AM > *To:* Lehmann, Greg (IM&T, Pullenvale) ; > sle-beta at lists.suse.com ; Libor Pechacek > > *Cc:* Michal Svec > *Subject:* Re: query on whether a kernel patch is backported > > Hi there, > > This patch looks too recent to me for being included in 15SP4, but I?m > no expert. > > @Libor Pechacek we need your help, could > you please comment? > > Thanks and have a nice day everyone, > > Regards, > > -- > Vincent Moutoussamy > SUSE Beta Program Manager > > JeOS Technical Project?Manager > > SLE Container Module Project Manager > Paris, France > > *From: *sle-beta > on behalf of > Lehmann, Greg (IM&T, Pullenvale) > *Date: *Wednesday, 23 March 2022 at 01:05 > *To: *sle-beta at lists.suse.com > *Subject: *query on whether a kernel patch is backported > > Hi SuSE, > > ??????????????? This article references a nice code change that could > help our Milan HPC cluster quite a bit, I think. Are there plans to > have it included in SLES 15 SP4? > > https://www.phoronix.com/scan.php?page=article&item=linux-imbalance-epyc&num=1 > > > Cheers, > > Greg > -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at suse.com Tue Mar 29 14:35:21 2022 From: beta-programs at suse.com (SUSE Beta Program) Date: Tue, 29 Mar 2022 16:35:21 +0200 Subject: PUBLIC Bugzilla products recent changes (openSUSE) Message-ID: <6243192955fb2_69012bc-28a@MacBouille-3.local.mail> In line with the recent openSUSE announcement (Entering Leap Bugs Gains New Clarity[1]), we had to change our Bugzilla products to make them more visible to our openSUSE community: - PUBLIC SUSE Linux Enterprise Server 15 SP4, - PUBLIC SUSE Linux Enterprise Desktop 15 SP4, - PUBLIC SUSE Linux Enterprise High Availability Extension 15 SP4 - and PUBLIC SUSE Linux Enterprise Micro 5.2 Unfortunately this cause two issues for Beta Testers, Customers, Partners and SUSE Colleagues: 1. Who bookmarked or have a saved query in Bugzilla utilising the PUBLIC products AND have classification set to SUSE only, will miss bugs from PUBLIC products in query results. 2. Who want to report bugs explicitly via the PUBLIC products have to report them through classification openSUSE unlike in the past when it was under SLES. So a change in workflow compared to the past. We are sorry for the inconvenience and hope that you can find back the PUBLIC products in bugzilla.suse.com or bugzilla.opensuse.org and adapt the search queries accordingly. Please check https://www.suse.com/betaprogram/public-bugzilla for more information on how to adapt your search queries and how to create bug reports for these products. Questions? If you have any questions, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[2] [1]:https://news.opensuse.org/2022/03/28/entering-leap-bugs-g ains-new-clarity/ [2]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from% 20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SLE %20Public%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at suse.com Thu Mar 31 12:24:50 2022 From: beta-programs at suse.com (SUSE Beta Program) Date: Thu, 31 Mar 2022 14:24:50 +0200 Subject: [ANNOUNCE] SUSE Linux Enterprise 15 SP4 Online Updates (RC1-202203)! Message-ID: <62459d928d9b1_167db2bc-2a7@MacBouille-3.local.mail> We are happy to announce another online updates for SUSE Linux Enterprise 15 Service Pack 4 labeled RC1-202203. Important notice SLE 15 SP4 Beta Registration Codes Please contact us at beta-programs at suse.com to request your Beta Registration Codes, in case you want to benefit from our Online Updates on your installed system or for testing online migration from SLE 15 SP3! Upgrading a PublicBeta-202202 installation to the latest Snapshot During the development of SLE 15 SP4 all packages are delivered via the Pool channel. These channels are updated with every new Release Milestone. To not override an existing installation, the Pool channel repositories on a Beta installation are set to not auto-refresh when zypper is called. If a beta tester wants to do an unsupported upgrade to a newer Release Milestone release, they either need to enable the auto-refresh of all Pool channels via sudo zypper -r repo-ID or call sudo zypper ref --force before every update. The repo-ID can be looked up via zypper lr. Just like with Tumbleweed the usage of sudo zypper dup is the recommended way of updating the system afterwards. Selection of package changes Added - arm-trusted-firmware-{imx8mm,imx8mq,poplar,qemu_sbsa,qemu,qem u_sbsa,rk3328,rk3368,rpi3,rpi4,sun50i_a64,sun50i_h6,tegra186, tegra210,zynqmp} 2.6-150400.4.1 - bijiben 40.1-150400.3.1 - bijiben-lang 40.1-150400.3.1 - driverctl 0.111-150400.1.1 - mpich_4_0_1-gnu-hpc 4.0.1-150400.1.1 - mpich_4_0_1-gnu-hpc-{devel,macros-devel} 4.0.1-150400.1.1 - mpich-ofi_4_0_1-gnu-hpc 4.0.1-150400.1.1 - mpich-ofi_4_0_1-gnu-hpc-devel 4.0.1-150400.1.1 - ongres-stringprep 1.1-150400.1.4 - ongres-stringprep-saslprep 1.1-150400.1.4 - perl-File-Slurper 0.012-150400.1.1 - rust1.58 1.58.0-150300.7.3.1 - rust1.59 1.59.0-150300.7.4.2 - scap-workbench 1.2.1+git20210604.1fc6def-150400.1.1 - system-user-mktex 1.0.0-150400.1.1 - bash-sh 4.4-150400.25.1 - qemu-SLOF 6.2.0-150400.33.4 - rust1.58 1.58.0-150300.7.3.1 - rust1.59 1.59.0-150300.7.4.2 - texlive-* (859 packages) Updated Kernel - kernel-source: 5.14.21-150400.12.2 => 5.14.21-150400.15.2 Updated - arm-trusted-firmware: 2.6-150400.3.1 => 2.6-150400.4.1 - at: 3.2.2-150400.2.3 => 3.2.2-150400.3.1 - bash: 4.4-150400.23.77 => 4.4-150400.25.1 - chrony: 3.2-9.24.2 => 4.1-150300.16.3.1 - crmsh: 4.4.0+20220208.5e6dca1d-150400.1.10 => 4.4.0+20220321.8cf6a9d1-150400.1.2 - cronie: 1.5.7-150400.81.45 => 1.5.7-150400.82.3 - frr: 7.4-2.25 => 7.4-150300.4.3.1 - fwupd-efi: 1.1-150400.2.9 => 1.2-150400.1.3 - fwupd: 1.7.3-150400.1.1 => 1.7.3-150400.2.1 - gdb: 11.1-8.27.1 => 11.1-8.30.1 - gnutls: 3.7.3-150400.1.7 => 3.7.3-150400.2.2 - java-11-openjdk: 11.0.13.0-3.68.1 => 11.0.14.0-3.74.2 - java-1_8_0-openjdk: 1.8.0.312-3.61.3 => 1.8.0.322-3.64.2 - kvm_stat: 5.3.18-17.14 => 5.14.21-150400.22.1 - libvirt: 8.0.0-150400.3.2 => 8.0.0-150400.4.1 - lifecycle-data-sle-module-live-patching: 15-4.66.1 => 15-4.69.1 - linuxrc: 7.0.31.5-150400.1.1 => 7.0.31.6-150400.1.1 - mdevctl: 0.78-1.24 => 1.1.0-150400.1.2 - Mesa: 21.2.4-150400.64.8 => 21.2.4-150400.65.1 - MozillaFirefox: 91.6.1-152.19.1 => 91.7.0-152.22.1 - mozilla-nss: 3.68.2-3.64.2 => 3.68.2-150400.13.2 - mpich-ofi: 3.4.2-150400.1.6 => 4.0.1-150400.1.1 - mpich: 3.4.2-150400.1.6 => 4.0.1-150400.1.1 - nodejs16: 16.13.2-150400.11.10 => 16.14.1-150400.1.8 - nvme-cli: 2.0~6-150400.1.1 => 2.0~7-150400.1.2 - ocfs2-tools: 1.8.7-150400.3.2 => 1.8.7-150400.4.1 - ongres-scram: 1.0.0~beta.2-1.87 => 2.1-150400.6.4 - openssl-1_0_0: 1.0.2p-3.46.2 => 1.0.2p-3.49.1 - openssl-3: 3.0.1-150400.1.1 => 3.0.1-150400.2.1 - perl-Business-ISBN-Data: 20140910.003-1.25 => 20210112.006-150400.1.1 - postgresql13: 13.5-5.22.1 => 13.6-5.25.1 - postgresql-jdbc: 42.2.16-1.88 => 42.2.25-150400.1.4 - qemu: 6.2.0-150400.32.23 => 6.2.0-150400.33.4 - rust: 1.57.0-21.13.1 => 1.59.0-150300.21.20.1 - SAPHanaSR-ScaleOut: 0.180.1-3.19.1 => 0.181.0-30.1 - SAPHanaSR: 0.154.1-4.14.1 => 0.155.0-4.17.1 - sapstartsrv-resource-agents: 0.9.0+git.1619681975.ad20a04-1.9.1 => 0.9.0+git.1645795466.55a8cca-1.12.1 - smartmontools: 7.0-6.1 => 7.2-150300.8.5.1 - strongswan: 5.8.2-11.24.1 => 5.8.2-150400.17.2 - stunnel: 5.57-3.11.1 => 5.62-3.14.1 - suseconnect-ng: 0.0.6~git9.33e5847-150400.1.2 => 0.0.7~git0.3ef988e-150400.1.1 - systemd: 249.10-150400.3.7 => 249.11-150400.1.8 - sysuser-tools: 2.0-4.2.8 => 3.1-150400.1.9 - tcl: 8.6.7-7.6.1 => 8.6.12-150300.14.3.1 - texlive: 2017.20170520-150400.26.17 => 2021.20210325-150400.27.2 - tk: 8.6.7-3.6.3 => 8.6.12-150300.10.3.1 - tomcat: 9.0.36-16.1 => 9.0.36-19.1 - util-linux: 2.37.2-150400.5.3 => 2.37.2-150400.6.3 - util-linux-systemd: 2.37.2-150400.5.1 => 2.37.2-150400.6.1 - virt-manager: 3.2.0-150400.13.1 => 4.0.0-150400.1.1 - xen: 4.16.0_04-150400.2.17 => 4.16.0_06-150400.1.7 Removed - amavisd-new - amavisd-new-docs - bind-chrootenv - libgupnp-1_2-0 - libpython2_7-1_0 - libsynctex1 - libtexlua52-5 - libvirt-daemon-driver-lxc - libvirt-daemon-lxc - libvirt-sandbox-1_0-5 - mpich_3_4_2-gnu-hpc - mpich_3_4_2-gnu-hpc-{devel,macros-devel} - mpich-ofi_3_4_2-gnu-hpc - mpich-ofi_3_4_2-gnu-hpc-devel - python-base - texlive-{aecc,alterqcm,babel-spanglish,bgreek,boxedminipage2e ,boxedminipage2e,ebong,ebong-bin,einfuehrung,einfuehrung2,FAQ -en,genmisc,geometry-de,hyperref-docsrc,ifetex,ifluatex,ifxet ex,knuth,knuthotherfonts,latex-bib2-ex,latex-bib-ex,latex-ref erenz,latex-tabellen,latex-tds,ltxindex,lua2dox,lua2dox-bin,m athalfa,math-e,mbenotes,mychemistry,pdftools,pdftools-bin,pow erdot-FUBerlin,presentations,presentations-en,pstools,pstools -bin,pst-spirograph,pst-vue3d,psu-thesis,ptex-fonts-fonts,rpu tover,spanish-mx,sympytexpackage,tabulars-e,tetex,tetex-bin,t exconfig,texconfig-bin,tkz-kiviat,tkz-linknodes,wasy2-ps,wasy 2-ps-fonts} - typelib-1_0-LibvirtSandbox-1_0 - virt-sandbox - wayland-protocols-devel - zoo Downgraded - go1.18: 1.18beta2-1.3.1 => 1.18-1.8.1 Architecture changes - None More information Schedule[1] Changelog[2] Known issues[3] Questions? If you have any questions, please contact us at beta-programs at suse.com. Your SUSE Linux Enterprise team Click here to unsubscribe[4] [1]:https://suse.com/betaprogram/sle-beta/#releases [2]:https://suse.com/betaprogram/sle-beta/#changelogs [3]:https://suse.com/betaprogram/sle-beta/#knownissues [4]:mailto:beta-programs at suse.com?subject=Unsubscribe%20from% 20SLE%20Public%20Beta%20Program&body=Unsubscribe%20from%20SLE %20Public%20Beta%20Program -------------- next part -------------- An HTML attachment was scrubbed... URL: