2026-03-06T09:17:21  <matrix-o-o> <Lubos Kocman> Hello team, seems like helios is down in multiple locations. Do we have a tracker for the issue_
2026-03-06T09:17:30  <matrix-o-o> <Lubos Kocman> * issue?
2026-03-06T09:20:29  <matrix-o-o> <Lubos Kocman> https://progress.opensuse.org/issues/197567
2026-03-06T09:24:27  <matrix-o-o> <Lubos Kocman> acidsys any chance you could look into it? This is quite urgen
2026-03-06T09:24:27  <matrix-o-o> <Lubos Kocman> * urgent
2026-03-06T09:52:59  <matrix-o-o> <Lubos Kocman> services seem to be running at least https://paste.opensuse.org/pastes/5534f08f2bf5
2026-03-06T09:54:09  <acidsys> lkocman: responded there; more details would be good
2026-03-06T09:55:05  <matrix-o-o> <Lubos Kocman> interesting for me the page doesn't load at all like not within 30 seconds at least
2026-03-06T09:55:20  <matrix-o-o> <Lubos Kocman> got
2026-03-06T09:55:20  <matrix-o-o> ERR_TIMED_OUT
2026-03-06T09:56:48  <matrix-o-o> <Lubos Kocman> acidsys: would it make sense to start to restart the service?
2026-03-06T09:59:01  <acidsys> no, problem is login proxy
2026-03-06T09:59:23  <acidsys> legacy login proxy that is
2026-03-06T09:59:25  <acidsys> now it will work for a while. but seems changes last week did not help, httpd still locks up
2026-03-06T10:14:51  <matrix-o-o> <Lubos Kocman> thank you! I confirm it works now. I'll write on project
2026-03-06T16:50:34  <DimStar> cboltz: Do you handle IRC cloaks? I just noticed that my user does not have one, even though it's listed in the membership database
2026-03-06T16:55:25  <acidsys> you need to request it explicitly
2026-03-06T16:56:26  <DimStar> adding entry to the database is 'explicit' :) how else to request it? (we should probably check all users with a registered cloak in the database to see if we missed some - that part was not understood in this case)
2026-03-06T16:56:30  <acidsys> if someone requests it as part of their membership application one of us usually does it directly, otherwise if reported in https://code.opensuse.org/project/irc/ or our admin tracker
2026-03-06T16:56:56  <acidsys> I didn't know IRC usernames were stored in the database
2026-03-06T16:57:34  <DimStar> they are - in the field libera_nick
2026-03-06T16:58:19  <acidsys> ok then I guess someone who is motivated could iterate /msg nickserv info or similar over it ;-)
2026-03-06T16:58:26  <DimStar> 26 users have a nick registered in that database
2026-03-06T16:58:39  <acidsys> but keep in mind not everyone who is using libera and an openSUSE member necessarily wants an openSUSE cloak
2026-03-06T16:59:18  <cboltz> to save some time, look at the comment field - when do cloak requests with freenode, I usually add a note there (often a ticket link)
2026-03-06T16:59:19  <DimStar> pretty sure we only added the username for people that requested it. otherwise I'd expect more than 26 entries
2026-03-06T16:59:38  <cboltz> so you only need to check those without a note
2026-03-06T16:59:46  <acidsys> I didn't know there was a comment field to update either, sure I did multiple without :D
2026-03-06T17:00:19  <DimStar> there is a field libera_clak_applied - mine is indeed empty
2026-03-06T17:01:14  <DimStar> I'll create a code.o.o request to set mine - and the user that just asked on the membership request about it. Those two are kinda clear
2026-03-06T17:02:16  <cboltz> no need for a formal ticket, "requested on IRC" is also a valid comment ;-)
2026-03-06T17:03:33  <DimStar> #23 - already done
2026-03-06T17:04:55  <DimStar> maybe we can streamline that a bit, like with the email setup?
2026-03-06T17:05:30  <cboltz> it is a manual process, see https://progress.opensuse.org/projects/opensuse-admin-wiki/wiki/#IRC-cloaks
2026-03-06T17:10:24  <DimStar> I see.. then we as membership officials will try to request the cloak for new users if this comes up during their registration; so from our end no need to fill the libera_nick, libera_cloak entries, right? We just shoot a code.o.o ticket over for the new member referencing the libera nick?
2026-03-06T17:11:41  <cboltz> even easier - I watch the membership tickets, and usually request the cloak after membership is accepted
2026-03-06T17:11:51  <cboltz> no need for additional paperwork/tickets ;-)
2026-03-06T17:12:11  <DimStar> cboltz: ok, even easier
2026-03-06T17:15:38  <DimStar> yay - I'm cloaked
2026-03-06T17:15:41  <DimStar> Thanks cboltz
2026-03-06T17:39:45  <knurpht> cboltz: could you cloak me too? Nick is knurpht, of course. TIA
2026-03-06T19:00:01  <cboltz> done
2026-03-06T19:28:00  <matrix-o-o> <knurpht - Gertjan> cboltz: Wunderbar. Danke dir.
2026-03-06T19:38:34  <cboltz> ok, that's interesting[tm]
2026-03-06T19:39:01  <cboltz> I installed the updates on mailman3.i.o.o (well, most - a few are remaining because of conflicts)
2026-03-06T19:39:21  <cboltz> now solr refuses to start with    fatal library error, lookup self
2026-03-06T19:39:29  <cboltz>     This script relies on a version of ps that supports the -p flag.
2026-03-06T19:40:15  <cboltz> to make things even more interesting,   ps -p 1   works
2026-03-06T19:40:42  <cboltz> any idea what could be wrong with solr?
2026-03-06T19:54:40  <cboltz> unrelated: reboooting matrix.i.o.o, expect a short downtime
2026-03-06T20:10:10  <cboltz> acidsys: when you have some time, can you please check what's wrong with solr on mailman3 (see above)?
2026-03-06T20:10:57  <cboltz> please also check the remaining conflicts on zypper dup on matrix and mailman3
2026-03-06T20:27:44  <DimStar> cboltz: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:G/apparmor/standard/x86_64 apparmor does not luke gnome 50
2026-03-06T21:02:00  <cboltz> the error message is interesting[tm]:
2026-03-06T21:02:05  <cboltz>      GLib-GIRepository-CRITICAL **: 18:00:59.225: Unable to load platform-specific GIO introspection data: Typelib file for namespace 'GLibUnix' (any version) not found
2026-03-06T21:02:50  <cboltz> I'm not sure where this comes from, but I can say for sure that the AppArmor code doesn't include such an error message
2026-03-06T21:05:20  <cboltz> likely candidates are probably   import gi   and   from gi.repository import GLib
2026-03-06T21:19:44  <DimStar> yes, imoort gi meabs you miss typelib(GLib) dep
2026-03-06T21:20:57  <cboltz> you mean   Requires: typelib(GLib)   could be enough?
2026-03-06T21:22:37  <DimStar> or BuldRequiree to have it in the build env
2026-03-06T21:22:56  <cboltz> probably both ;-)
2026-03-06T21:24:20  <DimStar> requires should be autodetected with BuildRequires: gobject-introspection
2026-03-06T22:01:05  <cboltz> just checked (on my laptop, not in Staging:G) - apparmor-utils require and BR python3-notify2, which requires python313-dbus-python, which requires python313-gobject, which requires typelib(GLib)
2026-03-06T22:02:07  <cboltz> so unless something in the dependency chain changed, adding an explicit Requires + BR for typelib(GLib) probably won't change something (I'm testing it nevertheless, waiting for the build results)
2026-03-06T22:11:37  <cboltz> fails as somewhat expected in https://build.opensuse.org/package/show/home:cboltz:branches:openSUSE:Factory:Rings:1-MinimalX/apparmor (builds directly against Staging:G)
2026-03-06T22:14:22  <cboltz> I'm open for other proposals, but I tend to say that this looks like a bug in python313-gobject with gnome 50 and should be fixed there
2026-03-06T22:16:44  *** spyonthewall_ is now known as spyonthewall