<beerman>
will you need more time to setup/test the git hooks with gitea? exchanging that should be as easy as to stop mirroring the gitweb content and push to that directly
<beerman>
just discovered one thing still missing from nginx: lists.crux.nu
SiFuh has quit [Remote host closed the connection]
SiFuh has joined #crux-devel
braewoods has quit [Remote host closed the connection]
braewoods has joined #crux-devel
<beerman>
should be working later, just skimmed through the existing config and that should be no problem
<beerman>
jaeger do you have any plans for the updates/changes yet?
<jaeger>
No specific plans as far as timing... but I plan to reach out to stx this week and reboot for the kernel update first... then if the kernel update causes no problems, update at least core packages from the latest ISO. Then rebuild/update the rest
<beerman>
alright, sounds good
<beerman>
checking for mailman also showed that we don't have a mailman port anymore
<jaeger>
Hrmm... there was one sometime in the past, I don't remember how long ago
emmett1_ has joined #crux-devel
<emmett1_>
hello
<beerman>
shouldn't be tough to recreate it but it might make sense to check if anything else should be revived
<beerman>
emmett1_ hello
<emmett1_>
hey, beerman
<beerman>
anyway, would suck to have to do it when you need it asap
<emmett1_>
tint2 crash randomly caused by latest glib
<emmett1_>
should i report to crux's bugtracker or the maintainer?
<beerman>
you can tag farkuhar and if he is here i am sure he will include it. the alternative would be to search for a replacement thats under more active development
<emmett1_>
i dont think i could find alternative, i've been used it since forever
<emmett1_>
i can just patch it on my local repo
<emmett1_>
just report in case happen to other people in the future
<emmett1_>
just make crux a better place
<beerman>
i am sure you can if you allow yourself to let go of old habbits
<emmett1_>
farkuhar, just tag you about this issue if you can look into it
emmett1_ has quit [Ping timeout: 244 seconds]
<farkuhar>
emmett1_: thanks for reporting. I'll test the patch and push it to the repo later today.
<beerman>
who even writes these nginx configuration articles?
<beerman>
"Mailman is crazy. This page used to focus on giving you options to install, configure, and run it as you wish. Because of the crazy that is mailman, this will show you the most common and best supported way to set up Mailman software behind NGINX."
<beerman>
why is it crazy? what has the author seen?
<beerman>
well, providing a good mailman config might not be as easy as thought... archwiki says: "Nginx must run with user http and group http or Mailman will complain."
<farkuhar>
last time I administered an instance of Mailman, the fashionable alternative to Apache was lighttpd. Nginx Inc. had not even been founded yet. That's how out of date my knowledge of Mailman and web servers is.
<beerman>
no worries, I am looking at how to get this going in the cleanest and maintainable way.
<beerman>
there is this fcgi wrapper script which looks sketchy but i used somewhere else in the past where i didn't care as much and it just worked. thttpd seems very unmaintained..
<beerman>
mailman probably can't be tested without recompiling it to accept the other group or to change the nginx user to run the server
<jaeger>
It won't hurt us to wait a bit :)
<beerman>
yeah i guess so too
<jaeger>
Looks easy enough to change mailman, I see the --with-mail-gid and --with-cgi-*id options
<beerman>
we should look into updating it anyway... though i doubt it will change anything about the cgi requirement
<beerman>
i am feeling good about the nginx and gitea config though, that should be fine
<jaeger>
Good
<jaeger>
I will take another look at the git hooks soon... currently only enabled for contrib and running in a tmux session for testing, I'll see about converting them to a service
<beerman>
heh, yeah :) i'd need to create another service for fcgiwrapper as well
<beerman>
i could go ahead and create a fitting nftables config though