 *sits on Dalton*
 But how?
 Manually? What manages it?
 the core infra is all containerized in a single server to isolate the envs from each other for cleanliness.  All LXD containers are mirrored weekly to an LXD server I have here at home for backups.  most of the deployed infra just runs itself
 initial setup was done by yours truly and Simon for some of it
 and by core infra we mean Phab, Weblate (translations), Discourse, CI (Jenkins), etc.
 some stuff is still in Canonical's stacks like ISOs.
 it's defined which kernel will be on 19.10?
 ask the Kernel Team that one
 not sure we reached kernel freeze yet - probably did but I dont have the freezes schedule right in front of me
 mmm ubuntu wiki tells me that next kernel meeting will be tuesday 1oth nov. 2015....
 sorry,
 10th.
 https://wiki.ubuntu.com/KernelTeam/Meeting
 they lurk on IRC in #ubuntu-kernel but I need the Eoan dev schedule lol
 phone is derping with the wiki
 Feature Freeze: August 22, 2019 …     Kernel Freeze: September 26, 2019 …     Final Freeze: October 10, 2019
 from: https://www.omgubuntu.co.uk/2019/05/ubuntu-19-10-release-features
 also from https://wiki.ubuntu.com/EoanErmine/ReleaseSchedule
 which i trust more 😜
 wxl: I'm doing the meta update thing, so far so good.
 and not, it takes tooooooo long,I went to bed and my system didn't woke up. Will try in another system tonight.
[18:05] <wxl> @HMollerCl i could run it in my container if you want. it's always running
 would be nice
[18:21] <wxl> Eickmeyer: did Studio have a failure with updating apt-xapian-index on today's ISO?
[18:21] <Eickmeyer> wxl: I haven't seen a fail mail...
[18:22]  * Eickmeyer goes to check some schtuff
[18:22] <wxl> might be a timing thing. yours might build later
[18:24] <Eickmeyer> wxl: Probably. I'll let you know if I get a fail mail. As far as I can see, ours is still 20190625, which means it might still be building. Usually it's done by about Noon PDT.
[18:24] <wxl> kk
[18:26] <tsimonq2> tl;dr Lubuntu ISO builds are failing because apt-xapian-index is depending on a deprecated python-apt feature that python-apt removed in the latest release.
[18:26] <teward> i saw an email giving a heads up about the apt change a few weeks ago I think
[18:27] <wxl> how did all the others pass through today?
[18:27] <teward> about that section being removed and might cause issues
[18:27] <teward> wxl: it's Simon's fault?
[18:27] <tsimonq2> We're the only one that depends on apt-xapian-index.
[18:27] <tsimonq2> (Assuming it's only failing for us.)
[18:28] <wxl> Studio, Kylin, and Budgie are on yesterday's
[18:28] <wxl> Studio may not have a problem though
[18:28] <wxl> i *thought* others used it
[18:28] <wxl> i seem to remember kubuntu did but i could be wrong
[18:29] <wxl> post-malone?
[18:31] <tsimonq2> wat? XD
[18:31] <tsimonq2> oh
[18:31] <tsimonq2> no
[18:31] <tsimonq2> ProposedMigration
[18:31] <tsimonq2> wxl: Also, ECHAN
[18:32] <wxl> no, i wanted to carry that over here :)
[18:33] <tsimonq2> XD
[18:38] <wxl> do we need it, especially if it's problematic and orphaned?
[18:39] <tsimonq2> No clue.
[18:59] <TJ-> as it's a Recommends of libqapt I'd have thought it is only needed if there are QT based software search tools using libqapt, like qapt-deb-installer 
[19:05] <kc2bez> We have qapt-deb-installer. I think we added it for Disco. 
 @kc2bez [<kc2bez> We have qapt-deb-installer. I think we added it for Disco.], yes, we did
 cause otherwise ark wanted to open them
[19:11] <wxl> @HMollerCl doesn't discover do those now, too?
[19:12] <kc2bez> Discover should be able to as well. 
[19:12] <kc2bez> But Discover...
[19:12] <wxl> discover is getting better soon
[19:12] <wxl> really there's very little wrong with it
[19:12] <wxl> the major problem is the lack of progress indicators and that's on the way
[19:12] <kc2bez> It is way better already. 
[19:13] <wxl> this is the "slow" thing
[19:13] <wxl> it's a perception, not a reality
[19:13] <wxl> we don't think of synaptic, apt, etc. as slow because we see an indicator, but they take the same amount of time
[19:13] <wxl> let's just get rid of it and be done with it. anyone got a problem with that?
[19:13] <kc2bez> It does use some resources on launch but it settles down shortly after. 
[19:14] <wxl> or maybe we wait to see how things settle out with upstream
[19:14] <wxl> thoughts, @tsimonq2 ?
[19:15] <lynorian> wxl discover doesn't install cli apps from a gui
 let me try discover again in my old machines.
