[03:45] <pitti> Good morning
[03:45] <Unit193> Howdy.
[03:49] <pitti> wgrant: hm, seeing all the -dbgsyms in https://launchpad.net/ubuntu/wily/+queue?queue_state=0 is moderately confusing
[03:54] <wgrant> pitti: Hm, indeed. +queue has its own special way of determining what is new, and it clearly doesn't work properly here.
[03:54] <wgrant> (but the calculation for when things should be held in new is correct)
[03:54] <wgrant> Can you file a bug?
[03:54] <pitti> wgrant: yep, will do
[03:55] <Snow-Man> mwahahahaha
[03:55] <Snow-Man> spread the good news- PostgreSQL now has UPSERT.
[04:29] <pitti> Snow-Man: that sounds like someone was interrupted by a phone call when writing SQL..
[04:30] <Snow-Man> hahaha
[06:19] <pitti> wgrant: filed bug 1452996 (should be "low" importance I guess, mostly just a visual distraction)
[06:23] <wgrant> pitti: Thanks.
[07:01] <dholbach> good morning
[07:02] <ts> morning bach
[07:15] <pitti> hey dholbach
[07:17] <dholbach> hey pitti
[07:19] <seb128> hey dholbach & pitti
[07:20] <dholbach> hey seb128 :)
[07:27]  * mgedmin wonders if pitti'll be interested in https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1453011
[07:44] <LocutusOfBorg1> hi folks, now that the builders are somewhat idle, can anybody please retry this build? https://launchpad.net/ubuntu/+source/hedgewars/0.9.21.1-5
[07:44] <LocutusOfBorg1> seems that locally it is building correctly now
[07:45] <LocutusOfBorg1> (at least the haskell stuff seems to be fine on amd64)
[07:47] <infinity> LocutusOfBorg1: amd64 still seems full of sadness.
[07:50] <LocutusOfBorg1> can you please explain me why in my local wily pbuilder-dist environment it doesn't behave like that? I'm lost
[07:50] <geser> LocutusOfBorg1: did you try building with wily-proposed enabled in your local builder?
[07:50] <infinity> LocutusOfBorg1: What he said.
[07:51] <LocutusOfBorg1> I tought proposed was enabled by default
[07:51] <LocutusOfBorg1> bad me, I didn't check
[07:52] <LocutusOfBorg1> how can I enable them in pbuilder-dist?
[07:52] <LocutusOfBorg1> I see from the man page they should be enabled by default
[07:53] <infinity> No idea, don't use pbuilder.
[07:53] <LocutusOfBorg1> anyway, I'll sort it out, sorry for the noise
[07:54] <LocutusOfBorg1> thanks
[07:55] <LocutusOfBorg1> anyway, seems that there is a bug in pbuilder, I see them
[07:55] <LocutusOfBorg1> http://paste.ubuntu.com/11022144/
[07:55] <geser> LocutusOfBorg1: not sure if there is an easier way, but login into your pbuilder (don't forget to add --save-after-login), edit /etc/apt/sources.list, logout (your changes will get preserved)
[07:55] <LocutusOfBorg1> (bad css is bad)
[07:55] <LocutusOfBorg1> geser, this is what I usually do, wondering if there is a better way :)
[08:00] <LocutusOfBorg1> infinity, I use proposed, but my apt seems to be smarter and discarding them
[08:01] <LocutusOfBorg1> http://paste.ubuntu.com/11022226/
[08:01] <LocutusOfBorg1> this is funny enough
[08:02] <cjwatson> LocutusOfBorg1: I've only got up to about the third layer of <lots> of Haskell
[08:03] <cjwatson> Snow-Man: yay, maybe http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/revision/17402 can be less messy at some point
[08:03] <geser> LocutusOfBorg1: http://people.canonical.com/~ubuntu-archive/transitions/html/ghc.html , hedgewars is at level 6
[08:03] <LocutusOfBorg1> cjwatson, the question is, why pbuilder-dist just discards the new haskell stuff and picks the release one?
[08:03] <cjwatson> LocutusOfBorg1: don't know, don't care :)
[08:04] <infinity> LocutusOfBorg1: Because pbuilder is erring on the side of "always make it build" instead of "do the right thing". :P
[08:04] <cjwatson> geser: and it's more complicated than that, because the transition order we actually want to follow is Debian's
[08:04] <cjwatson> which makes it hard enough to keep track without people jumping in and randomly retrying builds in the middle of it :)
[08:04] <LocutusOfBorg1> yeah, I think so, I should make it behave more correctly
[08:05] <infinity> LocutusOfBorg1: And that's aptitude, not apt.  The aptitude resolver is particularly silly in some cases.
[08:05] <infinity> (Granted that silliness is probably exactly what a "normal user" wants, but it's the exact opposite of what a buildd wants)
[08:05] <LocutusOfBorg1> yes, it is!
[08:05] <LocutusOfBorg1> pbuilder-dist should use apt then, not aptitude.
[08:06] <LocutusOfBorg1> I don't see any benefit in building something in the wrong way (at least in a developer tool)
[08:06] <cjwatson> LocutusOfBorg1: you could use sbuild then
[08:06] <infinity> ^
[08:07] <cjwatson> if you don't see any benefit in doing things wrong :)
[08:07] <geser> LocutusOfBorg1: check your pbuilderrc what is configured as build-dependency resolver
[08:08] <LocutusOfBorg1> I just never learned sbuild
[08:09] <LocutusOfBorg1> when a tool works flawlessly I don't see a need to change, but a bad resolver might be a good reason
[08:09] <LocutusOfBorg1> geser, yes, I need to check that too
[08:37] <pitti> seb128: hi! do you happen to be on the samba merge already? it currently causes a lot of uninstallability
[08:38] <pitti> (samba-libs in particular, needs to build against current libldb1)
[08:39] <seb128> pitti, hey, no I'm not, do I own that? I just did a bugfix upload, I was expecting zul or one of the usual samba maintainers to do that
[08:39] <seb128> technically you are the one who owns the merge due your upload from yesterday :p
[08:39] <pitti> seb128: right now, yes (TIL); I can look into it too, but indeed I've earned way too many merges due to doing archive fixes :)
[08:39] <seb128> pitti, I can have a look if you want
[08:40] <pitti> seb128: (no-change upload this morning, but it does feel like yesterday :) )
[08:40] <seb128> pitti, the TIL doesn't make much sense on complexe packages which have an usual maintainer and where somebody else do a tiny change upload
[08:40] <pitti> seb128: yeah, I know; I just don't think that samba has a "maintainer"
[08:40] <pitti> seb128: either way, just didn't want to step on your toes
[08:40] <seb128> I didn't start on it
[08:41] <seb128> I can have a look if you want though
[08:42] <pitti> seb128: doesn't look too hard; ok, I'll merge it
[08:43] <seb128> pitti, thanks
[09:09] <pitti> bdmurray: FYI, I committed http://bazaar.launchpad.net/~ubuntu-archive/apport/lp-retracer-config/revision/22 and rolled out to the LP retracers; we need the same for daisy
[09:11] <pitti> cjwatson, wgrant: I did some spot checks, and ddebs.u.c./ seems to get all the dbgsyms for wily \o/
[09:22] <cjwatson> pitti: excellent
[09:33] <wgrant> pitti: Great.
[09:44] <dodeluser> Got a question about editing "initrd.lz". According to this tutorial http://pastebin.com/qSkAXJdX   I made some changes successfully and repacked the file initrd.lz
[09:45] <dodeluser> But when copying it to /remasteredisofolder/capsper/  it has no effect...... something that I am doing wrong?
[09:45] <pitti> doko_: hm, the new version of python2.7/i386 consistently fails, this looks like a real regression?
[09:45] <pitti> doko_: (http://d-jenkins.ubuntu-ci:8080/view/Wily/view/AutoPkgTest/job/wily-adt-python2.7/4/ARCH=i386,label=adt/console)
[09:54] <mvo> pitti: silly question but what sets ADT_REBOOT_MARK in the snappy-selftes? is that outside of the selftest? I was looking into some simple upgrade test fakeing
[09:55] <pitti> mvo: adt sets it in the tests' environment, yes
[09:55] <mvo> pitti: cool, thanks
[09:55] <pitti> mvo: is the test losing it somehow? perhaps calling something through sudo which prunes the env?
[09:58] <pitti> mvo: (see https://lists.ubuntu.com/archives/snappy-devel/2015-January/000057.html for how to run them with autopkgtest, BTW)
[10:08] <mvo> pitti: no, all good, I was just curious how it works as I want to extend it
[11:25]  * LocutusOfBorg1 wonders how many packages can be syncd from unstable now that xorg is transitioning
[11:25]  * LocutusOfBorg1 looks at https://release.debian.org/transitions/html/xserver1.17.html
[11:26] <mitya57> Mirv: do you know if someone is working on qtcreator update to 3.2 / 3.3 / 3.4?
[11:27] <mitya57> The current old qtcreator has conflicting files with QBS, while a newer one can be built against our packaged QBS.
[11:45] <Mirv> mitya57: zbenjamin has probably the best estimate. he has been working on upstreaming a lot of the Ubuntu SDK modified parts like the whole CMake stuff, and the update relies on getting to some sort of state where eg. 3.4 or 3.5 is such that it makes sense to update the rest of the patches to it while dropping the upstreamed parts
[12:10] <mitya57> Mirv: ok. 3.4 was just released so maybe it's a good time to port the patches.
[12:23] <doko> pitti: can you retry?
[12:23] <pitti> doko: I can, but it didn't look flaky
[12:23] <doko> I don't see it upstream on the build bots
[12:23] <doko> http://buildbot.python.org/all/waterfall?category=2.7.stable
[12:24] <pitti> doko: running again (4th try)
[12:24] <pitti> amd64 is okay, i386 broken
[12:24] <pitti> (consistently)
[12:25] <zbenjamin> Mirv: i have a branch compiling against the current QtC master branch .
[12:25] <doko> ahh, i386 only?
[12:25] <zbenjamin> Mirv: so i would like to use that one
[12:29] <mitya57> zbenjamin: master is 3.5?
[12:29] <zbenjamin> mitya57: i think so
[12:30] <zbenjamin> mitya57: it has all our patches we need
[12:30] <mitya57> zbenjamin: Should be fine then. Can you include a change from Debian that makes it build against packaged qbs?
[12:31] <zbenjamin> mitya57: is that patch already done for QtCreator in the archive?
[12:32] <mitya57> Only in experimental.
[12:33] <mitya57> http://anonscm.debian.org/cgit/pkg-kde/qt/qtcreator.git/commit/?id=e885d186c540cc12a875640ca3d719d88d6ff1aa
[12:33] <zbenjamin> mitya57: not sure , can we Mirv?
[12:35] <Mirv> zbenjamin: yes please we can take preferably as much as possible from Debian's qtcreator packaging :)
[12:35] <Mirv> zbenjamin: we're pretty far out of sync unlike with Qt itself, but we don't necessarily need to yet to fully sync up
[12:36] <Mirv> zbenjamin: so your thought is to package 3.5 git snapshot to wily?
[12:37] <zbenjamin> Mirv: what is the release schedule for QtC?
[12:38] <zbenjamin> i hoped we get 3.5 in this cycle
[12:40] <Mirv> zbenjamin: it seems only in August https://wiki.qt.io/Qt_Creator_Releases
[12:40] <Mirv> so yes this cycle but it'd mean we're stuck with 3.1 until then
[12:46] <zbenjamin> Mirv: until then i'm fine with a snapshot i guess
[12:46] <zbenjamin> Mirv: important part is that we get a release before we do one :D
[12:47] <Mirv> zbenjamin: well wily is a development version so yes it'd be possible. as long as it like, you know, actually works :)
[12:47] <zbenjamin> Mirv: well it seems they will feature freeze in june
[12:47] <Mirv> zbenjamin: if we have that sprint we could hack on it together
[12:48] <zbenjamin> Mirv: +10000
[13:57] <mvo> pitti: is there a way to see the qemu terminal while adt runs? when it tries to ssh connect (I simulate a boot failure right now and would love to get some more info what is going on)
[13:59] <pitti> mvo: you mean the output during boot? yes, adt-run --- qemu --show-boot myvm.img
[13:59] <pitti> mvo: ah sorry, snappy runner, right?
[14:00] <pitti> mvo: hm, /usr/share/autopkgtest/ssh-setup/snappy calls -serial none
[14:01] <pitti> mvo: you could copy the script somewhere, change -serial none to e. g. -serial unix:/tmp//ttyS0,server,nowait
[14:01] <mvo> pitti: yeah, the snappy runner
[14:01] <mvo> pitti: aha, nice, let me try that
[14:01] <pitti> mvo: and then nc -U /tmp/ttyS0 while you run
[14:02] <pitti> mvo: that sounds like an useful option to add to the snappy setup script anyway, so bug report appreciated
[14:02] <mvo> pitti: can I haz this by default? maybe not with a predictable name, but as a option or something?
[14:02] <mvo> pitti: thanks :)
[14:02] <pitti> mvo: yeah, probably just to stdout?
[14:02] <mvo> +1
[14:02] <pitti> mvo: i. e. a --show-boot option?
[14:02] <pitti> (like qemu)
[14:02] <mvo> yes
[14:10] <mvo> pitti: added bug #1453154
[14:18] <pitti> mvo: ah, thanks
[19:11] <aitiba> hi
[19:11] <aitiba> ¿can I ask here about lxc - linux containers?
[19:14] <strikov> aitiba: #ubuntu-server might be the better place I think
[19:15] <aitiba> doing a "lxc exec d1 -- /bin/bash" I get "websocket: bad handshake" error ¿any ideas?
[19:15] <aitiba> sorry