On 19/06/2021 12.26, smurfd wrote:
> On 2021-06-19 10:35, Carlos E. R. wrote:
>> On Saturday, 2021-06-19 at 08:12 -0000, Lubos Kocman wrote:
> this happened for me aswell. just had to check since i was earlier able
> to download isos on release day.
> im getting redirected to : ftp.acc.umu.se and they do not now have a
> openSUSE-Leap-15.3-DVD-x86_64.iso in their
> /mirror/opensuse.org/distribution/leap/15.3/iso directory, they do
> however have a openSUSE-Leap-15.3-DVD-x86_64-Media.iso (same for NET)
> just for your info.
The problem seems to be that some of the mirrors do not have the files,
but the download redirector has the wrong information and thinks they do
have the files, so you get redirected sometimes to a bad mirror.
Thus, as shown by my post, if you use a smart downloader aware of
metalinks, you can download the things at full speed as I did.
Cheers / Saludos,
Carlos E. R.
(from 15.2 x86_64 at Telcontar)
seems like the redirect for Leap doesn't work as expected. People are
reporting that they're getting 404 for All Leap downloads. Same for me
(I get redirected to widehat.opensuse.org which then returns 404).
Seems like this is a very recent issue.
I did open the high priority ticket for Heroes as I couldn't see any
public item in the openSUSE admin queue. The ticket is private until
somebody from admins triages it.
Thank you for your understanding and we're sorry for the inconvenience.
Release Manager openSUSE Leap
is there a matrix server run by opensuse, that i can use with my OBS
Jabber (XMPP): lemmy(a)tuxonline.tech
IRC: [Lemmy] on freenode and ircnet (bouncer active)
gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
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
See, for example,
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.
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
I'd like to give big thanks to all of those who participated in our
openSUSE Leap 15.3 release retrospective.
We've received 605 responses which is almost 200 more than in 15.2.
I'm grateful for the increased participation as it shows us that it
makes sense to have this type of feedback loop.
First round of public interview will be held on the openSUSE conference
Everyone is welcome to join us. We'll schedule some more public rounds
on meet-o-o as well, as you can't review all of feedback + create
action items in a single session.
The outcome will then be categorized similarly as our *15.2
retrospective unless we all agree on some better structure.
For those who are interested the raw data from our survey is already
linked to this wiki page.
openSUSE Leap Release Manager
I have a weary wobbly notice on openSUSE and forums. It seems to me that the translation was made by Google translate. Leap15.3. As a Swede, rubbish. No success for Swedish newcomers. Maybe about have a mirror(30-100Mbit)on my site I have been thinking. No I have not upgrade yet to 15.3. May by I will ask for membership When R:B are away.
Today Tuesday, June 15, we will have planning meeting for the openSUSE
Conference at 18:00 UTC. The meetings will take place later in
https://meet.opensuse.org/bar. It will be the last meeting before the
conference. I will give an update on the talks that have been uploaded
and provide a status update on the event.
If you plan on attending the conference, please register
https://events.opensuse.org. Registered people will receive a token to
We are asking for volunteers to help moderate the conference talks. We
would like to fill 10 slots. If you are interested, please visit
https://etherpad.opensuse.org/p/osc21mods and put your name next one or
more of the times you would like to help moderate. We will have a
Practice Day on June 16 for live speakers and moderators.
Meeting minutes for Board call on 2021-06-07 @ 13:00 CEST
Attendees: Gerald, Gertjan, Simon, Neal, Syds
Absent: Vinz, Axel
Guests: Doug, Luna, Maurizio, Onralp, Bill
* Gerald asks for additional topics from the community
* Moderator accountability: https://code.opensuse.org/board/tickets/issue/9
Simon would like to have a consistent accounting of moderation/bans
for Board review
Gertjan notes that the forums banlist is almost entirely spammers,
trolls usually die out before bans/moderation has to be done
It's also noted that this is the same in Matrix, Discord, and
Telegram. Mau notes Discord moderation log is public already.
Gerald restates the topic for clarification and Simon agrees with it.
Simon wants a global (non-public) archive, Neal mentions we could
probably auto-archive into code.opensuse.org using APIs of all
Onralp notes Telegram has an API for this and he does this already with a bot.
Simon wants the archive to note who did the ban and when and on what platform.
Mau would not want the archive with moderator name public.
Simon really wants the moderator info to contact for mod/ban review.
Mau asks about the moderator list, Neal points out it may be
impractical due to how mods are managed.
Neal suggests a moderator lead for each platform, Simon wants all
moderators and thinks we don't have too many.
Gertjan notes that he's had targeted harassment as a moderator.
Board agrees that we should have a global archive in one place for
moderators to review and collect contact info for moderators.
Further implementation details TBD.
* Freenode -> Libera Chat for IRC:
Gerald asks what's left. Simon and Neal note we need to complete the switchover.
Gerald states a trite computer science phrase. "Every problem can be
solved with another level of indirection"
Neal suggests the Board needs to make a formal announcement and update
all the Freenode channel topics with that announcement, specifically
to avoid getting the Freenode hijack so that people *don't* get
Gerald asks Neal if he can handle it. Neal will write the announcement
and talk to darix about applying it to channels.
* Improving the Board meeting/attendance experience:
Luna asks for regular notifications of upcoming meetings.
Neal notes he and Sasi have been looking at deploying fedocal for
other reasons and would help here: https://pagure.io/fedocal
Gerald suggests the minute taker announce the next meeting as an
Gerald also asks that minute takers update the status of tickets
discussed so we don't accidentally discuss it over and over.
Meeting close 14:00 CEST
Neal Gompa (ID: Pharaoh_Atem)
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
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.
Release Manager openSUSE Leap