[01:21] <tsimonq2> arraybolt3: See your Matrix PMs :P
 @tsimonq2 i'm looking at a Sentry integrated CI that integrates with git too.  Sentry to track and autocreate issues on code runs.  just something as an fyi
 because its so nice to help correlate and combine the same errors and cases
 even across arches
 just an fyi
[01:24] <tsimonq2> k what is this ~ "Sentry" ~ and is it FOSS :P
 also i have phab in sandbox
 not open to net yet but SOON
 https://sentry.io/welcome/ - they are open source.  not necessarily pure FOSS but their free on prem version is fully functional and in fact is how i know what our discourse users use for crap webapp plugins that try to alter site content lol
[01:28] <tsimonq2> cool let's get er rolling
[01:28] <tsimonq2> config file format?
[01:28] <tsimonq2> (at your convenience, again)
 for...? (re @lubuntu_bot: (irc) <tsimonq2> config file format?)
 Sentry is its own beast.  CI is harder but i have some that should work with gitea
 Sentry integrates in the CI.
[01:30] <tsimonq2> for configuring the CI?
[01:31] <tsimonq2> Jenkins had individual XML files for each job
 ah i'll get that when i'm closer to deployment
[01:31] <tsimonq2> Nothing had to actually be put in the repo :P
[01:31] <tsimonq2> anyway
 @tsimonq2 well Jenkins is also EOL and has security risks
 we can set up default CI for our gitea at the ci web interface
 but overrides in the repo
[01:31] <tsimonq2> *shrug* worst case scenario we say $#@* it and write our own really bad one :P or *shudder* use LP
 which debhelper can clean out anyways
 no not LP
[01:32] <tsimonq2> I agree lol
 i have a template for automated CI for packaging on Gitlab from Salsa's CI I can adapt to alternatives
 but CI fully functional i dont see being at 100% until mid or end of January
 since we enter the holiday chaos fests now
 phab on limited access probably eod tomorrow.  phorge for tasks and wiki only, probably end of next week (thanksgiving)
 Welcome :) (re @Pitus: )
[07:24] <tsimonq2> Lots of general Ubuntu project work today. Good stuff.
[07:24]  * tsimonq2 EODs o/
[07:42] <guiverc> calamares (third party packages) as appears on box is larger than window allows; it sort of lets me scroll (a few pixels, thus feeling like it should allow scrolling) but won't let me scroll really (just bounces down so I can see a tad more, then on dropping mouse it springs to what I saw before)... it requires me to resize [calamares] window to see everything, doesn't feel ideal (but usable on current box)
 Yeah, that's been on my mind recently. It's on the list :)
 Thanks for bringing it up guiverc, btw, are you able to confirm Leó's earlier bug? I haven't gotten the chance to look at it yet
[07:51] <guiverc> i can't recall what the bug was, but I recall being asked to look at install log (install in progress currently)... 
 https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2044006
[07:52] -ubottu:#lubuntu-devel- Launchpad bug 2044006 in calamares (Ubuntu) "Installation failed - external command finished with errors" [Undecided, Confirmed]
[07:52]  * guiverc was to look for something in log; won't be found if 'job done right'... but I didn't plan on reading to what I need to look for until I've something to search...
 Regardless, just wanted to bring it to your attention :) thanks
 /me goes to bed
[07:54] <guiverc> sorry, didn't plan to read ^messages, so as to know what to look for. my wording is confused sorry
[07:54] <guiverc> thanks tsimonq2 
[07:54] <guiverc> & night; sleep well
[09:06] <guiverc> arraybolt3, did an install test; failure for what maybe a different reason, but https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2044084 may contain the log you wanted to me to search (re: hwclock)... not sure if it's the 'next' ISO, but what I just tested anyway...
[09:06] -ubottu:#lubuntu-devel- Launchpad bug 2044084 in calamares (Ubuntu) "lubuntu noble install; external command failed to finish (3rd party package krita)" [Undecided, New]
[15:44] <arraybolt3> checked log, hwclock is fixed, woot
 Nice - just checked and was about to let you know!! (re @lubuntu_bot: (irc) <arraybolt3> checked log, hwclock is fixed, woot)