2026-10-28T13:43:09 does src.opensuse not provide unauthenthicated/public git for regular users? needed for scmsync, just gonna use codeberg/gh if thats the case 2026-10-28T14:03:33 dza - what do you mean? To browse without beeing logged in? 2026-10-28T14:03:53 https://src.opensuse.org/GNOME/gnome-calculator -> can view that without being logged in 2026-10-28T14:05:46 oh wait :-) cant view the actual code, just list the dirs/files 2026-10-28T14:05:57 anti-ai measure I bet 2026-10-28T14:06:59 Bjørn: I suspect so... 2026-10-28T14:32:07 Bjørn: repo listed internal in gitea and https cloning/fetching seems disabled `git ls-remote https://src.opensuse.org/dza/test.git`: remote: Unauthorized. Idk if I'm missing something and you're able to authenticate via scmsync I haven't used openSUSE that long. 2026-10-28T14:40:18 did https://en.opensuse.org/openSUSE:Git_Packaging_Workflow tried creating git-obs token from gitea, scmsync didn't run when triggered with `osc remoterun` so I just assumed its manually requested/enabled or reserved for suse devs 2026-10-28T14:42:02 seems that token is used locally, so I'm not sure what its for then. thats why I assume its reserved for suse devs. 2026-10-28T14:47:07 no you can be a "regular" obs user and have it automagically work - Im not a suse dev, and use it all the time 2026-10-28T14:47:50 is the "git-workflow" matrix room available on irc? 2026-10-28T14:49:08 dza what is the obs branch repo where you are trying to "work" in? 2026-10-28T14:53:37 Bjørn: https://build.opensuse.org/projects/home:dza:shells/packages/bash-completion-git had repo, but deleted concluded it probably won't work need to be hosted on a public github/codeberg until I find out how to auth https://src.opensuse.org/dza/bash-completion-git.git#package-changes also tried without .git 2026-10-28T14:54:40 https://src.opensuse.org/dza/ does not exist on src.opensuse.org 2026-10-28T14:56:11 Bjørn: to me and admins it does must be non-public by default. I did make them public https://src.opensuse.org/dza/test try that 2026-10-28T14:56:32 nope 2026-10-28T14:56:55 If you're using phone it definetily won't work 2026-10-28T14:57:26 I also tried on my iPhone it won't access src.opensuse 2026-10-28T14:59:28 but in any case, if you have a active account on src.opensuse.org - did you do https://en.opensuse.org/openSUSE:Git_Packaging_Workflow#git-obs_login or https://en.opensuse.org/openSUSE:Git_Packaging_Workflow#SSH_Key_generation_and_registration 2026-10-28T15:00:11 via phone works if you go to "sub catalog" say https://src.opensuse.org/GNOME 2026-10-28T15:00:26 dza: iPhone users should use iGit 2026-10-28T15:01:15 knurpht - Gertjanits just the drop down menu that is borked on the landing page on mobile - not sure why, it works fine on sub-domaines :-) 2026-10-28T15:01:20 Bjørn: yes I did that, but it didn't get scmsync working. did you push initial _scmsync.obsinfo to your first thing or did you start from empty repo like that? https://build.opensuse.org/projects/home:iznogood/packages/gnome-backgrounds/meta 2026-10-28T15:01:51 its close to a year ago since I set it ut, so I do not remember 2026-10-28T15:02:28 but what I do know, at the start, it was the easier for me to do osc fork GNOME/foo 2026-10-28T15:02:53 that automagically sets up the "repo" as both osc/git 2026-10-28T15:03:06 thats basically what I want to know :) for future ref, cuz the double-workflow is what I tried to avoid, integrating with git's cool AF bash-completion extension like `git-obs` is the way.. it works like `git obs` btw thats a feature of git and its bash-completion :) 2026-10-28T15:03:39 or rather, it sets it up and correctly links the osc-scm link (you can manually change it via osc meta pkg -e home:user/foo-package 2026-10-28T15:04:06 yes I know, I just wanted the scmsync "initial" setup way via git :) to know what to store in my notes 2026-10-28T15:06:12 there are several ways to do it - osc fork is one, git-obs repo fork -> git-obs clone fork -> osc meta pkg -e home:xy/foo , 1 one is one step, the second is 3 steps, and there are probably more ways to do it 2026-10-28T15:07:25 TL:dr, when I just want to make a quick edit of something, and not bother having a "build on the obs" I use git-obs fork, else I do osc fork 2026-10-28T15:09:45 my question here just boils down to whether can be authenticated to src.opensuse for a regular public user, as it seems not, but then I saw your package.. 2026-10-28T15:12:48 osc meta pkg -e home:dza/gnome-backgrounds -> input whatever inside scmsync - example https://src.opensuse.org/GNOME/gnome-backgrounds.git#next or https://src.opensuse.org/GNOME/gnome-backgrounds.git#factory (the two branches gnome has). or if you have already forked the package from GNOME or from pool - > input your own git repo url 2026-10-28T15:58:11 Bjørn: git-obs repo fork pool/bash-completion --new-repo-name bash-completion-git && osc rmkpac home:dza:shells bash-completion-git --scmsync 'https://src.opensuse.org/dza/bash-completion-git.git#package-changes' --> "broken: fatal: could not read Username for 'https://src.opensuse.org': No such device or address" 2026-10-28T15:58:11 https://build.opensuse.org/package/show/home:dza:shells/bash-completion-git likewise `git ls-remote --heads https://src.opensuse.org/dza/bash-completion-git.git` remote: Unauthorized fatal: Authentication failed for 'https://src.opensuse.org/dza/bash-completion-git.git/' .. but yours`git ls-remote --heads 2026-10-28T15:58:11 https://src.opensuse.org/iznogood/gnome-backgrounds.git`. I did add token with git-obs again, all access. all I can infer is that people are allowed explicitly. otherwise this doesn't make sense to me. 2026-10-28T16:01:00 holy ... its solved.. all I had to do was set my user visibility as "public" in gitea. that wasn't obvious. 2026-10-28T16:02:04 humor me - do osc fork GNOME:Factory tali 2026-10-28T16:04:57 and what does : ssh -T gitea@src.opensuse.org -> say 2026-10-28T16:08:22 and after that we should quit, cause this is not the right room for this discussion 2026-10-28T16:21:43 Bjørn: hit me up I'm in the other rooms also have matrix user added note https://en.opensuse.org/openSUSE:Git_Packaging_Workflow#Setting_up_your_account_at_src.opensuse.org 2026-10-28T16:28:06 dza -> https://matrix.to/#/%23git-workflow:opensuse.org Those are the people you need to quiz about this 2026-10-28T19:38:01 acidsys: can you please have a look at galera1.i.o.o? Monitoring reports its down, and it doesn't respond to ping 2026-10-28T19:39:51 for additional fun, sudo fails on (at least) mailman3 and witch1 with 2026-10-28T19:39:05.089188Z ERROR Error from kanidm-unixd: KU003PamAuthFailed - Failed PAM account authentication step 2026-10-28T19:55:26 hi cboltz, same sudo problem on other machines, making it a bit interesting to "have a look" 2026-10-28T19:56:35 ok, su with root password reveals Oct 28 19:56:08 witch1 kanidm_unixd[1417]: e2b40a60-be68-4d14-bcb8-57e975cc324d ERROR ┝━ 🚨 [error]: client error | err: Http(503, None, "missing_kopid") 2026-10-28T19:58:06 ok, kanidm repaired, sudo works again. now galera 2026-10-28T20:07:57 quite frozen; login on serial console does not load password prompt before timeout. last lines sent to syslog server show oom killer being invoked by mysqld, but that was at 15:33 and shouldn't be so fatal? back after vm reset (galera is syncing itself) 2026-10-28T20:19:01 thanks for checking and fixing! 2026-10-28T20:19:54 thanks for noting; -alerts was missing from my autojoins 2026-10-28T20:21:12 mailman3 (mostly) updated, rebooting currently