openSUSE Project June 2022

project@lists.opensuse.org

19 participants
20 discussions

Community Meeting/ALP WG (cancelled this week): Week 26

by ddemaio

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 hour, 8 minutes

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

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

3 hours, 50 minutes

Re: Fwd: opensuse server issues going on now ?

by Luna Jernberg

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 > > >

3 days, 2 hours

Fwd: opensuse server issues going on now ?

by Luna Jernberg

---------- 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?

3 days, 6 hours

Leap 15.4 retro feedback is due to tomorrow night

by Lubos Kocman

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

5 days, 20 hours

Community Meeting/ALP WG: Week 25

by ddemaio

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

6 days, 6 hours

Board Meeting Minutes 2022-06-20

by Knurpht-openSUSE

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

6 days, 23 hours

Minutes of openSUSE Board meeting 2022-04-11

by Neal Gompa

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 week

Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)

by openSUSE Meeting Reminder

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 week, 2 days

Mirror infrastructure problems?

by Stefan Seyfried

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

1 week, 3 days

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Project June 2022