Hello,
the next heroes meeting will be on Tuesday (2022-03-01) at 19:00 UTC /
20:00 CET in https://meet.opensuse.org/heroeshttps://progress.opensuse.org/issues/105822 already lists the usual
topics. Feel free to add things you want to discuss, or just join the
meeting.
Regards,
Christian Boltz
--
> > That's the part where we create a flame war and then try to
> > collect some useful ideas afterwards. ;-)
> Let's collect ideas directly ;-)
Humm.. interesting.. never thought about that approach. :-)
[> Andreas Jaeger and (>>) Gustavo Niemeyer in opensuse-packaging]
hi,
Have you been able to look at my request?
I'm guessing that the tsp will be very much up and running again for the oSC :)
Best,
Syds
--
Syds Bearda
Treasurer openSUSE Project
opensuse(a)syds.eu
On Mon, 17 Jan 2022, at 12:57, Syds Bearda wrote:
> Hi,
>
> I hope this email address works :)
>
> Could you please look into my rights at tsp.o.o? I can't see and
> approve requests atm. And with the current state of the pandemic that
> was okay, but with the opcoming oS converence, i would prefer to be
> able to do it myself instead of only relaying on Doug.
>
> Best,
> Syds
>
> --
> Syds Bearda
> Treasurer openSUSE Project
> opensuse(a)syds.eu
>
> ----- Original message -----
> From: Syds Bearda <opensuse(a)syds.eu>
> To: progress(a)opensuse.org
> Cc: Douglas DeMaio <ddemaio(a)suse.com>
> Subject: Fwd: ticket - access TSP
> Date: Thursday, 13 January 2022 19:35
>
> Hi,
>
> I had emailed admin(a)opensuse.org, Knurpht said that this email is
> probably the right one.
>
> Could you please look into the underneath? As treasurer it's pretty
> helpful to have access to TSP.
>
> Thanks,
> Syds
>
> --
> Syds Bearda
> Treasurer openSUSE Project
> opensuse(a)syds.eu
>
> ----- Original message -----
> From: Syds Bearda <opensuse(a)syds.eu>
> To: admin(a)opensuse.org
> Cc: Douglas DeMaio <ddemaio(a)suse.com>
> Subject: ticket - access TSP
> Date: Friday, 10 December 2021 12:25
>
> Hi,
>
> Last night Doug and I approved a TSP request together since I couldn't
> see the request myself.
>
> When I click the direct link
> (https://tsp.opensuse.org/travel_sponsorships/457) I get the following
> error:
> `
> You are not allowed to access this page.
>
> If you think that you should, contact your administrator.
> `
>
> Could you please give me the proper access, so I can see and approve
> the requests?
>
> Thanks :)
> /Syds
>
> --
> Syds Bearda
> Treasurer openSUSE Project
> opensuse(a)syds.eu
Yesterday I ran state.apply, so far no apparent issues. Please let me
know if you notice any.
For various reasons, it's been a slightly long untertaking, but we made
it :-)
None of my doing really, I only supplied the mailserver knowledge, all
of the credit goes to Olav.
MX1 is next!
--
Per Jessen, Zürich (7.1°C)
Member, openSUSE Heroes
https://www.reddit.com/r/openSUSE/comments/sp5m9u/idp_problem_postmortem/
> Yesterday I fixed a small outage that likely started 2022-02-03 08:16 and continued til 2022-02-09 16:30 UTC.
>
> The effect was that user password changes via https://idp-portal.suse.com threw an error. Maybe other IDP functions to create and update accounts were also affected.
>
> Background: Since SUSE split out from MicroFocus in 2020 and could not continue using their Novell Accessmanager service for handling openSUSE user accounts. Since then we operate our own identity Provider (IDP) using Univention Corporate Server (UCS). That is a Debian-based solution with professional support.
>
> So what was the problem?
>
> The IDP setup uses a main server that gets all the writes via Kerberos and several replicas that handle the authentication, mostly via LDAP. Yesterday we learned that password-updates were broken.
>
> With the help of Univention support I could find that kpasswd did not work in a shell and with tcpdump -epni eth0 host 10.x.x.x I could see it try to communicate over UDP port 88 and see a reply of "Port unreachable". So I checked the main server and indeed, ss -uanp showed that port 88 was only bound to half of the IPs, but not the one it tried to reach.
>
> With a simple /etc/init.d/heimdal-kdc restart on the main server, the kerberos process started to listen on all IPs and thus password changes were fixed. While the immediate outage was over, I still spent the next morning to find out why it failed like this. With systemd-analyze plot > plot.svg I could see that kdc was started long before the network-online.target was reached. Since this is still using old SysV-init scripts, I added a $network to its Required-Start line and on next boot, the .svg looked better. This gave us back an IDP that is working even after a boot.
>
> The only remaining mystery is why this issue has not shown up earlier. At least https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=heimdal-kdc does not have reports in that direction and the debian.tar.xz in https://packages.debian.org/de/bullseye/heimdal-kdc contains the same problematic Required-Start line. So that mystery will probably remain...
Before you ask, yes, mailman was down from last night around 20:00 until
this morning at 10 when I started it up.
poo#106065
--
Per Jessen, Zürich (4.8°C)
Member, openSUSE Heroes
It often happens, usually once a day, that opening a bookmark to any particular
forum (e.g. hardware, or applications) opens https://forums.opensuse.org/ instead.
Is there something that can be done to prevent that nuisance from polluting
browser and tab history?
Also, why is it that every day, at least one logout is forced? What purpose is
served by it? I don't know of any other forums that do that, unless the browser is
closed and reopened.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
Hello,
here are the minutes of today's meeting:
status reports:
- Lars works on enabling DMARC for the opensuse.org domain, starting
with relaxed settings and looking for the outcome. If everything works
as expected, we can look further...
- Per worked on various issues, see
https://lists.opensuse.org/archives/list/heroes@lists.opensuse.org/
message/LK44FTIVAY3F2FOP7VZFZPXFZZNBVHIY/
Discussed mailman slowness (especially moderation queue, poo#104899),
but didn't come to a result. It's probably worth asking upstream at
https://gitlab.com/mailman
Ticket status "Resolved" and "Closed" can only be set by members of the
"Managers" group on progress.o.o - no idea why, there's no place in
progress that restricts ticket states to a specific group (at least we
didn't find one)
Regards,
Christian Boltz
--
Hätte Frau Merkel Twitter gefragt, wär's ein süßes Kätzchen geworden.
Aber keins, das schon mal 'ne Maus gefressen hat. #gauck
[https://twitter.com/jythma/statuses/171549518163230721]
Hello,
the next heroes meeting will be on Tuesday (2022-02-01) at 19:00 UTC /
20:00 CET in https://meet.opensuse.org/heroes
So far, the meeting ticket https://progress.opensuse.org/issues/104811
lists the usual topics. Feel free to add topics and/or status reports -
or just bring them up in the meeting.
Regards,
Christian Boltz
--
[Linux installieren] Ja, aber, wie war es denn nun - am Morgen nach der
Installation? Soviel dazu: Erschöpft, aber beruhigt eingeschlafen. Am
nächsten Morgen aufgewacht, Rechner eingeschaltet - geweint. Nein, nicht
vor Enttäuschung - vor Glück! [Bernd Graff auf www.sueddeutsche.de]
