June 2022 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] How we will use the GSoC money
by Vincent Untz 18 Jul '24

18 Jul '24

Hi, (let's see how a public discussion about money goes :-)) The Google Summer of Code brings us great students, but also means that the openSUSE project will get $8000 (if I'm not mistaken) at the end of the summer. That's $500 per student. A while ago, I requested comments on my blog about what to do with the money, but didn't get any feedback. So I take this as "do what you feel is best", and this mail is about the plan. As a reminder, the main issue is that we will likely not have the openSUSE Foundation created in time for this. For instance, Google would like us to get some form filled before the end of June; this is not a mandatory timeline, but I think it shows that we won't be ready with the Foundation for that. The current plan is to give that money to another organization we feel close to, and I have two candidates in mind: - the Software Freedom Conservancy (http://sfconservancy.org/) it's a really nice org that provides a home for various cool projects (see http://sfconservancy.org/members/current/) and those projects help make openSUSE a great project. - the Desktop Summit (https://www.desktopsummit.org/) it's one of the biggest event this year, and this would help us have some more visibility (since we'd be sponsors, I guess). I'm sure they would welcome this to secure their budget. Note that an alternative solution would be to leave the money to Google for a future GSoC or similar program, but I feel it's better to use the money where it can make a difference today. Now, it's not too late to change the plan. If you have a better suggestion, please tell us. There's no need to argue forever about it, just explain why you think it's good. Keep in mind that if we cannot receive the money ourselves, this also means that we cannot use it to buy stuff for openSUSE. Pavol and I will take the final decision since we are the GSoC admins for openSUSE. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

22 38

[Notice] - openSUSE Regular Board election 2021
by Ariez Vachha - openSUSE 01 Nov '22

01 Nov '22

Dear openSUSE members, openSUSE Board Election 2021 [1] It's time to elect new Board members to fill empty seats on the openSUSE Board. There are two seats for election in accordance per our normal election cycle. This is a regular election as defined in our Election Rules [2] ## Phase 0 01 November 2021 - Announcement of the Board Election 2021 - Call for Nominations and Applications for Board candidacy - Membership drive 22 November 2020 - Nominations and Applications for Board candidacy close ## Phase 1 22 November 2021 - Announcement of the final list of candidates - Campaign begins - Membership drive continues, opportunity to apply for openSUSE Membership, but members will only be eligible to vote and not run as a candidate ## Phase 2 13 December 2021 - Ballots open: Please cast your vote during this time - Campaign continues 30 December 2021 - Ballots close 31 December 2021 - Announcement of results To stand for a position in the openSUSE Board please send an email to: * project(a)lists.opensuse.org and * election-officials(a)lists.opensuse.org If a member would like to nominate another member, please inform the Election Committee and the officials will contact the nominee to ask whether they would like to run as a Board candidate. Only openSUSE members are eligible to run for openSUSE Board openings in accordance with the Eligibility and Validity section of our Election Rules [2]. The Election Committee [3] are hereby calling for Nominations & Applications for the openSUSE Board. [1] https://en.opensuse.org/openSUSE:Board_election [2] https://en.opensuse.org/openSUSE:Board_election_rules [3] Members: Ish Sookun, Edwin Zakaria and Ariez Vachha. -- Regards, The Election Committee election-officials(a)lists.opensuse.org

3 5

Community Meeting/ALP WG (cancelled this week): Week 26
by ddemaio 27 Jun '22

27 Jun '22

Hi all, The ALP WG is cancelled this week due to hack week. The WG will happen next week (week 27) and we should have a special guest to ask questions to about ALP. The Community Meeting is scheduled for Thursday at 19:00 UTC. Where: https://meet.opensuse.org/meeting You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. v/r Doug

1 0

Leap 15.4 retrospectife feedback is open unitil 7th July was Re: Leap 15.4 retro feedback is due to tomorrow night
by Lubos Kocman 27 Jun '22

27 Jun '22

On Tue, 2022-06-21 at 23:06 +0200, Per Jessen wrote: > Carlos E. R. wrote: > > > I expect devs/release managers to post to users lists if they want > > users feedback, yes :-/ > > Big plus one. > > Hello openSUSE! To start on the constructive note, to be fair with the community I've extended the Leap 15.4 survey for an extra week until 07.07 23:59 https://survey.opensuse.org/ Just for sake of history: We have 335 responses in total as of now. Regarding factory@ and project@ delivery that seems to be my fault as after looking in history, I see an undeliverable email as I did specify factory(a)opensuse.org and project(a)opensuse.org while cc`ing correctly devel(a)suse.de. So for that, I take the blame. See linked *pic, that the skip was not intentional. Factory users that read the release team report could still read it from our meeting minutes (was also shared on factory@, see subject: "openSUSE Release Engineering meeting 15.06.2022"). https://etherpad.opensuse.org/p/ReleaseEngineering-20220615 I do agree that his was not communicated well, due to my fault at correctly addressing recipients. For the future I think best way forward would be to simply make it part of release annoucement and not create a separate annoucement for that. Or even make it part of get-o-o, e.g. in form of popup as we do for fresh GAs, when user visits /testing/. [0] - https://ibb.co/PN7f69H Lubos

1 0

Re: Fwd: opensuse server issues going on now ?
by Luna Jernberg 24 Jun '22

24 Jun '22

Hey! Alright sorry then i know that for the future On Fri, Jun 24, 2022 at 9:55 AM Axel Braun <axel.braun(a)gmx.de> wrote: > Hi Luna, > > Am Freitag, 24. Juni 2022, 07:14:47 CEST schrieb Luna Jernberg: > > ---------- Forwarded message ---------- > > [...] > > Why to project? support@ deals with, hm, issues that require support. It > is > not a *project* related issue > > We have not too many lists - we just need to make proper use of the > existing > ones.... > > Cheers > Axel > > PS: Pls get a proper mail address. Frickin google blocks my @o.o address > > >

2 1

Fwd: opensuse server issues going on now ?
by Luna Jernberg 24 Jun '22

24 Jun '22

---------- Forwarded message ---------- From: Joe Salmeri <jmscdba(a)gmail.com> Date: Thu, 23 Jun 2022 18:23:02 -0000 Subject: opensuse server issues going on now ? To: factory(a)lists.opensuse.org I was attempting to update to the new 20220622 build that was just published. I use tumbleweed-cli to control which build I switch to. In does not show a new build as available until after the build has been copied to a build folder ( example: https://download/opensuse.org/history20220622 ) I switched tumbleweed-cli to build 20220622, here are my repoositories: Repository priorities in effect: (See 'zypper lr -P' for details) 90 (raised priority) : 1 repository 99 (default priority) : 7 repositories # | Alias | Name | Enabled | GPG Check | Refresh | URI --+----------------------------------+--------------------------------------+---------+-----------+---------+------------------------------------------------------------------------------------- 1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) (20220622) | Yes | (r ) Yes | Yes | http://download.opensuse.org/history/20220622/tumbleweed/repo/non-oss/ 2 | download.opensuse.org-oss | Main Repository (DEBUG) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/tumbleweed/repo/oss/ 3 | download.opensuse.org-oss_1 | Main Repository (Sources) | Yes | (r ) Yes | Yes | http://download.opensuse.org/source/tumbleweed/repo/oss/ 4 | download.opensuse.org-oss_2 | Main Repository (OSS) (20220622) | Yes | (r ) Yes | Yes | http://download.opensuse.org/history/20220622/tumbleweed/repo/oss/ 5 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/tumbleweed/ 6 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | https://dl.google.com/linux/chrome/rpm/stable/x86_64 7 | openSUSE-20210215-0 | openSUSE-20210215-0 | No | ---- | ---- | cd:/?devices=/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_10000000000000000001 8 | skype-stable | skype (stable) | Yes | (r ) Yes | Yes | https://repo.skype.com/rpm/stable/ 9 | vlc | VLC | Yes | (r ) Yes | Yes | http://download.videolan.org/pub/vlc/SuSE/Tumbleweed/ zypper dup or zypper refresh fails with: Retrieving repository 'Main Repository (NON-OSS) (20220622)' metadata ...........................................................................................[error] Repository 'Main Repository (NON-OSS) (20220622)' is invalid. [download.opensuse.org-non-oss|http://download.opensuse.org/history/20220622…] Valid metadata not found at specified URL History: - Download (curl) error for 'http://download.opensuse.org/history/20220622/tumbleweed/repo/non-oss/repod…': Error code: Connection failed Error message: Failed to connect to mirrorcache-us.opensuse.org port 80 after 98 ms: Connection refused - Can't provide ./repodata/dc7b3afc60d401de7ee4b3ef2816045a98feb2e30153cffcb43f32300f5dc389-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Main Repository (NON-OSS) (20220622)' because of the above error. Retrieving repository 'Main Repository (DEBUG)' metadata ........................................................................................................[error] Repository 'Main Repository (DEBUG)' is invalid. [download.opensuse.org-oss|http://download.opensuse.org/debug/tumbleweed/rep…] Valid metadata not found at specified URL History: - Download (curl) error for 'http://download.opensuse.org/debug/tumbleweed/repo/oss/repodata/f889c274abb…': Error code: Connection failed Error message: Failed to connect to mirrorcache-us.opensuse.org port 80 after 84 ms: Connection refused - Can't provide ./repodata/f889c274abb0761e4b3869ff0c8bacb1bd2f253449c86e2a193bbdb5fb1a55bb-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Main Repository (DEBUG)' because of the above error. Retrieving repository 'Main Repository (Sources)' metadata ......................................................................................................[error] Repository 'Main Repository (Sources)' is invalid. [download.opensuse.org-oss_1|http://download.opensuse.org/source/tumbleweed/…] Valid metadata not found at specified URL History: - Download (curl) error for 'http://download.opensuse.org/source/tumbleweed/repo/oss/repodata/a743c61b4c…': Error code: Connection failed Error message: Failed to connect to mirrorcache-us.opensuse.org port 80 after 84 ms: Connection refused - Can't provide ./repodata/a743c61b4c1af8cc7cc4c46638a9892e5a46781cf86c2a3b49b09578a4b72337-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Main Repository (Sources)' because of the above error. Retrieving repository 'Main Repository (OSS) (20220622)' metadata ...............................................................................................[error] Repository 'Main Repository (OSS) (20220622)' is invalid. [download.opensuse.org-oss_2|http://download.opensuse.org/history/20220622/t…] Valid metadata not found at specified URL History: - Download (curl) error for 'http://download.opensuse.org/history/20220622/tumbleweed/repo/oss/repodata/…': Error code: Connection failed Error message: Failed to connect to mirrorcache-us.opensuse.org port 80 after 84 ms: Connection refused - Can't provide ./repodata/90d89069e262e73545f7149e8ce79f699ef7f2fe8198b599dfe601fe6836274f-appdata.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Main Repository (OSS) (20220622)' because of the above error. Repository 'Main Update Repository' is up to date. Repository 'google-chrome' is up to date. Repository 'skype (stable)' is up to date. Repository 'VLC' is up to date. Some of the repositories have not been refreshed because of an error. If I go to the one of the 20220622 download locations in Chrome https://download.opensuse.org/history/20220622/tumbleweed/repo/oss/x86_64/ And then try to manually download a single item like: konsole-22.04.2-1.1.x86_64.rpm It returns: This site can’t be reached mirrorcache-us.opensuse.org refused to connect. I have a direct internet connection ( No proxy ) so it appears that there is a problem with the cache servers. Going to an older build like 20220606 which is what I am currently running has the same issues so that eliminates that 20220622 had not finished copying yet. Anybody else seeing this?

2 1

Leap 15.4 retro feedback is due to tomorrow night
by Lubos Kocman 21 Jun '22

21 Jun '22

Hello openSUSE! The Leap 15.4 retrospective survey is still open until 22.06.2022 at 23:59 UTC. You can access the survey at survey.opensuse.org. If you downloaded Leap 15.4, please make sure to give us feedback. It will not take more than 2 minutes as the survey has only two questions. We have not received even half of the responses that we have received for 15.3. The openSUSE release team would highly appreciate any sharing or advertisement. Thank you Lubos

2 1

Community Meeting/ALP WG: Week 25
by ddemaio 21 Jun '22

21 Jun '22

The ALP WG will take place today at 14:30 UTC The Community Meeting is on Thursday at 19:00 UTC. Both meetings will be in https://meet.opensuse.org/meeting You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. v/r Doug

1 0

Board Meeting Minutes 2022-06-20
by Knurpht-openSUSE 20 Jun '22

20 Jun '22

Minutes for the latest public Board Meetings = Board Meeting Monday 20June 2022 13.00 CEST = Present: Attila, Axel, Gerald, Gertjan, Neal (~13:15), Syds (~13.30) Guests: Emily Excused: Maurizio == Follow-up from oSC: "role of the board" == * Role of the board: * wait for oSC videos to be published, with reference to the board session ask broader community to ** think about desired (required) organization elements ** find volunteers for roles within org structure * These are prevailing steps in order to get legal structure running AI Syds: contact Patrick Fitzgerald * Emeritus memberhips: Simon Lees volunteered to propose an update to Election Rules (aka "Constitution") * plus (orthogonal): * https://code.opensuse.org/board/tickets/issue/49 "Make Membership / Election officials aware of all members of the Emeritus Members group." == Housekeeping: Inactive maintainers on OBS == * Several users on OBS have an invalid mailaddress, but still are maintainers of packages * AI: Axel to trigger housekeeping with OBS Team (Adrian? buildservice(a)l.o.o?) -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team

1 0

Minutes of openSUSE Board meeting 2022-04-11
by Neal Gompa 20 Jun '22

20 Jun '22

Sorry that this took a while to push out, it's been a bit hectic... The minutes are also available here: https://en.opensuse.org/Archive:Board_meeting_2022-04-11 = Minutes of openSUSE Board Meeting Minutes 2022-04-11 = Attendees: Axel, Neal, Gerald, Knurpht, Syds, Maurizio, Stefan Behlert, Lubos Kocman, Doug DeMaio Guests: Luna, Emily Excused: Atilla Minutes: Neal == Status on Open Letter == Axel prepared email to send, ran into LibreOffice bug, waiting on a few folks and will send tomorrow. == Adaptive Linux Platform (SLE-next) == Stefan: SUSE wishes to inform openSUSE about the next SUSE Linux Enterprise code stream. It's currently codenamed ALP to indicate significant rethinking of the future of SUSE Linux Enterprise. Notably, the biggest change is the entire codebase will be developed in the open in the Open Build Service. Members will be able to contribute and SUSE engineering will be developing it entirely in the open (modulo embargoed changes and sensitive security things). The goal is to make a true open SUSE Linux Enterprise platform. The plan is to launch the next SLE platform in fall 2023, which is ambitious, but we're hopeful. The change of the architecture leads to a change from products to solutions. The host OS will generally be small, while layered stuff supporting workloads will lifecycle separately. This will allow different aspects of the system to lifecycle accordingly. The development has started already and a working ALP is functional and useful for use and contribution. There will not be an alpha/beta release, and instead it will be continuously developed and maintained in OBS running up to the formal release. The goal is to change everything, it will not be like how things were in the past, and hopefully it will be better than ever before. Lubos: Has started getting feedback about the future of desktop in SLE. Syds: Is it immutable for the host OS? Stefan: It depends on what the customers want to set up, probably. One advantage of what we're doing is that we can start looking at how to support combinations in supported/unsupported content well. Believes in the Linux desktop. :) Is not sure how this affects existing products yet. Most likely the current plan will continue? Lubos: Idea is Leap 15.5 will be be based on SLE 15.5, maybe next Leap will be based on ALP, depending on how things go. Neal: We can reuse the Leap feature process for coordinating ALP development. Lubos: People might be afraid of the new thing, so Leap Micro might be a nice bridge between Leap 15 and ALP. Stefan: Not sure which OBS project it is yet. Maurizio: How is this going to work from a contributor point of view? Stefan: Not sure. Frederic Crozat and Jiří Šrain will know better i think. Neal: Is very excited about this and wants to get more hands-on with it. Gerald: It's very important that we will be able to offer a continuity of experience and not scare off regular users. Lubos: We should track work on providing an upgrade path. Gerald: In many ways, this is an evolution of what we've done in SUSE Linux over the decades. We've always tried to open things up more and making it more participatory. Stefan: There may be a bit of a bump because the x86_64 microarchitecture level is planned to be bumped to x86_64-v3 (6th generation Intel, 1st generation AMD Ryzen). == Latam Event == Two persons from Brasil, joined the Thursday Weekly meeting last week (7th April 2022) and wanted to create an openSUSE event in Latin America Emily: Idea around it is to grow the mindshare and presence of openSUSE beyond Europe. Lubos: Also would be good to grow SUSE mindshare there for usage and employee base. == Freewear == Freewear collects some % of the money for openSUSE things bought for the openSUSE Project, where to put the money? Neal: We could put the money into the fund for supporting contributors to travel for openSUSE? Axel: We could donate to friendly projects (e.g. Fedora, KDE, etc.). Doug: It could also go into funding giveaways for contributor swag. We'll figure out what to do with this at some point, the preference is to donate to projects, but we trust Doug to come up with a good solution. -- Neal Gompa (ID: Pharaoh_Atem)

1 0

Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)
by openSUSE Meeting Reminder 18 Jun '22

