[01:08] <Trevinho> duflu: hey, i've pushed your xwayland patch for now, adding to the stable branch too
[01:08] <Trevinho> duflu: I suggest you to use git-bz though https://wiki.gnome.org/Git/WorkingWithPatches though
[01:20] <duflu> Trevinho, thanks, yeah I looked in the archive and didn't find it
[01:21] <Trevinho> duflu: just grab this
[01:21] <Trevinho> http://git.fishsoup.net/cgit/git-bz/plain/git-bz
[01:21] <Trevinho> chmod +x in your local path and that's it
[01:23] <duflu> Trevinho, also this week is crazy busy. I'm not inclined to try many new things as much as just trying to keep up
[01:34] <jbicha> I think I'm going to eventually package git-bz in Debian
[01:39] <duflu> Cool. Although, wasn't Gnome moving off BZ?
[01:39] <duflu> Or was that something else?
[01:45] <jbicha> yes, they're probably moving to gitlab.gnome.org eventually (maybe next year?)
[01:46] <jbicha> I believe you can still use git-bz with other sites like freedesktop.org
[06:08] <oSoMoN> good morning desktoppers, and happy Friday!
[06:14] <duflu> Morning oSoMoN
[06:15] <oSoMoN> hey duflu
[06:44] <didrocks> good morning!
[07:07] <duflu> Morning didrocks
[07:07] <duflu> RAOF: Is it theoretically possible a 10-bit monitor has longer gamma ramps?
[07:07] <duflu> I think it would
[07:07] <doko> oSoMoN: I cancelled the LO builds on arm*, will ftbfs anyway due to new debhelper (see https://launchpad.net/ubuntu/+source/libreoffice/1:5.4.1-0ubuntu2/+build/13620400)
[07:08]  * duflu is wondering if Gnome's default colour profiles might therefore be truncated
[07:11] <didrocks> hey duflu!
[07:11] <duflu> Hey hey
[07:11] <duflu> hey
[07:12] <RAOF> duflu: gamma ramps are a property of the GPU rather than the display.
[07:14] <RAOF> You could have a larger LUT for a 10-bit framebuffer, but you wouldn't need to.
[07:14] <duflu> RAOF: Just trying to find reasons why the default Gnome profile messes up colour (best to turn it OFF). All without devoting time to further debugging
[07:15] <duflu> Maybe that shouldn't be surprising. If it's a profile at all, it's likely nonlinear
[07:15] <RAOF> duflu: do you have redshift on? 😀
[07:15] <duflu> RAOF: No. Also the problem is identical in Unity7 on 16.04
[07:16] <RAOF> The default profiles don't do any display correction.
[07:16] <duflu> Or shouldn't
[07:16] <duflu> But they do
[07:16] <RAOF> Well, they literally don't have display correction data in them, so...
[07:17] <duflu> RAOF: Interesting. OK I have too many other bugs to deal with. Let's drop this and say happy EOW for you
[07:17] <RAOF> 😀
[07:45] <oSoMoN> doko, ack
[07:46] <seb128> good morning desktopers
[07:47] <seb128> (doh, that needs to be auth mode, my client failed to join the channel again this morning, I just noticed)
[07:54] <sil2100> hm, since when is this channel +r?
[07:55] <oSoMoN> good morning seb128
[07:56] <jamesh> sil2100: I think someone was flooding it earlier.  The flag could probably be turned off again
[07:57] <seb128> hey oSoMoN jamesh sil2100, happy friday!
[07:58] <seb128> was that the right way (-r)?
[08:00] <willcooke> morning all
[08:00] <didrocks> I think so
[08:00] <didrocks> hey willcooke
[08:03] <oSoMoN> morning willcooke
[08:03]  * didrocks tries sasl auth
[08:04] <seb128> hey willcooke
[08:06] <duflu> Morning seb128, willcooke
[08:06] <seb128> hey duflu
[08:07] <didrocks> sasl works at least, so you can autojoin channels once you are authenticated
[08:07] <duflu> And good afternoon jamesh
[08:07] <duflu> Also sil2100, how goes it?
[08:08] <duflu> Oh and alan_g, morning
[08:08] <alan_g> duflu: o/
[08:10] <duflu> o\   (upside down)
[08:11] <duflu> Hmm, can I assume my upstream mutter fixes will just arrive in 18.04 soon enough? (no need to distro patch)?
[08:22] <willcooke> duflu, oh, did they get accepted?
[08:22] <duflu> willcooke, one landed, another is about to
[08:22] <willcooke> nice!
[08:22] <willcooke> congrats
[08:26] <sil2100> Morning!
[08:26] <sil2100> duflu: not bad, how about you?
[08:27]  * sil2100 yesterday switched to a new laptop + artful and is pretty happy with his new desktop
[08:27] <duflu> sil2100, dazed but about to hit the weekend. Unfortunately that's already overbooked and not fun
[08:30] <oSoMoN> seb128, I haven't started on the LO 5.4.2 SRU paperwork, wondering if we have some previous examples that I could follow? (I couldn't find any recent one when I went through the LO bugs)
[09:04] <doko> who is supposed to care about the touch/unity related packages (those ftbfs at http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.65.html)
[09:25] <oSoMoN> popey, can you recommend a lightweight snap app that uses opengl, for testing purposes?
[09:26] <popey> ohmygiraffe! :D
[09:27] <oSoMoN> thanks!
[09:28] <oSoMoN> it might be interesting to snap glxgears for diagnosis purposes
[09:29] <popey> ohmygiraffe is way more fun than glxgears :D
[09:40] <sil2100> doko: uh oh, I'll try looking at those in a minute if no one else volunteers
[09:40] <seb128> oSoMoN, not that I know offhand, but just open a bug about "update to 5.4.2" and copy the NEWS ... is there a testplan for libreoffice which can be used for the test case?
[09:43] <oSoMoN> seb128, there's the autopkgtest, and I usually do a fair bit of smoketesting, I'll inquire if there's a written testplan
[09:44] <andyrock> seb128: hey hey
[09:45] <andyrock> seb128: did you see the patch I proposed for that OEM bug?
[09:53] <seb128> hey andyrock
[09:53] <seb128> andyrock, not yet, did you subscribe me? let me have a look
[09:53] <andyrock> https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1716359
[09:57] <seb128> andyrock, thanks
[09:58] <andyrock> so, in the last two comments I explain my opinion about the bug
[09:58] <andyrock> let me know what do you think
[09:58] <andyrock> if you agree I can also try to propose the same fix to g-c-c upstream
[09:58] <andyrock> it's harder to reproduce
[09:58] <andyrock> but because it's a race condition
[09:59] <seb128> duflu, ^ can you maybe give feedback on that change from andyrock? it's around sound/pulseaudio and you might have some insight on why things are done the way they are and if the change sounds correct
[09:59] <seb128> andyrock, +1 for proposing upstream
[10:02] <duflu> seb128, saw it this morning but no familiarity
[10:02] <duflu> Sorry
[10:02] <duflu> Night
[10:13] <andyrock> seb128: also for livepatch we need https://github.com/go-macaroon-bakery/py-macaroon-bakery in main
[10:13] <andyrock> my plan is to start from Bionic
[10:14] <andyrock> I can try to package it but I'm not so good in that :D
[10:19] <seb128> andyrock, let me know if you need help with the packaging
[10:19] <andyrock> sure thing
[10:19] <andyrock> I'll propose the g-c-c patch upstream and then I'll start packaging it
[10:20] <andyrock> seb128: I'm not sure how to deal with the fact that it's in github
[10:20] <andyrock> if I just have to create the debian directory in launchpad
[10:21] <andyrock> or if I need to create a new branch in launchpad
[10:21] <andyrock> or if I can do everthing in github
[10:21]  * andyrock is confused
[10:25] <seb128> andyrock, what is in github?
[10:26] <seb128> oh, the new package
[10:26] <andyrock> the code
[10:26] <seb128> that doesn't make a different, we package from tarballs
[10:26] <andyrock> kk
[10:26] <andyrock> I'll take a look
[10:26] <seb128> you don't need to have the debian dir in the vcs
[10:26] <seb128> most packages don't
[10:26] <seb128> (e.g GNOME)
[10:26] <andyrock> sorry but after 6/7 years here this is my first deb :D
[10:46] <seb128> andyrock, it's never too late :-)
[11:49] <andyrock> seb128: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1716359
[11:49] <andyrock> let me know if I need to do something more
[11:49] <andyrock> I'm testing the fix on g-c-c and I will propose a patch before lunch
[14:41] <seb128> andyrock, the SRU bug/code changes look good thanks! the SRU is probably not going to be accepted on a friday afternoon but we should be good for monday :-)
[14:41] <andyrock> seb128: np!
[14:41] <andyrock> I'll keep listening music to test the change :P
[14:42] <seb128> ahah
[14:57] <oSoMoN> seb128, I've filed bug #1728072 for the LO SRU, and packages are ready in https://launchpad.net/~osomon/+archive/ubuntu/lo-test/+packages
[14:57] <oSoMoN> seb128, can you push them to -proposed ?
[14:58] <seb128> oSoMoN, sure
[14:58] <seb128> oSoMoN, well, I can upload to the queue rather, I can't approve to proposed since I'm not in the SRU team
[14:59] <seb128> oSoMoN, the SRU bug looks good
[15:00] <oSoMoN> seb128, yeah, I meant to the queue, of course!
[15:00] <seb128> :-)
[15:03] <oSoMoN> seb128, the only gotcha is that the changelog doesn't have a reference to the SRU bug since I build the packages before filing the bug, I can amend that if you think the SRU team will dislike it
[15:11] <jbicha> oSoMoN: next time I recommend filing a stub bug to put in your changelog and you can fill in the bug's details later
[15:13] <oSoMoN> jbicha, yes, I should have done that
[15:44] <andyrock> seb128: should I propose pymacaroonbakery in debian buster before?
[15:44] <andyrock> what's the normal workflow?
[15:46] <jbicha> is there a Debian team to maintain that kind of stuff?
[15:47] <andyrock> not sure
[15:47] <jbicha> I'm uploading snapd-glib under the pkg-ayatana umbrella soon
[15:48] <seb128> oSoMoN, if that's not too much work for you, otherwise I think I can just edit the .changes (but then it doesn't match the changelog)
[15:49] <seb128> oSoMoN, the issue is that without bug reference http://people.canonical.com/~ubuntu-archive/pending-sru.html has no entry and they can't see that it was verification-done and those SRUs tend to sit there then
[15:49] <seb128> andyrock, it doesn't hurt to propose in Debian
[15:49] <andyrock> kk
[15:49] <oSoMoN> seb128, yes, I'm rebuilding a source package with the bug reference in the changelog as I write
[15:50] <oSoMoN> will have it ready for you to upload soon
[15:51] <seb128> oSoMoN, thanks
[16:06] <oSoMoN> ricotz, thanks for addressing bug #1725238 !
[16:07] <ricotz> oSoMoN, np :)
[16:08] <ricotz> doko, oSoMoN, did you check if this is really a no-change rebuild? https://launchpad.net/ubuntu/+source/libreoffice/1:5.4.1-0ubuntu2
[16:09] <ricotz> chrisccoulson, thanks for cargo 0.22, do you have an eta for rust 1.21?
[16:09] <oSoMoN> I didn't
[16:10] <oSoMoN> ricotz, why wouldn't it be a no-change rebuild?
[16:10] <ricotz> oSoMoN, the errors seems to suggest it isn't, e.g. some altered debian/control
[16:10] <ricotz> or some debhelper change is triggering it
[16:11] <andyrock> seb128: upstream suggested me a fix for the patch of the oem bug
[16:12] <andyrock> I'll try to suggestion and update the MPs
[16:15] <oSoMoN> ricotz, doko mentioned a debhelper change this morning, indeed
[16:18] <seb128> andyrock, great!
[16:19] <ricotz> oSoMoN, so a debhelper bug?
[16:21] <oSoMoN> ricotz, I don't know if it's a bug in debhelper or something that will need addressing in the LO packaging, need to look into it
[16:21] <oSoMoN> but that will have to wait till Monday
[16:21] <ricotz> oSoMoN, ok, will blindly push a 5.4.3~rc1 rebuild :\
[16:28] <oSoMoN> seb128, updated source packages ready at https://people.canonical.com/~osomon/libreoffice-5.4.2/
[16:29] <ricotz> oSoMoN, ok, looks like a lo packaging problem indeed
[16:33] <oSoMoN> you figured it out already? great :)
[16:38] <chrisccoulson> ricotz, not yet, there's quite a few new test failures that I'm investigating at the moment
[16:38] <ricotz> oSoMoN, not really, but the error is logical and valid, I assume it wasn't fatal before
[16:39] <ricotz> chrisccoulson, great
[16:39] <chrisccoulson> one of the test failures is fairly bad too
[16:41] <ricotz> I see, looks like debian is ignoring the test-suite now, which seems problematic
[16:41] <chrisccoulson> they've effectively unimplemented target_feature when using the system llvm, and there's a lot of conditionally compiled code in firefox that uses that
[16:41] <ricotz> note, that ff57 ppc64el builds now
[16:41] <chrisccoulson> yeah, ignoring the test failures isn't an option. You may as well just not run them
[16:51] <ricotz> oSoMoN, jfyi, this will require numerous changes to get it fixed
[16:54] <oSoMoN> ricotz, ack, do you know if that has already been addressed in debian?
[16:55] <ricotz> oSoMoN, _rene fixed one case locally, will try to get to the other ones
[16:56] <ricotz> I want to get a 6.0 build on bionic ;)
[16:56] <seb128> oSoMoN, thanks
[16:56] <seb128> on that note callin it a week
[16:56] <seb128> have a nice w.e desktopers
[16:57] <willcooke> you too seb128
[16:57] <willcooke> also heading out
[16:57] <willcooke> night all
[17:00] <oSoMoN> seb128, have a good one!
[17:05] <andyrock> seb128: patch updated!
[17:05] <seb128> andyrock, thanks
[17:05] <seb128> and on that note nice w.e
[17:05] <seb128> see you on monday
[17:56] <oSoMoN> I'm off too
[17:56] <oSoMoN> have a good week-end everyone!
[18:15] <Saviq> huh, so I don't have a menu bar in quasselclient (Qt IRC app, if anyone's not familiar), any ideas?
[18:33] <ladd> hello
[18:34] <ladd> I could use some help installing an epson xp-420 printer
[18:39] <flocculant> ladd: hi there - this isn't actually a support channel, try #ubuntu
[18:40] <ladd> ok np thanks
[18:41] <flocculant> cheers
[21:13] <ricotz> chrisccoulson, please update the embedded libgit2 to 0.26.0 in cargo