[02:34] <barry> bdmurray: yes, it will
[03:36] <bdmurray> barry: okay, I did that then
[04:59] <Unit193> pitti: Howdy.
[05:07] <pitti> Good morning
[05:07] <pitti> hey Unit193, how are you?
[05:08] <Unit193> I think I'm alive, but I'd have to check. :)
[05:18] <Mirv> doko: no, those other Qt packages are not from qt.io upstream, so not part of Qt as such. but our stack has a lot of other Qt/QML modules too.
[06:17] <pitti> I'm stunned, what am I doing wrong?
[06:18] <pitti> -rw-r--r-- 1 root root 289 Jul 16 08:11 /etc/init/autopkgtest-worker.conf
[06:18] <pitti> $ sudo initctl status autopkgtest-worker NAME=1
[06:18] <pitti> initctl: Unknown job: autopkgtest-worker
[06:18] <pitti> I even tried initctl reload-configuration and rebooting
[06:18] <pitti> (that's on trusty)
[06:18] <pitti> s/status/start/ of course (it fails with any command)
[06:19] <sarnold> pitti: tru initctl --system
[06:19] <pitti> same
[06:20] <sarnold> pitti: iirc trusty introduced the user session stuff, and automatically uses --user if the right environment variable is available
[06:20] <pitti> sarnold: right, but no $UPSTART_SESSION and no user upstart instance running
[06:20] <pitti> either way, --system doesn't help, and I'm calling this through sudo
[06:22] <pitti> "initctl status ssh" works fine, it just doesn't seem to like my custom job
[06:23] <pitti> this is an "instance" job, but trusty has other jobs with "instance"
[06:26] <pitti> Jul 16 08:25:04 autopkgtest kernel: [  768.186277] init: /etc/init/autopkgtest-worker.conf:12: Unknown stanza
[06:26] <pitti> aah!
[06:26] <pitti> here's to useful error messages
[06:28] <sarnold> aha :)
[07:00] <LocutusOfBorg1> hi folks, how do you feel about syncing virtualbox from experimental?
[07:00] <LocutusOfBorg1> I uploaded yesterday 5.0
[07:04] <LocutusOfBorg1> I don't see a way to sync from experimental with requestsync
[07:05] <seb128> LocutusOfBorg1, -d experimental?
[07:06] <LocutusOfBorg1> oops bad monday :) thanks
[07:06] <LocutusOfBorg1> that kind of monday that persists until saturday I mean
[07:06] <seb128> lol, I see
[07:07] <LocutusOfBorg1> usually with backportpackage -d means "destination"
[07:07] <LocutusOfBorg1> so I got confused ;)
[07:07] <LocutusOfBorg1> bugs filed, thanks
[07:08] <seb128> yw!
[07:13] <dholbach> good morning
[07:18] <seb128> hey dholbach
[07:18] <dholbach> hey seb128
[11:00] <doko> Laney, seb128, Mirv: poppler ftbfs with the current qt5, see http://paste.ubuntu.com/11887104/
[11:00] <doko> triggered by
[11:00] <doko> # enable all the hardening options
[11:00] <doko> export DEB_BUILD_MAINT_OPTIONS = hardening=+all
[11:01] <doko> that's what adds the -fPIE
[11:03] <Mirv> right, Qt 5.4.2 bans now -fPIE usage
[11:03] <Mirv> more info at http://code.qt.io/cgit/qt/qtbase.git/commit/?id=36d6eb721e7d5997ade75e289d4088dc48678d0d + http://code.qt.io/cgit/qt/qtbase.git/commit/?id=3eca75de67b3fd2c890715b30c7899cebc096fe9
[11:04] <doko> I'm now just uploading a poppler with that commented out to the silo 16
[11:04] <Mirv> with GCC 5
[11:09] <Laney> doko: not "-pie"?
[11:10] <doko> no, -fPIE triggers the macro
[11:17] <cjwatson> FYI, all newly-created amd64/i386 LP builds will now be dispatched to scalingstack (lcy01-*/lgw01-*), even if they're in non-virtualised archives such as the primary Ubuntu archive or ci-train silos
[11:18] <cjwatson> Retries of builds created prior to this change will still go to the bare-metal build farm for now, until we're confident enough in things to do the more invasive database surgery
[11:41] <Laney> doko: Sorry, was checking - I mean hardening=+all,-pie
[13:16] <doko> Laney, sure, but's the default in Ubuntu anyway
[13:16] <Laney> well we're not using that here, so needs fixing
[13:36] <pitti> Laney: does that look correct? http://paste.ubuntu.com/11887745/
[13:36] <pitti> kde4libs is blocking too much, and apparently there's no interest in fixing it
[13:37] <pitti> Laney: so far I modded results.history, but this should last a bit longer
[13:38] <Laney> pitti: looks right to me - do you have a hint entry in the britney config file?
[13:38] <pitti> Laney: no, I'm going to commit that next
[13:38] <Laney> right
[13:38] <pitti> Laney: http://paste.ubuntu.com/11887766/
[13:39] <Laney> nod
[13:41] <pitti> Laney: both committed; I'll check excuses
[13:42] <Barbariandude> Hello! I'm anxiously awaiting the arrival of AMDGPU from the 4.2 kernel. If I were to compile and test it myself (for my R9 285 GPU), would I also need to compile and install the AMDGPU branch of Mesa as well?
[13:59] <commander_> #ubuntu-devel
[13:59] <commander_>  hello i am packing a Qt webkit based application am confused what should i put as dependencies my app executable ldd output is here in pastebin http://pastebin.com/mfgdrEtz
[13:59] <commander_> popey,  hello i am packing a Qt webkit based application am confused what should i put as dependencies my app executable ldd output is here in pastebin http://pastebin.com/mfgdrEtz
[14:03] <ikonia> try ##ubuntu-app-devel ?
[14:03] <ikonia> oops one #
[14:03] <ikonia> not two
[14:04] <commander_> ikonia, thanks i joined it
[14:04] <commander_> yeah i got it
[14:45] <bdmurray> barry: python-apt has an autopkgtest regression, did something else need uploading first?
[14:46] <barry> bdmurray: it's unclear.  it builds right?  i wasn't able to do any dep-8 tests in the ppa, so my first order of business will be looking at clearing python3-defaults promotion issues
[14:47] <bdmurray> barry: yes, it builds. here is the failure - https://jenkins.qa.ubuntu.com/job/wily-adt-python-apt/lastBuild/ARCH=amd64,label=adt/artifact/results/log/*view*/
[14:47] <barry> bdmurray: ah, PendingDeprecationWarning printed to stderr
[14:47] <barry> shouldn't be hard to fix
[14:48] <barry> bdmurray: i'll take that one first
[14:48] <bdmurray> barry: okay, thanks!
[14:48] <pitti> infinity, Laney, slangasek: FYI: "run-autopkgtest --help" on snakefruit if you want to (re-)run an autopkgtest; e. g. "run-autopkgtest -s wily -a i386 libpng" (if you skip -a it'll run on all arches)
[14:48] <pitti> infinity, Laney, slangasek: ^ in the cloud, that is
[14:49] <pitti> infinity, Laney, slangasek: it's very simple-minded right now, and we'll probably extend it to do stuff like "re-run all failed/tmpfail tests" or something such, we'll learn the use cases over time
[14:49] <pitti> but that should be good enough for next week while I'm away
[14:56] <pitti> infinity: yay, the ddeb-retriever run from hell finally finished
[15:00] <Laney> pitti: cool, thanks - I guess the eventual goal is to provide something for uploaders in general to retry stuff?
[15:02] <pitti> Laney: if we can somehow hook u1 auth to that, sure
[15:03] <pitti> sso, I mean
[15:04] <pitti> Laney: then again, we've never had this anyway, so it's not a regression
[15:06] <Laney> no, but it's been an annoying wart of the current setup that only (~canonical ∩ (~ubuntu-core-dev ∪ ~ubuntu-release)) or so can retry things
[15:06] <pitti> Laney: well, I'm not sure whether we want so many people hit retry buttons all the time, given our limited resources
[15:07] <pitti> but in practice we actually have the opposite problem, not enough people watching excuses.html
[15:07] <pitti> but then again, cleaning up requires lots of overrides, which is ~u-release
[15:07] <pitti> I spent an hour yesterday to flush out tons of stuff that got stuck
[15:10] <Laney> not pretending that retrying can fix everything, does help sometimes though
[15:10] <pitti> yes, especially with uninstallables
[15:11] <pitti> Laney: anyway, it's a question of "how to get SSO there", not "I want to keep my toys for myself"
[15:11]  * Laney nods
[15:12] <Laney> for me it's "I don't want to have to do button clicking for people" and "I don't like requiring membership of ~canonical for Ubuntu dev tasks". :)
[15:12] <Laney> WTF, 16:12 and I haven't had lunch
[15:12]  * Laney brb
[15:14] <jamespage> mterry, hey - thanks for all the MIR reviews - much appreciated
[15:14] <mterry> jamespage, yw, good break from other work for me  :)
[15:15] <jamespage> and if there are any archive-admins around, we have a hole load of main promotions that can be done for wily to unblock dep-waits for numerous openstack bits and pieces
[15:29] <slangasek> pitti: will there be a way for developers to rerun a test from the web ui, like exists today for jenkins?
[15:32] <pitti> slangasek: lots of work and doesn't seem like a blocker, so not at the top of my list right now
[15:32] <pitti> if we can get it behind SSO, sure
[15:35] <slangasek> pitti: right, no need for it to be at the top of the list, I just don't like the idea of retries having to be managed by a small set of people with ssh access to the right server
[15:35] <pitti> slangasek: extending this to "everyone in canonical" is reasonably easy, but as it requires VPN extending it beyond that is lots more work
[15:36] <pitti> err, not actually VPN, we just need to open the firewall; but again, need to find a way to put SSO in front of rabbitmq
[15:36] <slangasek> right, so having that in the web interface would be nice :)
[15:37] <pitti> ac
[15:37] <pitti> k
[16:07]  * Laney likes that the same discussion just happened twice :P
[16:08] <bdmurray> mvo: regarding apt-clone if o.origin is empty and archive is not now, is it fair to say the package was installed from a .deb file?
[16:18] <mvo> bdmurray: most likely in this case the Release file has nothing/not much set in its headers. there is no distinction right now for "from-some-archive" or "from-dpkg-directly"
[16:20] <bdmurray> mvo: got it
[18:59] <barry> where is codespeak-lib 1.4.30-1?  this failure makes no sense: https://launchpadlibrarian.net/211833349/upload_7660667_log.txt
[19:07] <hjd> barry: Hm... If you search for the binaries, you can find that they do indeed exist http://packages.ubuntu.com/wily/python3-py, but seem to have come from a completely different package https://launchpad.net/ubuntu/+source/python-py
[19:08] <barry> hjd: ah from that changelog it looks like maybe codespeak-lib source package should be removed from the archive?
[19:09] <hjd> Looks like it. Just found https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792109
[19:10] <barry> hjd: looks like i should remove-package -s it from ubuntu too
[19:11]  * barry something else since apparently -s doesn't mean "source" any more
[19:19] <barry> slangasek, infinity perhaps has permission for ^^ ?
[20:09] <bdmurray> pitti: Do you have any plans for an apport upload before your holiday? I'm thinking about bug 1470572.
[22:44] <bdmurray> slangasek: in MIR bug 1315313 oxide-developers ended up being subscribed to the package which isn't a team in the package to team mapping. Do you think the MIR process should include a list of team names?
[23:05] <slangasek> bdmurray: as long as there's a process for adding other teams to the list also