18 Jun '22

Hello all, The biweekly board conf call will be held in two days at 13:00 Europe/Berlin time (CET = UTC+1) Meeting will be in the regular Board Meeting Room https://meet.opensuse.org/OSBoard Current Topics: https://code.opensuse.org/board/tickets/issues?status=Open&tags=meeting Board Members: If you cannot participate, please advise by replying to this mail.

1 0

Mirror infrastructure problems?
by Stefan Seyfried 17 Jun '22

17 Jun '22

Hi all, I seem to remember that there have recently been changes to the mirror infrastructure. I'm seeing problems with that, since maybe around one week. It manifests like that: Retrieving package btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64 (1/1192), 420,1 KiB ( 1,2 MiB unpacked) Retrieving: btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm ............................[not found] File './x86_64/btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm ............................[not found] File './x86_64/btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm ............................[not found] File './x86_64/btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: btop-1.2.7+git20220528.c3eb02f-lp154.31.1.x86_64.rpm ............................[done] Retrieving package fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64 (2/1192), 11,9 KiB ( 11,4 KiB unpacked) Retrieving: fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm ....................................[not found] File './x86_64/fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm ....................................[not found] File './x86_64/fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: fusefile-0.1~3_g1bfc0a7-lp154.1.1.x86_64.rpm .........................................[done] Retrieving package ipxe-bootimgs-1.21.1+git20210908.02ec659b-lp154.48.1.noarch (3/1192), 1,9 MiB ( 4,8 MiB unpacked) Retrieving: ipxe-bootimgs-1.21.1+git20210908.02ec659b-lp154.48.1.noarch.rpm .................[not found] File './noarch/ipxe-bootimgs-1.21.1+git20210908.02ec659b-lp154.48.1.noarch.rpm' not found on medium 'http://download.opensuse.org/repositories/home:/seife:/testing/15.4' Abort, retry, ignore? [a/r/i/...? shows all options] (a): r Retrieving: ipxe-bootimgs-1.21.1+git20210908.02ec659b-lp154.48.1.noarch.rpm ........[done (218,1 KiB/s)] So I'm getting a 404 for packages (or metadata also), and after retrying a few times (or just repeating the "zypper ref" a few times, it finally succeeds. This is mostly happening on "fringe" repos: my home project, CrossToolchain:avr, ..., only very seldom on the main opensuse repos. I'm guessing that I'm first redirected to a mirror which does not carry this repos (or is outdated) and after a few retries, I'm actually redirected to a "good" mirror. This can be up to 6 or 7 retries. Often, once a good mirror is found, more packages from the same repo can be downloaded without retry, but sometimes almost every single package needs retries (right now this is happening with http://download.opensuse.org/repositories/home:/seife:/vdrdevel/15.4) Is there a bugzilla category for such problems? Or should I just bounce this mail to admin(a)opensuse.org? Apparently I am not the only one seeing this as I have gotten reports that http://download.opensuse.org/repositories/vdr/15.4 would not carry binary packages only to get an update a few minutes later that retrying solved the issue. Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

2 1

Update on next generation of SLE
by Stefan Behlert 14 Jun '22

14 Jun '22

(Sending to both openuse-project as well as opensuse-factory. Please keep discussions on the -project list to make life easier for all.) Moin, In the last months many people have brought up the topic of "When will the next SLE major version come out?". Today we would like to give you a first update on the plans. Since 2018, when SLE 15 was initially released a lot of things have changed, including requirements from users and customers, technologies, the speed of new versions of applications, languages and their libraries appearing. Also the connection between Leap and SLE has changed. And while some bits and pieces got better, we firmly believe we can do better. SLE 15 is a great general purpose operating system, yet challenges with some use cases, now places of deployment, and the type of enhancement requests show that it's time for a successor. With the next generation of Enterprise releases we want to tackle the above. Intending to do radical changes (regarding technology- but also design-wise) we choose "Adaptable Linux Platform" or short "ALP" as codename for that next generation. This indicates already that some things will be quite different than a "mere "SLE 15++ would be ;) First and foremost, ALP will be developed in the open. We are not going to put the pieces together internally and then share outside, as in the past. No, we are creating and building in the openSUSE Build Service - in a project next to you :). You get to directly see to see what is going on and participate more easaily. Another important point is that we intend to split what was a more generic, everything is closely intertwined into two parts: One smaller hardware enabling piece, a kind of "host OS", and the and the layer providing and supporting applications, which will be container (and VM) based. You might say "This is very generic, can you tell us more?" - of course. In the upcoming weeks more and more will crystalize, and we will share as quickly and regularly as possible. This is just a first heads-up to inform you that we are in the process of setting everything up - from project to feedback channels, from documentation to testing. Of course, you will have lots of other questions - how will contribution work, what impacts this has on LEAP and get-o-o, how migration could work, and many more. We kindly ask you for a little bit of patience. We promise we will share as soon as possible more details. ciao, Stefan -- Stefan Behlert, SUSE Software Solutions Product Management SUSE Linux Enterprise Maxfeldstr. 5, D-90409 Nuernberg, Germany SUSE Software Solutions Germany GmbH, GF: Ivo Totev (HRB 36809, AG Nuernberg)

11 23

Community Meeting/ALP WG: Week 24
by ddemaio 14 Jun '22

14 Jun '22

The ALP WG will take place tomorrow at 14:30 UTC The Community Meeting is on Thursday at 19:00 UTC. Both meeting will be in https://meet.opensuse.org/meeting You can read the notes from last week's at https://etherpad.opensuse.org/p/weeklymeeting20220609 You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. v/r Doug

2 1

Re: Why all the fear?
by Lukáš Krejza 10 Jun '22

10 Jun '22

Dne čtvrtek 2. června 2022 21:13:37 CEST, iob napsal(a): <snip> > pretty much same here. snapper is enabled for example. Never had a > serious problem and never used those fancy stuff. it was not always > perfect and with some configuration here and there, i consider TW > stable for a rolling distro. > > But in the other side, i think it is very easy to mess up or break the > system. Usually with some repo that you found online or someone > recommended etc. > > IMO one of the reasons for the fear comes from the lack of good/working > documentation and tutorial. > Yeah, that is why i mentioned documentation as one of the three most important parts that should be mentioned on the openSUSE web page here: [1]. But i guess nobody cares or noticed that, since the thread got massively off-topic. [1]: https://lists.opensuse.org/archives/list/project@lists.opensuse.org/ message/V76ABRHJ6AYC5S4UW5CE4TLQYUNZZRUW/ Regards, Gryffus

1 0

openSUSE @ Open Source Day (Mentoring)
by Sarah Julia Kriesch 09 Jun '22

09 Jun '22

Hello together, last year was the first time, that I and my zsystems team has participated at th virtual Open Source Day [0]. The Open Source Day is a hackathon day in the USA, where female mentees can contribute to open source projects. I was asked because they had looked for a Linux community and a female community Representative. I can say, that we had success and have received also some new openSUSE Members on this way. But we had provided only s390x tasks. We want to join again. Is anybody else interested to join our team as a Mentor? Then we can provide more tasks (outside of s390x). These tasks can be also packaging related or other (development) stuff. But most should be entry level. The next Open Source Day is Friday, September 16th, 2022. A small warning for all openSUSE Contributors from Europe: That will be a hack night for us! ;) We (from the zsystems team) are planning to join this event again. We would be happy about additional openSUSE Mentors, because the former assigned Mentors were more on an intern level as a qualification. In parallel, a female Release Manager by a hardware distributor should have been a Mentee and interacted as a Mentor. If you are interested to join us, answer to this email and apply on the Open Source Day page[1] as a Mentor. Best regards, Sarah [0] https://opensourceday.anitab.org/agenda/session/570707 [1] https://ghc.anitab.org/programs-and-awards/open-source-day/

