[06:55] <voxadam> I don't know if this is the right place to ask about infrastructure but it's all I could find.
[06:56] <voxadam> I'm downloading an image from fwts.ubuntu.com and for some reason it's incredibly slow, <500 KB/s.
[06:57] <voxadam> It looks like fwts.u.o is a CNAME for cranberry.canonical.com.
[07:30] <eoli3n> Hi, session-wrapper doesn't work anymore on ubuntu 18.04, any help to find a quick workaround would be appreciated
[07:30] <eoli3n> bug is pretty easy to reproduice
[07:30] <eoli3n> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773189
[07:30] <eoli3n> session-wrapper var from lightdm, i mean
[08:00] <eoli3n> fixe
[08:00] <eoli3n> d
[13:34] <seb128> wgrant, cjwatson, can we get cosmic translations open?
[13:48] <GunnarHj> seb128: Even if translations for cosmic is opened, bionic should keep being in focus until 18.04.1 has been released, right?
[13:48] <seb128> GunnarHj, yes
[13:49] <GunnarHj> seb128: ok
[13:52] <GunnarHj> seb128: Another translation matter: The email conversation about langpack updates we had with sil2100 halted. Do you have any further input before you leave for vacation?
[13:53] <seb128> GunnarHj, we should do a full langpack refresh before .1 I think
[13:53] <seb128> but that's something for the second half of june imho
[13:54] <seb128> I'm going to be back before that
[13:55] <GunnarHj> seb128: Yeah, it's my understanding that we have an agreement so far. I was rather thinking about a possible update for 16.04.5. But also that can probably wait until you are back.
[14:03] <cjwatson> seb128: I'll have a look on Tuesday.  It's a somewhat delicate operation and has gone wrong in ways requiring database surgery in the past, so I don't really want to try it on a Friday afternoon.
[14:04] <seb128> cjwatson, thanks (and fair enough for waiting newt week)
[14:05] <seb128> GunnarHj, well, that doesn't require me, but +1 on having a refresh on 16.04
[14:12] <GunnarHj> seb128: The question I raised was if a 16.04 refresh would be done for all languages or only tested ones. In case of the latter I suppose it's not sufficient for the gnome-software update you mentioned, or..?
[14:16] <seb128> GunnarHj, we should perhaps bundle the translations in gnome-software in xenial, it change more than langpacks are able to
[14:16] <sil2100> GunnarHj: I think we only discussed the matter of releasing all translations for .1's
[14:16] <sil2100> GunnarHj: not for all point-releases
[14:17] <sil2100> GunnarHj: I'm +1 on .1 having a full language update, I have mixed feelings about doing the same for .5 - I'd stick with the previous schema
[14:19] <sil2100> GunnarHj: could you schedule a langpack update for .5?
[14:19] <sil2100> (on the translation release schedule that is)
[14:21] <GunnarHj> seb128: Yeah, bundling them in xenial for g-s is probably the way if we don't skip the test requirement.
[14:22] <GunnarHj> sil2100: Ok, that clarifies your view. Sure, I can add a .5 round for xenial langpack updates.
[14:24] <sil2100> GunnarHj: it's that for xenial IIUC we didn't have a full langpack update for a long time, and without any automated testing I wouldn't suddenly want to break translations for some languages that we didn't test
[14:25] <GunnarHj> sil2100: Right, that's how the procedure has been for quite some time. But in the mail I mentioned that Martin apparently made an exception for 14.04.5.
[14:26] <GunnarHj> sil2100: (Which in effect made all the previous test efforts for 14.04 meaningless.)
[14:27] <sil2100> It was a bold move! I mean, probably the risk of getting things busted is low
[14:27] <sil2100> But I'd really like to have some bare sanity-tests before we do things like this so late in a series life-cycle
[14:28] <sil2100> I already talked about this to get it prioritized enough so I can work on it
[14:29] <sil2100> Anyway, whatever we decide ultimately getting a call for testing and release scheduled for an export before .5 is needed
[14:29] <GunnarHj> sil2100: Great. I'd really like to consider the approach for 18.04.2+.
[14:30] <GunnarHj> sil2100: Yeah, let's treat 16.04.5 in accordance with the established procedure.
[15:07] <cascardo> https://bugs.launchpad.net/ubuntu/cosmic/+source/nbd/+bug/1772024
[15:07] <cascardo> can anyone review/sponsor my debdiff for nbd? target is cosmic
[16:59] <smoser> seeing this again
[16:59] <smoser> Could not establish FTP connection to upload.ubuntu.com: timed out
[17:00] <smoser> got through that time. took 15 or 20 times in a loop
[17:07] <cjwatson> smoser: cause is known, doesn't need further reports
[17:08] <cjwatson> (SAN is failing; daily apt-ftparchive DB vacuum therefore sends that system's load through the roof for a while each day; see https://rt.admin.canonical.com/Ticket/Display.html?id=111700 for planned remediation steps)
[17:09] <smoser> cjwatson: sorry to pester. thanks.
[19:31] <femme> https://iapp.org/resources/article/guide-to-basic-data-anonymization-techniques/
[19:45] <acheronuk> would someone be kind enough to no change rebuild field3d and pink-pony against new ilmbase? they are blocking transition of that and openexr
[20:23] <ginggs> acheronuk: looking
[20:25] <acheronuk> ginggs: thanks. they may be the last 2 things to depend on the old libilmbase12
[20:31] <ginggs> acheronuk: ok done, but where do you see they are the last 2 things?
[20:38] <acheronuk> ginggs: comparing reverse depends of libilmbase12 and libilmbase23 in cosmic release and -proposed respectively
[20:39] <ginggs> acheronuk: ok, i'll take your word for it
[20:40] <acheronuk> time will tell. that's why I said 'may be'. thanks :)
[21:42] <Unit193> Hello!  What are the chances dh-autoreconf can see a backport to bionic? :)
[21:43] <nacc> rbasak: do you need anything from me currently re: git-ubuntu?