[19:18] <wxl> try it with a cli app of some kind. tmux, let's say, @HMollerCl
[19:18] <wxl> oh i guess i need to upload lubuntu-meta
 my guess is that discover will consume uneeded resources only for open a .deb, like refreshing cache and others.
[19:19] <wxl> right, @tsimonq2 ?
[19:19] <tsimonq2> wxl: I don't quite have a preference.
 if muon does, muon is a better option.
[19:21] <Eickmeyer> wxl: Yep, got a fail mail. You're not alone.
 let's all blame Simon
 because reasons.
[19:21]  * Eickmeyer throws @tsimonq2 under a bus
 @teward001 [let's all blame Simon], we could also sue him XD
[19:24] <tsimonq2> hey XD
[19:24] <TJ-> I think you don't need to worry if the issue a FTBFS - is that the case?
[19:24] <wxl> no it's not TJ- 
[19:25] <TJ-> wxl: I thought it was due to apt-xapian-index failing due to python-apt changes?
[19:26] <wxl> it fails but not fails to build
[19:26] <TJ-> wxl: sorry, fails *tests* 
[19:29] <TJ-> wxl: without seeing the fail logs hard to tell, but I suspect this commit addresses the issue:  https://salsa.debian.org/apt-team/python-apt/commit/68227b7f16a8e3a2569368cabe2dff03468336b3
[19:30] <wxl> TJ-: https://launchpadlibrarian.net/430708403/buildlog_ubuntu_eoan_amd64_lubuntu_BUILDING.txt.gz
[19:31] <wxl> don't think that's it
[19:33] <TJ-> wxl: you're correct; thanks for the log. Here's the commit that broke it: https://salsa.debian.org/apt-team/python-apt/commit/fedd51be48be53d00d386c45eab8f63f462db202
[19:34] <TJ-> "* The `section` attribute has been removed from :class:`apt_pkg.Package`"
[19:34] <wxl> yep nice catch
[19:34] <TJ-> Looks like you need to report a regression bug against that as it broke apt-xapian-index
[19:35] <TJ-> I was looking through the python-apt mailing list but couldn't find any discussion on removing those features
[19:35] <wxl> there's this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931132
[19:35] <wxl> and this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931133
[19:36] <wxl> which should, in reverse order, fix the problem and keep it from happening again
[19:36] <TJ-> wxl: apt-xapian-index has been removed from Debian experimental
[19:38] <tsimonq2> Removal from Debian Experimental means nothing.
[19:39] <tsimonq2> Debian Experimental is just a test pocket.
[19:39] <TJ-> tsimonq2: sorry, I got myself confused here
[19:39] <tsimonq2> ah :)
[19:39] <tsimonq2> np
[19:39]  * TJ- has a fever today and is quite spaced out
[19:40] <TJ-> I think I need to turn off this flourescent green colour theme
[19:42] <TJ-> I suppose the question is, how long will it take for the fix to percolate through
[19:43] <TJ-> looks like there's a bugette in Setting up uuid-runtime (2.33.1-0.1ubuntu2) .. too
[19:44] <TJ-> it's creating the group before the user and causing "Warning: The home dir /run/uuidd you specified can't be accessed: No such file or directory"
[19:44] <TJ-> or maybe not; that's weird! "Not creating home directory `/run/uuidd'."
[19:48] <wxl> @tsimonq2: um. i'm confused. it doesn't seem that when i build lubuntu-meta it GPG signs anything, though afaik you need to force debuild to NOT do so. i just did the same thing on libfm-qt6 and all is well. but of course dput gets unhappy without a signature. catch-22?
[19:50] <wxl> alias "cd.."="cd .."
[19:50] <wxl> don't tell me you wish you had it at least at one point XD
[19:52] <tsimonq2> wxl: debuild -S -d *-us -uc*
[19:52] <tsimonq2> Those two flags go without signing it.
[19:52] <wxl> yeah i *want* to sign it
[19:53] <tsimonq2> However, if you're sponsoring an upload, you still need to run debsign -kMYKEYIDHERE /path/to/source.changes
[19:53] <wxl> so `debuild -S` should just do it afaik. it's done it on everything i've ever done
[19:55] <wxl> it does the debsign for that matter
[19:55] <wxl> which is why i have DEBSIGN_KEYID in ~/.devscripts
[19:55] <tsimonq2> ok
[19:55] <wxl> but there i'll just debsign it myself i guess
[19:56] <wxl> i just don't understand why that's the case. it's super bizarre
[19:57] <wxl> should i NOT be uploading lubuntu-meta? is this actually generated?
[19:57] <tsimonq2> Well, does the changelog check out?
[19:57] <tsimonq2> Wait
[19:57] <tsimonq2> Are you sponsoring this?
[19:58] <wxl> well i'm trying to figure it out
[19:58] <wxl> that was my intention but now things are going all weird
[19:58] <wxl> the changelog is your script
[19:59] <wxl> or some script
[19:59] <tsimonq2> What is in the changelog?
[20:00] <wxl> this is the big update https://phab.lubuntu.me/rLUBUNTUMETAPACKAGING3cdce7d79da6891daa2f3879f8aada7b6e1fc177
[20:00] <wxl> it seems messed up
[20:01] <wxl> but does that explain why it doesn't GPG sign? noooooooo
[20:01] <tsimonq2> Nope, just dch -r
[20:01] <tsimonq2> Then try
[20:02] <wxl> hah
[20:02] <wxl> it does explain it
[20:02] <wxl> *b*i*z*a*r*e* but cool
[20:16] <wxl> ~lubuntu-packaging wasn't subscribed to lubuntu-meta bugs *FACEPALM*
[20:17] <wxl> anyone want to go through and triage it would make my day https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bugs?orderby=-id&start=0
 some we can ix easy wxl
 'search: 14.04 OR Trusty OR Precise OR 12.04 OR {InterimReleases}   |   ACTION: Close.
 :P