1 0

Community Meeting: Week 23
by ddemaio 09 Jun '22

09 Jun '22

Hi all, There will be a Community Meeting this evening.All meeting take place in https://meet.opensuse.org/meeting You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. Cya later v/r Doug

1 0

openSUSE Community Releases Leap 15.4 Version
by ddemaio 09 Jun '22

09 Jun '22

On behalf of all contributors to the openSUSE Project and the release team, I would like to inform you that we have released openSUSE Leap 15.4. Please view the announcement online at https://news.opensuse.org/2022/06/08/leap-offers-new-features-familiar-stab… I would like to thank all those involved in the release. A special thank you to the developers, release team, packagers, testers, bug reporters, partners and community projects. I want to personally thank those who helped with the release notes, translations, release announcement, artwork and social media. v/r Doug

3 2

Re: openSUSE Release Engineering meeting 04.05.2022
by Luna Jernberg 06 Jun '22

06 Jun '22

Will miss the meeting this week as another thing popped up, but will read the minutes about what was said later and download 15.4 Stable later that day On Wed, May 11, 2022 at 8:49 AM Luna Jernberg <droidbittin(a)gmail.com> wrote: > Will attend the meeting live today :) > > On Sun, May 8, 2022 at 12:39 PM Luna Jernberg <droidbittin(a)gmail.com> > wrote: > >> Hey! >> >> Did read up on this now, has had too much to do earlier this week, and >> started working a bit on the Swedish Translations of the Leap 15.4 Release >> notes, and @Johan Dot <jonte1(a)gmail.com> promised to continue to work on >> them later today :) >> >> On Thu, May 5, 2022 at 3:56 PM Lubos Kocman <lubos.kocman(a)suse.com> >> wrote: >> >>> All meeting minutes can be found here: >>> https://etherpad.opensuse.org/p/ReleaseEngineering-meeting >>> Meeting is hosted here >>> https://meet.opensuse.org/ReleaseEngineeringMeeting >>> >>> ## Attendees >>> guillaumeg, DimStar, rbrown, lkocman, mpiala, ddemaio, maurizio >>> (m4u).maxlin, Sarah >>> >>> ## Internal SUSE IT Supported distribution >>> >>> Guests: Martin Piala, Vojtech Pavlik >>> >>> Idea: openSUSE Leap as supported system by SUSE IT! >>> Vadim G. is looking for a help to kickstart the effort. >>> We're thinking of starting a hackweek with a Leap 15.4 spin with some >>> preinstalled tools for SUSE environment. >>> >>> https://hackweek.opensuse.org/21/projects/opensuse-build-supported-by-suse-… >>> >>> Our feature tracker for any issue references. >>> https://code.opensuse.org/leap/features/issue/77 >>> >>> Next steps collect requirements for Minimal Viable Product >>> I believe Vojtech could help us there. >>> >>> How does Rancher product portfolio fit in? >>> >>> Datto is using gnome-initial-setup for post-install tweaks. >>> https://github.com/endlessm/gnome-initial-setup/blob/master/HACKING >>> We could start there as well. However, they're already looking for some >>> futher management tools. >>> I believe that we do not need any 3rd party tools. Perhaps SUMA could >>> help with post-installation management. >>> >>> Martin: currently supported systems by IT are Windows 10 and MacOS, we >>> would like to change this >>> Martin: we'd like to have pre-installed tools required for daily work. >>> slack, teams. >>> We have company portals for Windows10 and Mac and some of the apps can >>> be already preinstalled for the image. >>> Martin: we do not yet have experience for responsibility of building >>> Linux apps and we need your help. >>> Ideally it should be done by the end of the quarter. End of July >>> >>> It's not decided yet what should we use. Whether we need a script post- >>> install. >>> >>> Richard: I do have a couple of questions: >>> >>> Which HW are we talking about? >>> * How often will be the recommended hardware changing? >>> Martin: We have some predefined laptops specific. 2 hardware specs >>> (standard, power). New ones are Lenovo, we're also rotating the older >>> Dells. >>> Martin will discuss this with team. In the next HW rotation we should >>> take the support of the chosen OS into consideration. >>> * Would the best option be Leap based? And perhaps risk some of the >>> missing hardware support? >>> * Or should we consider something Tumbleweed based? Perhaps you will >>> end up with something like MicroOS >>> * Desktop. Teams, Slack would be then consumed from Flatpaks. >>> >>> lkocman: I recommend to consider two approaches: provide root password >>> to the user or not. For less technical users it would be preferred if >>> SUSE it would do most of the changes. >>> Martin: For IT are also preferred these two options, one with admin >>> access (here the user is responsible for the setup), and another with >>> limited permissions, where IT is responsible for maintenance + the >>> laptop must be enrolled (most probably in VMware Workspace One, >>> currently under research). >>> >>> ## Leap >>> >>> Leap Micro 5.2 is RC! >>> >>> We've also progressed on release-notes-leap-micro (Thanks cboltz and >>> Lukas) >>> https://doc.opensuse.org/release-notes/x86_64/openSUSE/LeapMicro/5.2/ >>> >>> Rework of LeapMicro get-o-o layout >>> community worked on overview for Leap Micro >>> https://etherpad.opensuse.org/p/weeklymeeting20220505#L51 >>> We should also consider single page layout MicroOS and backport >>> overview changes as well >>> https://github.com/openSUSE/get-o-o/pull/87 >>> >>> >>> A lot of changes from SLE 15 SP4 post-RC. Removing snapshot at this >>> point in time was not so good choice in the end. Some more changes will >>> be taken in today, tomorrow. Mass rebuild is planned in next few days >>> (Friday/Saturday). Maint snapshot for SLE 15 SP4 on Sunday. >>> We need to be able to finish the RC build, that's not possible now. >>> >>> Leap Desktop/Workstation workshop is next week! >>> 50+ people have signed up for workshop >>> >>> https://www.reddit.com/r/openSUSE/comments/udr5ly/desktop_workshop_for_next… >>> - syncup with Scott and Yi Fan prior the acutal workshop >>> Looking for drivers who could help us "kickstart the initial workshop". >>> Long story We need some people who already know what to do (how lucid >>> works, create some initial topics) to inspire others. >>> >>> Interesting last minute feature for laptop customizations. (Big thanks >>> Dirk) I'll see what would be easily adoptable. SLED is interested as >>> well. >>> https://code.opensuse.org/leap/features/issue/75 >>> >>> >>> ## openSUSE Tumbleweed >>> >>> openSUSE:Factory build fail stats: 108 failed, 10 unresolvable (last >>> week: 123/11) >>> https://tinyurl.com/ysy4nnnz >>> >>> * GNOME 42.1 shipped in snapshot 0501 (snapshot 0429 and 0430 were >>> blocked due to dracut) >>> * KDE Plasma 5.24.5 staged - ready for either 0504 or 0505 >>> * Meson 0.62 is staged - another round of 'syntax validation getting >>> stricter' (not too many issues seen though) >>> * GCC12 as default compiler still staged, results are looking very good >>> (Staging QA all passed, waiting for the final go) >>> lkocman: I hope that Alp will adopt to the new default(s) as well. >>> Mentioned the llvm situation in Leap 15.X >>> >>> GPG Key to sign packages/repos is planned to be updated to be a >>> 4096/RSA key (implementation schedule pending) >>> Tracker bug : https://bugzilla.suse.com/show_bug.cgi?id=1199184 >>> >>> OBS seems to have some hard time finding workers for ceph and kernel >>> builds: very frequently, staging projects are blocked by waiting for >>> the 4 same packages still being scheduled (ceph, kernel-default, >>> kernel-vanilla, kernel-debug) (constraints limit to 18 (ceph) resp 24 >>> (kernels) workers) >>> >>> ## Richard (Kubic/MicroOS) >>> >>> Started Discussion with the Kubic community about winding down the >>> Kubic project and focusing more attention on MicroOS (and MicroOS >>> Desktop) - >>> >>> https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org/thread/23… >>> For those currently on Kubic, Kubernetes atop MicroOS is best addressed >>> with using k3s/RKE direct from Rancher. Whether we need >>> tooling/documentation to help with potential migrations is an open >>> question. >>> lkocman: This topic was raised also on the community meeting. Isn't >>> Kubic the only Kubernetes and CNCF certified distro that we have now? >>> Richard: depends on your definition of 'we' - CNCF certification is >>> specific to the Kubernetes that is part of Kubic. Rancher k3s supports >>> MicroOS and is itself CNCF certified, so 'we' will still have that. >>> lkocman: The question that popped up was how to get the k3s running on >>> Leap Micro. I did share the whitepaper for SLE Micro 5.1. Richard: this >>> should just work with 5.2+. >>> >>> Objecting to the Leap Micro get.opensuse.org page overstating it's case >>> at the expense of other openSUSE Projects that address the same use >>> cases - https://github.com/openSUSE/get-o-o/issues/88 >>> >>> MicroOS (GNOME) Desktop has a fresh community effort to get out of >>> beta, possibly by writing a fresh notification tool for transactional- >>> updates instead of relying on PackageKit. Join the Telegram/Matrix >>> MicroOS Desktop channel to join the effort. >>> >>> Podman 4.0.x now working perfectly >>> >>> Working on various interesting MicroOS research tracks: >>> - kiwi-less/container first VM image building Status: POC >>> - nerdctl support in toolbox Status: Broken prototype >>> - buildkit and its limit as a container builder >>> - TW-to-MicroOS conversion >>> - curl-minimal and making it default (like Fedora) Status: >>> Investigating >>> - Re-arranging Factory so products like MicroOS can build with >>> different PrjConf than Tumbleweed >>> - MicroOS Desktop using TIU instead of transactional-update (ie. >>> remove all individual rpm package management) (research not sure if >>> it's worth updating docs yet) >>> Please ping rbrown(a)suse.com if you are interested/have opinions on any >>> of the above, feedback/thoughts/existing knowledge is welcome. >>> >>> ## Max >>> >>> Leap Micro >>> * Have a look repotred Leap Micro selfinstall has different behavior >>> compare to SLEM on openqa, it should boot iso instead of raw image for >>> the testing, bsc#1197877 >>> * Removed beta flag >>> >>> Leap 15.4 >>> * Look into python-certbot bug, the culprit is: python-pyopenssl in >>> SLE15 SP4 has been updated to version 20, it's requiring python- >>> cryptography > 3.2 however we had 2.8 in SLE, the minimal requirement >>> can not filled, this should affected many packages rely on pyopenssl, >>> bsc#1198851 (There is a SLE maintenance request for python-cert*, but >>> it's a major version bump) >>> Marcus does not recommend forking package in Leap as there are other >>> SLE python modules that will depend on it. >>> * Removed snapshot repo >>> * Preparing 15.4 RC build >>> Lubos will send an annoucement that RC will be delayed because of >>> incoming changes from SLE 15 SP4. >>> * Build fail stats in Leap 15.4: 20 build fails, 0 unresolvables >>> lkocman: I'll open individual bugs for remaining build failures. >>> >>> Santiago mentioned that he'll have more free cycles for Leap/openQA >>> this week. I'll reach out to him regarding focus on the migration >>> scenarios. >>> >>> ## Guillaume - Arm >>> >>> Tumbleweed: >>> * Rolling again >>> * Upcoming GCC 12 tested for aarch64: >>> >>> https://build.opensuse.org/project/show/home:dirkmueller:branches:openSUSE:… >>> >>> Leap 15.4: >>> * aarch64: >>> * Issue with Numpy/openBLAS fixed: >>> https://bugzilla.suse.com/show_bug.cgi?id=1198885 >>> * armv7: >>> * Enlightenment package still fails in rpmlint check (missing >>> whitelist?): https://bugzilla.opensuse.org/show_bug.cgi?id=1194047 >>> lkocman: will reach out to simotek and Wolfgang >>> * scc product class looks wrong (Marina/Marcus) (for all non-intel >>> arches). x86_64 has OPENSUSE-BETA while for the others the class is >>> SLES-ARM64-BETA, SLES-PPC-BETA, SLES-Z-BETA. >>> https://sd.suse.com/servicedesk/customer/portal/1/SD-82355 (Internal, >>> Ticket with SCC team, team lead is aware of the request). Request is >>> now resolved. (lkocman: Correction trello shows me that 2/4 items are >>> still pending). SCC team confirmed that this is done. I did check non- >>> intel arches and they seem to all use OPENSUSE-BETA. >>> >>> Leap Micro 5.2: >>> * SR to add Default-SelfInstall image for aarch64: >>> https://build.opensuse.org/request/show/974751 >>> Lubos will open a JIRA for 5.3. I'll ask if it would be option for 5.2 >>> as well. >>> >>> lkocman to check if we could remove the firefox tests from the >>> 42.X/15.0 upgrade test suite. It doesn't seem to happen outside of that >>> (same for TW). >>> lkocman will try to look into this >>> >>> ## Sarah - s390x >>> >>> SUSE has shutdown 3 LPARs because of performance issues >>> Issue has been also reported to the CTO for ZSystems of IBM >>> >>> Tumbleweed: >>> * Is rolling >>> >>> >>> openSUSE Leap Beta: >>> * no issues at the moment >>> >>> * maven issues are existing -> discussions about upgrading the Java >>> version or how to fix it >>> >>> lkocman: slightly related topic, should we perhaps re-consider >>> recommended memory amount in Release Notes? I think we still recommend >>> something like 2G minimal / 4G or 8G optimal. >>> * KDE for s390x adopted >>> >>> ## Doug >>> * TSP >>> * Solution seems to be found >>> * No update on status on when it can be implemented >>> * Community Meeting >>> * Discussion/workshop planned for community meetings on May 10 & 12 to >>> discuss successor of Leap >>> * >>> >>> https://lists.opensuse.org/archives/list/project@lists.opensuse.org/thread/… >>> * oSC22 >>> * Will cancel all talks on confrimed by May 6 >>> * Schedule mostly complete >>> * Ordering badge and signage >>> * Setting up venueless platform >>> * Slides need to be 16x9 >>> * OSCAL oSC22 >>> * Will start creating schedule >>> * Reached out to people to confirm their talks >>> * GSoC >>> * 4 proposals ranked for May 12 deadline >>> >>> Installfest in CZ. CfP deadline was Monday midnight: >>> MicroOS >>> Leap and Leap Micro >>> D-Installer >>> >>> talks were submitted >>> >>> ## Dirk >>> >>> Not available >>> >>> lkocman: Thanks for the framework laptop setup >>> We're not currently listed as framework laptop compatible distro >>> https://gist.github.com/cornfeedhobo/8f32430dc6c52b9a4776df91701b1d96 >>> >>> * switched obs-arm-11 worker to aio=io_uring away from aio=threads >>> which appears to reduce I/O cost (bsc#1197746), which caused issues on >>> x86_64. still chasing that down. >>> * did a full rebuild of openSUSE:Factory:ARM as Guillaume was away and >>> openqa was broken anyway :) did introduce more issues than it fixed it >>> appears >>> * Still to work rust 1.59 / ghc issues on armv6 and armv7: all have the >>> same root cause, use of SWP/SWPB instructions which is imperfectly >>> emulated by the aarch64 host kernel. works fine with armv6/v7 kernel. >>> * looked into gcc11 build failures >>> >>> In backlog: https://code.opensuse.org/leap/features/issue/17 >>> >>> ## Wolfgang (Package Hub), Scott Bahling >>> >>> Not available >>> >>> ## Maintenance team (Marina or Marcus, Maurizio (m4u)) >>> >>> - Marcus: 15.4 is set up channel wise, updates will go in testing >>> occasionaly, if you need more ping me, no openqa setup yet >>> lkocman: could you please help me with cleanup of maintenance tasks in >>> https://progress.opensuse.org/projects/opensuse-leap-15-4/issues/gantt >>> lkocman: will contact Jan Stehlik. Santi (PO for the topic) mentioned >>> he'll work on it. >>> lkocman: messaged Jan >>> - Marcus: 15.3 openQA is ok again. >>> >>> lkocman: (still pending) will open a release notes entry for a change >>> Security Advisory identification >>> TODO Marcus: could you give me example of old and new values? >>> >>> - Marina and Maurizio: SLE-PackageHub overlaps >>> (https://github.com/openSUSE/openSUSE-release-process/issues/71) work >>> in progress following the initial list of overlapping packages >>> (https://progress.opensuse.org/issues/106610#note-3) More incidents >>> are under QA. Work is going on and under control (and tracked >>> internally as jsc#MSC-303). >>> Already released: (AH PERFECT!) >>> SUSE:Maintenance:22929:265929 (babl libbabl-0_1-0 typelib-1_0-Babl-0_1) >>> SUSE:Maintenance:23000:266006 (MozillaThunderbird enigmail) >>> SUSE:Maintenance:23009:266004 (freerdp freerdp-devel freerdp-proxy >>> libfreerdp2 libgsm) -> libgsm1 was missing in PH making freerdp not >>> installable >>> SUSE:Maintenance:22928:266007 (argyllcms csync libcsync0 libcsync- >>> plugin-sftp libcsync-plugin-smb) >>> SUSE:Maintenance:23015:267052 (gfbgraph-devel libgfbgraph-0_2-0 >>> typelib-1_0-GFBGraph-0_2 librest gcr) -> librest, gcr and libgoa are >>> needed too for making gfbgraph installable >>> SUSE:Maintenance:23334:268316 (gutenprint gutenprint-devel) >>> SUSE:Maintenance:23486:268867 (hp-drive-guard, upower) --> needs >>> libupower-glib3 >>> SUSE:Maintenance:23487:268897 (liba52-0 liba52-devel) >>> SUSE:Maintenance:23506:268899 (libdvdread4 libdvdread-devel) >>> >>> Meet product security at the openSUSE Conference. There are about 3 >>> talks on the maintenance and security topics. Come and say Hello! >>> >>> ## Adrian - OBS >>> >>> Not present >>> >>> feedback loop on mirrored submissions doesn't workstation. Lubos wills >>> end an email with an example to Marco and Adrian. (Sent last week) >>> Marco has reached out to me regarding the mirroring. He has example(s) >>> from SUSE:SLE-15:SP4:GA >>> >>>

