=== negronjl_ is now known as negronjl
[02:07] <lamont> pjdc: doko: +1
[05:34] <cpaelzer> doko: hi, one question about tracking syncs
[05:35] <cpaelzer> doko: I saw you asked jbicha about brotli - I always wondered how one could/would track who did a sync
[05:35] <cpaelzer> did you derive that from the changes file that was generated on the sync?
[05:35] <cpaelzer> or what are your usual steps to determine who has done a particular sync?
[05:41] <Unit193> cpaelzer: Eg, https://launchpad.net/ubuntu/+source/brotli/1.0.4-1/+publishinghistory expand the proposed one.
[06:02] <cpaelzer> Unit193: yeah, thanks
[06:02] <cpaelzer> I was expecting to see it anywhere on https://launchpad.net/ubuntu/+source/brotli/1.0.4-1 as well
[06:02] <cpaelzer> but from publishing history is fine, this isn't an info you need very often anyway
[06:02] <Unit193> Can be useful though.
[06:02] <cpaelzer> absolutely
=== lifeless_ is now known as lifeless
[09:33] <GunnarHj> wgrant: Can you please look at bug #1758684. LP fails to import some (randomly determined?) strings over and over again. Manual uploads work.
[09:33] <ubottu> bug 1758684 in Ubuntu Translations "LP only imported a fraction of the snappy translation template" [High,In progress] https://launchpad.net/bugs/1758684
[10:05] <wgrant> GunnarHj: Hm, where did you get the POT that you manaully uploaded?
[10:05] <wgrant> GunnarHj: Pretty sure LP is in the right here; compare the sizes of the top six tarballs on https://launchpad.net/ubuntu/bionic/+queue?queue_state=3&queue_text=snapd
[10:06] <wgrant> snapd seems to product different POTs depending on the arch it's built on, which is certainly innovative.
[10:07] <wgrant> wgrant@lamuella:/tmp$ diff -u {arm64,i386}/source/po/snappy.pot | diffstat
[10:07] <wgrant>  snappy.pot | 1622 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
[10:07] <wgrant>  1 file changed, 1620 insertions(+), 2 deletions(-)
[10:08] <wgrant> Never seen anything quite like that.
[10:10] <GunnarHj> wgrant: Hmm.. That's an aspect I haven't even noticed. Always looked at the amd64 tarballs.
[10:12] <GunnarHj> wgrant: But I'm aware of the fact that the snapd template generating is fragile. That's a separate snapd issue. But it would be good if we could make LP behave as expected given the templates which are generated.
[10:12] <wgrant> GunnarHj: Yeah, I only thought to check because it made literally no sense at all otherwise.
[10:12] <wgrant> GunnarHj: LP is behaving as expected. The most recently uploaded template wins.
[10:12] <wgrant> Unioning the templates isn't sensible.
[10:12] <wgrant> LP's doing all it can.
[10:14] <GunnarHj> wgrant: Ah, is that it. That may explain it then. Thanks for valuable input!
[10:14] <wgrant> GunnarHj: Thanks for looking at this.
[10:14] <wgrant> Hopefully snapd people have some idea on this bug.
[10:14] <wgrant> i'll certainly be following it just because the bug has to be pretty entertaining to have this result...
[10:16] <GunnarHj> wgrant: Wouldn't use the word "entertaining" ... :(
[10:20] <GunnarHj> wgrant: The are using something called xgettext-go:
[10:20] <GunnarHj> https://github.com/snapcore/snapd/blob/master/update-pot
[10:21] <wgrant> GunnarHj: Hm, that uses "go install" so it's probably not the thing that's run during the build on LP
[10:21] <wgrant> Unless something weird is going on
[10:22] <wgrant> Oh though xgettext-go is from snapd itself
[10:22] <wgrant> because of course it is
[10:23] <wgrant> Though I can't see what runs update-pot
[10:23] <wgrant> i18n/i18n.go://go:generate update-pot
[10:23] <wgrant> unless it's that
[10:23] <cjwatson> Yes, that comment isn't a comment
[10:23] <cjwatson> /o\
[10:24] <cjwatson> https://blog.golang.org/generate
[10:25] <wgrant> Do I want to know
[10:25] <cjwatson> No
[10:25] <GunnarHj> wgrant, cjwatson: If you see something weird there, I'm sure the snapd team would appreciate a hint.
[10:26] <cjwatson> I'm just remarking on the ridiculous Go overloading of comments; I have nothing particularly useful to contribute
[10:26]  * wgrant is firing up a VM to run update-pot and see what happens
[10:37] <Skuggen> Does anyone have an overview of the configuration of autopkgtest used in Ubuntu? I'm working on some MySQL 8.0 packaging, and get some dep8 failures because the test suite need more ram and test timeout than the default setting
[15:44] <sil2100> Laney: I just accepted all your gstreamer packages for bionic - just make sure that the few 1.14.1 packages that are still stuck in cosmic-proposed migrate
[15:45] <sil2100> Since there were a few that were still sitting there
[15:45] <Laney> sil2100: thanks!
[15:45] <sil2100> yw!
[15:45] <Laney> they're stuck in the migration of hell
[15:46] <Laney> which I saw people were working on; so, hopefully when that moves on a bit they'll go in
[15:46] <Laney> or at least we'll see if there's anothe rproblem
[15:46] <doko> cpaelzer_: usually I get this from the changes emails (I'm subscribed to these)
=== smoser1 is now known as smoser
[16:49] <xnox> slangasek, when upstart chroot sessions are disabled; initctl version still responds inside a chroot, when the host system has upstart. Do you think that is correct symantics? or a bug, which we should have fixed...?!
[16:49] <xnox> sladen, balint and I discovered this yesterday, in the context of building trusty images
[16:52] <slangasek> xnox: seems like correct semantics to me
=== lifeless_ is now known as lifeless