<beerman>
Sounds good. What is left to prepare for us to make the switch happen?
<jaeger>
Do we have some way to migrate tickets over?
<beerman>
no
<beerman>
its either by hand
<beerman>
or not at all
chrcav_ has quit [Quit: Lost terminal]
<jaeger>
Maybe a script to pull from mysql and create tickets with that info
<beerman>
maybe, but before I would've finnished that I would be done importing them by hand
<beerman>
also with gitea we can create tickets in their corresponding repository, e.g. pkgutils
<beerman>
so "more logic than just copy paste" is needed, imo
<SiFuh>
php
<beerman>
next grafana update doesn't build the frontend anymore due to what seems to be an openssl 3 incompatibility.. i'll need to import nodejs lts which will itself depend on the old ssl stack.. luckily I already had that in my overlay, and changes to make use of the new /usr/opt were easy to adopt it seems
<jaeger>
Hopefully I'll have time to finish the gitea hook API in the next couple days. The signature check wasn't hard to figure out but still need to add logging to the notification hook and write the repo gen hook
<farkuhar>
In order for a migration of tickets from FS to Gitea to be quicker by hand than with a script, I suppose we're not considering to migrate all the closed tickets. Some of those closed tickets retain institutional memory of how our tools have evolved, so we risk making that history harder to reconstruct, if we don't go through all the old tickets to decide what's worth keeping.
<farkuhar>
someone who's been with CRUX for as long as SiFuh might be able to reconstruct the history from the git log alone, but the FS discussions add more context for users who started on CRUX at a later date. Lose the old FS tickets, and newer CRUX users will have only the mailing list archives to learn about their distro's evolution.
<SiFuh>
Why do we need the old database?
<SiFuh>
Scrap and start afresh
<SiFuh>
Gitea supports MYSQL does it not? Then maybe leave the old crap in MYSQL and use gitea to access it separately from the new tickets?
<SiFuh>
Just my thoughts
<beerman>
would be easier to keep a static copy around..
<jaeger>
Personally I would like to see ticket history preserved. I'll do some research on how to accomplish that
<SiFuh>
jaeger: php has some ways to do that
<jaeger>
I'm not a fan of php, but any language that supports mysql and HTTP requests should be able to do it
<SiFuh>
Would it not be easier to preserve rather than transfer?
<jaeger>
Of course it would be easier, but it would be nice to have everything in one place if we can do it without an enormous amount of trouble
<SiFuh>
Alright
<SiFuh>
jaeger: Would it be possible to
<jaeger>
It doesn't need to be a blocker to switching, just something I'm going to look into
<SiFuh>
provide an mysql dump that others could consider looking into?
<beerman>
sure, having it all in one place would be neater
<jaeger>
possibly, though I need to look at it first to see if there's anything sensitve in there
<SiFuh>
jaeger: Of course, don't want to offend some people ;-)
<SiFuh>
I will be available probably 12 days from.
ivandi has quit [Quit: WeeChat 3.6]
stenur has quit [Remote host closed the connection]