02:03 <jaeger> poking at the webhook a bit, not hard to parse out the commit message from it, for example:

02:04 <jaeger> msg: [contrib/3.6]: libaom: 3.4.0 -> 3.5.0

02:04 <jaeger> I took the ".git" out of the repo name this time, seemed superfluous

06:25 <beerman> sounds good

13:24 <beerman> jue: i have integrated a markdown plugin on the nginx pmwiki instance

13:25 <beerman> it seems to work pretty good: https://crux.nu:82/Main/Test2

13:25 <beerman> you might want to register at gitea as well, in preperation for the move. The system will send you an email. after you are registered I can promote your account to admin

14:23 <jue> beerman: done

14:26 <jue> anything we should add to our release notes?

14:26 <beerman> jue: great, will add you as soon as I’m home,

14:31 <beerman> Remember our Mail correspondence in April or something? A lot is in there

14:32 <beerman> And of course from our todo list. Maybe highlighting changed defaults would make sense

15:14 <jaeger> It'll take me a little bit of work this week to get the webhooks for gitea working, it's a little more complicated now... but should be able to make it work. Already know what I need for the cruxbot and email notifications, just have to work out how I'm going to do the repo regeneration one

15:15 <jaeger> But I guess there's no requirement to switch to gitea and do the release at the same time

15:15 <beerman> Of course not

15:18 <jue> I've started to update some of our web pages, ChangeLog is up-to-date already

15:18 <jaeger> OK. With the ChangeLog updated I can go ahead and build the final ISO

15:20 <jue> relase notes are ready as well

15:21 <jaeger> ok, pulled latest handbook and release notes

15:22 <jaeger> I'll get the ISO built and a torrent file created

15:22 <jaeger> Looks like the torrent tracker is a bit messed up, will look at that as well

15:31 <beerman> jue: you are updated to admin on gitea

15:31 <beerman> anything else i can help with today?

15:31 <jaeger> ok, tracker is fixed... I think I will remove all torrents from it older than 3.6, unless you guys see value in keeping those around

15:32 <jue> yep, go for it

15:32 <beerman> i always stopped sharing the previous iso as soon as a new release is out

15:33 <jaeger> I usually keep the current and previous versions seeding

15:33 <jaeger> The tracker goes all the way back to 2.7.1, though, which isn't really all that useful now

15:33 <beerman> its just that the previous version goes out of fashion very quickly. I know I am so done with rebasing, I won't push anything into 3.6 branches any longer

15:34 <beerman> maybe i should try that one on the proliant xD

15:34 <beerman> (jk, because 3.6 actually worked just fine, still no idea)

15:39 <jue> jaeger: is the torrent at a different place?

15:42 <jaeger> I haven't made the new one yet, was about to do that... but I did move the torrent files on disk on crux.nu to match the default hefur location

15:43 <jue> ok

15:47 <jaeger> OK, the new torrent file is in place

15:48 <jaeger> also uploading the ISO and source ISO to the morpheus.net mirror, slowly

15:49 <jaeger> For clarification, there are copies of the torrents in 2 locations on crux.nu - one is served up via the web server for people to download, the other is hefur's location so it knows which torrents to allow

15:50 <jaeger> I didn't change the web location, just the hefur location

15:50 <jaeger> https://crux.nu/files/crux-3.7.torrent

15:52 <beerman> i'm jumping on it

15:55 <jaeger> Finished the mirror upload as well

16:00 <jaeger> Getting pulled into a work call, back in a bit

16:19 <jaeger> OK, back... you guys get the torrent ok?

16:19 <jue> just changed the default HEAD to 3.7 for gitweb and for the timeline

16:19 <jue> jaeger: yes, works fine

16:21 <beerman> yep, works fine for me too

16:21 <jaeger> great. I've updated the cron job that generates repology data

16:22 <jaeger> I'll update the portdb versions next

16:24 <jaeger> ok, that's done, will update on the next run

