2020-10-29T03:18:28 *** okurz_ is now known as okurz 2020-10-29T05:50:55 cboltz: I don't have ns3 access 2020-10-29T12:55:01 klein: ping 2020-10-29T17:34:29 *** King_InuYasha is now known as Conan_Kudo 2020-10-29T17:34:41 *** Conan_Kudo is now known as King_InuYasha 2020-10-29T20:25:30 cboltz: can you create me an openSUSE:infrastructure:pagure OBS project? 2020-10-29T20:37:15 just curious what content do you envision to be hosted in a pagure instance? 2020-10-29T20:39:48 Eighth_Doctor: yes, of course - done 2020-10-29T20:39:54 thanks 2020-10-29T20:40:31 darix: well, one of the first things to go there will be a public sanitized version of the salt repo 2020-10-29T20:40:58 and we're looking at migrating openSUSE Heroes project administration there 2020-10-29T20:41:30 additionally, bmwiedemann and aplanas' obsgit stuff will start living there too 2020-10-29T20:42:01 so the gitlab instance is not working? 2020-10-29T22:57:16 cboltz: will you set up {code,pages,ev,releases}.o.o in the proxy? 2020-10-29T22:58:00 that will probably require some special firewall/proxy stuff later, but let's start with just simple website access before we get there ;) 2020-10-29T22:59:17 give me some minutes ;-) 2020-10-29T23:03:58 also an mr https://gitlab.infra.opensuse.org/infra/salt/-/merge_requests/447 2020-10-29T23:05:57 I'm not sure if I like fixed filenames in /tmp/ - that's just calling for symlink attacks 2020-10-29T23:14:59 hmm 2020-10-29T23:15:16 yeah, the problem is that sockets are broken everywhere else for some reason 2020-10-29T23:16:22 what about a directory somewhere[tm] that is only writeable for pagure (and related services), but not world-writeable? 2020-10-29T23:17:46 BTW: https://code.opensuse.org/ and the other subdomains are available 2020-10-29T23:18:29 well, I tried every other directory with the sockets, but nginx complains it can't read it even though it should be able to 2020-10-29T23:21:12 /srv/gitolite is git:git 750 which explains why nginx can't access it - not a member of the git group 2020-10-29T23:21:21 try chmod 755 2020-10-29T23:22:07 hmmm 2020-10-29T23:22:59 as a sidenote, I can see the red command prompt stopped working on root, I wonder why 2020-10-29T23:23:27 I also noticed it, but didn't have time to debug it 2020-10-29T23:24:47 just tested my usual prompt - coloring still works: PS1='$( ret=$? ; test $ret -gt 0 && echo "\[\e[41;93m\] [$ret] \[\e[0m\]" )\[\e[101m\]\u\[\e[0m\]@\h:\[\e[1;37;44m\]\w\[\e[0m\]> \[\e]0;\w - \u@\h\a\]' 2020-10-29T23:25:44 the default prompt is \h (pagure):\w # - no color codes :-( 2020-10-29T23:26:17 hm, that's annoying 2020-10-29T23:27:38 ah, I think I found it 2020-10-29T23:28:15 /etc/bash.bashrc checks for $UID -eq 0 and then if test -n "$TERM" -a -t ; then 2020-10-29T23:28:33 $TERM is xterm-256color 2020-10-29T23:28:54 so: 2020-10-29T23:28:59 # 2020-10-29T23:29:00 $TERM -a -t 2020-10-29T23:29:01 If 'xterm-256color' is not a typo you can use command-not-found to lookup the package that contains it, like this: 2020-10-29T23:29:03 cnf xterm-256color 2020-10-29T23:30:40 but cnf doesn't find it in any package :-( 2020-10-29T23:32:12 hmm 2020-10-29T23:44:53 reported as https://bugzilla.opensuse.org/show_bug.cgi?id=1178283 2020-10-29T23:57:32 in case you wonder - I use https://cboltz.de/en/linux/bashprompt/ 2020-10-29T23:57:55 (+ https://github.com/magicmonty/bash-git-prompt to make the shell even more colored when I'm in git directories)