[01:16] <ximion> robert_ancell: I can likely package it next week, this week and at the weekend I have almost no time
[01:18] <ximion> that quirk stuff is a feature of appstream-glib and has nothing to do with the specification. I could only add a similar feature to the reference implementation, but since it is specified nowhere on how a developer is actually verified, it would just give people yet-another-bitfield that they can easily build themselves in their software center
[01:31] <robert_ancell> ximion, yeah, was wondering if you thought a boolean is sufficient for AppStream or it needs something more. In doing this feature in Ubuntu it really seems you want the verified part to be quite loosely defined because if you make it more complicated it loses its value (everyone ends up verified).
[01:31] <robert_ancell> ximion, I'll email you a diff for the appstream-glib update if you want
[01:32] <ximion> I think I've seen the patch, it doesn't affect the spec at all, only the extra fluff in asglib
[01:33] <ximion> for something in AppStream we would need to define some procedure on how we can actually verify the developer, which is going to be quite hard
[01:33] <ximion> (if not impossible - only a repository could do that, like Flathub or the Ubuntu store, which is out of scope for the AppStream metadata specification)
[01:35] <robert_ancell> ximion, right, this is very much something that comes from the store.
[01:35] <robert_ancell> I guess it must come out of band then.
[01:36] <robert_ancell> The meaning is very much "the store especially trusts this publisher, so you probably should to"
[01:36] <ximion> I could add something to libappstream that makes recording the information in AsComponent possible, but I don't think we can implement this in a way that works for all bundling systems in libappstream
[01:37] <ximion> yes, AppStream knows nothing about stores and stuff - the most it knows is bundle names and package names
[01:38] <robert_ancell> ximion, yeah, does it make sense for a repository to add such a flag when it collates the AppStream data together? An app definitely shouldn't be allowed to set this.
[01:39] <ximion> ah, now I see what you mean
[01:39] <ximion> the answer to that question is yes, maybe
[01:39] <ximion> something like <developer_name trusted="yes">Mozilla</developer_name>
[01:39] <robert_ancell> yes
[01:40] <robert_ancell> To stop someone publishing <developer_name>MOzilla</developer_name> that might confuse users
[01:41] <robert_ancell> (or more likely using obscure unicode to do something similar)
[01:41] <ximion> this will cause quite a bit of trouble when merging metadata though, we need to ensure that trusted flag gets dropped on any merge or data extension
[01:41] <robert_ancell> right
[01:44] <robert_ancell> ximion, I emailed you a patch to update appstream-glib
[01:45] <robert_ancell> I can't do merge proposals to salsa can I?
[01:45] <ximion> you should be able to do merge proposals...
[01:46] <ximion> but I never tested that
[01:46] <ximion> this patch is trivial
[01:46] <robert_ancell> yeah
[01:46] <robert_ancell> it's a pretty small update
[01:46] <ximion> I can't add it before Sunday though, I am travelling the whole day tomorrow and am at a wedding on Saturday, so I'll likely have close to zero time
[01:46] <robert_ancell> Mostly because *someone* added a new entry into a bitfield
[01:46] <robert_ancell> :)
[01:47] <robert_ancell> ok, np
[01:47] <ximion> if this is urgent for you, go ahead and upload the changed package
[01:47] <robert_ancell> ximion, I don't have Debian upload right
[01:47] <robert_ancell> s
[01:48] <ximion> ah, I thought you were DD :P
[01:48] <ximion> anyway, it's almost 4 am here, I really should sleep ;-)
[01:48] <robert_ancell> sorry, yes please do!
[01:48] <robert_ancell> Perhaps Laney is keen to upload, I'll CC him
[03:41] <duflu> RAOF, I've been toying with lowering colour temperatures to expand gamut coverage. Is that what you did? I vaguely recall you like it warm
[03:43] <duflu> Or is that just an accidental consequence of choosing a 6500K white point?
[04:45] <RAOF> That's just a consequence of choosing a 6500K white point.
[06:30] <oSoMoN> good morning desktoppers
[07:25] <seb128> good morning desktop, happy friday!
[07:25] <seb128> lut oSoMoN, en forme ?
[07:30] <duflu> Morning seb128
[07:31] <duflu> wie gehts?
[07:32] <duflu> I am stuck in ongoing bug and code review debates still. Feel like Friday's going nowhere, but if I escape the discussions that will be some progress
[07:33] <duflu> Oh. Morning oSoMoN, also
[07:34] <seb128> hey duflu, happy friday!
[07:35] <seb128> duflu, oh, arguing over what? still commit messages?
[07:36] <duflu> seb128, no, more sensible things like whether A is better than B
[07:37] <seb128> ah, well that's better indeed
[07:38] <seb128> is that still on the input lag thing?
[07:41] <duflu> seb128, No, which is good news
[07:42] <oSoMoN> salut seb128, hey duflu
[07:52] <duflu> mpt, remember that colour profile problem from a year ago? Can you say what type of GPU that was?
[07:55] <mpt> duflu, I’m using the same machine. What command do I use to get the GPU type?
[07:56] <duflu> mpt, Settings > Details should be enough
[07:56] <mpt> Graphics: Intel® 965GM x86/MMX/SSE2
[07:57] <duflu> Ta
[08:02] <Laney> ahoy, happy friday
[08:02] <duflu> Hi Laney. Back atcha
[08:05] <seb128> hey willcooke Laney mpt, how is the island today?
[08:07]  * duflu wonders what the definition of island is
[08:08] <duflu> That's enough wikipedia
[08:08] <mpt> seb128, day 114 of my confinement here. Panic is setting in. There are rumours of food shortages.
[08:08] <Laney> https://en.wikipedia.org/wiki/Alney_Island
[08:08] <Laney> Island within
[08:09] <seb128> mpt, :-)
[08:11] <mpt> Hmm, if someone’s using Livepatch on 18.04 and they’re invited to upgrade to 18.10, do they get told “Hey, you won’t have Livepatch any more”
[08:16] <seb128> mpt, no
[08:18] <seb128> the livepatch page is disabled in the wizard and software-properties UI reflect it's not available iirc but there is nothing warning you directly before/during/after upgrade
[08:19] <willcooke> But you're not "invited" to upgrade to a non-LTS from an LTS though right?
[08:19] <seb128> indeed not, unless you changed the combo option
[08:19] <seb128> which defaults on LTS to "only suggest LTS upgrades"
[08:19] <seb128> in software-properties
[08:19] <Laney> what if you upgraded to that lts from a non-lts?
[08:19] <Laney> does it get set in that case?
[08:20] <seb128> good question, I don't think it changes on upgrade
[08:20] <seb128> it probably depends of the initial install
[08:20] <seb128> which would make sense
[08:21] <seb128> if you install artful and upgrade to bionic then you probably are not wanting to follow the LTS
[08:24] <seb128> well I'm saying that but unsure, probably better to check
[08:24] <seb128> not that it really makes a difference for livepatch
[08:33] <willcooke> So, keyboard aficionados....  I went cheap.  Surprise right?!
[08:33] <willcooke> I got this one:
[08:33] <willcooke> https://www.amazon.co.uk/gp/product/B010IIKHBK/
[08:33] <willcooke> and it's really great!
[08:33] <willcooke> Would recommend it
[08:34] <duflu> Morning willcooke
[08:34] <willcooke> 'lo duflu
[08:34] <willcooke> Happy Friday afternoon
[08:35] <duflu> Looks clicky. I liked clicky till halfway through the 90's then got with the times ;)
[08:36] <willcooke> It is very clicky.
[08:36] <willcooke> It also has 100% anti-ghosting
[08:36] <willcooke> can confirm, no ghosts
[08:37] <duflu> That said, I think I might be going back. Not hipster back to a typewriter, but some audible feedback seems to help the brain
[08:39] <duflu> willcooke, that was fast. How quick is Amazon there?
[08:40] <willcooke> Next day on most prime things
[08:40] <willcooke> There's a big distribution centre in Milton Keynes which is about 30 miles away
[08:40] <willcooke> but even so, most Prime things are next day
[08:40] <willcooke> but an increasing number of things are now 2 day
[08:42] <duflu> Wow. Seems they offer the same to all of Australia now. I am used to everything taking a week (from one side to the other)
[08:44] <duflu> Clearly I'm not with the times any more
[09:02] <willcooke> Get yourself a clicky keyboard, then you'll be cool again
[09:03] <duflu> willcooke, popey, would anyone be able to close this topic for me? I think it's been going too long: https://discourse.ubuntu.com/t/call-for-testing-video-playback-in-18-04
[09:03] <popey> sho thang
[09:04] <popey> done
[09:04] <duflu> Ta
[11:38] <Laney> THUNDER!
[11:44] <ginggs> nananana nana na na
[12:34] <tkamppeter> seb128, I have seen the buid problem of ghostscript. It is ppc64el-only, so how can one debug that? Is this some problem in the upstream code or in the build server?
[12:35] <tkamppeter> seb128, do we have some ppc64el expert who could look after that?
[12:51] <andyrock> Laney: hey, on spare time I tried to update gtk to 3.23.2
[12:51] <seb128> tkamppeter, use a porter box I guess and build there ... I don't know if it's stuck or just taking too long
[12:51] <andyrock> Laney: do you want me to propose it on salsa so you can have a look ?
[12:52] <Laney> hi andyrock, cool, sure!
[12:52] <Laney> there's probably a salsa bit and an LP bit?
[12:58] <andyrock> Laney: I only have the salsa bit for the moment
[12:59] <Laney> okey
[13:10] <tkamppeter> seb128, is ppc64el still important? Is it not some stone-old processor architecture?
[13:18] <andyrock> Laney: changes to salsa proposed, I think it's easier to wait for the debian/3.23.2 tag to be in salsa before starting working on the lp bits right?
[13:18] <Laney> andyrock: you can start to work by merging debian/master and then rebasing or re-merging once it is finalised
[13:19] <andyrock> kk
[13:19] <andyrock> debian/experimental right?
[13:19] <Laney> sure, whichever one you changed
[13:21] <seb128> jbicha, thanks for syncing gnome-bluetooth but that was not needed, I especially opened a bug on launchpad to say that I was going to do it once available, that feels like a bit stealing credit for work other did even if I know that's not the intend
[13:21] <jbicha> seb128: it autosynced
[13:22] <seb128> jbicha, well you closed the bug at least, comment applies still for that
[13:22] <seb128> there is enough to do that you don't need to jump on things being handled by others :)
[13:23] <jbicha> ok I won't touch bug 1786295 then 😐
[13:23] <seb128> thx :)
[13:24] <seb128> jbicha, btw you follow the evo stack more than me, do we want 3.29?
[13:24] <seb128> and do you plan to do those updates? :=
[13:24] <seb128> :)
[13:26] <jbicha> seb128: I did the 3.29 packaging but didn't upload yet because I didn't how to handle a conf file moving from evo to eds
[13:26] <jbicha> /etc/xdg/autostart/org.gnome.Evolution-alarm-notify.desktop
[13:27] <tkamppeter> kenvandine, hi
[13:28] <tkamppeter> kenvandine, I have mailed to doko because of the MIRs now and CCed you. Is there also some other prson in charge of MIRs in the case that doko is off for longer time (vacation, sick, ...)?
[13:29] <kenvandine> tkamppeter, thanks.  Just look at the members of ~ubuntu-mir
[13:30] <kenvandine> didrocks and cyphermox
[13:30] <seb128> tkamppeter, yes, ppc64el is important and it's "current", ppc was old not the 64el version
[13:30] <seb128> didrocks is on holidays for some weeks as well
[13:31] <seb128> jbicha, I'm unsure, I would just have the new binary Replaces the old one and not do anything special to handle the conffile, it's not really a conffile
[13:31] <seb128> well it is but not likely to be worth migrating
[13:32] <andyrock> seb128: does the diff comment here looks correct to you? https://code.launchpad.net/~muktupavels/compiz/ccsm-python3/+merge/351940 https://usercontent.irccloud-cdn.com/file/iP4cmCHf/image.png
[13:33] <jbicha> seb128: ok, I added the breaks/replaces and I'll just otherwise ignore the etc file, uploading now-ish then
[13:34] <seb128> jbicha, thx!
[13:36] <seb128> andyrock, that looks boggus to me, Breaks would be to use if it make the other package not work and usually are versioned, see https://wiki.debian.org/PackageTransition
[13:36] <seb128> andyrock, I would just not do anything in those case and let the old binding around/be autoremoved, unless they stop working with the new version?
[13:36] <jbicha> eds will be going through Debian's NEW queue
[13:36] <seb128> k
[13:57] <tkamppeter> seb128, do we have some ppc64el expert who could know what is happening with the ghostscript build?
[13:58] <seb128> tkamppeter, I don't think so, it's probably something ghostscript is doing, it either takes too long or it's stucked, you probably need to try a build on a porter box and see if's slow or stucked?
[13:58] <seb128> you can also try asking on #ubuntu-devel maybe Steve or someone from foundations has a clue
[14:30] <Laney> jbicha: you can probably rm_conffile it from the old package and pick up the .dpkg-bak file in the new one's preinst if it exists (rename it into place)
[14:30] <Laney> probably needs some kind of ordering relation
[14:51] <jbicha> Laney: hmm, I don't think I'm going to work on that for this case since it's unlikely for people to be making important customizations to that file
[14:51] <Laney> take your chances with the policy gods, I see
[15:43] <seb128> Laney, re udisks2, upstream reproduced and it's a bug in mdadm and they decided to skip the test until it's resolved ("This is a bug in mdadm on s390, it repors 2 "different" UUIDs for the array and it completely confuses udisks"), they also fixed some of the timing flakyness
[15:43] <seb128> xnox, ^
[15:46] <Laney> ah right
[15:46] <Laney> well, thanks for pushing it
[15:52] <seb128> np!
[16:09] <willcooke> Also Thunder!
[16:10] <Laney> 👏
[16:10] <Laney> there was some nice lightning
[16:33] <seb128> jamesh, kenvandine, did you see my ping on https://trello.com/c/T4kwJMKr/14-add-snap-support-to-gnome-builder ?
[16:35] <seb128> willcooke, and you https://trello.com/c/qdOBH0j7/51-talk-to-community-about-migrating-reviews-to-odrs ? ;)
[16:39] <willcooke> thank you seb128
[16:39] <willcooke> I will sort that next week for sure this time
[16:39] <kenvandine> seb128, looking
[16:57] <willcooke> happy weekend everyone
[16:57] <willcooke> see all y'all next week
[17:19] <oSoMoN> seb128, I'm looking at bug #1717926 and it makes sense and looks good, what's the process to ack it and hand it back to the MIR team?
[17:20] <oSoMoN> https://wiki.ubuntu.com/MainInclusionProcess mentions that the MIR team might delegate the decision to a particular team (which they did), but it doesn't say how that team should acknowledge
[17:22] <Laney> oSoMoN: looks like desktop-bugs is already subscribed, so probably a comment and fixing the status is good enough
[17:22] <Laney> and on that, night, happy weekend
[17:22] <oSoMoN> Laney, status back to "New" ?
[17:23]  * oSoMoN just installed debian stable in a VM, hadn't done that in ages
[17:23] <oSoMoN> the installer doesn't offer my keyboard layout by default, meh
[17:45] <oSoMoN> have a great week-end everyone!