May 2021 - openSUSE Factory - openSUSE Mailing Lists

Moving from Freenode to Libera.Chat
by Gerald Pfeifer 17 Jun '21

17 Jun '21

Hi everyone, as some of you noticed, lately there've been challenges around Freenode, the IRC network that has been home to a number of openSUSE channels for years. See, for example, https://arstechnica.com/gadgets/2021/05/freenode-irc-has-been-taken-over-by… https://news.itsfoss.com/freenode-controversy/ Approached by several of you we discussed this with those, the board, and the weekly release meeting. There is consensus to move our channels to Libera.Chat ( https://libera.chat ), a new network many other projects are migrating to as well. With help from Antonio and Sasi I already registered the openSUSE project with Libera.Chat (which by itself is not a move yet) and Marcus R. and others are ready to execute the move. The plan of record is to move quickly. If you have any concerns or questions, please advise as soon as possible. Likewise if you support. Thanks, Gerald PS: https://code.opensuse.org/board/tickets/issue/4 publicly tracks this matter on the openSUSE side; feel free to chime in there. -- Dr. Gerald Pfeifer <gp(a)suse.com>, CTO @SUSE + chair @openSUSE

33 105

Heads up: Early Feature request deadline for SLE 15 SP4 / Leap 15.4 is on 26th June 2021
by Lubos Kocman 14 Jun '21

14 Jun '21

