[01:31] <sarnold> bdmurray: polite poke re https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738581  :)
[05:46] <slangasek> nacc: enabled> ugh.  I'd say there are no good interfaces here, and it'll be hard to implement this in a way that won't break once things start to move to systemd (not necessarily in tandem)
[10:14]  * xnox wonders if i am back on irc
[10:15] <Odd_Bloke> xnox: You appear to be.
[10:16] <xnox> whoop whoop
[10:17] <Unit193> Nah, you aren't, xnox.
[11:06] <juliank> I don't entirely understand MoM's days old. For example, wpa's Oct 2017 upload was merged, but it says 326 days old
[11:09] <cjwatson> I believe it's supposed to be the date on which it was superseded - i.e. the creation date of the first Debian source publication with a higher version
[11:13] <juliank> cjwatson: hmm, there was a newer version in experimental before that, amybe it picked thatu p
[11:13] <juliank> jbicha: Seems we can sync libsecret now? gjs is back on s390x, and you pushed the disable vala & python there patch to Debian
[11:19] <rbasak> I think MoM only sees unstable, not experimental.
[11:19] <rbasak> Even if Ubuntu is synced to experimental.
[11:19]  * rbasak is guessing
[11:20] <jbicha> juliank: yes
[11:20] <juliank> jbicha: ok, done.
[11:27] <cjwatson> rbasak,juliank: mm, except there is a bug here.
[11:27] <cjwatson> at least arguably
[11:32] <cjwatson> juliank: fixed for the next run, fingers crossed.  http://bazaar.launchpad.net/~ubuntu-core-dev/merge-o-matic/trunk/revision/303
[11:32] <juliank> cjwatson: awesome!
[11:35] <rbalint> lool: do you mind if i merge flash-kernel from unstable?
[11:36] <juliank> oh, it's about time for that one :)
[11:36] <juliank> 3.0~rc.4ubuntu66
[11:37] <rbalint> juliank: i figured no one wanted touch it :-)
[11:38] <juliank> I wonder if I should have a go at wpa
[11:39] <juliank> ^ mostly mdeslaur 's playground :)
[11:39] <rbalint> juliank: it is a desktop package, so i'm trying to fix foundations ones first
[11:40] <juliank> There aren't many _good_ ones left :D
[11:41] <juliank> Oh coreutilsmight be nice
[11:42] <juliank> strace is blocked on 3 broken tests, I should figure out why they're broken. ugh.
[11:49] <juliank> We should add some classes and javascript to the MoM output so we can filter out the green and gray stuff, and perhaps a search thingy, that would be nice.
[11:52] <rbalint> juliank: i'd prefer a way different strategy, driving the outstanding merges so low that we should not care about the filtering :-)
[11:53] <juliank> that works too
[11:53] <juliank> I already took out 4 of them today so far
[11:53] <juliank> two on monday, two more queued in a ppa
[11:53] <juliank> and what, 7 or 8 last week?
[11:53] <rbalint> juliank: great! :-)
[11:54] <juliank> My bionic is a bit unstable. From time to time, it does not register clicks
[11:54] <juliank> only for like 5 seconds, then it works again
[11:55] <juliank> using the X session :D
[12:05] <mdeslaur> juliank: I'm not a wpa expert, go ahead if you feel like it!
[12:25] <willcooke>  juliank hey!  Re: mouse clicks, could it be this?  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1181666
[12:42] <juliank> willcooke: sounds like it
[12:43] <juliank> willcooke: though for me it's only temporary and solves itself
[12:59] <willcooke> juliank, I think soving itself is in keeping with what duflu is saying.
[12:59] <willcooke> I'll follow up with him and see whats going on there
[13:04] <rbalint> pitti: i'm looking at merging procps from unstable if you don't mind
[13:04] <pitti> rbalint: sure, go ahead; I don't have taps on anything right now
[13:10] <lool> rbalint: absolutely not, would love if you would
[13:25] <rbalint> pitti, lool: thanks, taking them then
[14:09] <juliank> apw: if you don't mind I'll have a go at merging cryptsetup
[14:11] <juliank> apw: Though I don't quite understand why you did all these changes like dropping c99, they seem pointless to me.
[14:11] <juliank> oh, that might just be wrongly indented changelog
[14:12] <juliank> xnox: seems you made the _BSD_SOURCE => _DEFAULT_SOURCE, removal of -std=c99 changes in cryptsetup. May I ask why? seems like a useless diff
[14:13] <juliank> * last year in August
[14:14] <xnox> juliank, because the new world order is c11; and it FTBFS; _BSD_SOURCE no more; it's _DEFAULT_SOURCE now
[14:14] <juliank> It FTBFS due to std=c99?
[14:14] <xnox> no, it's just std=c99 used be higher than the default standard; now it's lower than the default standard; and hence I upgraded to c11.
[14:15] <xnox> and _BSD_SOURCE was tripping up the preprocessor i believe.
[14:15] <juliank> #define _GNU_SOURCE
[14:15] <juliank> #define _BSD_SOURCE
[14:15] <juliank> #define _POSIX_C_SOURCE 1
[14:15] <xnox> yes
[14:15] <juliank> that's what Debian uses now....
[14:15] <xnox> well, that's nuts =)
[14:15] <juliank> seems more complicated than yours :D
[14:15] <juliank> "Oh, let's see what we can add to make it compile"
[14:16] <xnox> juliank, i'm all for dropping delta's and going with whatever debian has, on the grand scheme of things, this is marginally irrelevant.
[14:16] <xnox> juliank, i hope they have dropped c99, or have they not?
[14:16] <juliank> xnox: No they have not.
[14:16]  * xnox ponders if _DEFAULT_SOURCE works on kfreebsd and hurd
[14:16] <xnox> maybe i should forward them a patch, but not sure if i care about these thigns.
[14:16] <juliank> xnox: But the thing is, it could be a mere statement that this is supposed to be C99
[14:17] <juliank> Not neccessarily for technical reasons
[14:17] <xnox> i think it would fail to compile with 89
[14:17] <xnox> cause it actually relied on c99
[14:17]  * xnox that's from memory
[14:18] <juliank> xnox: They also pass -pedantic though, so they kind of have to pass -std=c99 or something, as gnu99 or gnu11 is not pedantic enough :D
[14:20] <juliank> I don't think you even need _DEFAULT_SOURCE in gnu11 mode
[14:20] <juliank> But since this is debian/-only, I wonder anyway why they want to build in ISO C mode
[14:47] <rbasak> sil2100: any idea what's going on with bug 1718824 and pulseaudio in Xenial genreally?
[14:47] <rbasak> For example publishing history https://launchpad.net/ubuntu/+source/pulseaudio/+publishinghistory for 1:8.0-0ubuntu3.5
[14:48] <rbasak> I see no SRU process comments in the bug
[14:48] <rbasak> But you've been involved, I think
[14:48] <rbasak> And there is stuff in the queue.
[14:52] <sil2100> rbasak: hm, I don't know anything about this sadly
[14:52] <sil2100> rbasak: I don't remember being involved in this bug, but maybe my memory is just wrong?
[14:52] <rbasak> I don't see your involvement in the bug specifically.
[14:52] <rbasak> But I saw you in publishing history for  1:8.0-0ubuntu3.7
[14:57] <sil2100> I did some publishing of it in the past indeed, let me take a look at what's in this SRU
[15:42] <nacc> slangasek: ok, for context, LP: #1740892
[20:28] <juliank> cjwatson: The MoM change seems to have worked well :)
[20:29] <juliank> Better merge prioritisation possible :D
[21:51] <tsimonq2> Speaking of MoM, now that I know where the source code is and I'm remembering to do it: https://code.launchpad.net/~tsimonq2/merge-o-matic/increase-graph-size/+merge/336265
[21:51] <tsimonq2> :D
[21:52] <juliank> +1
[21:54] <tsimonq2> juliank: Could you merge it then? You're a Core Developer ;)
[21:58] <juliank> tsimonq2: merged
[21:59] <juliank> tsimonq2: not sure if it needs somebody to update some infra or not
[22:01] <tsimonq2> Good point. cjwatson?
[22:04] <juliank> I should add search filter javascript stuff
[22:05] <tsimonq2> +1
[22:05] <juliank> and of course make MoM useful for non-native packages by using unapplied patches states
[22:05] <juliank> * more useful
[22:07] <tsimonq2> YES
[22:07] <tsimonq2> That annoys me SO MUCH
[22:07]  * tsimonq2 slides juliank a preemptive cold one
[22:08] <tsimonq2> (er, maybe not the right word, you get it :) )
[22:10] <juliank> tsimonq2: it's not that easy it seems
[22:10] <juliank> or it should be
[22:11] <tsimonq2> juliank: Right, it might involve some tweaking irt patches.ubuntu.com
[22:11] <tsimonq2> afair it grabs the patches from there and then applies them
[22:17] <juliank> tsimonq2: https://code.launchpad.net/~juliank/merge-o-matic/skip-patches/+merge/336267
[22:18] <juliank> tsimonq2: it generates patches.ubuntu.com
[22:18] <juliank> AFAICT
[22:19] <tsimonq2> oh
[22:20] <tsimonq2> juliank: lgtm (although I'm not a ~core-dev so you'll have to merge it yourself :) )
[22:21] <juliank> I'll leave that up to someone who knows what they're doing
[22:22] <tsimonq2> Ok
[22:22] <nacc> slangasek: infinity: when there is a buggy prerm of a package, is there any pattern established for how to handle that in a fix? In this case, it's corosync, where the old package's prerm stops corosync, which ends up stopping pacemaker, and nothing currently starts pacemaker back up. I don't know of a way to determine in the postinst (when using --restart-after-upgrade to dh_installinit) that
[22:22] <nacc> pacemaker was running when the old prerm ran.
[22:24] <nacc> my initial stab tried to use /etc/init.d/pacemaker status in the init script, but that's run from the postinst, which means pacemaker is in the stoppe state
[22:35] <cjwatson> juliank,tsimonq2: deployed MoM r305
[22:36] <tsimonq2> cjwatson: ack, many thanks
[22:37] <tsimonq2> cjwatson: How often does cron run there?
[22:37] <cjwatson> tsimonq2: 05,35 * * * *   /srv/patches.ubuntu.com/code/cron.daily
[22:37] <cjwatson> though that's subject to locking
[22:38] <juliank> cjwatson: Opinions on https://code.launchpad.net/~juliank/merge-o-matic/skip-patches/+merge/336267 welcome too, if you have time :D
[22:38] <cjwatson> not tonight I'm afraid
[22:39] <juliank> cjwatson: no problem :)
[22:40] <tsimonq2> cjwatson: thanks
[23:09] <juliank> tsimonq2: big graphs look better, yeah
[23:09] <juliank> :D
[23:09] <juliank> latest merge page has them now
[23:10] <tsimonq2> I saw :D