 Well, I've set up a CI system before XD
 you mean the Jenkins you set up that caused its own problems?  :P
[03:01] <arraybolt3> Sooooo... you know how we wanted Qt6 apps to look just like the rest of the OS? Well guess what. There is no Breeze for Qt6 yet because Breeze is part of KDE :P
[03:02] <arraybolt3> So I actually will get to move Lubuntu off of Breeze because I'm going to have to in order to have a single Qt5 and Qt6 theme.
[03:02] <arraybolt3> Hope y'all meant it when you said I should try to make a theme :P
[03:04] <arraybolt3> Does anyone have thoughts on Kvantum as a theme engine possibly in Lubuntu? I see it's made by one of the LXQt devs (tsujan in particular). Don't know how heavy it is.
[03:06] <arraybolt3> ugh, actually Kvantum Qt6 is still experimental :(
[03:19] <arraybolt3> so, it looks like if we want uniform Qt6 and Qt5 theming, our only good option is the default Fusion theme.
[03:19] <arraybolt3> Skulpture looks old, Windows looks old, QtCurve is KDE and probably isn't Qt6 yet, Breeze isn't Qt6 yet in a form we can use, and Kvantum isn't Qt6 yet in a form we can use.
[03:21] <guiverc> arraybolt3, have you seen https://jriddell.org/2023/11/08/qqc2-breeze5-style-6-alpha/ ?
[03:21] <arraybolt3> I think that's so Qt6 distros can make Qt5 apps look right, whereas we're a Qt5 distro trying to make Qt6 apps look right.
[03:22] <guiverc> (sorry I have little detail; i see stuff like that pass on uwn; that was from issue 813 - theming sure ain't something that worries me much)
[03:32] <arraybolt3> I think we're probably better off waiting until 24.10 to try to unify Qt6 and Qt5 theming. Our best bet if we want something that doesn't look ugly is Kvantum or Breeze, and both of those won't be non-experimentally Qt6 until then.
[03:32] <guiverc> ack.  
[03:32] <arraybolt3> Unless RikMills wants to give us a Qt6/KF6 Breeze in 24.04 that we could then use :P
[03:33] <arraybolt3> (which would be an awfully tight squeeze given the Plasma 6 release schedule)
[03:46] <Eickmeyer> Studio uses Materia-KDE which uses Kvantum currently.
[03:46] <arraybolt3> Kvantum Qt6 isn't even in Ubuntu yet is it?
[03:46] <Eickmeyer> No, but that's neither here nor there.
[03:47] <arraybolt3> Well it sort of is a problem since our conundrum is how to get Qt6 and Qt5 apps to look the same in Lubuntu.
[03:47] <arraybolt3> I'm fairly certain we'd need Qt6 Kvantum to get Qt6 theming.
[03:47] <Eickmeyer> Plasma doesn't have that problem currently. Qt6 apps just seem to work with what they're given.
[03:48] <arraybolt3> hmm... really? Can you install qbittorrent and send a screenshot?
[03:48] <Eickmeyer> Well, an example I'm used to is qjackctl.
[03:49] <arraybolt3> I have Kvantum installed in my Lubuntu VM and it's not showing up as an available style in Qt6 Configuration Tool.
[03:49] <Eickmeyer> And I can't right now, unfortunately. I'm on Edubuntu doing Rpi stuff in an SSH session.
[03:49] <arraybolt3> np
[04:09] <arraybolt3> Found our hwclock issue root - hwclock is (I believe) the right command to use (no need to "port to systemd" or something), but we should *install* hwclock if we want it to be used :P
[04:10] <arraybolt3> probably just need to add util-linux-extra as a dep of Calamares.
[04:28] <arraybolt3> New Calamares uploaded with util-linux-extra as a runtime dep.
[04:30] <arraybolt3> guiverc, Leokolb: ^ when the next ISO comes out, please check the installer logs after your next install and look for "hwclock" stuff. If you can't see anything about hwclock erroring out, I did my job right.
[04:30] <arraybolt3> And with that, I think I'll consider this my EOD. o/
[15:36] <arraybolt3> any advice for what to do when an upstream doesn't GPG-sign their sources?
[15:36] <arraybolt3> Packaging redshift-qt, there's no GPG key distributed along with.
[15:49] <Eickmeyer> Not all packages need a gpg key.
[15:51] <Eickmeyer> arraybolt3: Just exclude it. It's optional.
[15:54] <arraybolt3> +1
[15:55] <arraybolt3> In that event I *think* I have a valid redshift-qt package almost (just need to make sure it builds on Debian now) :D
[15:56] <arraybolt3> also does anyone know how to lintian-override a source package lintian gripe? I never did figure it out before and still haven't figured it out.
 debian/lintian-overrides
[16:18] <arraybolt3> tried that, no worky
[16:18] <arraybolt3> it either tells me I've mismatched the override (if I do "prefer-uscan-symlink *" or "redshift-qt: prefer-uscan-symlink *", or it tells me that I have a syntax error if I do "redshift-qt source: prefer-uscan-symlink *"
[16:19] <arraybolt3> Both of these are experimental Lintian tags, so I think it would be best to just ignore them.
 It's really fidgety, I always have to brute force it
[16:20] <arraybolt3> yeah
[16:34] <arraybolt3> tsimonq2: If you get a chance, I'd appreciate if you could review this for me: https://salsa.debian.org/ArrayBolt3/redshift-qt
[16:49] <arraybolt3> (just made a fix to the control file)
[16:57] <Eickmeyer> Wait... you're trying to override experimental tags? Those don't even count. 🤦
[16:58] <Eickmeyer> Never *once* has an AA or FTP Master dinged me on those.
[16:58] <Eickmeyer> They're proposed policy but not yet policy.
[17:01] <Eickmeyer> Bottom line: don't give yourself more stress than is necessary.
[17:02] <arraybolt3> Eickmeyer: heh, well I am using Lintian with -EvIL +pedantic after all :)
[17:03] <Eickmeyer> arraybolt3: Yes, but if you see experimental warnings, just ignore them. They're not even necessary. They're more informative that you *might* have to change something down the line. That's the only reason why you need to check that when running Lintian.
[17:04] <arraybolt3> ah, good to know
[17:04] <Eickmeyer> Not sure even tsimonq2 knows that.
[17:04] <arraybolt3> lol
[17:04] <arraybolt3> well he's my sponsor and reviewer so only his opinion matters :P
[17:04] <arraybolt3> *ducks*
[17:05] <Eickmeyer> From my flying days: if a bad flight instructor causes a student pilot to crash, it's on the flight instructor. I think the same principle applies here.
[17:06] <Eickmeyer> By crash, I mean mental health.
[17:08] <arraybolt3> fair enough, though I don't think it's going to cost me any mental health to deal with those.
[17:08] <arraybolt3> But I couldn't figure out how to anyway, so I just left them since that's what I've always done when Lintian couldn't be overridden, and it seems to work.
[17:09] <arraybolt3> (as in, no one's ever yelled at me yet)
[17:10] <arraybolt3> I do find it curious why Lintian would suggest that I use a local-only option instead of a filenamemangle in my watch file though... doesn't that make it so only some machines can download a package? I just ignored it and left the filename mangle since I had to turn a file that was named, I kid you not, "v0.6" (it's a .tar.gz but has no filename
[17:10] <arraybolt3> extension or identifying name) into a file named "redshift-qt-0.6.tar.gz".
[17:10] <arraybolt3> Thanks GitHub for providing a tarball with one of the single most non-descriptive names I've ever seen.
[17:11] <arraybolt3> could be worse I guess, it could have named it "0" XD
[17:11] <Eickmeyer> Watch files are my weak spot. I usually rely on a script and if it doesn't work, README.debian it.
[17:12] <arraybolt3> they're mine too, but we use them everywhere in Lubuntu so I learned to live with them. regex101 helps sometimes.
[17:12] <arraybolt3> Also I learned that macros don't always do what they appear to do and that replacing a macro with what it expands to sometimes helps.
[17:12] <arraybolt3> (had to do that to package... something... don't remember now)
[17:13] <arraybolt3> ah, right, updating the watch file for Calamares
[17:13] <Eickmeyer> I've had watchfiles that, no matter what, don't work. Hence the README.debian.
[17:13] <arraybolt3> +1
[17:16] <arraybolt3> In Fedora they don't even bother with watch files. You just paste a download URL into the spec file, or make a script that downloads the sources, and call it good enough. Perhaps it's just because of how much maintenance work I've done on watch files, but I think I prefer it their way :P
[17:16] <arraybolt3> sounds like you have a way to do the same sort of thing for a Debian package sorta
[17:16] <arraybolt3> I'm pretty sure you used to (possibly still do) work with Fedora Jam, so you know this already, I'm just griping about Debian :P
[17:17] <Eickmeyer> I don't do anything with Fedora Jam anymore, had to give that up when I worked with Kubuntu Focus.
[17:17] <Eickmeyer> Didn't have the time.
[17:17] <Eickmeyer> What I'm talking about is https://github.com/pombredanne/debian-package-init/blob/master/deb_create_watch.py
[17:17] <Eickmeyer> It'll save your life, except that's the old version.
[17:18] <Eickmeyer> Here we go: https://salsa.debian.org/debian/debian-package-init/-/blob/master/deb_create_watch.py
[17:22] <arraybolt3> oh that's cool
 Roasting coming shortly. :P
 > `export DH_VERBOSE=1`
 Is there a reason to not comment that out?
 Also, aren't you accomplishing in `override_dh_auto_install` what a debian/install file would do?
 Looks like you used a tab, not a space, for your own name in the changelog
 I would also suggest that using @ubuntu.com or @lubuntu.me would help
 Today's ISO failed see bug https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2044006
[17:27] -ubottu:#lubuntu-devel- Launchpad bug 2044006 in calamares (Ubuntu) "Installation failed - external command finished with errors" [Undecided, New]
 Make sure to assign the ITP bug to yourself as well, arraybolt3. I'll run it through my usual automated tests and actually try building the package.
[17:30] <arraybolt3> tsimonq2: Not sure about DH_VERBOSE, I *think* having it there may have helped me debug an issue.
[17:30] <arraybolt3> The override is *not* doing what a debian/install file would do, there's a subtle difference which I'll explain in a bit.
[17:31] <arraybolt3> Quite possible that Vim did something weird with my name in the changelog, will check and fix.
[17:31] <arraybolt3> And I'll try to assign the ITP bug to myself.
[17:31] <arraybolt3> The override in debian/rules is actually doing the whole entire whopping job of installation. redshift-qt's build system doesn't actually have a `make install` command :P
[17:32] <arraybolt3> I tried using an install file to install the build artifact redshift-qt's `make -j8` generates, and it failed miserably since it's designed to say where "installed" but not really installed files are supposed to go, whereas I was dealing with a freshly built, but entirely uninstalled file.
[17:33] <arraybolt3> (if I'm understanding install files correctly that is... perhaps I'm not)
[17:33] <arraybolt3> actually... hmm... you might be right now that I think about it
[17:33] <Eickmeyer> Is it even compiling anything?
[17:33] <arraybolt3> yep
[17:33] <arraybolt3> it compiles just fine into an executable, it just doesn't install it.
[17:33] <Eickmeyer> Ok, so then would a debian/install file just take care of that?
[17:33] <arraybolt3> It's probably technically a bug in redshift-qt, but I didn't want to patch the build system if I didn't absolutely have to.
[17:34] <arraybolt3> Eickmeyer: I thought an install file worked differently, but I'm remembering something that makes me think that an install file probably would work.
[17:34] <Eickmeyer> That's the entire purpose of an install file.
[17:34] <arraybolt3> I forgot that it doesn't only grab things out of debian/tmp.
[17:35] <arraybolt3> I'm used to install files looking like "/usr/share/whatever" whereas just "redshift-qt /usr/bin/" should work.
[17:35] <Eickmeyer> Exactly.
 Bingo.
[17:35] <arraybolt3> tsimonq2: Thanks for catching that!
 Of course ;)
 The only exception would be is if it needs different permissions, but you'd either do that via a patch, or override like you've done, actually running dh_install as part of that, then chmod
[17:36] <arraybolt3> yeah that looks right
 Anyway, if you look at the output of DH_VERBOSE, it literally shows a cp command I think ;P
[17:37] <arraybolt3> tsimonq2: you meant that it looked like I used a tab rather than a space for my name in the *copyright* file right?
 Yeah
[17:37] <arraybolt3> That was on purpose.
[17:37] <arraybolt3> Aligning it with the name "Valerii Malov" above.
[17:37] <arraybolt3> It's five spaces.
 Hmmmmmmm
 *shrug* it works just looks weird imo :)
 Not a Volcker
