[00:01] <bdmurray> pitti: Could you have a look at bug 1579949? (fwiw I can't assign apport project bugs to you)
[00:02] <TJ-> cjwatson: thank-you, I'll do that :)
[00:02] <cjwatson> (there's a SetState method that you want to look at too)
[00:03] <mwhudson> has something changed in the last week or so in the area of autopkgtest infra and proxies?
[02:27] <rlaager> cjwatson: Are you saying you no longer maintain GRUB in Ubuntu and cyphermox does?
[02:28] <Unit193> Likely part of his stepping back, and moving to LP things.
[02:31] <cjwatson> rlaager: I still maintain the Debian package, but as Unit193 says I now spend most of my time on Launchpad development, so things I don't have time for include spending lots of time tracking down GRUB bugs in Ubuntu.
[02:31] <rlaager> I'm just trying to figure out who might be able to accept: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1527727/comments/31
[02:31] <rlaager> I know we missed Xenial on that, and I'm not necessarily even intending to propose an SRU, but it'd be nice to get into yakkety, so we have the correct fix, rather than the current workaround.
[02:31] <Unit193> cjwatson: Oh, any update on being able to re-generate PPA gpg signing keys?
[02:33] <cjwatson> Unit193: As opposed to just re-signing with current digests?  No, we haven't done any work on that, sorry.
[02:33] <Unit193> OK, thanks.  Sorry for buggin'
[02:48] <cyphermox> rlaager: hello
[02:49] <rlaager> cyphermox: Hi! I'm someone interested in ZFS in Ubuntu, and I'm trying to help out with packaging work to that end.
[02:50] <sarnold> s/trying to help/helping/  :)
[02:52] <cyphermox> rlaager: ah, that's where I remember your name from then
[02:53] <cyphermox> rlaager: I'm not in the right frame of mind to do grub changes now (and I have to fill in the Canada census), but I can look at the grub bugs for ZFS and shepherd things along tomorrow morning
[02:53] <rlaager> I want two things: 1) To get changes into Ubuntu. 2) To know what I'm doing wrong or could do better to accomplish #1. :) So I'm still trying to learn the procedures here.
[02:54] <cyphermox> rlaager: my morning would be in some 8-9 hours, would you still be around then or should I just comment on the bugs?
[02:54] <sarnold> canadians really take this census seriously :) you're the fourth or fifth person I've heard talk about it :)
[02:55] <cyphermox> sarnold: it's either that or multiple hours of community service, or potentially other punitive methods.
[02:55] <sarnold> cyphermox: yikes
[02:55] <cyphermox> I'm really stretching it given that the deadline is in about 1 hour 5 minutes in theory ;)
[02:56] <sarnold> eek
[02:56] <sarnold> is that "local midnight" or a specific midnight? :)
[02:57] <cyphermox> local midnight
[02:57] <cyphermox> TBH I have no idea
[02:57] <cyphermox> usually "by May 10" should parse as before; but for government it may actually mean on May 10 at the latest
[02:58] <rlaager> cyphermox: I'm in US/Central. This week, I'm at a work (telecom) conference followed by a Rotary conference in a different city. So my availability on IRC will be limited. So commenting on the bugs is probably best.
[02:58] <cyphermox> and then I guess the TZ for that might be Ottawa's, but who knows ;)
[02:58] <cyphermox> rlaager: will do
[02:59] <sarnold> long form or short form? :)
[02:59] <cyphermox> rlaager: I kind of also wanted to know how cjwatson felt about some of these, so we could get Ubuntu and Debian back in sync (which means I need to apply some other changes in the Debian vcs too
[02:59] <cyphermox> sarnold: I don't know; I think it might be long form? we haven't had a census in a while
[02:59] <cyphermox> I don't remember ever filling one
[03:00] <sarnold> other friends who got the short form lamented they couldn't put 'jedi' in an official govt document. heh.
[03:01] <cyphermox> sarnold: yeah, neither can you identify as anything but male or female.
[03:02] <sarnold> maybe next decade..
[03:03] <cyphermox> well they have the concept of marriage down ok, it seems
[03:04] <cyphermox> and apparently, copyright attribution of census data!?
[03:05] <sarnold> no kidding? :)
[03:05] <cyphermox> no kidding.
[03:05] <cyphermox> "do you accept that the census data from 2016 be accessible in 2108? (92 years after the census)"
[03:05] <sarnold> <3
[03:06] <rlaager> Is that even a question? You can't actually say "no" can you?
[03:06] <cyphermox> you can actually say not
[03:06] <cyphermox> *no
[03:06] <cyphermox> I have no idea what that would change.
[03:07] <rlaager> hmm. Everything's better in Canada I guess.
[03:07] <cyphermox> I'm mildly curious, would look up census data from 92 years ago, if only my curiosity was higher than my laziness.
[03:07] <cyphermox> sarnold: I suppose it had to be the short form, there weren't many questions
[03:08] <sarnold> done with 53 minutes to spare? :) go-getter!
[03:08] <cyphermox> rraaaahh!
[03:09] <sarnold> the last .us census I did, I was selected for in-person interviews too, with another ~45 minutes of questions. The only question I remember now is how lop-sided their view of marijuana is: "Everyone should try marijuana" "strongly disagree", "disagree", "neutral", "agree". They left off "strongly agree" from that one... wonder why.
[03:10] <cyphermox> fifth? :)
[03:10] <cyphermox> or whatever amendment to not incriminate yourself
[03:10] <Unit193> That does not sound fun.
[03:10] <Unit193> Fifth.
[03:12] <cyphermox> Unit193: I don't know, aside from having to go somewhere, it might be fun
[03:12] <sarnold> funny enough there's some rules about how the results of census can't be used against you in court.
[03:12] <sarnold> they came to the house!
[03:13] <cyphermox> for example, how badly can you mess up the data while giving truthful answers.
[03:13] <sarnold> hehe
[03:15] <mwhudson> pitti: http://people.canonical.com/~pitti/scripts/britney-indexes-ppa needs updating for bz2 -> xz :-)
[03:30] <mwhudson> sigh http://paste.ubuntu.com/16336342/
[03:31] <sarnold> ouch
[03:31] <sarnold> kind of hard to tell what error needs fixing..
[03:32] <sarnold> can you reach your amqp server from that machine?
[03:46] <mwhudson> i don't have an amqp server
[03:46] <mwhudson> oh i see that's actually required
[03:46] <mwhudson> i mis-read https://wiki.ubuntu.com/ProposedMigration/LocalSetup
[03:50] <mwhudson> sarnold: "I: [Tue May 10 15:50:39 2016] - data/yakkety-proposed/autopkgtest/results.cache does not exist, re-downloading all results from swift" is also a pretty implausible line
[05:26] <sarnold> mwhudson: hopefully that means your local swift :)
[05:26] <sarnold> otherwise..
[05:37] <Unit193> So 1562358 is "fixed" then, but not in the LTS...
[05:39] <sarnold> it's got a 'xenial' 'new' task -- did you just add that?
[05:41] <Unit193> I have no superpowers, may have missed that.
[05:42] <sarnold> I can't recall seeing it hte first time I viewed the bug but it was there after I viewed the main lpsrc page. it's either poor memory or someone added the task in the middle. :)
[05:48] <Unit193> I didn't get an email.
[05:49] <cpaelzer> good morning
[07:44] <doko> nacc, Trying easy from autohinter: php-zend-stdlib/3.0.1-1 php-zend-hydrator/2.2.1-1
[07:45] <doko>     * amd64: php-zend-search
[07:45] <doko> FAILED
[07:45] <doko> Depends: php-zend-stdlib (>= 2.3.4-2~), php-common, php-zend-stdlib (<< 3~~)
[07:46] <mwhudson> now britney is segfaulting for me
[11:33] <ginggs> hi, How can I get dolfin into xenial as an SRU?  It was removed along with python-scientific (LP: #1542928). The lastest upload of dolfin drops the dependency on python-scientific.
[11:46] <mdeslaur> @pilot in
[12:25] <sidi> Is there a document somewhere that describes the security checks done on packages in the Ubuntu repositories? And specifically, is there any difference in how main and community packages are checked/validated?
[12:27] <shadeslayer> chrisccoulson: poke
[12:28] <shadeslayer> chrisccoulson: I wanted to talk to you about firefox/thunderbird
[12:28] <shadeslayer> chrisccoulson: for some reason dpkg-buildpackage on my CI on the ff package makes it always error out on the configure step
[12:30] <chrisccoulson> shadeslayer, I don't really do anything with firefox or thunderbird these days, other than the minimum of work to provide updates
[12:30] <chrisccoulson> I'm pretty busy with other stuff
[12:30] <shadeslayer> Oh .. ok ...
[12:30] <shadeslayer> guess I'll need to try and figure it out by myself
[12:30] <shadeslayer> ( it's weird because it builds fine in sbuild , but apparently not with docker )
[12:43] <bigon> hi I posted that on #ubuntu-server, not sure it was the correct place so I'm trying here again
[12:43] <bigon> 13:29 < bigon> are there any objections if I'm hijacking the "selinux" package name in debian?
[12:44] <bigon> 13:29 < bigon> ATM we have a selinux-basics package in debian an I was thinking about renaming it
[12:44] <bigon> 13:30 < bigon> in ubuntu I see that there are some upstart scripts there
[12:44] <bigon> 13:30 < bigon> do you actually care?
[12:44] <bigon> 13:31 < bigon> last upload of that package is 2012, so...
[12:49] <mdeslaur> bigon: I don't think anyone cares, I doubt selinux is in a working state in Ubuntu right now. Go ahead.
[12:49] <mdeslaur> bigon: thanks for asking
[13:18] <Laney> @pilot in
[13:18] <Laney> 94 :(
[13:18] <mdeslaur> Laney: I'm currently doing openldap, so don't take that one :P
[13:18] <Laney> k
[13:19] <Laney> probably wouldn't have been my first choice :-)
[13:19] <mdeslaur> hehe
[13:20]  * dholbach hugs Laney and mdeslaur 
[13:21]  * mdeslaur hugs dholbach
[13:44] <rbasak> infinity: with mvo out, could you take a look at bug 1571174 please?
[13:44] <rbasak> I'm not sure if this is an apt bug, or maybe fallout from the dpkg conffile renaming hacking going on in there.
[13:45] <jamespage> slangasek, good morning
[13:45] <jamespage> slangasek, I have net-tools on my merge list which we deferred from Xenial due to the large amount of changes the new snapshot from debian makes to output
[13:46] <jamespage> slangasek, I last touched to unblock a sru that was causing some openstack-y issues
[13:46] <jamespage> slangasek, would your team like to steal that from me?
[14:40] <barry> pitti: ping
[15:05] <smoser> barry, https://bugs.launchpad.net/ubuntu/+source/pyflakes/+bug/1580214 is kind of painful.
[15:05] <smoser> err.. https://bugs.launchpad.net/pyflakes/+bug/1560134
[15:05] <barry> smoser: i saw the emails ;(
[15:05] <smoser> ok. its enough for me to know you're on it.  i noticed when curtin FTBFS now.
[15:06] <barry> smoser: yep.  i'll take a look asap
[15:13] <caribou> Could someone from the backport team help out with LP: #1335068 pls ?
[15:15] <Laney> caribou: yep, I'll look in 2 minutes
[15:15] <Laney> thanks!
[15:15] <caribou> Laney: thanks to you ! This is the one we discussed previously
[15:16]  * Laney remembers
[15:26] <nacc> doko: will look
[15:30] <mdeslaur> @pilot out
[15:30] <infinity> rbasak: It's not your fault (not apt's), it's ufw's.  Or, more annoyingly, it's that we need to sort out how to upgrade ufw early.
[15:31] <jdstrand> infinity: is this related to that trigger change you made?
[15:31] <infinity> jdstrand: Well, the trigger change was to get around it, but yes.
[15:31] <infinity> jdstrand: The trigger change was correct, but it doesn't entirely fix the world unless ufw upgrades before things that trigger it.
[15:31] <jdstrand> interesting
[15:32] <jdstrand> infinity: fyi, I'm working with kees to get that change into Debian
[15:32] <infinity> I'll give it some thought.
[15:32] <Laney> @pilot out
[15:33] <infinity> rbasak: Fixing this specific case could be done by having squid Breaks << the new ufw, but that's a lie.  If the upgrades are happening in the right order, I can do the Breaks from dpkg, but that might not help wily->xenial.  I'll ponder a fix that will more globally be correct.
[15:36] <rbasak> infinity: thanks
[15:40] <hallyn> pitti: hey - i assume you're busy sprinting and can't, but it would be awesome if you could take a look at bug 1579922
[15:47] <jderose> cyphermox: FYI, "Download updates while installing" has no effect with the 16.04 ISOs - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1580232
[16:01] <infinity> kees, mdeslaur, slangasek, stgraber: TB meeting?
[16:03] <slangasek> jamespage: we can probably swing that
[16:05] <jamespage> slangasek, awesome
[16:47] <infinity> slangasek: Are you SRUing for https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1578006 as well?
[16:47] <infinity> slangasek: Seems like the sort of cosmetic cleanup we'd want in an LTS.
[16:47] <slangasek> infinity: it's on my "list"
[16:48]  * infinity adds a series task.
[16:49] <infinity> slangasek: Kay.  I'm just reading through my apt-listchanges on my yakkety upgrade today and going "oh, that looks like it should be in xenial, ..." over and over again.
[16:53] <infinity> slangasek: The other one that jumped out was the Debian maintainer of bsd-mailx reverting the removal of -b (BCC), thinking "hey, that's something spammers^Wsysadmins probably expect to work".
[17:04] <bigon> is there a way of doing mass bug closing in lp?
[17:07] <mitya57> There is an API :P
[17:09] <bigon> but there is no std tool for that?
[17:10] <mitya57> Not that I know of.
[17:10] <bigon> :/
[17:11]  * bigon says something about the mail interface of the debian bts
[17:11] <cjwatson> bigon: LP has a mail interface too.
[17:11] <cjwatson> You just have to sign mails that involve status changes.
[17:11] <bigon> oh
[17:11] <cjwatson> The normal API tends to be easier to use.
[17:12] <cjwatson> https://help.launchpad.net/API/launchpadlib
[17:12] <bigon> thx
[18:12] <juliank> Laney: seb128: Is just running AppStream even on (partial) apt update failure OK for you guys? This should fix the gnome-software issue mentioned in #1562733
[19:01] <juliank> infinity: What does it take for us to get apt 1.2.11 SRUed to xenial, and 1.2.12 once it's released and tested (changes for that being https://github.com/Debian/apt/compare/1.2.y...julian-klode:1.2.y?expand=1) - those are upstream micro releases with extensive test suite.
[19:02] <juliank> 1.2.11 diff for the curious: https://github.com/Debian/apt/compare/1.2.10...1.2.11?expand=1
[19:03] <juliank> I picked a commit that removes the annoying "There is no public key available for the following key ID" for 1.2.12, as that's really annoying now for the repos migrating from DSA to RSA (it only shows if one of the keys used to sign the repo is unknown, but the other sigs are valid)
[19:07]  * juliank is trying to have an upstream 1.2 LTS series (for merging into xenial)
[19:09] <juliank> Not all future 1.2 releases would be in Debian, but they  be tagged, and run their test suite using APT's usual CI tools
[19:09] <juliank> Opinions welcome
[19:09] <juliank> :D
[19:15] <sarnold> any chance this gets rid of the "can't install package, package already installed" errors from dpkg? :)
[19:19] <smoser> infinity, i've tested bug d-i kernels at bug 1568918 on i386, amd64 and ppc64el. what else would you want done before promotion to trusty-updates ?
[19:22] <infinity> smoser: Test a xenial daily ISO too (any arch, don't care) and see if that's doing the right thing.
[19:22] <infinity> smoser: Otherwise, I think we should be good.
[19:22] <infinity> smoser: (d-i bits are used on the ISO, hence the connection)
[19:22] <smoser> infinity, where do i get that ?
[19:23] <smoser> xenial daily ?
[19:23] <smoser> or trusty daily
[19:23] <infinity> smoser: Err, trusty.  That one. :P
[19:23] <smoser> http://cdimage.ubuntu.com/ubuntu-server/trusty/daily/20160510/
[19:23] <smoser> right ?
[19:24] <infinity> smoser: Yep.
[19:24] <infinity> juliank: If the 1.2 branch is bugfix only and all changes have extensive test coverage, that should fit our new and improved micro-release SRU process, so I'd be more than happy to let 'em in.
[19:31] <juliank> infinity: I did not run coverage checks (but the test suite is huge!), most commits even add coverage, as they include regression tests. There are some exceptions that cannot really be tested like https://github.com/Debian/apt/commit/57f16d51f4158dce1a49f6d5f5f05f057125b871 (but this one includes error messages for unwanted failure cases!)
[19:34] <infinity> juliank: Sure, sometimes a single commit just isn't feasibly testable, but in general, every change in a microrelease should be regression tested to the best of upstream's ability to fit the new policy, that's all.
[19:34] <infinity> juliank: I think we're on the same page there.
[19:34] <juliank> That's the plan for all APT bug fixes in general.
[19:35] <infinity> juliank: And if this won't be going to unstable (because you're moving on to 1.3.x), an apt-maintainers PPA that you use for pre-release CI would be a good idea, so we can have a better look at the state of 1.2.x on xenial before accepting an upload.
[19:36] <juliank> infinity: That's quite useful, yes. We also run CI on all pushes using travis
[19:36] <infinity> juliank: But, yeah, I don't see any fundamental issues with a 1.2.x branch for the LTS.
[19:36] <juliank> travis runs on trusty IIRC
[19:36] <juliank> (JFTR)
[19:37] <infinity> juliank: The upshot of the PPA is we can get it building/testing on all arches with fairly minimal effort.
[19:38] <infinity> juliank: Anyhow, we can hammer out details, but I'm happy to put a +2 (+1 from SRU team, +1 from TechBoard) on the idea.
[19:38] <juliank> That's fine. I'd also like an recipe-built PPA like for master, but I don't think that's possible yet.
[19:38] <infinity> juliank: git recipes are possible.
[19:38] <juliank> Oh
[19:38] <juliank> Maybe I should try playing with that
[19:39] <infinity> juliank: I don't think we have automagic imports yet, though, so you'd have to run a local job to mirror git.d.o to git.lp.n
[19:39] <infinity> But that's not too onerous.
[20:40] <fo0bar_> infinity: https://wiki.ubuntu.com/ARM/RaspberryPi/RaspberryPi3#Bugs_filed updated with experimental -> yakkety merge request, and I've addressed your comment in MP: #293959 (and filed a corresponding bug for good measure).  that *should* be everything needed to get a working raspi3 target on yakkety
[20:46] <infinity> fo0bar: Ta.
[20:49] <infinity> smoser: d-i     passwd/user-password-crypted    password $6$.1eHH0iY$ArGzKX2YeQ3G6U.mlOO3A.NaL22Ewgz8Fi4qqz.Ns7EMKjEJRIW2Pm/TikDptZpuu7I92frytmk5YeL.9fRY4.
[20:49] <infinity> smoser: ^-- Is that sha512 for "ubuntu"? :)
[20:50] <smoser> you cracked my secret password
[20:54] <infinity> smoser: I used to have a des crypt() NULL password string memorized (what a useless skill THAT is), but sha512 is a bit rougher.
[20:56] <infinity> smoser: Do you still have that daily ISO sitting on your hard drive?
[20:56] <smoser> well, on *a* hard drive
[20:57] <infinity> smoser: I meant locally, so I can get you to do one more quick test (if not, I'll do it).
[20:57] <smoser> sure
[20:57] <infinity> smoser: Just wanted you to boot into the installer, hit a shell, and verify the booted installer kernel is also 4.4.0
[20:57] <smoser> i have it booted to my install but i can do another isntall
[20:57] <smoser> ah. yeah, i forgot.
[20:57] <infinity> smoser: Which it should be.
[21:01] <smoser> infinity, posted in bug
[21:02] <infinity> smoser: Danke.  Will release to updates and fix up cdimage/netboot etc this afternoon.
[21:02] <smoser> k. i'm out now.
[22:10] <doko> ginggs, next gdal transition? omg