[22:05] <TJ-> I'm working on Bug #1828663  -- looks to be a polkit problem
 @TJ- [<TJ-> I'm working on Bug #1828663  -- looks to be a polkit problem], damned politicians....
[22:24] <TJ-> Looks to be a segfault in lxqt-policykit 
[22:32] <wxl> @HMollerCl you'll find network-manager-gnome is now in lubuntu-meta
 goof
 good
 as soon as we have a new iso I will test it and if works change the defaut coneection-editor for nm-tray in nm-tray package.
[22:35] <wxl> might take a while given the apt-xapian-index issue
[22:54] <TJ-> I came up with a 1-line fix for that :P
 we didn't we have Tj- before?
 TJ-
[23:08] <wxl> no but tj is a god send :)
[23:10] <kc2bez> +1
 (Photo, 1280x800) https://i.imgur.com/gQyRjhM.jpg Hello. This is not a Walpaper proposal, this is just a small experiment made from a change in the hummingbird image of the Lubuntu 1804 wallpaper.
[23:13] <wxl> i like the direction you're headed with that
 me too
[23:14] <kc2bez> Hmm, makes me think about our SDDM background too.
 I was just playing around 😊
[23:17] <kc2bez> Here is some inspiration perhaps: https://github.com/Rokin05/SDDM-Themes/tree/master/.github/medias/screenshots/arc
[23:17] <kc2bez> With the humming bird image that @JyotiGomes has started on for a backdrop.
 @JyotiGomes [<reply to image>], that looks really cool
 I think that if later Lubuntu will have a logo of its own, replacing the lxqt logo (which is not specific to Lubuntu but rather to LXQt), it could well be this Lubuntu 1804 hummingbird. I do not know who created it, but it's fine. The hummingbird is a super fast, intelligent bird, active, effective and very beautiful 🙂
 @kc2bez [<kc2bez> Here is some inspiration perhaps: https://github.com/Rokin05/SDDM-Theme …], they work in lubuntu or are they only for plasma?
[23:32] <kc2bez> Here are the manual install instructions: https://github.com/Rokin05/SDDM-Themes#-others-environments--manual-install-
 @kc2bez [<kc2bez> Here are the manual install instructions: https://github.com/Rokin05/SD …], Ok, thanks!
 (Photo, 1280x800) https://i.imgur.com/NFShh6G.jpg Just more this version of color, I do not want to annoy you too much
[23:49] <wxl> not that one so much
[23:50] <TJ-> With my Blind Society hat on, I'd ask you to consider how these images will be perceived by visually impaired people, who need strong contrasts and also have a better experience when certain colours are used
[23:50] <wxl> there's probably a design guideline for that somewhere..
[23:53] <TJ-> Re the policykit issue; looks like there may be two problems but I'm not familiar enough with the code bases to figure it out. 1) should a user already a member of "sudo" group even be prompted to select the user they wish to authenticate as?  and 2) when they do something goes wrong and there's a SIGSEGV which looks like it may be caused in libpolkit-qt5 
[23:54] <TJ-> I've updated the bug report but not sure I can take it much further
[23:56] <wxl> might have to dig upstream and see if there's anything sensible that shakes out of the trees
[23:57] <TJ-> Already done that; there don't appear to be any relevant commits (in fact very few commits in recent times at all)
[23:58] <wxl> to be clear i'm referring to lxqt-policykit.. or maybe even the lxqt-config-users or whatever it is
[23:58] <TJ-> right, I looked at that and libpolkit-qt5
[23:59] <TJ-> Looks like tsimonq2 is the committer on github for lxqt-policykit and the recent changes have been predominently translations
[23:59] <wxl> i know with lxqt there's often a lot of chatter that happens in issues, so sometimes i just dig in there for keywords and see if i can shake something out