[02:12] <wxl> TJ-: does /etc/os-release never change????
 @wxl [<wxl> @The_LoudSpeaker working on that but the GoToDesktop keys are still in ope …], Yup! I sent you wrong file. 😝 Will send the correct one in a few hours.
 I went and cleaned up Discourse support topics a bit.
 All topics autoclose after 30 days of inactivity to prevent spam.
 (in the Support category)
[05:02] <wxl> so let them!
 Let them autoclose or let people spam?
[05:03] <wxl> the former
 That's because I went and set the option ;)
 They didn't beforew
 They do now
[05:04] <wxl> i thought they did
[05:04] <wxl> we need the solved plugin
 Oh?
[05:07] <wxl> there's a task for that
 Where? XD
[05:08] <wxl> in infrastructure
[05:10] <wxl> @tsimonq2: so here's today's dumb question of the week: what are the equivalent of git branches in bzr?
 They don't have an equivalent as far as I know.
 Bazaar predates Git; to the best of my knowledge, "branches" were meant to be fully remote on Launchpad
[05:11] <wxl> so if i'm trying to do an SRU on on usb-creator all the way back to xenial, how do i do that?
 Where do you want to start?
[05:14] <wxl> the SRU template isn't a problem
[05:14] <wxl> doing it eoan isn't a problem
[05:14] <wxl> but now what about previous to that?
 The tl;dr: …  1. `for i in EVERY_RELEASE; do pull-lp-source usb-creator $i; done` …  2. Fix what needs to be fixed. …  3. Bump the changelog.
 Voila.
[05:17] <wxl> kthx
 np
 I need to sponsor though
 Maybe ask cyphermox why you can't upload if it's in our seed :)