[17:38] <arraybolt3> I generally try to do that everywhere so that BIG copyright files are all aligned, I guess it's not strictly necessary here but I preferred to be consistent.
 *blocker
[17:38] <arraybolt3> I can fix it if it's helpful :P
 Jeez Talk to Texan
[17:38] <arraybolt3> *Texans
[17:38] <arraybolt3> :P
 *shrug* up to you
 XD
[17:39] <Eickmeyer> Vocking talking to Texans. like amypenguin.
[17:39] <arraybolt3> can someone send me an email to my ubuntu.com address just to make sure it works?
[17:39] <Eickmeyer> (amypenguin grew up in Texas)
[17:41] <arraybolt3> tsimonq2: All issues fixed, except I still need to assign the bug.
[17:42] <Eickmeyer> arraybolt3: Email sent
[17:45] <arraybolt3> tsimonq2 seems to have sent one too, and it works :D
[17:45] <arraybolt3> now I need to set up TB to be able to send from it again
 arraybolt3: I'll look to sponsor this to Debian in the early afternoon. Meanwhile, consider whether you'd like to ask me to also upload this to Ubuntu (and file the appropriate LP bug if so)
 Debian NEW is slow. You *can* poke in #debian-ftp on OFTC, but unless you have a good reason, try not to abuse that
 An example of when it would be okay to ping there is NEW reviews during an approved transition
