2026-10-26T10:47:46 Could you guys put a general ban on obujefezo15@gmail.com, they are spamming our MLs with Greek spam messages 2026-10-26T10:50:26 done 2026-10-26T10:54:11 thanks 2026-10-26T18:46:20 the counter.o.o embed in https://en.opensuse.org/Main_Page says 16.1 has 7 days to go. clicking it goes to https://en.opensuse.org/Portal:16.0 where the release widget thing says 16.1 is the latest stable regular release already 2026-10-26T18:47:20 and https://en.opensuse.org/Portal:16.1 says 16.1 was released on nov 3 2026 2026-10-26T18:47:28 I'm not sure if my calendar is correct 2026-10-26T18:49:25 the bug is that clicking it goes to the 16._0_ portal ;-) I missed to update it (in salt) when updating the counter (which nobody did before) 2026-10-26T18:51:49 https://git.infra.opensuse.org/infra/salt/pulls/2845 2026-10-26T18:52:39 aha, thanks 2026-10-26T18:52:56 I suppose that still leaves the wrong text in Portal:16.1 itself 2026-10-26T18:55:04 Nov 3 sounds right (and matches en.o.o/Roadmap), I guess someone was to lazy to write "will be released" and change that to "was released" on that day 2026-10-26T18:57:44 I see, same in Features_16.1 2026-10-26T20:40:45 great, "failed to connect to github.com port 443" now also hit the CI for the salt PR :-/ 2026-10-26T20:41:11 I hate to ask, but - do we have a way to merge despite these (unrelated) test failures? 2026-10-26T20:42:44 (for now, I updated the redirect in the apache config manually) 2026-10-26T20:45:23 yes, I thought you had the option too 2026-10-26T20:46:15 the merge button only offers two variants of "... if checks succeed" 2026-10-26T20:50:26 (I'm just re-running the failed tests, so far it seems they survive the rate limiting (?) on github if started individually) 2026-10-26T20:51:27 the options are a bit lacking, I can either not enforce branch protection for repository admins (but that includes not only status checks but also push to branch etc) or I can set a pattern of checks which are required (currently it's "*") 2026-10-26T20:52:09 there is a draft to fake github.com but it got a bit out of hand 2026-10-26T20:53:07 we should keep branch protection 2026-10-26T20:54:22 if you change the required checks, does that mean a) failures will always be ignored or b) there will be a "merge despite CI failures" button/option I have to explicitely choose? 2026-10-26T20:57:24 speaking about failures - now that it's finally merged, sync to volva* failed (permission denied), only witch1 was updated :-/ (IIRC we had a similar problem in the past) 2026-10-26T20:57:43 rebased https://git.infra.opensuse.org/infra/salt/pulls/2735, I think what was left was about some of the dummy repositories not containing the right branches or similar 2026-10-26T20:58:39 not sure about your question, don't have test account to check. as instance admin it shows a dropdown option like "merge despite" 2026-10-26T20:59:45 I suppose easy solution in your case is to add you to forgejo-ioo-admins in kanidm 2026-10-26T21:00:24 no objections ;-) 2026-10-26T21:01:47 you need to log out and back in to forgejo 2026-10-26T21:03:24 re: volva, it means site to site tunnel or routing is broken .. I repaired it the other week, but apparently not sufficiently >:( 2026-10-26T21:04:10 there was also a todo to add alerts for this 2026-10-26T21:04:17 thanks, I'm just looking around in /admin 2026-10-26T21:05:29 just keep in mind the users and "infra" group are managed from idp, if you want to make changes some day 2026-10-26T21:06:02 ok 2026-10-26T21:06:09 BTW, actually you seem to have a test account, crameleon-test 2026-10-26T21:07:07 of course, I meant I don't have it as, I don't have it handy :)