[03:02] <Unit193> Dancing Dingo have a name yet?
[06:45] <flocculant> Unit193: yup Deeply Dippy
[06:46] <Unit193> ...Dunkin' Donuts.
[06:46] <flocculant> :)
[07:26] <flocculant> bluesabre: were you aware that upgrades from 18.04 on 32 bit aren't supported anymore? That being the case we should revisit the 32bit story (again) https://i.imgur.com/xzmjB5H.png
[07:27] <flocculant> that's a bog standard 32 bit install - god only knows how many 'You've got to be joking's' someone like Unit193 would see if they didn't use the terminal to do things :p
[07:28] <flocculant> and perhaps we should add something to the release notes for 18.04/18.10
[07:28] <Unit193> flocculant: Yeah I knew that upgrades were discouraged for 32bit.
[07:31] <flocculant> I didn't - unsurprisingly this cycle
[07:31] <Unit193> It wasn't very loudly advertised, I believe. :/
[07:31] <flocculant> we shouldn't really be giving it to people with that being the case imo
[07:32] <flocculant> Unit193: right - I did read something this week in -release, just assumed it wasn't Looby Lou and us
[07:32] <Unit193> LTS → normal release will fail, normal → normal should be fine.
[07:32] <Unit193> flocculant: Sorry if I didn't mention it and should have, I think I had a crank in -ot but that'd have been it.
[07:33] <flocculant> that makes some sense given LTS to LTS would be 2021
[07:33] <flocculant> Unit193: well I'd likely not have noticed anyway this cycle ...
[07:33] <Unit193> I'd say we should certainly point to the LTS for new 32bit users.
[07:34] <flocculant> why? 
[07:34] <flocculant> there's even less chance of a successful upgrade with 32 bit in 2021
[07:34] <flocculant> fingers keep doing 2012 instead of 2021
[07:35] <flocculant> we should point 32 bit users to a shop ...
[07:35] <Unit193> Right, but Bionic will be supported slightly longer, I think.
[07:35] <Unit193> Hah, well there is that.
[07:35] <flocculant> :p
[07:37] <Unit193> I think I'm going to give up on the 32bit argument.
[07:37] <flocculant> lol
[07:37] <flocculant> possibly have to move off of the fence here 
[07:38] <Unit193> (And won't secretly hold it aginst the Xubuntu team either, if I want to still run 32bit I can just push them to Debian.  If I were sane,I wouldn't though.)
[07:38] <Unit193> Eh, the fence is a nice seat.
[07:38] <flocculant> getting a bit thin lately :D
[11:00] <bluesabre> flocculant: noticed it on the general release note on release day
[11:00] <bluesabre> didn't know who we'd have to bribe to get 32bit upgrades for (l/x)ubuntu (studio)
[11:02] <flocculant> bluesabre: I sort of read it on Thursday - didn't think about it affecting us till someone mentioned it in #x
[11:02] <flocculant> personally I'm now at the position where we should knock that on the head
[11:03] <flocculant> I put it on the agenda for whenever slickymaster bothers setting up the next meeting :D
[11:04] <bluesabre> great
[18:54] <brainwash> bluesabre: is this fix good? https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1754872/comments/27
[19:03] <brainwash> lightdm, lightdm-gtk-greeter -> lightdm-gtk-greeter, lightdm
[19:04] <brainwash> this way lightdm will not pull in unity-greeter because gtk-greeter is already checked for being installed
[19:07] <brainwash> xfce4-session pulls in xscreensaver still, so moving light-locker from recommends to depends may be the only way to fix that I think
[19:09] <brainwash> or making xfce4-session recommend light-locker, xscreensaver
[19:10] <brainwash> maybe with xfce4-screensaver this will be solved anyway
[19:12] <brainwash> ali1234: do you still think that my added upstream report is not related? bug 1771227
[20:54] <Unit193> I would be very much against changing recommends to depends.
[20:55] <brainwash> even when light-locker is replaced with xfce4-screensaver?
[20:55] <Unit193> It's just not a depend of the package, so listing it as such isn't accurate.
[20:56] <brainwash> of xubuntu-desktop you mean?
[20:56] <Unit193> xfce4-session, as mantioned.
[20:58] <brainwash> xubuntu-desktop depends on xfce4-session, and xfce4-session recommends xscreensaver | light-locker
[20:59] <brainwash> xubuntu-desktop only recommends light-locker
[20:59] <brainwash> this way xscreensaver is pulled in
[20:59] <brainwash> and later light-locker is installed too
[20:59] <brainwash> when doing apt install xubuntu-desktop
[21:01] <brainwash> making xubuntu-desktop depend on light-locker would solve this, but it's not a nice fix
[21:01] <brainwash> neither is making xfce4-session recommend light-locker | xscreensaver
[21:02] <brainwash> I assume that with xfce4-screensaver both light-locker and xscreensaver could be replaced
[21:03] <brainwash> therefore, solving the issue anyway
[21:03] <Unit193> Arguably that latter change isn't as distasteful as some others, considering what Debian does.
[21:08] <brainwash> what does Debian do?
[21:09] <Unit193> No xscreensaver rec, he finds upstream's attitude very distasteful.
[21:10] <brainwash> no screen locker at all then? or only light-locker?
[21:10] <Unit193> Only light-locker.
[21:11] <brainwash> in that case ubuntu could make it light-locker | xscreensaver
[21:11] <Unit193> Most certainly.
[21:12] <brainwash> okay
[22:54] <pleia2> if there are no objections, I'm going to go ahead and do the free storage upgrade on xubuntu-dev
[22:55] <pleia2> still need to do the 18.04 upgrade (it's 16.04 right now) but I'll need more time for that and should coordinate it so knome can have a look at everything after ;)
[22:56] <Unit193> Coolio, sounds great.
[22:58] <Unit193> Let me know if there's anything I can help with.
[22:58] <pleia2> thanks :)
[23:00] <pleia2> ok, server is migrating now, they say it'll be down for 45 minutes or so
[23:11] <pleia2> Filesystem      Size  Used Avail Use% Mounted on
[23:11] <pleia2> /dev/root        48G  9.0G   36G  21% /
[23:12] <pleia2> and now
[23:12] <pleia2> Filesystem      Size  Used Avail Use% Mounted on
[23:12] <pleia2> /dev/root        79G  9.0G   66G  13% /
[23:12] <pleia2> \o/
[23:12] <pleia2> 45 minutes was conservative ;) it's done
[23:13] <Unit193> Yeah they tend to over estimate.
[23:14] <pleia2> yeah, my personal one took longer than this one because it had a lot more data, but even that didn't take 45 minutes