[02:38] <jbicha> rbasak: I don't think I have anything additional to add for the ostree SRU bug. I know that Ken wanted to see flatpak 1.0 get into Ubuntu 18.04 LTS archives after it's released
[08:08] <sil2100> rbasak: hey! The letsencrypt xenial SRU is stalled since over 300 days now, with some build failures blocking it (+ lack of verification)
[08:09] <sil2100> rbasak: LP: #1640978
[08:09] <sil2100> rbasak: that's a lot of packages that would be a waste to just remove, but if no movement happens in this area I'll have to do that
[08:10] <sil2100> rbasak: the developer raised concerns that the update is still needed, so that would be a shame
[13:12] <xubuntu000> hey all. pulseaudio 12 has been available for several weeks now and it has some much needed patches
[13:13] <xubuntu000> currently the most up to date pulse in repos is 11.1
[13:13] <mdeslaur> xubuntu000: 12.0 is in cosmic-proposed
[13:14] <xubuntu000> oh nice!
[13:15] <xubuntu000> wow, as of yesterday even
[13:16] <xubuntu000> thanks mdeslaur! you're awesome
[15:29] <doko> bdmurray: are you currently the one looking at apport? seeing failing autopkg tests on amd64
[15:32] <bdmurray> doko: I'll have a look today
[15:32] <doko> ta
[15:37] <bdmurray> jibel: Could you elaborate on how you recreated bug 1778817?
[15:44] <jibel> bdmurray, I installed 17.10, set the screen lock timeout to 1 min, upgrade to 18.04 with the GUI, and the screen lock goes off before the inhibit command is issued.
[15:45] <bdmurray> jibel: ah so, maybe setting it to 1 minute is the issue?
[15:45] <bdmurray> slangasek: Do you know what period you had for the lock timeout?
[15:47] <jibel> bdmurray, I don't think 1min is the issue, the issue is that the screen can lock between the moment the user proceeds with the upgrade and cannot cancel anymore and the moment the inhibit command is executed
[15:47] <jibel> bdmurray, why not disabling the screen lock earlier?
[15:50] <bdmurray> jibel: I'll have a look at where we can move it.
[15:50] <slangasek> bdmurray: no, I don't know what the interval was, I could look that up with effort.  but as jibel says, ordering should be that the lock inhibition should take place before the user hits the button, not after
[15:51] <bdmurray> Yeah, before they click "upgrade"
[19:30] <tsimonq2> rbasak: Yesterday I implemented the mirroring of those imported USD repositories, and I was wondering... what's the difference between use of the <usd-importer-do-not-mail@canonical.com> email address and <ubuntu-server@lists.ubuntu.com> wrt the importer?
[19:41] <rbasak> tsimonq2: I'm not sure we've pinned down the spec wrt. the addresses used. Where are you seeing each case?
[19:42] <tsimonq2> rbasak: See https://phab.lubuntu.me/source/quassel-archive/history/debian%252Fjessie/ and https://phab.lubuntu.me/source/quassel-archive/history/importer%252Fdebian%252Fdsc/ (hovering over the name in each commit displays the email address).
[19:42] <tsimonq2> rbasak: One is usd-importer and one is Ubuntu Git Importer.
[19:43] <rbasak> tsimonq2: it might have been changed but those repositories not yet reimported
[19:43] <rbasak> Or it could be that the dsc branch does it differently
[19:44] <rbasak> tsimonq2: it's bug 1728685
[19:45] <rbasak> tsimonq2: we'll specify it, add tests to make sure the spec is followed. Before we reimport the world and leave experimental status.
[19:45] <tsimonq2> rbasak: Gotcha.
[19:46] <rbasak> The dsc and pristine-tar branches are a bit special mind. Really they contain data rather than commits. We might not force them a particular way and rely on the person running the importer's settings.
[20:14] <nacc> right, in one case, the authoer and commitere are distinct, in the meta-branches, they are not
[20:55] <tsimonq2> OK, thanks.
[21:14] <nacc> tsimonq2: it's definitely a bug that they are different, and it will presumably be fixed by the above :)
[21:25] <tsimonq2> nacc: Great. :)