[00:17] <robert_ancell> ochosi, how odd!? Does normal screensaver stuff work?
[00:17] <robert_ancell> cjwatson, I'm working on merging it now, I *think* it's just a matter of making the -core package out of the existing packages, but not 100% sure I've missed something
[00:18] <cjwatson> robert_ancell: well, if you can get it to work ... I'd suggest fairly careful upgrade-testing in schroot instances though
[00:19] <cjwatson> I won't actually be *that* sorry to lose touched-it-last on that one
[00:19] <ochosi> robert_ancell: yeah, within the session everything is fine, but XSetScreensaver (..) and XForceScreensaver don't seem to cause a reaction in the greeter (even though it's all plain xlib as far as i understand)
[00:20] <robert_ancell> cjwatson, :)
[00:20] <ochosi> i.e. "xset s $timeout" works also with nouveau during a session
[00:20] <robert_ancell> ochosi, did you try calling xset from the greeter to confirm it's not your code?
[00:21] <ochosi> robert_ancell: ehrm, how would i do that? is there an interactive console hidden in the greeter? :)
[00:21] <robert_ancell> ochosi, I mean using system()
[00:21] <ochosi> robert_ancell: ah, never tried that (and didn't know about it), thanks, will give that a go!
[00:26] <Noskcaj> Can someone take a look at bug 1244629 ? It's my first attempt at an SRU bug
[00:30] <ochosi> robert_ancell: ok, seems like the values in X get set accordingly, the screen just doesn't blank with nouveau (i.e. something with the X11-screensaver extension seems borked there)
[01:13] <Noskcaj> doko, Can you merge the NMU for python-werkzeug to ubuntu? It should fix the test failure
[01:51] <robert_ancell> cjwatson, you blacklisted the fonts-* packages (http://paste.ubuntu.com/6748084/) "to conflicts with existing Ubuntu-versioned binaries" - I can't see any existing binaries with those names
[02:02] <cjwatson> robert_ancell: that's the thing you're working on
[02:02] <robert_ancell> cjwatson, the ttf-indic-fonts source package?
[02:03] <robert_ancell> cjwatson, we appear to have all the font packages available (e.g. fonts-lohit-beng-bengali) which obsolete the ttf-indic-fonts binary packages
[02:03] <cjwatson> robert_ancell: yes - fonts-beng ships a ttf-bengali-fonts binary package, which is currently in ttf-indic-fonts
[02:03] <cjwatson> robert_ancell: does fonts-beng not need a -core version then?
[02:04] <robert_ancell> cjwatson, no, fonts-beng just has "Depends: fonts-lohit-beng-bengali, fonts-lohit-beng-assamese, fonts-beng-extra"
[02:04] <robert_ancell> and all those exist in the archive
[02:04] <cjwatson> oh, it's actually a recent change for it to have dropped ttf-bengali-fonts
[02:04] <robert_ancell> and fonts-indic just depends on fonts-beng and friends
[02:04] <robert_ancell> yeah
[02:04] <cjwatson> look at rmadison -u debian -S fonts-beng and you'll see what I mean
[02:05] <cjwatson> so is it all fine enough grained now that we can just select a reasonably small set of fonts by package name?
[02:05] <robert_ancell> no, but we have all the binary font packages there and not the metapackages
[02:05] <cjwatson> one serif and one sans-serif per language was apparently the former criterion
[02:05] <robert_ancell> so it seems like we might as well have those too
[02:06] <cjwatson> we shouldn't sync if it's going to regress this though
[02:06] <cjwatson> if we still need to apply a split, that's effectively a merge
[02:06] <robert_ancell> we still have the old ttf-* package that is on the image, but it is just removed if you install the newer fonts-* packages
[02:06] <cjwatson> sure, but that's not indicative in itself ...
[02:07] <robert_ancell> cjwatson, so, you're saying we should hold back the metapackages until we have a solution for more finely grained fonts?
[02:07] <cjwatson> I dunno, it's late.  Please batch up the set of things you think I should be removing from the blacklist and mail them to me so I can think about them when I'm awake?
[02:07] <robert_ancell> sure, thanks
[03:25] <slangasek> /usr/include/qt4/QtCore/qatomic_arch.h:98:38: fatal error: QtCore/qatomic_aarch64.h: No such file or directory
[03:25] <slangasek> hmph
[03:31] <Logan_> slangasek: I just got that same FTBFS on a package that I just uploaded
[03:31] <slangasek> Logan_: cool, are you feeling inspired to track down the bug in qt4-x11? :)
[03:32] <Logan_> I am actually feeling especially inspired today
[03:32] <Logan_> lemme see what I can do
[03:33] <Logan_> this came about with the latest upload, right?
[03:33]  * Logan_ pokes shadeslayer just in case he's alive
[03:33] <slangasek> no idea; I just saw it in an avahi build
[03:34] <Logan_> looking at the diff
[03:35] <Logan_> oh wonderful, it's making Firefox hang
[03:38] <Logan_> https://launchpadlibrarian.net/162395910/buildlog_ubuntu-trusty-arm64.unixodbc-gui-qt_2.3.0-3ubuntu1_FAILEDTOBUILD.txt.gz is the other package that just FTBFSed on arm64, fwiw
[03:39] <slangasek> O horror, a delta for unixodbc-gui-qt and you haven't forwarded it to the Debian maintainer ;)
[03:39] <Logan_> oh hi maintainer :P
[03:40] <Logan_> slangasek: I'm going to take a gander
[03:40] <Logan_> I think:
[03:40] <Logan_> -usr/include/qt4/Qt/qatomic_aarch64.h
[03:40] <Logan_> in the .install diff has something to do with it :P
[03:40] <slangasek> heh
[03:41] <Logan_> the file still exists, so I think it's just a semi botched merge
[03:41] <Logan_> should I try adding it back to the install file?
[03:41] <slangasek> makes sense to me
[03:41] <Logan_> watch this be maintained in a Bazaar branch
[03:42] <Logan_> I hate it when that happens
[03:42] <Logan_> oh, it's also in Main
[03:42]  * Logan_ isn't a core dev :'(
[03:45] <Logan_> slangasek: what should we do? you're a core dev, so you can upload to Kubuntu branches
[03:47] <Logan_> slangasek: here's the relevant part of the diff: http://paste.ubuntu.com/6748482/
[03:48] <Logan_> Riddell: Around?
[03:50] <slangasek> Logan_: you could certainly do a bzr mp for it; grabbing the branch now to look
[03:50] <Logan_> Kubuntu tends to ignore merge proposals on their branches, unfortunately
[03:50] <Logan_> I've tried in the past
[03:51] <Logan_> shoot, now Qt stuff in the rebuild queue is failing, which will create false positives
[03:53] <Logan_> slangasek: unless you were to approve my mp? :P
[03:53] <slangasek> I could presumably do this :)
[03:53] <Logan_> okay, I'll propose in a few. I'll ping you
[03:55] <Logan_> ...don't mind me
[04:02] <Logan_> slangasek: here's your freshly-baked mp: https://code.launchpad.net/~logan/kubuntu-packaging/qt4-x11-arm64/+merge/201535
[04:04] <Logan_> thanks Steve! :)
[04:06] <slangasek> Logan_: sure thing :)  (now, finding all the bits so that I can actually upload it is another matter)
[04:06] <Logan_> right
[04:06] <Logan_> should we test it in a PPA first?
[04:08] <Logan_> or is this relatively trivial?
[04:12] <slangasek> Logan_: I'm not testing in a ppa.  Have you done a test binary build?
[04:13] <Logan_> slangasek: I can't really do it locally - it takes 1.5 hours to build on the build
[04:13] <slangasek> looks like it'll take another 4 minutes for the tarball to get here over the pub wifi, so you have time yet to test ;)
[04:13] <Logan_> buildd
[04:13] <slangasek> ah, k
[04:14] <Logan_> so should I push to a PPA?
[04:14] <Logan_> it'll probably take forever...
[04:16] <slangasek> Logan_: nope, it's not worth taking the ppa time up for verifying something that's as low-risk as this
[04:16] <Logan_> ok
[04:25] <micahg> hggdh: thanks, done
[04:27] <Logan_> hey Micah!
[04:34] <Logan_> slangasek: How's it going?
[04:35] <slangasek> Logan_: uploading now
[04:35] <Logan_> sweet
[05:10] <Netsnipe> hi everyone
[05:12] <Netsnipe> does anyone know which package/project that the Ubuntu AMIs are covered by in Launchpad?
[05:13] <Netsnipe> Ubuntu AMIs in AWS that is.
[05:14] <Logan_> tumbleweed: Are you around?
[05:30] <pitti> Good morning
[05:30] <pitti> Logan_: indeed, I guess it's about time
[05:30] <Logan_> pitti: Morning! I forget when it happened the last cycle. Should I check?
[05:31] <pitti> Logan_: it's usually "when we have the feeling it's a good time" :)
[05:31] <Logan_> Ah.
[05:31] <Logan_> I'm indifferent, honestly. I've been getting hardly any crashes.
[05:31] <pitti> there isn't that much churn on GNOME etc. that we expect much breakage in the beginning
[05:31] <pitti> and we have errors.u.c., too
[05:31] <Logan_> True.
[05:33]  * Logan_ shrugs. Just a thought.
[05:34] <Logan_> Maybe closer to Alpha 2 would make more sense.
[05:34] <Logan_> That's when it was done for Oneiric, at least.
[05:37] <Logan_> It was enabled on June 21 for Trusty, which was before Alpha 1. Hmm.
[05:37] <pitti> right, that's our usual time
[05:37] <Logan_> So I guess it makes sense to enable it now.
[05:39] <Logan_> Especially since this will be an LTS. We want crash reports to be as visible as possible, I think.
[06:14] <Logan_> slangasek: it built successfully on a few arches so far, so that's good - I'll try rebuilding the affected packages in the morning
[06:14] <slangasek> Logan_: spiff, thanks
[07:55] <dholbach> good morning
[08:30] <Logan_> slangasek: https://launchpad.net/ubuntu/+source/unixodbc-gui-qt/2.3.0-3ubuntu1/+build/5455791 hooray
[08:45] <mitya57> LoganCloud: thanks for fixing it!
[09:05] <Laney> @pilot in
[09:20] <darkxst> Laney, can you take a look at gnome-themes-standard during your shift?
[09:20] <Laney> okay
[09:23] <doko> zul, ntdb needs a MIR (b-d of samba)
[09:27] <doko> seb128, unicode-data needs a MIR (b-d of gucharmap)
[09:27] <doko> same for the recommends of http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg ttf-indic-fonts
[09:28] <seb128> doko, thanks for pointing it out
[09:28] <doko> and see indicator-datetime and lightdm
[09:28] <doko> and fonts-wqy-microhei
[09:29] <seb128> ?
[09:29] <seb128> doko, you are looking at component-mismatch?
[09:30] <seb128> doko, those are not real issues, they are provides resolved in a confusing way because of ppc64el builds missing
[09:31] <seb128> well, they are issues in the sense that we should make e.g unity-greeter and unity build on ppc64el
[09:31] <seb128> it's just that e.g lightdm recommends a greeter, with unity-greeter as preferred, but that one is not available so it fallback to the gtk one
[09:32] <seb128> the indicator has the same issue, it needs a rendered and our default one is unity
[09:33] <seb128> doko, unicode-data ... https://launchpad.net/ubuntu/+source/unicode-data ... do you know why it was demoted in trusty?
[09:33] <seb128> doko, it has a MIR approved/closed and was in main in saucy
[09:34] <doko> seb128, maybe it did fell out, and pitti was quick to demote it? ;p
[09:34] <doko> re-promoting
[09:34] <seb128> I don't think pitti does archive admin cleanups nowadays, you need to find somebody else to point finger there ;-)
[09:34] <seb128> danke
[09:35] <doko> in the past he was quicker than I could fix bugs ;)
[09:36] <mitya57> doko: fonts-wqy-microhei is a rename of ttf-wqy-microhei, if the previous one was in main the new one can also be safely promoted
[09:36] <doko> micahg, yes, needs a MIR for xdelta3
[09:36] <doko> mitya57, ^^^
[09:36] <mitya57> Do renames really need a MIR?
[09:37] <mitya57> Oh, or is it a new dependency?
[09:37] <doko> mitya57, it's a new b-d
[09:37] <Laney> Has our ubuntu delta been applied to fonts-wqy-microhei?
[09:38] <mitya57> Laney: yes
[09:38] <mitya57> I am amazed by the changelog, but it doesn't say anything about xdelta
[09:39] <Laney> wow, that changelog
[09:46] <doko> tkamppeter, pitti: please see the splix ftbfs in -proposed, seems to be apport related. https://launchpadlibrarian.net/162345035/buildlog_ubuntu-trusty-i386.splix_2.0.0%2Bsvn315-1fakesync1_FAILEDTOBUILD.txt.gz
[09:47] <pitti> doko, seb128: no, I didn't touch component-mismatch recently
[09:47] <doko> pitti, there was a smiley ...
[09:47] <pitti> tkamppeter: ^ seems the merge/sync dropped our apport hook?
[09:48] <pitti> doko: (no worries)
[09:50] <mitya57> pitti: the changelog says "* Add apport hook on Ubuntu and derivatives (reduces the package delta)."
[09:50] <pitti> yeah, I figure someone forgot to git add the file
[09:51] <mitya57> Also, the restriction doesn't make much sense as Debian has apport package as well
[09:51] <OdyX> tkamppeter already reported it to debian-printing, I'm waiting on the maintainer (or a patch). Best would be a normal bug with a patch that'd allow NMU.
[09:56] <mitya57> doko: xdelta3 package looks sane to me, do you know any team that can be subscribed to bugs/
[09:56] <mitya57> s/\//?/
[09:56] <ggvaberi>  hello. I need to write bash script and need some gnome theme setting. for example icon-theme. I use gsettings command for it but not sure if this command is stable part of gnome. can i use this command and be sure that it will come with gnome always?
[09:57] <doko> mitya57, fonts? desktop? enoclue
[09:57] <mitya57> ggvaberi: Yes, gsettings is stable and is not going to go away
[09:57] <mitya57> doko: It is a binary variant of diff/patch, mostly unrelated to fonts or desktop
[09:58] <mitya57> Will you approve the MIR if I'll be the only person subscribed?
[09:58]  * mitya57 was one who synced fonts-wqy-microhei, so I feel responsive for fixing the mess :)
[09:59] <doko> mitya57, no, should be a team. seb128, could the desktop team do that?
[10:01] <seb128> mitya57, doko: subscribe desktop-bugs if you want
[10:01] <doko> thanks
[10:03] <mitya57> I can't do that
 thank you. :)
