[02:37] <callmepk> good morning
[06:30] <didrocks> good morning
[06:30] <oerheks> oui
[06:31] <oSoMoN> good morning desktoppers
[06:32] <didrocks> salut oSoMoN 
[06:33] <oSoMoN> salut didrocks, ça va?
[06:40] <didrocks> oSoMoN: petites nuits, mais ça va, et toi ?
[06:41] <oSoMoN> didrocks, ça va, beaucoup bricolé et jardiné ce week-end, pour changer :)
[07:04] <marcustomlinson> morning desktoppers
[07:04] <oSoMoN> morning marcustomlinson, how are you?
[07:06] <marcustomlinson> hey oSoMoN, doing alright thanks, regular 2 day weekend’s are lame though :P you?
[07:07] <didrocks> hey marcustomlinson 
[07:08] <oSoMoN> marcustomlinson, I completely agree, that week-end felt short :) I'm pretty good otherwise
[07:08] <marcustomlinson> hey didrocks, how things?
[07:10] <didrocks> short nights, but good, thanks, and you?
[07:11] <marcustomlinson> similar answer ;)
[07:44] <pieq> hey desktoppers! On my 18.04 desktop, I often had issues with the Ubuntu Dock extension when I was maximizing windows: the dock was supposed to appear when I put my cursor on the left side of the screen, but after a while it wouldn't.
[07:44] <pieq> I upgraded to 20.04 and I'm still facing the same issue. I saw in GNOME Extensions that Ubuntu Dock points to this URL: https://micheleg.github.io/dash-to-dock/
[07:44] <pieq> should I raise a bug there?
[07:44] <pieq> (restarting the extension using GNOME Extensions fixes the problem)
[07:53] <didrocks> pieq: hey! yes, this is the upstream repo
[07:54] <pieq> didrocks, thanks for the confirmation!
[08:02] <Laney> \o o/ \o o/
[08:07] <oSoMoN> hey ho Laney 
[08:07] <didrocks> hey hey Laney 
[08:14] <Laney> lo oSoMoN & didrocks 
[08:24] <marcustomlinson> hey Laney
[08:34] <Laney> ahoy marcustomlinson 
[08:47] <luna_> Updating to the Alpha of the Gorilla now :)
[09:36]  * marcustomlinson wonders if groovy gorilla will be borrowing disco's headphones
[09:45] <Laney> right :(
[09:45] <Laney> now I've done all the other commits in britney, I've just got the hardest one left
[09:45]  * Laney saved the best for last
[09:45] <Laney> "Add autopkgtest policy"
[09:49] <luna_> On the testing branch of the Gorilla now
[09:49] <Laney> think I'll do this manually without cherrypicking
[09:49] <Laney> oh my monitor just turned off
[09:56] <Laney> bzzt-ing noises, not at all concerning, but it came back on ...
[10:24] <didrocks> it did it to me last week and then, making horrible noises
[10:24] <didrocks> I changed it
[10:26] <Laney> hopefully the power cord was just a bit loose
[10:26] <Laney> was fiddling with it yesterday
[10:29] <didrocks> crossing fingers :)
[13:58] <kenvandine> yikes... gtk-common-themes in candidate is broken
[13:58] <kenvandine> -./share/themes/Yaru
[13:58] <kenvandine> +./share/themes/YaruFlavours
[13:59] <kenvandine> whew... Yaru fixed it this morning :)
[13:59]  * kenvandine rebuilds
[14:14] <oSoMoN> Laney, I've verified that a no-change rebuild of gdk-pixbuf would fix the failing autopkgtests (https://trello.com/c/lS5l2kyo/180-gdk-pixbuf-autopkgtest-failing), would you mind uploading that for me, when you have a moment?
[14:16] <Laney> oSoMoN: can do, do you have a changelog entry that explains why that works?
[14:18] <oSoMoN> Laney, unfortunately not. All I know is that rebuilding gdk-pixbuf-tests is sufficient. The resources embedded in the test binaries in that package appear to be incomplete (missing ICC profile in PNG images for example), but I haven't determined why that is
[14:20] <oSoMoN> I mean, maybe the above explanation would suffice for a changelog entry?
[14:20] <Laney> yeah sounds good
[14:44] <Laney> oSoMoN: just test building / testing to verify this, will upoad if good
[14:44] <oSoMoN> Laney, thanks!
[14:48] <Laney> indeed, it works!
[14:48] <Laney> what a world we live in
[14:49] <oSoMoN> :)
[15:00] <hellsworth> good morning desktopers
[15:03] <oSoMoN> morning hellsworth 
[15:03] <hellsworth> hi there oSoMoN 
[15:09] <didrocks> good morning hellsworth 
[15:09] <hellsworth> hi there didrocks 
[15:14] <Laney> hmm
[15:14] <Laney> not sure we should be optipnging those images in gdk-pixbuf's installed tests
[15:15] <Laney> hope that's not the actual problem (I have that turned off for local builds)
[15:15] <Laney> hey hellsworth 
[15:16] <hellsworth> moin Laney 
[15:18] <tsimonq2> Laney, et al.: In case someone finds it useful, I recently wrote a Jenkins policy for Britney2: https://phab.lubuntu.me/source/britney2-ubuntu/browse/master/britney2/policies/jenkinspass.py
[15:31] <oSoMoN> Laney, is this optimization also turned off by default for PPA builds?
[15:32] <Laney> not sure, you can see it acting at the end of builds
[15:32] <Laney> ah yeah, this sucks, it fails now
[15:33] <oSoMoN> darn, it looks like it's disabled for PPA builds indeed
[15:34] <oSoMoN> so I got the problem the other way around: it's not the resources in the test binaries that lack metadata, it's the png files in the test package
[15:35] <Laney> it was your comment which made me go "hmm" when I saw it in the build log
[15:35] <Laney>     # also skip when disabling explicitly
[15:35] <Laney>     if [ -n "$NO_PNG_PKG_MANGLE" ]; then
[15:35] <Laney> 	echo "pkgstripfiles: Disabled PNG optimization for package $PKGNAME."
[15:35] <Laney> 	return
[15:35] <Laney>     fi
[15:35] <Laney> we need that I think
[15:37] <oSoMoN> right
[15:38] <oSoMoN> Laney, want me to prepare the debdiff, or are you taking care of it?
[15:40] <Laney> oSoMoN: I'll do it, can be uploaded to unstable
[15:40] <oSoMoN> thanks
[17:07] <ahasenack> oSoMoN: hi, still around?
[17:24] <oSoMoN> ahasenack, yes, what's up?
[17:25] <ahasenack> oSoMoN: hi, just sent you an email about it
[17:27] <oSoMoN>  ahasenack: I touched it out of necessity (firefox required a newer version to build), but I'm neither particularly familiar with it, nor really keen on investing the time
[17:28] <oSoMoN> ahasenack, that said I have backported 12.16.1 to xenial, bionic and eoan (https://launchpad.net/ubuntu/+source/nodejs-mozilla), so I don't expect getting it into groovy would be very difficult
[17:30] <ahasenack> except for the migration :D
[17:31] <ahasenack> thanks for that ppa, that is a good starting point
[18:56] <KGB-1> orca pristine-tar 5e8ad9f Samuel Thibault orca_3.36.3.orig.tar.xz.delta orca_3.36.3.orig.tar.xz.id * pristine-tar data for orca_3.36.3.orig.tar.xz * https://deb.li/3GOen
[18:56] <KGB-1> orca upstream/latest cde6835 Samuel Thibault * pushed 1 commits * https://deb.li/3UXEs
[18:57] <KGB-1> orca tags 411eaac Samuel Thibault upstream/3.36.3 * Upstream version 3.36.3 * https://deb.li/3oRn
[19:23] <KGB-1> orca upstream/stable 32552f7 Samuel Thibault * Merge branch 'upstream/latest' into upstream/master * https://deb.li/3rRDA
[19:46] <KGB-1> orca pristine-tar 0d78001 Samuel Thibault orca_3.37.2.orig.tar.xz.delta orca_3.37.2.orig.tar.xz.id * pristine-tar data for orca_3.37.2.orig.tar.xz * https://deb.li/CpBy
[19:47] <KGB-1> orca upstream/beta 32552f7 Samuel Thibault * Merge branch 'upstream/latest' into upstream/master * https://deb.li/3rRDA
[19:47] <KGB-1> orca upstream/beta 9b0ce1e Samuel Thibault (22 files in 6 dirs) * New upstream version 3.36.3 * https://deb.li/3cRh4
[19:47] <KGB-1> orca upstream/beta 521da94 Samuel Thibault * Merge branch 'upstream/beta' into upstream/stable * https://deb.li/6l3M
[19:47] <KGB-1> orca upstream/beta 9d84a12 Samuel Thibault (133 files in 28 dirs) * New upstream version 3.37.2 * https://deb.li/iwecj
[19:47] <KGB-1> orca upstream/beta 4b92601 Samuel Thibault * Merge branch 'upstream/stable' into upstream/beta * https://deb.li/KljA
[21:45] <hellsworth> why is it that 'sudo do-release-upgrade' on an 18.04 system says No new release found... 20.04 has been released for some time now so this should be seen, no?
[21:46] <hellsworth> will just have to update sources.list then..
[21:48] <sarnold> hellsworth: use -d
[21:49] <hellsworth> but that will update to the latest dev release, groovy and I don't want that
[21:49] <sarnold> hellsworth: I'm 90% sure it won't do that -- and it'll give you a chance to say yes / no
[21:50] <hellsworth> hmm well next time since i've already got the update going.. but then how would one update to groovy? -d should be for the development release.. i know this is how i updated to 20.04 *before* it was released..
[21:51] <sarnold> hellsworth: if that 90% guess is correct, to get from bionic to groovy requires do-release-upgrade -d *twice* -- once to upgrade to focal, again to upgrade to groovy
[21:51] <RikMills> !ltsupgrade
[21:52] <hellsworth> aaah ok it makes sense now. thank you both sarnold and RikMills for the combined answer :)
[21:52] <RikMills> https://changelogs.ubuntu.com/meta-release-lts-development
[21:52] <RikMills> says focal is still latest LTS dev release
[21:53] <RikMills> so if you are on LTS only upgrades, I guess you can't go beyond focal
[21:53] <sarnold> hellsworth: depending upon how strongly you feel, a comment on https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1875522 might be nice :)
[21:54] <RikMills> it would be nice if there was a non -d way to force it for those that want to
[21:54] <RikMills> would certainly be less confusing for all
[21:58] <hellsworth> right i completely agree.. just read through the bug and will add my opinion :)