[05:18] <wxl> k i'm going to bed
 You're not allowed XD
 (night, I'm doing the same)
 Wait ploxxx
 What's up?
 This is, after all, async communication.
 Put stuff here and we'll get back to you :)
 @kc2bez [It seems like we get many build failures for 18.04 on the devel list. Are we sub …], Because Falkon master has changes that need Qt >= 5.10 now I think
 @wxl [<wxl> @acheronuk how's falkon doing these days? i'd like to re-evaluate the idea …], Need a qtwebengine rebuild to start with in Eoan … Generally though, no idea. I don't use it
 Wxl: The thing is, that day I had actually copied the global config of openbox. Made changes to it and then pasted it to .config/openbox/lxqt-rc.xml. … Then made required changes to lxqt config using gui (the shortcut keys from menu) … But this led to changing of overall openbox theme. So when I had to send you the files, I ma
 @wxl [<wxl> @acheronuk how's falkon doing these days? i'd like to re-evaluate the idea …], You guys considered waterfox? It's also very good. I use it when I don't want to mix browsing history of two different topics I am working on.
 @The_LoudSpeaker [You guys considered waterfox? It's also very good. I use it when I don't want to …], I'm not a fan of Waterfox myself
 @tsimonq2 [I'm not a fan of Waterfox myself], Any particular reason?
 It's been in good development recently.
 Not enough people using it, not up-to-date at the same quality as Firefox in Ubuntu
 I'd rather not take on responsibility for a web browser
 That's worse than an installer 😂
 XD
 @tsimonq2 [Not enough people using it, not up-to-date at the same quality as Firefox in Ubu …], Yeah it's a bit late than Firefox for updates.
 The huge benefit of Firefox is that its always up to date and security maintained by Canonical. That outweighs most small issues with it IMO
 I will not be happy with a move to the Firefox snap, whenever Canonical decides to pounce on thst
 *that
 @tsimonq2 [I will not be happy with a move to the Firefox snap, whenever Canonical decides …], Shhhhhhhhhhhhhhhhhhhhhhhhhhhhh 🤐
 It's a regression in user functionality with the current state of the Firefox snap
 Don't speak of such horrors!
 hahahaha
 @The_LoudSpeaker [Wxl: The thing is, that day I had actually copied the global config of openbox. …], I use falkon but not on eoan yet
 I have not heard of waterfox
 @lynorian [I have not heard of waterfox], Give it a try.
 not a deb in repos?
 No. You will have to download it from its website.
 @lynorian [not a deb in repos?], @lynorian  … https://www.waterfox.net/releases/
 I am a falkon user
 Our timezones are soo unsynchronized. I am having breakfast and wxl is sleeping. XD
 @The_LoudSpeaker [Our timezones are soo unsynchronized. I am having breakfast and wxl is sleeping. …], wlecome to the internet
 dang it I realized I missed a change in 19.04 for fresh installs like the fake tiling no longer is installed I think to make super key open the menu right
 Anyone up? Can someone tell me if the user level config files for lxqt and openbox are generated from their global versions at /etc/xdg/openbox/ ?
 On creation, yes. It is part of default settings. https://phab.lubuntu.me/source/lubuntu-default-settings/browse/ubuntu%252Feoan/src/etc/xdg/xdg-Lubuntu/openbox/
 @The_LoudSpeaker [Anyone up? Can someone tell me if the user level config files for lxqt and openb …], Yes
 There is also a lubuntu-xdg
 In the same direvtory
 In phab the repo is called default settings
 Yup! Then I just added a comment to T59. Someone test it please.
 ref: https://phab.lubuntu.me/T59/#1266
 @The_LoudSpeaker [Yup! Then I just added a comment to T59. Someone test it please.], chris ?
 wxl: our nm-tray repo doesn't have changelog
 @tsimonq2 lugito container has the Lubuntu Infrastructure internal CA cert added to ca-certificates, see if that fixes the Lugito SSL issues
 if not then it probably rolls its own cert store
 wxl wrt Discord backups, that's a lot harder because Docker.  I'll have to look into the 'proper solutions' for that.  Also need to figure out why live cloning of LXD containers doesn't want to work with our infra but that's its own evil
 @HMollerCl [wxl: our nm-tray repo doesn't have changelog], found it, I already uploaded the patch https://phab.lubuntu.me/D16
 I followed the changelog numeration that existed though.
 @wxl @tsimonq2 if you would prefer, though, I can grab the Discourse data and try and transfer them to the Docker host I have here which replicates to a backup storage nightly via Veeam (for the VM that runs my Docker 'system')
 that'd move it to my location though in the process 😐
 @wxl @tsimonq2 alternatively, I can work on nesting Docker inside an LXD container.  Which is actually easier in latest LXD :|P
 then it's a straight LXD snapshot and copy
 @The_LoudSpeaker [ref: https://phab.lubuntu.me/T59/#1266], Hey! @teward001 if you are free and don't mind, can you test this?
 in the middle of patching Anki for reasons.
 give me a bit
 @The_LoudSpeaker 404 Not Found, i might not have access to see it
 @teward001 [in the middle of patching Anki for reasons.], What'd you break? *shot*
 @tsimonq2 me?  Nothing.  PyQt broke Anki :)
 see #ubuntu-bugs from a few days ago on IRC :P
 *hands teward the maintainer hat for all of PyQt*
 OOPSIES
 no but unrelated I can't see T59 that @The_LoudSpeaker is referring to
 is it restricted-view?
 https://phab.lubuntu.me/T59#1266
[17:11] <teward> huh interesting
 @The_LoudSpeaker [Hey! @teward001 if you are free and don't mind, can you test this?], I don't have an Eoan Lubuntu to test on yet
 i can get that later once i'm at home where my mirrors are
 @teward001 [I don't have an Eoan Lubuntu to test on yet], Test in on 19.04. i also don't an eoan set up yet.
 @teward001 [i can get that later once i'm at home where my mirrors are], Yeah. Do it at your convenience.
 @teward001 [no but unrelated I can't see T59 that @The_LoudSpeaker is referring to], How's that happening? It's not restricted. Afaik.
 @The_LoudSpeaker [How's that happening? It's not restricted. Afaik.], because you had an extra / in the link
 the one that @aptghetto reposted got me there
 *cracks open a CocaCola and chugs to regain energy*
 @teward001 [because you had an extra / in the link], 😂😂😂
[19:56] <tsimonq2> The CI is fixed.
[19:56] <tsimonq2> teward broke SSL certs. :P
 correction: Lets Encrypt broke itself
[19:56] <tsimonq2> I then had to deal with plugin updating.
 but yes CI is working now
[19:57] <tsimonq2> You're getting blamed anyway *shot*
 i just had to make CI use the internal cert that phab, etc. are already using :)
 The builders are about to get nuked :P
 which means y'all can blame Simon for your PPAs taking an eternity to build.
 Back to nuking the infra every 12 hours :P
 Perhaps I should make that a daily instead of a semi-daily
 lol
 @tsimonq2 i'm sure everyone would appreciate daily instead of every 12 hours
 i know of nobody except you with 12-hour build cycles :P
 @teward001 [@tsimonq2 i'm sure everyone would appreciate daily instead of every 12 hours], Probably
 :P
[20:09] <tsimonq2> After this daily is done, I'm going to stop i386 builds for the CI. Apparently we still do those.
 yes.  kill i386.  burn i386.
[20:10] <tsimonq2> That will involve one of two ways to not make Britney freak out:
 i386 must die.  BURN IT!  *shot*
[20:10] <tsimonq2> 1) Remove all i386 binaries in "the release pocket"
[20:10] <tsimonq2> 2) Move everything from the release pocket to -proposed and then do a Britney run
[20:10] <tsimonq2> 2) is easier but requires more resources :P
[20:10] <tsimonq2> 1) is doable
[20:10] <tsimonq2> but meh
[20:12] <tsimonq2> I might do a combination of the two. Stop the Britney run for now, and once all the builds have settled down from this master job, nuke most of the stuff in the release pocket. Then do a Britney run to have all of the stuff be replenished.
[20:12] <tsimonq2> Yeah, that works.
[20:16] <tsimonq2> Britney job temporarily disabled.
 Hey! wxl: did you check T59? If it's okay then let's pack it asap. I am cloning lubuntu-default-settings now.
 Should I clone eoan branch or disco branch?
 Eoan.
 Okay.
 @tsimonq2 can you check T59? Check the last 2 comments please.
 When I can, sure.
[21:01] <tsimonq2> Alright, so I made Britney stop caring about i386.
[21:01] <tsimonq2> Both proposed PPAs have i386 builds disabled.
[21:01] <tsimonq2> I'm going to kick off one more master job before I go to class, which should build non-i386 packages and allow Britney to replace them on the next run.
[22:20] <wxl> everyone go test https://phab.lubuntu.me/D17
[22:20] <wxl> guiverc: ^
 @wxl [<wxl> everyone go test https://phab.lubuntu.me/D17], Wait. It's useless unless tye other file is in place.
[22:23] <guiverc> ack, had hoped to test t59 yesterday but was unable, will do probably thus arvo; is it the same as t59?
 How do I go about patching the patch from rlxqt-globalsettings? wxl:
 @guiverc [<guiverc> ack, had hoped to test t59 yesterday but was unable, will do probably …], Yeah but. There will be two DSomethings. First this one then another one for globalkeyshortcuts.conf.
[22:25] <wxl> @The_LoudSpeaker you actually have to do a full on debian patch. so you basically get the repo, download the source, tell quilt you're making a new patch, make the changes, tell quilt your done, build it and make sure it works, and arc diff it. see packaging tutorial
[22:26] <guiverc> is D17 change reflected on daily?  or do I need to use installed?
 @wxl [<wxl> @The_LoudSpeaker you actually have to do a full on debian patch. so you ba …], Umm. Okay. I will try.
[22:33] <teward> *randomly yells REEEEEEE*
[22:33] <teward> Simon broke it
[22:38] <wxl> oh actually (correct me if i'm wrong @tsimonq2 ) but this seems like another case where you can just edit that patch to your likeing, @The_LoudSpeaker
 After running 'quilt header --dep3 -e', While writing the description, do I write it inside '< >' or outside of it?
 @The_LoudSpeaker [After running 'quilt header --dep3 -e', While writing the description, do I writ …], Delete the < >
[22:50] <wxl> @The_LoudSpeaker did you not see my note above? you should just be able to edit the patch to your liking.
[22:50] <wxl> right @tsimonq2 ?
 @wxl [<wxl> @The_LoudSpeaker did you not see my note above? you should just be able to …], Ah, that's what you meant. Yes.
 @wxl [<wxl> @The_LoudSpeaker did you not see my note above? you should just be able to …], You mean me editing your patch and not creating a new one?
[22:51] <wxl> @tsimonq2: on the other hand, given the scope of changes that might be painful....... suggestions?
 What I'm saying is, hand edit patch descriptions. You're a masochist if you hand-edit patches
[22:52] <wxl> well i mean that's what we told hans to do
[22:52] <wxl> of course his change was trivial
[22:52] <wxl> so it sounds like we're adding a patch
 Right, if it's like that, I wouldn't worry about it
[22:52] <wxl> keep doing what you're doing @The_LoudSpeaker :)
 Well, remember, native packages don't get patches
[22:53] <wxl> this ain't native
 Which package again?
[22:53] <wxl> globalkeys
 @tsimonq2 [Well, remember, native packages don't get patches], :)
 @wxl [<wxl> this ain't native], on hold.
[22:54] <wxl> but
[22:54] <wxl> maybe we should review again...... why did we change it in globalkeys again?
 @wxl [<wxl> maybe we should review again...... why did we change it in globalkeys agai …], Coz there is no globalkeyshortcuts.conf in rLUBUNTUDEFAULTSETTINGS
[22:56] <wxl> well i mean we could add one. that's not a big deal
 Should we? I guess only one of them is needed then. If we add  one to lubuntu-default-settings then there is no need of rLXQTGLOBALKEYSPACKAGING
[22:58] <wxl> @tsimonq2: thoughts?
[22:59]  * wxl listens to the empty vacuum of space
[22:59] <kc2bez> no crickets?
[22:59] <wxl> no, he doesn't have crickets in his skull
[22:59] <kc2bez> :D
[22:59] <teward> lol
[23:00]  * teward puts a single cicada inside tsimonq2's head, and laughs at the cacaphony it causes
[23:00] <wxl> i love cicadas
[23:00] <wxl> i think they are quite sonorous
[23:01] <kc2bez> Seriously though, we need to change the win key behavior somehow right?
[23:01] <wxl> that's essentially what we're trying to do here
 Imo we should keep rLXQTGLOBALKEYSPACKAGING, isnlt it the one having commands which make local config file for globalkeyshortcuts.conf ?
 And not add to lubuntu-default-settings
[23:01] <kc2bez> Global keys is where it is currently defined so something needs to change there I think.
[23:01] <wxl> the immediate need: remove any super key shortcuts in openbox
[23:02] <wxl> the bigger desire: limit any shortcuts from openbox that we can't put in lxqt
[23:02] <wxl> other stuff: remove unnecessary/old crap and add missing stuff
 @wxl [<wxl> the immediate need: remove any super key shortcuts in openbox], Then I am continuing what I am doing. Rest lite.
[23:02] <kc2bez> Ah, got it, my brain had it backwards.
[23:03] <wxl> @The_LoudSpeaker yeah i mean we can always move it to default settings later. i don't remember why but where we would normally patch it in default settings, we had to make the change in globalkeys. 
 @wxl [<wxl> the bigger desire: limit any shortcuts from openbox that we can't put in l …], That is also almost done here now only. I just couldn't add those send to desktop shortcuts because lxqt doesn't has a specific command to to do. openbox has.
[23:04] <wxl> yep makes sense
 Now send a coffee, its 4.34 am
[23:05]  * kc2bez passes a coffee to @TheLoudSpeaker
 The night canteen guy decided to sleep today. :-:
 @lubuntu_bot [*kc2bez: passes a coffee to @TheLoudSpeaker*], *Gulps it in one go!*
[23:11] <kc2bez> It looks like it did what you were hoping for in your openbox patch.
[23:11] <kc2bez> keybinds are pretty clean there.
 Should I do 'dch 17' or 'dch -i' now, after 'quilt header --dep3 -e' ? If I do dch 17, will it merge it with the differential version of openbox patch.
 @kc2bez [<kc2bez> keybinds are pretty clean there.], Thanks :) … *Gulps another glass of coffee*
[23:12] <wxl> dch has nothing to do with phabricator/arc/differential revision
[23:12] <wxl> so dch -i
 So what does it do then?
 @wxl [<wxl> so dch -i], k.
[23:13] <kc2bez> debian changelog
[23:13] <wxl> incrememnts the debian changelog version number and gets you in an editor where you can add a changelog entry
 @kc2bez [<kc2bez> debian changelog], Noice.
[23:13] <kc2bez> dch is a helper tool
[23:13] <wxl> you can't actually have a differential revision that refers to two separate repos, so you'll have to have a new `arc diff`
[23:14] <wxl> you can edit the description of them both so that they point at each other
 @wxl [<wxl> you can't actually have a differential revision that refers to two separat …], okay. Noted.
 @wxl [<wxl> you can edit the description of them both so that they point at each other], Sure. Will do that. I think the D17 talks about this, I will just add a line stating new Differential version of lxqtconfig.