[02:22] <FourDollars> Hi, I would like to do a SRU for https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1100546 on xenial. Could you help me?
[02:22] <ubottu> Launchpad bug 1100546 in indicator-power "Power indicator favours 'not present' mouse over laptop battery level" [Medium,Triaged]
[02:25] <sarnold> FourDollars: have you seen this yet? https://wiki.ubuntu.com/StableReleaseUpdates
[02:26] <FourDollars> sarnold: I am reading it.
[02:40] <FourDollars> sarnold: Is there any thing I missed?
[02:42] <sarnold> FourDollars: I -think- just a mention that you've been running it locally without trouble, mention if the zesty fix has had any bugs reported or not, and maybe bug the sru team
[02:43] <sarnold> FourDollars: this handy chart should say who is on sru duty any given day https://wiki.ubuntu.com/StableReleaseUpdates#Publishing
[02:44] <FourDollars> sarnold: OK. I see.
[02:44] <FourDollars> sarnold: Thx for your information.
[02:44] <sarnold> FourDollars: you're welcome :) I hope it's useful, hehe
[02:45] <FourDollars> sarnold: But I need to nominate it for xenial first. Do you have the permission to nominate it?
[02:46] <sarnold> lets find out :)
[02:46] <sarnold> yay looked like it worked :)
[02:46] <FourDollars> sarnold: OK. Thx a lot. :)
[08:21] <pitti> barry: I just ran the systemd "upstream" autopkgtest on debian sid, which also recently got kernel 4.9; same problem with the qemu crash apparently
=== jamespag` is now known as jamespage
=== _salem is now known as salem_
[12:07] <ahasenack> hi, any idea why apt on xenial would "Ign" downlading a Release.gpg file when there is no InRelease file?
[12:07] <ahasenack> http://pastebin.ubuntu.com/23821750/
[12:08] <ahasenack>  /var/lib/apt/lists only has the two files at the bottom: Packages and Release
[12:08] <ahasenack> it's missing Release.gpg, which the repository has (http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/)
[12:08] <ahasenack> if I run apt update again, it still won't download the gpg file
[12:08] <ahasenack> only if I remove the two files it downloaded (Packages and Release), then it will download the gpg one and be happy with the signature
[12:16] <cpaelzer> ahasenack: I can confirm your finding once I forced it into the state http://paste.ubuntu.com/23821784/
[12:16] <cpaelzer> I don't know how you got there, but if I just drop the gpg file I kind of end up like your pastebin
[12:17] <cpaelzer> ahasenack: with Ign and the gpg not being refreshed
[12:17] <ahasenack> I see
=== scottt is now known as Guest45126
[14:14] <barry> pitti: that's interesting, right? :)
=== JanC_ is now known as JanC
=== tumbleweed_ is now known as tumbleweed
=== giraffe is now known as Guest98986
=== Adri2000_ is now known as Adri2000
=== tarpman_ is now known as tarpman
=== bigon_ is now known as bigon
=== stgraber_ is now known as stgraber
[18:11] <juliank> bdmurray: Ah, I just found out what is wrong with apt xenial test case. The bug only involves redirects from http to https in xenial
[18:12] <juliank> And the provided test case tests a https->https redirect so it does not break in xenial, because we let curl handle it internally there
[18:12] <juliank> I should replace the test case then with "install ttf-mscorefonts-installer" I think
[18:16] <juliank> 1/4th of my dinner is burnt because I was so eager to find out what happened :/
[18:16] <bdmurray> that seems more fragile to me
[18:17] <juliank> Oh, I can also do my own test case
[18:17] <juliank> but that one is in the test suite already...
[18:20] <juliank> bdmurray: You could also try "https://people.debian.org/~jak/a b/c" - in 1.2.18 it will request "~jak/a b/c" which apache redirects to "~jak/a" causing a 404
[18:21] <juliank> Ehm, with http not https
[18:21] <juliank> Although it fails with https as well in 1.2.18
[18:23] <bdmurray> okay, that failed and succeeded for me
[18:24] <juliank> bdmurray: Now we're getting all kind of weirds report that it does not work on the bug because users just upgraded apt and not apt-transport-https ...
[18:25] <juliank> The same used to happen with libapt-pkg and friends
[18:25] <juliank> All people ever do is "apt install apt" and then wonder why things did not get fixed :)
[18:25] <bdmurray> maybe put the package name in the test case?
[18:26] <juliank> I added a note now
[18:26] <juliank> I wonder if I should add a "Breaks: apt-transport-https (<< ${source:Version}" to apt anyway.
[18:26] <juliank> That simplifies things a bit.
[18:27] <juliank> but it seems a bit overkill
=== salem_ is now known as _salem
[20:03] <pdeee> hlieberman, RAOF: is one of you working on https://bugs.launchpad.net/ubuntu/+source/python-letsencrypt/+bug/1640978/comments/25 ?
[20:03] <ubottu> Launchpad bug 1640978 in python-letsencrypt-apache (Ubuntu Yakkety) "letsencrypt 0.4.1 contains numerous bugs fixed upstream" [Undecided,New]
[20:04] <pdeee> I'm not sure who the right person to handle rbasak's request is
[20:07] <pdeee> meanwhile the upstream Certbot team is wanting to change what we say about Xenial at https://certbot.eff.org/
[20:09] <doko> coreycb: python/trusty ping ...
[20:12] <pdeee> the options are use our certbot-auto script, which is a bit janky but works, or use Ondřej Surý's PPA, which has recently reached maturity, but which might also create complexity because it contains a bunch of other packages
[20:12] <acheronuk> anyone able to help with the failing (timeout) unity8 test which is blocking migration on qtbase here?
[20:12] <acheronuk> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtbase-opensource-src
[20:15] <coreycb> doko, hi
[20:15] <doko> coreycb: were you able to test your patch with the python2.7 version in trusty?
[20:16] <coreycb> doko, yes, i believe it's in the trusty upload queue now
[20:16] <doko> coreycb: cool, thanks! did you have time to look at the other issues?
=== kees_ is now known as kees
[20:19] <coreycb> doko, that fix (for kombu) fixed up cinder and glance. i just noticed nova also had a failure.  i'll see if that's also fixed by the kombu update.
[20:19] <setuid> Can someone with access to kernel.ubuntu.com please run 'git update-server-info' in the ubuntu-zesty.git repo root?
[20:19] <setuid> It's a broken repository right now
[20:20] <doko> coreycb: thanks!  I'll give back the builds once the fix is in the archive
[20:20] <coreycb> doko, ok great
[20:20] <setuid> $ git clone http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-zesty.git
[20:20] <setuid> Cloning into 'ubuntu-zesty'...
[20:20] <setuid> fatal: repository 'http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-zesty.git/' not found
[20:20] <setuid> It's a valid directory and URI, but the repo is broken
[20:26] <cjwatson> setuid: you may get more relevant eyeballs in #ubuntu-kernel; I expect you could also work around it for yourself by cloning https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/zesty instead
[20:27] <setuid> cjwatson, I was looking for current mirrors, found some... questionable.. mirrors
[20:28] <cjwatson> setuid: I *believe* that the kernel.ubuntu.com repo is itself a mirror of the one on Launchpad ...
[20:28] <cjwatson> (or maybe it's the other way round, not totally sure)
[20:28] <setuid> ubuntu-xenial, 9 commits. ubuntu-yakkety, 9 commits, ubuntu-trusty, 422087 commits
[20:28] <setuid> aye
[20:29] <cjwatson> Certainly the intent was eventually for LP's git hosting to supersede kernel.u.c, though there are some long-standing feature requests we need to sort out regarding fine-grained access control before that can really happen
=== wxl_ is now known as wxl
[21:30] <doko> slangasek, infinity: we need to address the dpkg merge at some time, and decide about pie on some archs. my understanding with kees (private discussions) is that performance regressions should be considered
[21:43] <rharper> slangasek: rbasak:  I've marked verification-failed on  bug 1649931 ; added comments;  it's likely we may want the nvme fix to go in asap and then re-submit the DNS issue after that clears through;
[21:43] <ubottu> bug 1649931 in resolvconf (Ubuntu Yakkety) "systemd-networkd needs to ensure DNS is up before network-online.target" [Medium,Fix committed] https://launchpad.net/bugs/1649931
[21:43] <slangasek> rharper: yep, I have already uploaded the new systemd to the queue, thanks :)
[21:44] <rharper> cool!
[21:44] <slangasek> (and accepted it)
=== _salem is now known as salem_
[23:24] <achiang> teward: hola, noticed that you maintain the nginx ppa -- wondering if you could upload a 1.10.2 stable version to pick up some bug fixes...
[23:25] <teward> achiang: relevant: https://twitter.com/teward001/status/814545963960377345 and https://twitter.com/teward001/status/817472538230030336 and https://twitter.com/teward001/status/821855809361608708 and all comments on the first one.
[23:25] <teward> in that order chronologically
[23:25] <teward> achiang: always track my twitter, where I make notices about those PPAs.
[23:25] <teward> such as when things don't build and i'm stuck at not being able to make it work, etc.
[23:25] <teward> working on stuff now though (just don't bug me until it's done)
[23:26] <teward> *swears on the live of his ex and his current love interest he will smack the next person to ask for the PPAs to get updated*
[23:26] <teward> achiang: also relevant: https://bugs.launchpad.net/nginx/+bug/1657596
[23:26] <ubottu> Launchpad bug 1657596 in Nginx "[PPA] fPIE/fPIC build problems" [Critical,In progress]
[23:27] <achiang> teward: ok, sorry for the noise. didn't realize twitter was the best way to keep up with this ppa
[23:29] <teward> achiang: I always announce updates there
[23:29] <teward> a lot of PPA users follow me just for those announcements
[23:29] <teward> achiang: it also never hurts to look at https://launchpad.net/~teward/+archive/ubuntu/nginx-stable-testing/+packages either, 'cause test packages get uploaded there
[23:30] <teward> when you see a lot of red Xes next to the archs, and a package revision of 1.10.2-* you know something is being worked on but it blew up
[23:30] <teward> this took me almost 3 weeks to debug
=== StevenK_ is now known as StevenK