[17:47] <arraybolt3> tsimonq2: I figured it would just "float" into Ubuntu as part of autosync, no?
[17:47] <Eickmeyer> No reason not to upload to Ubuntu and when Debian gets around to it, sync it.
[17:47] <arraybolt3> If you'd like to upload to Ubuntu right away that's fine too though :)
[17:47] <arraybolt3> probably will earn me a future MOTU point
[17:47] <Eickmeyer> ^ +1
 It *definitely* earns you a future MOTU point.
[17:48] <Eickmeyer> Honestly, the DMB likes to see uploads directly to Ubuntu.
 Also, speaking of that, block out a day or two and just throw me Many merges and uploads if you can, let's get this MOTU stuff done ;)
[17:48] <arraybolt3> sounds like a plan :)
[17:49] <arraybolt3> I'm trying to keep contributing to Lubuntu and not just pursue my own "rising through the ranks", but as it seems like something y'all would like me to do, I should go ahead and get it done :P
[17:50] <Eickmeyer> Trust me when I say this: living on an island gets you nowhere.
 It would really help with stuff like this, too. When you become a MOTU, really besides your normal uploads, you could also pick a few uploads off the sponsorship queue every once in a while.
 I try to do a few a day if I have time
[18:05] <arraybolt3> https://bugs.launchpad.net/ubuntu/+bug/2044008
[18:05] -ubottu:#lubuntu-devel- Launchpad bug 2044008 in Ubuntu "[needs-packaging] redshift-qt" [Wishlist, In Progress]
[18:06] <arraybolt3> uh... I am sort of signing up "Lubuntu Developers" as the maintainer here... that might be a bit assumptive of me?
[18:07] <arraybolt3> I mean I believe that we're hoping to add this to Lubuntu if it works right, in which case it will be our package, but right now it's just "a package".
[18:07] <arraybolt3> If I need to change that I'm happy to.
[18:31] <teward> arraybolt3: just wait for Debian.  Then we sync right from Debian directly.
[18:32] <teward> typical Universe packages have Ubuntu Developers or similar as maintainer but that does nothing in Ubuntu :P
[18:32] <teward> so i would say let the Debian process run
[18:33] <teward> then just ask for a sync from any coredev
[18:33] <teward> once its accepted in Debian and added to unstable
[18:33] <arraybolt3> tsimonq2: ^
[18:33] <arraybolt3> now look what you've done, the orbital striker has me targeted
[18:34] <teward> Simon should know this anyways.  *smacks Simon*
[18:42] <Eickmeyer> teward: It'll just autosync and show up as a new binary for the AAs. No coredev involvement needed. :P
[18:43] <teward> Eickmeyer: i'm assuming that it'll take a while for Debian to look at it
[18:43] <teward> since Simon hasnt even uploaded it yet to Debian
[18:43] <teward> which is a Bad Sign :P
[18:43] <teward> so when autosync shuts off... :P
[18:44] <Eickmeyer> teward: Well, yes, and we were also assuming it'd take less time for an Ubuntu AA to look at it since the Debian FTP Masters queue is currently longer than ... *points to extremely long road*
[18:44] <teward> that said YOU are being blamed on this too Eickmeyer 
[18:44] <Eickmeyer>  ¯\_(ツ)_/¯
[18:44] <teward> arraybolt3 just threw you under the bus
[18:45]  * arraybolt3 eats bus
[18:45] <Eickmeyer> I just explained my rationale. 
[18:45] <Eickmeyer> My rationale is sound.
[18:52] <arraybolt3> I figured it would be an easy bus to divert for one side or the other
[18:53] <arraybolt3> I agree with Eickmeyer and tsimonq2 (as you can see in the backlog - I was going to do it the way teward's recommending now but then changed my mind), I was just pointing back to where I got my info.
[18:54] <Eickmeyer> Bus didn't even hit me. If anything I drove the bus.
[18:54] <arraybolt3> (random aside - I really dislike Matrix threads. They hide bits of the conversation, they're used rarely, they make it hard to "read" all the messages in a room to get the annoying blip out of your way, etc. Thankfully you can right-click on a room and click "Mark as read" to take care of them quickly, but it's still two clicks rather than the
[18:54] <arraybolt3> original one.)