[01:23] <cjwatson> I see walbon's left, but just in case they're reading logs, "apt-listchanges --all foo.deb" is probably the single straightforward command they were looking for
[02:08] <tsimonq2> What does the SRU Team think about bug 1770678?
[02:09] <tsimonq2> It's the Debian maintainer asking for a no-change rebuild of their package in Artful.
[04:57] <ipatrol> Guess https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1117481 can be closed up with perhaps a little QA
[12:51] <ginggs> tseliot: hi, will you SRU the /dev/nvidia-uvm-tools fix for bionic as well please?
[12:55] <tseliot> ginggs: yes, I uploaded in cosmic today, and I hope to SRU that soon
[13:22] <ginggs> tseliot: thanks
[13:52] <ahasenack> jbicha: hi, good morning/afternoon, #1737053 came to my attention as I'm preparing a new apache upload for cosmic
[13:52] <ahasenack> jbicha: looks like brotli is still in universe
[13:53] <ahasenack> should I just upload the new apache which can depend on it, and then libbrotli1 will be pulled into main? Or should some action be taken before by an AA about it?
[13:54] <ahasenack> I don't see it in excuses, even though cosmic-proposed has one upload from may 4th
[13:54] <ahasenack> ah, that upload is the one that failed the armhf build
[13:54] <jbicha> go ahead and upload, it will be noticed for promotion to main once something in main pulls it in
[13:57] <ahasenack> rbasak: hi, could you please import brotli? It's in universe now, but will be promoted to main
[13:59] <rbasak> ack
[14:00] <ahasenack> rbasak: th
[14:00] <ahasenack> thx
[14:02] <rbasak> Importing
[15:13] <rbasak> ahasenack: the import was successful
[15:14] <ahasenack> rbasak: thanks
[15:30] <teward> anyone know how to fix mk-sbuild in Xenial to get a Cosmic schroot?  It's failing to create the schroot with 'Package pkg-create-dbgsym has no installation candidate" in mk-sbuild.  (I'm not yet able to upgrade to Bionic at this time)
[15:32] <mdeslaur> teward: ignore the warning
[15:32] <mdeslaur> teward: I got that on bionic creating bionic schroots too but it seems to work fine
[15:33] <teward> mdeslaur: well I ask because it hard-failed
[15:33] <mdeslaur> oh, hrm
[15:33] <teward> mdeslaur: 'twas not a warning, was a hard-fail "error"
[15:34] <teward> i've got a Bionic system at home, I can test there to see if this is a Xenial-specific mk-sbuild issue, and if it is then I'll probably open bugs, but until then I can't test it (because "work")
[15:34] <mdeslaur> I got a hard fail too, IIRC, and the schroot still works
[15:34] <mdeslaur> have you tried the resulting chroot?
[15:35] <teward> waiting for the other schroots to finish updating (I have a "fire and forget" script that fires off all the updates for supported release chroots)
[15:35] <teward> i've only got so much computing power on this here system :p
[15:37] <doko> ginggs: mrbayes and esys-particle autopkg tests are still running, but any other openmpi autopkg test failures are real
[15:39] <teward> mdeslaur: huh, working now.  I worry that something that's supposed to be in the chroot isn't because installation exploded at one step.
[15:43] <ginggs> doko: ok, will have a look - not sure what can be done about all the armhf FTBFS
[15:44] <femme> Have differential privacy/data anonymization been evaluated for the ubuntu telemetry? for example this could be used http://arx.deidentifier.org/
[18:23] <Odd_Bloke> debootstrap in bionic doesn't know about cosmic yet; how can I work around that?
[18:23] <Odd_Bloke> (To mk-sbuild, for clarity.)
[18:24] <cjwatson> sudo ln -s gutsy /usr/share/debootstrap/scripts/cosmic
[18:26] <Odd_Bloke> Hmm, that should have been more obvious to me.
[18:26] <Odd_Bloke> Thanks!
[18:33] <wxl> i had the same question, actually. are you suggesting, cjwatson, to just build as "gutsy" after the symlink?
[18:33] <teward> wxl: i did that
[18:33] <teward> and have for bionic, etc.
[18:34] <teward> it's basically what i've had to do while not on the latest release(s)
[18:34] <wxl> huh, ok
[18:34]  * wxl buys more band-aids :/
[18:53] <Odd_Bloke> wxl: The debootstrap hasn't changed since gutsy, so it's just reused via symlink.
[19:07] <wxl> Odd_Bloke: well i guess it DOES make sense then :)
[20:25] <rbasak> doko: does bug 1770748 have to go directly to the TB? Why not the ubuntu-devel@ ML first?
[20:26] <rbasak> I'm talking about should-we-maintain-C++-symbols-files in this case question.
[20:27] <rbasak> (because I have an opinion on that technical point, and I'd like to hear the opinions of others)
[20:56] <doko> rbasak: sure, we can have the technical discussion there, not sure about the procedures
[23:53] <jbicha> I personally think that this escalated way too quickly
[23:54] <wxl> jbicha: re: i386?
[23:55] <jbicha> no, me being referred to the TB about the ilmbase issue
[23:55] <wxl> ah. can't really comment there.
[23:56] <jbicha> I assume the referral wasn't meant to be personal but that doesn't help relieve the stress much
[23:57] <wxl> yeah it doesn't read as personal to me
[23:59] <teward> mdeslaur: just an FYI, I didn't run into that issue with pkg-create-dbgsym during chroot development when building the Cosmic chroot in a Bionic environment.  Guess something with Xenial's sbuild/schroot doesn't like Cosmic?