1 0

Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)
by openSUSE Meeting Reminder 04 Jun '22

04 Jun '22

Hello all, The biweekly board conf call will be held in two days at 13:00 Europe/Berlin time (CET = UTC+1) Meeting will be in the regular Board Meeting Room https://meet.opensuse.org/OSBoard Current Topics: https://code.opensuse.org/board/tickets/issues?status=Open&tags=meeting Board Members: If you cannot participate, please advise by replying to this mail.

3 2

ways to contribute to openSUSE
by Per Jessen 03 Jun '22

03 Jun '22

Just now I happened to stop by https://www.opensuse.org, and noticed this: CONTRIBUTE TO OPENSUSE Be part of our community contributing with any of the following: Code or hardware. Firstly, I appreciate it is written in capitals, but shouldn't it still be "openSUSE" ? Second, code and hardware are the only ways to contribute ?? That seems a bit limited - shouldn't we be a bit more inclusive? I know the overlay that appears once you click "code" has more options, largely copied from here: https://en.opensuse.org/Portal:How_to_participate Maybe it's just me, but when the first reply to "How to contribute" is "code or send us some hardware", that's a bit too limited. "Hardware" is surely not exactly the most common option either ... I honestly don't know what the most common ways are, although I expect code is certainly one. -- Per Jessen, Zürich (27.1°C) Member, openSUSE Heroes