Hello openSUSE! I'd like to communicate an early feature deadline for SUSE Linux Enterprise 15 SP4, which is on 26th June 2021. This deadline is for having requests reported in jira.suse.com, not for the actual code submit requests. This is very important to openSUSE Leap 15.4 contributors as 1/3 of Leap 15.4 binaries will be re-used with SUSE Linux Enterprise and therefore submit requests are accepted there. This is important to keep in mind if you plan to update Leap exclusive package which depends on e.g. a library from SUSE Linux Enterprise. This will be the most common type of request according to my current experience from SP3. I was personally a bit surprised to have this deadline so early even prior the OBS setup, as last year had it shortly after the first Alpha. Just to clarify, this deadline is the same for everyone be it a largest partner, community contributor or an employee. openSUSE Leap and Package Hub exclusive packages will have similar deadlines as described in https://en.opensuse.org/openSUSE:Roadmap. We're aiming for the Leap 15.4 GA in early June 2022, therefore deadlines will only slightly vary from the previous release. We already have to feature requests open for 15.4 (usage of appx-utils instead of fb-utils-appx and update of python-pycairo to 1.20). If you're interested and have some open questions, feel free to pop up on Monday's meeting at 3:00 CEST ( https://meet.opensuse.org/FeatureRequests). More details about jira access and meeting at https://en.opensuse.org/Portal:Jump/Policy/CommunitySLEChangeRequests#Weekl… This call is mainly to identify very obvious updates or requests for features that we'd like to have in SLE 15 SP4 and therefore inherited to Leap 15.4. We'll have a harder time to justify requests that cause massive rebuilds, have large impacts, or seem to be risky (package renames etc) later in the development. Here I'd like to clarify that SUSE Linux Enterprise uses a layered structure and in many cases packages have to be updated in the oldest supported code-stream. I recommend checking the true origin of the package (see referenced wiki). Larger or backward incompatible changes to these packages would result in package forks in SP4. Therefore it's not so easy, but the openSUSE release team is here to help you. Requests during later development cycle have a bit more complicated path but there is processes for it as well (https://en.opensuse.org/ECO ). These are just bit more complication to pass and it generally takes longer, so if you want to have less work, please request it early. I'm acting as sort of a partner manager and I'm going to help you with reporting and deduplication on the SUSE side. I'm processing requests together with Neal Gompa and others who join our call on Mondays. Neal and I would like to work on opening the request even further to the community (Most likely by skipping the jira.suse.com from initial report), but I'm bit afraid we won't make it new few weeks. If you're unsure, please reach out to me or Neal over telegram/Email or even irc or simply join the Monday afternoon call. As a side note, SUSE Linux Enterprise 15 SP4 is considered to be the feature release (Tick-tock model). Therefore, we have relatively free hands with requests of updates as soon as they are backed by some reasoning (I need this for x.y.z). Thank you very much for your understanding. Lubos Kocman Release Manager openSUSE Leap

2 4

ZoL 2.0 on Leap 15.1?
by Sebastian M. Ernst 14 Jun '21

14 Jun '21

Hi all, I just noticed that ZFS / ZoL 2.0 has been packaged for Leap 15.1 [1]. Thanks! I am running a few production machines with Leap 15.1 and ZoL 0.8.x and I am considering to update to ZoL 2.0. Has anyone already made any real-world experiences with this update and the new packages on Leap 15.1 (or 15.2 for that matter)? Sebastian 1: http://download.opensuse.org/repositories/filesystems/openSUSE_Leap_15.1/x8…

6 13

NodeJS 10 is EoL on April 30, any plans of moving out of main repo?
by Nicolas FORMICHELLA 08 Jun '21

08 Jun '21

Hello, A user on Reddit pointed me a weird oddities about nodeJS in TW repos (https://old.reddit.com/r/openSUSE/comments/n0d65s/nodejs_missing_versions_i…) Only Node 10 and 15 are on main repo, but one in EoL in 2 days, and the other is not recommended for production use. There should be only 14 (Latest LTS), 15 (latest current version) and 16 (upcoming LTS) in the main repos. Is there a plan to change that? Nicolas

6 11

Python build issues in SLE-12
by John Paul Adrian Glaubitz 06 Jun '21

06 Jun '21

Hi! I'm currently updating some Python packages in our Public Cloud repositories for SLE-12 and I ran into a repeating issue that I'm not sure what it's causing but I assume it's an issue with RPM macros: [ 70s] error: Too many levels of recursion in macro expansion. It is likely caused by recursive macro declaration. [ 70s] error: Too many levels of recursion in macro expansion. It is likely caused by recursive macro declaration. [ 70s] error: Too many levels of recursion in macro expansion. It is likely caused by recursive macro declaration. [ 70s] error: Too many levels of recursion in macro expansion. It is likely caused by recursive macro declaration. [ 70s] error: lua script failed: [string "<lua>"]:45: bad argument #2 to 'format' (string expected, got nil) [ 70s] error: line 38: Provides: python2-cffi = 1.14.5-2.1 [ 70s] %package -n python36-cffi Thanks, Adrian

3 3

15.2 to 15.3 dup, endless nokey additional rpm info, keys missing? 39517xxxxxx and 65176565xxxx
by cagsm 05 Jun '21

05 Jun '21

hi list, 15.2 to 15.3 dup, endless nokey additional rpm info, keys missing? 39517xxxxxx and 65176565xxxx something like that. is this the way dup goes? did dup according to upgrade instructions on wiki ty

10 25

BEWARE: OBS may allow source change after review
by Ludwig Nussel 02 Jun '21

02 Jun '21

Hi, tl;dr if you rely on package reviews for your development process in OBS make sure requests have a revision. Only osc shows the information you are looking for. Turns out submit request in OBS do not necessarily refer to a specific revision in the originating package. Means the sources can change after a review passed. Unfortunately changing the sources does not reset reviews and reviews do not record the revision they were done for. That obviously defeats the purpose of source reviews. Accepting a request without revision may therefore lead to accepting something different from what was reviewed (resp staged). AFAIK this feature has been in OBS since the very beginning, it's just well hidden as the official interfaces osc and the webui do add a revision when creating requests. There is no way to turn that off either. Also tools such as bots that use osc as python module automatically generate submit request with revision. This is not because the server enforces it but because the client code does it. So anyone who wants to fool reviewers just has to use a custom client. According to the OBS team this hidden behavior is actually considered a feature. The security team doesn't treat it as security issue as it's kind of documented¹, even though osc doesn't behave in the documented way. There are plans to add a special attribute to disallow unversioned requests per project². IMHO a global setting to require revisions by default with the option for exceptions would have been more sensible. Anyway, apparently the fix needs some time to ripe still. Meanwhile the factory-auto bot was enhanced to decline unversioned requests to Factory (thanks Fabian). If you are using reviews in eg your devel project or run your own OBS you need to create your own bot or watch out manually. The webui does not seem to display any revision at all, so not helpful. In osc it looks like this: Request: #12345 submit: foo:bar/baz@42 -> blah Absence of the @number means no revision. cu Ludwig [1] https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.request_an… [2] https://github.com/openSUSE/open-build-service/pull/10992 -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg)

6 6

openSUSE Leap 15.3 GM has not arrived in the repo yet
by dieter 02 Jun '21

02 Jun '21

Hi, openSUSE Leap 15.3 Build 160.3 seems not to be available in the online repo yet: https://download.opensuse.org/distribution/leap/15.3/repo/oss/ Regards, Dieter

5 6

I want to know a few things about the factory
by Norbert Cserpnyák 31 May '21

31 May '21

Hi! My name Empire. I would like to know how the Factory works. How to install Tumbleweed latest package? I heard he was being tested before he got into Tumbleweed. I am obsessed with constant freshness. Look forward to their response! Best regards Empire201

2 1

openSUSE Leap 15.3 is Gold!
by Lubos Kocman 31 May '21

31 May '21

Hello openSUSE! I would like to share some great news with you on behalf of the openSUSE Release team. openSUSE Leap 15.3 Build 160.3 was accepted as the Gold Master. So we're on time for the planned Global Availability next week on the 2nd of June. Submissions that didn't make it will have be released as maintenance updates. The entire openSUSE release team would like to give a big thanks to all of you who participated in the release. You all made Leap 15.3 happen! Talking about dates, I'd like to correct my previous statement about SUSE Linux Enterprise 15 SP3 GM date as it happened last Thursday, therefore according to the schedule. There seem to have been some miscommunication on both sides. Some changes to the release process that you will most likely notice. We did adapt the release process to pre-agreed changes from openSUSE Leap 15.2 retrospective and will no longer explicitly hide images. We expect to eliminate any issues on the mirror side. We've had a discussion about this on last year's retrospective review. The outcome can be found in https://en.opensuse.org/Portal:15.2/Retrospective#.28In-.29Visibility_of_GM… We also improved the signing of images as suggested in the retrospective. This will hopefully show you that we take retrospectives seriously. The official release announcement will be sent on the 2nd of June as planned in our https://en.opensuse.org/openSUSE:Roadmap This date is important not only from a marketing point of view but also for the 0day maintenance part of the release. Some updates that we'd like to have available with the GA are aiming at that date. Same as last year, the Release retrospective survey will be open on GA day. We'd like to kindly you about what went well and what didn't go too well in this release. We will then review it together on my Workshop on the upcoming *oSVC2021. [0] https://events.opensuse.org/conferences/oSVC21/ Thank you very much for all the hard work! openSUSE Release team

4 5