16:24 <jaeger> Hrmm, what else needs updating?

16:25 <beerman> crux.nu lol :D

16:25 <jaeger> ah, git hooks

16:25 <beerman> we might do that when we are ready to decomission apache etc

16:26 <jue> well, hope that I didn't forget to update any web page ...

16:28 <beerman> are we bothering with updating flyspray?

16:28 <beerman> it still has 3.5 in it (for reported version while opening a new ticket) and 3.6, no 3.7

16:29 <beerman> with gitea we won't need flyspray anymore

16:31 <jue> 3.7 is now available

16:31 <jaeger> non-gitea hooks are updated

16:32 <beerman> jue: i am probably not wording it correctly. when you go ahead and open a new ticket, you will be able to select a version where you hit the problem. your current choices are 3.5 and 3.6

16:32 <jue> ... I meant in flyspray ;)

16:32 <beerman> ah

16:32 <beerman> nevermind :D

16:32 <jaeger> We should probably maintain flyspray until we've fully switched over... I have no objection to ditching it after that

16:32 <jue> yeah

16:33 <beerman> sure, i am not saying we should ditch it today

16:33 <jaeger> Sure, I just mean that my answer to your "should we update it" question is yes, for now :)

16:33 <beerman> right, makes sense

16:34 <jaeger> Got another work meeting coming up, would you guys mind handling the release announcement mail and update the topic in #crux?

16:34 <jue> I'll write the announcement

16:35 <beerman> sure, i can't help with the topic though, i never got op status and also I have no clue if the matrix client supports sending irc commands like that :D

16:36 <jaeger> Looks like nobody has op in there at the moment but I think either jue or I can fix that... I'll do it when I get back if needed

16:36 <beerman> 👍️

16:37 <beerman> meanwhile, my rss log is flooded with all the 3.7 commits from the past months, sweet

16:37 <jaeger> heh

16:44 <jue> lol

16:51 <beerman> anyway, great work gents, thanks :)

16:51 <jue> mail sent, guess we did it mostly, thanks :)

16:53 <jaeger> awesome, thanks as well :)

17:19 <jaeger> topic is updated

17:24 <beerman> perfect

17:24 <pitillo> thanks for your work guys!

17:32 <beerman> :)

17:35 <jaeger> cheers :)

18:34 <crash_> nice too see a new release is out :)

18:59 <darfo> thanks for the new release!

21:28 <stenur> Very nice!

21:30 <stenur> Now i can change my pkgmk.conf to no longer use per-port directories. And likely can speed up my super-expensive port-trim.sh! You would not believe how slow crawling alongside port tree is even on a 1.5GB/sec NVME.

22:25 <darfo> not sure what you mean. i've had my pkg files in one dir and source files in another dir since CRUX 3.1 or so with http://ix.io/4bxj in /etc/pkgmk.conf

22:27 <darfo> the PKGMK_WORK_DIR is so if I us -kw the build files are all in one place for easy clean up.

23:42 <farkuhar> i'm not sure what stenur means either, but i wonder if he's celebrating no longer having to maintain a separate port tree for his contributions to CRUX 3.6? (similar to how beerman is "so done with rebasing, won't push anything into 3.6 branches any longer")

23:44 <stenur> busy sorry! and sooo later!

23:44 <stenur> i still have these things

23:44 <stenur> PKGMK_SOURCE_DIR="`d=/x/balls/\"\`basename ${PWD}\`\"; if [ -n "${DOMKDIR}" ]; then [ -d \"${d}\" ] || mkdir -p -m 2770 \"${d}\"; fi; echo \"${d}\"`"

23:44 <stenur> and such

23:44 <stenur> farkuhar: oh yes!

23:57 <fishe> @Romster: it seems you're the maintainer of `scrot` in the contrib repo? 1.6 no longer builds, on my system changing version to 1.7 and adding `libbsd` to dependencies allowed 1.7 to build