21 95

Why all the fear?
by Lukáš Krejza 01 Jun '22

01 Jun '22

Hey Geekos, First of all, sorry for this cross-post, but it is relevant to all of the lists specified. I am just wondering if my experience is so much different, or if I use the distro differently than other users, that it seems so much stable for me. Often i see people recommending against "zypper dup", recommending "tumbleweed-cli" instead of "zypper dup", using "opi" for codecs install instead of 1-click install on opensuse-community, and so on, because the system "could" or "will for sure" break at some time. Why there is a need for all this fancy and new stuff and is it possible that these combinations and diversity increases possibility for issues? Given all of these, I should have had my home machines broken already a million times and burned to death. - I am using Tumbleweed - I have all these repositories enabled: [1] (yes, no priorities currently) - I have "zypper dup", "zypper inr", "zypper ve" in my daily cron job - I have enabled vendor changes in zypper conf - I have disabled multiversion.kernel in zypper conf (keeps kernel packages with their dependencies and/or DKMS clean and working) - I have disabled snapper as a whole - I have installed some VMWare software from their crappy .run packages, which means some parts are compiled from source During my over-15 years-long experience with *SUSE, i never experienced an unbootable system or a serious issue, except: - Nvidia driver issues before they were packaged for *SUSE and you had to use the .run installation ( ancient SaX2 times, before Xorg autoconfiguration ). On my gaming system i have just enabled nvidia repos and forgot about it. - Akonadi issues because of my experiments with bleeding edge mariadb in combination with my mailbox containing few million e-mails, also many years back - Btrfs issues (total system crash) when it was unstable and i had enabled snapper an ran out of space - which was resolved by reinstall and re-mounting my /home/ (i am not using snapper since then) So my question is - have the RPM dependencies gone weaker than they were "before" or something? Could that combination of all the emergency safe features, like btrfs snapshots in combination with multiversion kernel and/or packages, tumbleweed-cli, opi, etc...? Why are RPM deps not enough to keep the system solid anymore? My experience with *SUSE has always been rock-solid-stable and one of the very few things i do manually from time to time is firing up yast2 sw_single, removing unmaintained packages and checking change-logs of some packages i am interested/care of. Take this as a congrats and thanks for all the maintainers, developers and everyone taking care. And most importantly, the OBS, which does pretty neat job with automatic package dependencies and all that stuff. One more time - thank you OBS and all the people developing and working on it! :) And while i am doing this braindump, please revive SUSE Studio :P :) And last, but not least - thanks Packman people :) [1]: https://paste.opensuse.org/view/raw/38599835 Regards, Gryffus

1 0