[10:11] <doko> mvo, https://launchpad.net/ubuntu/+source/aptdaemon/1.1.1-1ubuntu2/+build/5304049/+files/buildlog_ubuntu-trusty-i386.aptdaemon_1.1.1-1ubuntu2_FAILEDTOBUILD.txt.gz
[10:20] <ggvaberi> and one more question. Is possible to access to key org.gnome.desktop.interface icon-theme by dbus? for make alternate to this command 'gsettings get org.gnome.desktop.interface icon-theme' but using only dbus, without gtk gio or GSettings.
[10:36] <mitya57> doko: bug 1268905 filed
[10:36] <mitya57> Had to submit a watch file to Debian for that :/
[10:41] <mitya57> doko: please really subscribe desktop-bugs if you can
[10:41] <doko> mitya57, seb128 has to do that
[10:44] <doko> jamespage, please subscribe to the new packages in https://bugs.launchpad.net/ubuntu/+source/parsedatetime/+bug/1268909
[10:45] <seb128> doko, mitya57: done
[10:56] <doko> mitya57_, promoted
[10:57] <mitya57_> thanks!
[11:08] <mitya57> Laney: hi, are you still piloting? Can you maybe upload lp:~kubuntu-packagers/kubuntu-packaging/qt, which fixes bug 1268690?
[11:09] <Laney> mitya57: ok
[11:09] <mitya57> Thank you!
[11:14] <Laney> xnox: could you please check the argyll merge?
[11:14] <Laney> I'm not sure if your patch is obsoleted
[11:19] <cjwatson> pitti: Are the precise language packs good to promote to -updates?
[11:19] <pitti> cjwatson: I built them one week ago; I haven't heard any problems about them, so yes from my POV
[11:19] <pitti> cjwatson: they were meant for 12.04.4 preparation, and we thought we'd build them early to have them in iso testing
[11:20] <pitti> (and I checked a few of them with binary debdiffing)
[11:21] <cjwatson> pitti: OK, cool, I'll see about copying those then
[11:21] <pitti> $ sru-release --pattern precise language-pack-
[11:22] <pitti> cjwatson: thanks
[11:22] <cjwatson> Yep, I just found the operator guide off the AA wiki
[11:32] <jodh> Laney: xnox is away this week.
[11:33] <Laney> jodh: I see
[11:41] <tumbleweed> LoganCloud: hi
[11:54] <ahmed__> hi
[11:54] <ahmed__> hi
[11:54] <ahmed__> how to create .deb file ?
[11:55] <ahmed__> I have project wanna to publish in .deb format
[11:56] <davmor2> ahmed__: that is better asked on the #ubuntu-app-devel channel, but there are some wiki guides for building a deb package
[12:13] <ahasenack> pitti: hi, around? Question about postgresql 9.1 -> 9.3 upgrade to trusty
[12:13] <ahasenack> pitti: there is no 9.1 in trusty, and no 9.3 in < trusty, so if you upgrade, your db is gone (not erased, just not accessible)
[12:14] <ahasenack> what's the plan, upgrade to 9.3 from apt.postgresql.org on ubuntu < trusty and then upgrade to trusty?
[12:14] <pitti> ahasenack: why is -9.1 gone? it shouldn't get removed during upgrade, we have some special handling for that in update-manager
[12:15] <pitti> ahasenack: the intention is that on upgrade you keep the precise (or saucy) -9.1 packages and the "obsolete version" debconf note which explains how to upgrade to 9.3
[12:15] <ahasenack> pitti: 9.1 packages are not in trusty as far as I can see, only plperl, client and server-dev
[12:15] <pitti> ahasenack: right, only -plperl, as we don't want to support *installing* -9.1 in trusty
[12:15] <ahasenack> pitti: https://launchpad.net/ubuntu/+source/postgresql-9.1/+changelog rbasak pointed me at that
[12:15] <ahasenack> pitti: the 9.1 packages were removed as far as I can tell, let me try to find sometihng in the logs
[12:15] <pitti> ahasenack: we need plperl as precise's/raring's etc. plperl packages don't work in trusty, due to how perl is packaged; but the rest works
[12:16] <pitti> ahasenack: yes, yes, I know
[12:16] <pitti> ahasenack: they are removed from the trusty *archive*
[12:16] <ahasenack> pitti: the machine was "accidentally" upgraded to trusty, I don't know who did it (it's a shared machine)
[12:16] <pitti> ahasenack: but they shoudln't get removed *from your system* on upgrade
[12:16] <ahasenack> pitti: so let me double check that, but the person who found this out had to install 9.1 from apt.postgresql.org
[12:17] <pitti> ahasenack: ok, I'd need the /var/log/dist-upgrade/ logs for that, to see why postgresql-9.1 got removed
[12:17] <ahasenack> ok
[12:17] <pitti> it's certainly not intended that it gets removed; and as you say, this would lock you out from your clusters
[12:22] <ahasenack> pitti: I think it was a hackjob, whatever happened release-upgrade wasn't involved, those logs are from may 2013
[12:22] <ahasenack> pitti: I'll ping again if i find anything that points to a bug
[12:22] <pitti> ahasenack: apt-get dist-upgrade should be fine, too
[12:23] <pitti> ahasenack: do you know from which release it was upgraded? I can try in a chroot
[12:23] <ahasenack> pitti: so keeping 9.1 would not be a release-upgade trick, just plain packaging deps
[12:23] <ahasenack> pitti: I was told saucy, but i see commented quantal lines in sources.list
[12:23] <pitti> ahasenack: right; the "trick" in u-m is just to avoid removing packages which went away
[12:23] <pitti> ahasenack: i. e. usually u-m does that, but it shouldn't for postgresql
[12:24] <ahasenack> ok, saucy, confirmed
[12:24] <ahasenack> via .save files in sources.list.d
[12:24] <pitti> I'll try after lunch
[12:44] <jamespage> doko, ubuntu-server subscribed to those two packages
[13:00] <Laney> @pilot out
[13:00] <Laney> mitya57: I uploaded it
[13:00] <Laney> there's some autopkgtest failures on excuses for the previous version
[13:01] <mitya57> Laney: Thanks, will take a look at the failures
[13:01] <mitya57> Oh, so all those users who filed those bugs were using -proposed :(
[13:02] <Laney> yeah, it happens
[13:02] <Laney> on the bright side it found a bug
[13:03] <mitya57> Right :)
[13:13] <mitya57> Humm, both those tests never passed, not sure if they should really block the migration
[13:38] <hggdh> micahg: ubuntu-uploaders membership does not expire anymore
[14:42] <mterry> @pilot in
[14:44] <barry> doko: how's the test rebuild going?  is there a new page with results?  the link you gave me last week still has no results for anything but main
[14:45] <doko> barry, there's enough to fix in main ;)
[14:45] <doko> barry, also, jamespage might want your help with python-django-compressor
[14:46] <barry> doko: yeah ;)  i'm going to try to spend some time on that today.
[14:46] <barry> jamespage: sure thing, feel free to ping me
[14:49] <doko> cinder
[14:49] <doko>   needs webop?
[14:49] <doko> click:
[14:49] <doko>   test failures
[14:49] <doko> distro-info:
[14:49] <doko>   test failures
[14:49] <doko> genshi:
[14:49] <doko>   test failures
[14:49] <doko> germinate:
[14:49] <doko>   test failures
[14:50] <doko> grub2-signed:
[14:50] <doko>   test failures
[14:50] <doko> barry: ^^^ these are python3.4 as default related ftbfs
[14:51] <barry> doko: ack.  i'll look at those first
[14:58] <mterry> cyphermox, I'm looking at bug 1264630.  Do you have any background info on how safe that sync would be?
[14:59] <Laney> we already talked about that in #ubuntu-desktop earlier
[14:59] <mterry> oh
[14:59] <Laney> someone should have commented :(
[14:59] <Laney> but cyphermox said he'd handle it, so I'd assign it to him and remove sponsors
[14:59] <mterry> ok, will do
[15:01] <micahg> hggdh: thanks
[15:09] <knocte> Cimi: ping
[15:09] <Cimi> knocte, pong
[15:10] <knocte> Cimi: hey! been already a week since your review: https://code.launchpad.net/~knocte/ubuntu-themes/bring-back-zebra-striping/+merge/200429 why is not merged? I thought the bots would do it
[15:15] <knocte> Cimi: if I'm missing some very important aspect about launchpad, please enlighten me!
[15:15] <Cimi> knocte, I don't know :) I'll have a look later
[15:15] <knocte> cool thanks :)
[15:16] <Laney> knocte: Cimi: At the very least it hasn't been top approved
[15:16] <knocte> Laney: what does that mean?
[15:16] <Cimi> Laney, you right
[15:16] <Cimi> Laney, top apprived
[15:16] <Laney> Status: needs review
[15:16] <Laney> -> approved
[15:17] <knocte> oh thanks, is there any launchpad docs where it explains this better? I find https://dev.launchpad.net/UsingMergeProposals a bit lacking
[15:18] <Laney> umm, not sure, it's part of the Ubuntu-specific CI process
[15:20] <Laney> https://wiki.ubuntu.com/DailyRelease/ & friends is probably useful, although that is being redesigned a bit atm
[15:22] <knocte> Laney: cheers
[15:27] <zul> doko/barryw: doko ping
[15:28] <doko> ?
[15:28] <zul> doko:  python-lxml  imports beautifulsoup but there is not build dependency? does that make sense
[15:30] <doko> zul, maybe not
[15:31] <tumbleweed> isn't that only in the soupparser module?
[15:31] <zul> doko:  im asking because beautifulsoup is in universe and bs4 is in main
[16:29] <LoganCloud> Tumbleweed: I noticed that you originally added DDE support to pull-lp-source. It appears to be dead, so the script now hangs for a bit, trying to resolve it, if you don't specify an actual package
[17:36] <rbasak> I'm about to upload an apache2 merge, where some functionality has moved to a different source package (mpm-itk) that has already synced to universe. There's a transitional binary generated by the apache2 source now, which depends on that. How do I get that transitional binary overriden to universe, and is this the right thing to do?
[17:37] <rbasak> (I'm not sure that we need an MIR for mpm-itk, but in any case I'd like to at least get apache2 done first)
[17:38] <cjwatson> rbasak: tell #ubuntu-release when it appears in NEW
[17:38] <rbasak> OK, thanks.
[17:38] <cjwatson> rbasak: or just don't worry about the overrides and we'll figure it out
[17:38] <rbasak> Great. Just wanted to make sure that I'm not causing trouble :)
[17:47] <infinity> rbasak: Well, we need to make a decision (you need to make a decision) about whether you want to support mpm-itk installations, and thus move it all to main, or vice versa.
[17:48] <infinity> rbasak: But yeah, if your take is that the install base is low, you don't care about main-only upgrades, and you'd rather have itk in universe, that'll pretty much sort itself, cause we'll demote things the tools tell us to demote due to not being seeded.
[18:08] <rbasak> Hmm. It looks like apache2-mpm-itk has always been in universe, so maybe it's overridden already.
[18:27] <glass|2> hi, i've unsquashed and then resquashed filesyste.squashfs, rebuilt the iso but at boot it show only a initrd shell. how fix this?
[18:33] <mterry> @pilot off
[18:33] <udevbot> (pilot (in|out)) -- Set yourself an in or out of patch pilot.
[18:33] <mterry> @pilot out
[18:33] <mterry> ahem
[18:38] <tumbleweed> LoganCloud: aah, best solution is probably to fix DDE
[18:39] <LoganCloud> Tumbleweed I have no idea how long it's been dead
[18:40] <tumbleweed> yeah, I always use src: syntax
[18:40] <LoganCloud> Maybe we should contact the maintainer
[18:41] <LoganCloud> Lunch, bbl
[18:41]  * cjwatson swears at hg and runs "git hg clone http://hg.python.org/cpython" so he has some hope of deciphering the history
[18:41] <tumbleweed> LoganCloud: erm, seems to be working just fine for me
[18:42] <LoganCloud> Tumbleweed http://dde.debian.net/dde/
[18:43] <LoganCloud> Couldn't connect to server
[18:43] <tumbleweed> oh, I lie
[18:43] <tumbleweed> I'll poke enrico
[18:43] <LoganCloud> Ok thanks
[18:45] <tumbleweed> LoganCloud: apache seems down on that box
[19:29] <kentb> is there a way to test whether or not a fix works for a ftbfs on ppcel64?
[19:29] <kentb> err ppc64el
[19:32] <cjwatson> No porter boxes as yet, but you can often guess fairly reliably by e.g. observing whether a build on another architecture updates the autotools files that need to be updated
[19:33] <cjwatson> (Or rather, not ones that are generally available)
[19:36] <kentb> ok. thanks!
[19:37] <kaie> Hi darkxst: Regarding your gdm update 3.0.4-0ubuntu15.2 which is used on 12.04 lts. It broke automatic startup of the display manager. On my system, the plymouth-ready event, which have added as a precondition for starting gdm, is never produced.
[19:38] <kaie> I had to remove that precondition from /etc/init/gdm.conf
[20:15] <kaie> I sent email to Tim. Cheers
[20:30] <Logan_> How can we bootstrap ghc for arm64 and ppc64el? It needs itself apparently...
[20:31] <Logan_> Oh, never mind. I see the ML thread.
[20:31] <Logan_> cjwatson: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2013-December/014796.html Any chance of getting that going?
[20:40] <cjwatson> Logan_: I tried for ppc64el, still haven't got it working
[20:40] <Logan_> :/
[20:40] <cjwatson> Logan_: (but not given up)
[20:40] <Logan_> so much yellow in the FTBFS list, lol
[20:40] <cjwatson> Logan_: AFAIK arm64 needs upstream work; maybe with 7.8
[20:41] <cjwatson> Logan_: I did get a stage1 ghc that sort of worked to the point of producing a useful hello-world, but it crashed upon trying to do anything complicated
[20:41] <cjwatson> Logan_: and unfortunately it tends to take hours per iteration
[20:41] <cjwatson> (to build on my laptop, that is)
[20:42] <cjwatson> so, yeah.  will try again soonish
[20:42] <Logan_> ah, cool. thanks for your work!
[20:43] <Laney> keep an eye on https://ghc.haskell.org/trac/ghc/ticket/7942
[22:25] <barry> infinity, wgrant: doko said i should ping you about his test rebuild and put backs.  i just uploaded a new version of nose to the main archive, which should fix several of his build failures.  can you copy these to his test-rebuild-20140108 and put back the following packages: pastedeploy, python-dbusmock, python-oauthlib, python-webob ?  (if webob builds okay, then there will be a couple more retries)
[22:25] <infinity> barry: If it's already built and in the release pocket, there's nothing to copy.  Just some give-backs.
[22:27] <barry> infinity: cool.  nose 1.3.0-2.1ubuntu1 hasn't been promoted from proposed yet, so i'll wait for that and then ping you for the retries
[22:27] <barry> infinity: https://launchpad.net/ubuntu/+source/nose/1.3.0-2.1ubuntu1
[22:27] <infinity> barry: Yeah, found it. :)
[22:27] <barry> :)
[22:35] <infinity> barry: Looks like you just got promoted.
[22:38] <jtaylor> barry: would you sponsor a cython test fix?
[22:38] <jtaylor> I want to get numpy in, but I guess I need to fix cython first :/
[22:39] <jtaylor> at some point we need 0.20 for py3.4
[22:39] <jtaylor> but its not released yet
[22:47] <barry> infinity: yay!  can you do the give backs?
[22:47] <infinity> barry: Once the publisher's done, yeah.
[22:47] <barry> jtaylor: sure, i'll take a look
[22:48] <barry> infinity: thanks
[22:49] <barry> jtaylor: if you tell me where to look ;)
[22:49] <jtaylor> its not done yet, just checking if some one would look at it
[22:50] <barry> jtaylor: ah, okay.  nearing eod but i'll be here for a little while longer
[22:50] <jtaylor> I'll file a merge tomorrow, won't get a build done today anymore, takes about 3 hours :/
[22:51] <barry> jtaylor: lucky for you i'm also piloting tomorrow :)
[22:55] <jtaylor> are there any plans to backport a way to get the multiarch tag to precise?
[22:56] <jtaylor> I'm guessing no, but it makes it impossible to propose sane fixes to upstreams :/
[22:56] <jtaylor> *from python
[22:59] <infinity> barry: Those 4 seemed to be much happier.
[22:59] <barry> infinity: awesome, thanks.  will look in a sec
[23:07] <barry> infinity: looking good!  can you retry cinder (might work with the new webob now)
[23:08] <infinity> barry: That's not going to work.  The rebuild archive doesn't rebuild against itself, only against the primary archive (it throws away the binaries).
[23:08] <infinity> barry: But if the goal here is to make these all have py3.4 support, perhaps some archive uploads are in order?
[23:09] <barry> infinity: ah, didn't know that.  yep, i'll take it from here.  thanks
[23:54] <apb1963> Setting up google-chrome-stable (32.0.1700.77-1) ...
[23:54] <apb1963> /var/lib/dpkg/info/google-chrome-stable.postinst: 26: /var/lib/dpkg/info/google-chrome-stable.postinst: update-desktop-database: not found
[23:54] <apb1963> oops.  Sorry
[23:54] <apb1963> Wrong button
[23:54] <apb1963> Does anyone know how to update Qt to a later version? Kubuntu 12.04.3, KDE 4.12.0, Qt 4.8.2
[23:57] <apb1963> In reference to
[23:57] <apb1963> Setting up google-chrome-stable (32.0.1700.77-1) ...
[23:57] <apb1963> /var/lib/dpkg/info/google-chrome-stable.postinst: 26: /var/lib/dpkg/info/google-chrome-stable.postinst: update-desktop-database: not found
[23:57] <apb1963> dammit
[23:57] <apb1963> In reference to: https://bugs.kde.org/show_bug.cgi?id=329793
[23:58] <apb1963> Which just happened to me again now.
[23:59] <sarnold> apb1963: yikes. if you do replace your qt with upstreams, you're going to be on one funky system...
[23:59] <sarnold> apb1963: have you filed the bug against ubuntu yet?
[23:59] <apb1963> Well, it seems my system is already funky