[13:31] 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? [13:32] it looks like symbols are the issue there. I took a quick peek at it last night. [13:35] 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? [13:45] @kc2bez [it looks like symbols are the issue there. I took a quick peek at it last night.], libfm-qt? yes. symbols [13:49] 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 [13:50] Here is some info on symbols https://wiki.debian.org/UsingSymbolsFiles [14:58] @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 [15:37] @kc2bez [Also, I poked at the welcome center and got it so it builds and all the buttons …], Yay!! [15:37] B3twiise was added by: B3twiise [15:44] @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 [15:44] *have [15:49] but I have built it for amd64 only [15:53] Try building it in a sbuild of 32bit [15:57] 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. [15:58] I know my friend mapreri may hate me for saying this (he maintains pbuilder in Debian) but sbuild > pbuilder :) [15:59] @tsimonq2 [I know my friend mapreri may hate me for saying this (he maintains pbuilder in D …], 10/10 highly recommend [16:49] https://github.com/calamares/calamares/issues/1279 [16:58] 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? [16:59] There will be something that will come from LC. [16:59] thanks [17:00] 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 [17:03] I think it is the same person. [17:14] @The_LoudSpeaker [Try building it in a sbuild of 32bit], do you have some docs for doing it? [17:14] @HMollerCl [do you have some docs for doing it?], There's docs on ubuntu wiki. I will have to dig up. One sec. [17:15] https://wiki.ubuntu.com/SimpleSbuild [17:15] ^ here you go. @HMollerCl [17:16] thanks [17:17] @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 [19:58] @kc2bez in ci the buidling is done by packaging info? [19:59] I mean, maybe there is an issuw with packaging [20:02] @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 [20:02] pcmanfm-qt depends on libfm-qt as a library [20:03] If it were me I would simply enable the PPA on a test machine and upgrade [20:03] @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 [20:03] That way the entire dependency chain is taken with it [20:04] @HMollerCl [yes, but @kc2bez told me that libfm-qt builds fails in ci https://launchpadlibra …], Right, with symbols [20:04] Fun little things... [20:04] I have built libfm-qt in 2 systems w/o problem [20:04] @RikMills right? :P [20:04] @HMollerCl [I have built libfm-qt in 2 systems w/o problem], It's the dependency chain [20:04] libfm-qt depends on libraries that are also built from Git [20:04] So newer versions [20:04] We need to fix the libfm-qt build first [20:05] @tsimonq2 [We need to fix the libfm-qt build first], yes, i know I did tha on 2 systems. w/o problems [20:05] I wonder why it won't buld in ci [20:05] What's your process? [20:05] and I've used plain focal packages for it. [20:05] @HMollerCl [and I've used plain focal packages for it.], Ahh [20:06] Try enabling the PPA when you run it through sbuild [20:06] So just a default focal sbuild run with libfm-qt (as a baseline) and then run it through again with the CI PPA enabled [20:06] If I'm understanding you correctly, those should produce different outputs [20:07] mm I don't get it. [20:07] I would expect the libfm-qt build with only focal packages to succeed and the CI-enabled build to fail [20:07] aaaaa, ok [20:07] now I get it. [20:07] Okay :) [20:08] Simplified scientific method ;) [20:08] @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 ? [20:08] @The_LoudSpeaker [To keep that ppa persistent across builds, change the pristine image. Right @tew …], That's correct [20:08] However, I don't have a clean chroot with a PPA enabled unless the PPA changes base packages [20:08] You can enable a PPA as an argument when you run sbuild [20:08] It's called golden image i guess. on that wiki page i sent earlier @HMollerCl [20:09] Right [20:09] isn't better to use a container than sbuild or chroot? [20:09] @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 [20:09] @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 [20:09] lxd? [20:09] @tsimonq2 [Again, I see where you're coming from, and yes that's technically correct, but i …], I know [20:09] @HMollerCl [isn't better to use a container than sbuild or chroot?], YMMV [20:09] @HMollerCl [lxd?], Faar better and easier [20:10] YMMW? [20:10] YMCA? [20:10] I use sbuild schroots [20:10] @HMollerCl [YMMW?], Your Mileage May Vary [20:10] @HMollerCl [YMCA?], Bahahaha [20:10] But can we create lxd of different architectures? Wxl: [20:10] We can, yes [20:10] Again, it depends on your use case [20:10] @HMollerCl [YMCA?], Circle, Narayanguda, Hyd, India. [20:11] Just completing the address. XD [20:11] @The_LoudSpeaker [Circle, Narayanguda, Hyd, India.], Hahahaha [20:11] @HMollerCl [YMCA?], ITS FUN TO STAY AT THE [20:11] @UniversalSuperBox [ITS FUN TO STAY AT THE], *does arm motions* [20:12] @tsimonq2 [We can, yes], I didn't know that. Will have to try it then. [20:13] 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. [20:13] There is an important distinction I want to make here... [20:13] *setting [20:13] If you want a set container environment that you can easily iterate on changes, LXD is great [20:14] However, if you need to have an ephemeral build environment (for example, testing a build before uploading), use an schroot with sbuild [20:14] Like I said before, YMMV [20:14] Also, sbuild closely mimics the actual packaging environment na? As compared to lxd? [20:15] wxl (rightfully so) pushes LXD hard but it's not the end-all be-all answer [20:15] @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 [20:15] However, here's where it gets fun... [20:15] In the infrastructure they run autopkgtests... With LXD XD [20:16] Lol! [20:16] So part of the infra uses LXD and for testing autopkgtests I would use it [20:16] However, that's mostly outside the scope of our work here [20:17] 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 [20:18] @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. [20:33] Oh. Okay. [20:57] OMG GITHUB HAS CODE NAVIGATION WTH [21:03] Microsponge? [21:16] wait what/ XD [21:37] Pinky and the Brain, Microsponge [21:38] ohhhh wow nice [22:06] @wxl [ wait what/ XD], +1 [22:07] i think pinky and the brain is officially a boomer show [22:08] Oh. [22:08] @wxl [ OMG GITHUB HAS CODE NAVIGATION WTH], So no reference to this? [22:16] it is [22:16] but a very vague one [22:18] It looks like language support is somewhat limited but python is one of the supported. [22:19] @kc2bez [ It looks like language support is somewhat limited but python is one of …], It's a start. [22:20] Yeah, it is pretty nice. [22:21] 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] 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] but haskell? good god people [22:23] i mean i like haskell but come on [22:23] i'm going to come out with a new language and call it avocado toast. it'll be that hip. [22:23] Okay boomer [22:23] XD [22:23] whatever. you'll use it [22:25] we'll denote lambdas with emojis. probably exploding head. [22:25] 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