 I'm almost ready with individual wallpaper (same for all) for multimonitor. Problem is that test it's not easy because latest libfm-qt is needed. What do we need for ci tu work?
 it looks like symbols are the issue there. I took a quick peek at it last night.
 Also, I poked at the welcome center and got it so it builds and all the buttons work. @tsimonq2 do you want me to push my changes to phab?
 @kc2bez [it looks like symbols are the issue there. I took a quick peek at it last night.], libfm-qt? yes. symbols
 libfm-qt, yes. Here is the latest buildlog https://launchpadlibrarian.net/453526762/buildlog_ubuntu-focal-amd64.libfm-qt_0.14.1+git201911290108~focal-0ubuntu1~ppa1_BUILDING.txt.gz
 Here is some info on symbols https://wiki.debian.org/UsingSymbolsFiles
 @kc2bez [Also, I poked at the welcome center and got it so it builds and all the buttons …], Go for it
[15:00] -lugito:#lubuntu-devel- [rWELCOME72495165535b: Fix welcomecenterresource file] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rWELCOME72495165535b
[15:00] -lugito:#lubuntu-devel- [rWELCOME9eb1c261d5b5: Fix contributing button link] kc2bez (Dan Simmons) committed: https://phab.lubuntu.me/rWELCOME9eb1c261d5b5
 @kc2bez [Also, I poked at the welcome center and got it so it builds and all the buttons …], Yay!!
 @kc2bez [libfm-qt, yes. Here is the latest buildlog https://launchpadlibrarian.net/453526 …], I ave been able to build git libfm-qt 2 machines w/o problems
 *have
 but I have built it for amd64 only
 Try building it in a sbuild of 32bit
 It will need some effort to put up a sbuild or pbuilder. But trust me, it's good for testing i still have one lying around.
 I know my friend mapreri may hate me for saying this (he maintains pbuilder in Debian) but sbuild > pbuilder :)
 @tsimonq2 [I know my friend mapreri may hate me for saying this (he maintains pbuilder in D …], 10/10 highly recommend
 https://github.com/calamares/calamares/issues/1279
 Will there be a statement from the LC or should I answer, that we use https://ipapi.co/json to set the url in /etc/apt/sources.list?
 There will be something that will come from LC.
 thanks
 There is also this thread in our forum from (maybe) the same user => https://discourse.lubuntu.me/t/calamares-unauthorised-data-leaking-ethics-and-eu-data-regulations/550/4
 I think it is the same person.
 @The_LoudSpeaker [Try building it in a sbuild of 32bit], do you have some docs for doing it?
 @HMollerCl [do you have some docs for doing it?], There's docs on ubuntu wiki. I will have to dig up. One sec.
 https://wiki.ubuntu.com/SimpleSbuild
 ^ here you go. @HMollerCl
 thanks
 @kc2bez [Here is some info on symbols https://wiki.debian.org/UsingSymbolsFiles], when tryng to use git pcmanfm with released libfm-qt this error araises :"./pcmanfm-qt: undefined symbol: _ZN2Fm16ProxyFolderModel13setHiddenLastEb"
[18:55] -lugito:#lubuntu-devel- [T17: Write a Welcome Center] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T17#2743
 @kc2bez in ci the buidling is done by packaging info?
 I mean, maybe there is an issuw with packaging
 @HMollerCl [when tryng to use git pcmanfm with released libfm-qt this error araises :"./pcma …], Right, so you need to use libfm-qt from Git as well
 pcmanfm-qt depends on libfm-qt as a library
 If it were me I would simply enable the PPA on a test machine and upgrade
 @tsimonq2 [pcmanfm-qt depends on libfm-qt as a library], yes, but @kc2bez told me that libfm-qt builds fails in ci https://launchpadlibrarian.net/453526762/buildlog_ubuntu-focal-amd64.libfm-qt_0.14.1+git201911290108~focal-0ubuntu1~ppa1_BUILDING.txt.gz
 That way the entire dependency chain is taken with it
 @HMollerCl [yes, but @kc2bez told me that libfm-qt builds fails in ci https://launchpadlibra …], Right, with symbols
 Fun little things...
 I have built libfm-qt in 2 systems w/o problem
 @RikMills right? :P
 @HMollerCl [I have built libfm-qt in 2 systems w/o problem], It's the dependency chain
 libfm-qt depends on libraries that are also built from Git
 So newer versions
 We need to fix the libfm-qt build first
 @tsimonq2 [We need to fix the libfm-qt build first], yes, i know I did tha on 2 systems. w/o problems
 I wonder why it won't buld in ci
 What's your process?
 and I've used plain focal packages for it.
 @HMollerCl [and I've used plain focal packages for it.], Ahh
 Try enabling the PPA when you run it through sbuild
 So just a default focal sbuild run with libfm-qt (as a baseline) and then run it through again with the CI PPA enabled
 If I'm understanding you correctly, those should produce different outputs
 mm I don't get it.
 I would expect the libfm-qt build with only focal packages to succeed and the CI-enabled build to fail
 aaaaa, ok
 now I get it.
 Okay :)
 Simplified scientific method ;)
 @tsimonq2 [So just a default focal sbuild run with libfm-qt (as a baseline) and then run it …], To keep that ppa persistent across builds, change the pristine image. Right @teward001 ?
 @The_LoudSpeaker [To keep that ppa persistent across builds, change the pristine image. Right @tew …], That's correct
 However, I don't have a clean chroot with a PPA enabled unless the PPA changes base packages
 You can enable a PPA as an argument when you run sbuild
 It's called golden image i guess. on that wiki page i sent earlier @HMollerCl
 Right
 isn't better to use a container than sbuild or chroot?
 @tsimonq2 [You can enable a PPA as an argument when you run sbuild], Nah. Too many arguments in one line. Let me do it separately
 @The_LoudSpeaker [It's called golden image i guess. on that wiki page i sent earlier @HMollerCl], Again, I see where you're coming from, and yes that's technically correct, but in practice it can get difficult to maintain
 lxd?
 @tsimonq2 [Again, I see where you're coming from, and yes that's technically correct, but i …], I know
 @HMollerCl [isn't better to use a container than sbuild or chroot?], YMMV
 @HMollerCl [lxd?], Faar better and easier
 YMMW?
 YMCA?
 I use sbuild schroots
 @HMollerCl [YMMW?], Your Mileage May Vary
 @HMollerCl [YMCA?], Bahahaha
 But can we create lxd of different architectures? Wxl:
 We can, yes
 Again, it depends on your use case
 @HMollerCl [YMCA?], Circle, Narayanguda, Hyd, India.
 Just completing the address. XD
 @The_LoudSpeaker [Circle, Narayanguda, Hyd, India.], Hahahaha
 @HMollerCl [YMCA?], ITS FUN TO STAY AT THE
 @UniversalSuperBox [ITS FUN TO STAY AT THE], *does arm motions*
 @tsimonq2 [We can, yes], I didn't know that. Will have to try it then.
 But @HMollerCl since you set up sbuild today, i suggest go with it only for now. Set up lxd later, takes a bit of time. It's like seeing the whole system again.
 There is an important distinction I want to make here...
 *setting
 If you want a set container environment that you can easily iterate on changes, LXD is great
 However, if you need to have an ephemeral build environment (for example, testing a build before uploading), use an schroot with sbuild
 Like I said before, YMMV
 Also, sbuild closely mimics the actual packaging environment na? As compared to lxd?
 wxl (rightfully so) pushes LXD hard but it's not the end-all be-all answer
 @The_LoudSpeaker [Also, sbuild closely mimics the actual packaging environment na? As compared to …], It more closely resembles how packages are built in the Ubuntu infrastructure, he's
 However, here's where it gets fun...
 In the infrastructure they run autopkgtests... With LXD XD
 Lol!
 So part of the infra uses LXD and for testing autopkgtests I would use it
 However, that's mostly outside the scope of our work here
 Anyway, my point is, yes, you can use LXD, but we want our local testing to resemble what the actual infra uses Just In Case
 @The_LoudSpeaker [But @HMollerCl since you set up sbuild today, i suggest go with it only for now. …], thanks, but actually is teh other way around. I have lxd and have not sbuild.
 Oh. Okay.
[20:57] <wxl> OMG GITHUB HAS CODE NAVIGATION WTH
 Microsponge?
[21:16] <wxl> wait what/ XD
 Pinky and the Brain, Microsponge
[21:38] <wxl> ohhhh wow nice
 @wxl [<wxl> wait what/ XD], +1
[22:07] <wxl> i think pinky and the brain is officially a boomer show
 Oh.
 @wxl [<wxl> OMG GITHUB HAS CODE NAVIGATION WTH], So no reference to this?
[22:16] <wxl> it is
[22:16] <wxl> but a very vague one
[22:18] <kc2bez> It looks like language support is somewhat limited but python is one of the supported. 
 @kc2bez [<kc2bez> It looks like language support is somewhat limited but python is one of …], It's a start.
[22:20] <kc2bez> Yeah, it is pretty nice. 
[22:21] <wxl> i like this suggestion of a terminal interface to cala https://discourse.lubuntu.me/t/not-using-an-attached-vga-monitor-may-make-installation-impossible/554
[22:22] <wxl> c* isn't even on the list of work in progress for the underlying library boooo https://github.com/github/semantic#language-support
[22:22] <wxl> but haskell? good god people
[22:23] <wxl> i mean i like haskell but come on
[22:23] <wxl> i'm going to come out with a new language and call it avocado toast. it'll be that hip.
 Okay boomer
 XD
[22:23] <wxl> whatever. you'll use it
[22:25] <wxl> we'll denote lambdas with emojis. probably exploding head.
[22:25] <wxl> or hahahahah the recycle emoji X''''D
[23:41] -lugito:#lubuntu-devel- [rMANUALfbd251282c8a: Fix capitilization] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALfbd251282c8a
[23:41] -lugito:#lubuntu-devel- [rMANUAL40955dfa5566: Fix capitlization] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL40955dfa5566