[00:37] <Noskcaj> BenC, I don't have enough internet to check right now, but i believe there's a small database of debian developer locations used to find people for keysigning
[02:19] <rsalveti> xnox: was syncing the package in the archive with the branch, because I was planning on doing a small upload against it
[02:19] <rsalveti> wasn't in sync
[02:20] <rsalveti> would be nice to keep the packages in sync with the uploads
[05:52] <mitya57> lpotter: hi, is https://codereview.qt-project.org/102665 something we need to have in vivid 5.3.2 packages?
[05:52] <mitya57> I see Timo uploaded that to a silo but didn't commit to bzr for some reason.
[06:12] <pitti> Good morning
[06:12] <pitti> gnuoy`: feel free to steal merges :)
[06:14] <pitti> stgraber: network config which hangs> oh, can you please write a bug about that? will look at that ASAP
[06:15] <stgraber> pitti: bug 1414544
[06:18] <pitti> stgraber: ah, merci
[07:11] <dholbach> good morning
[08:53] <LocutusOfBorg1> hi developers
[09:39] <LocutusOfBorg1> hi pitti I'm wondering if my mail went into your spam folder :)
[09:42] <pitti> LocutusOfBorg1: no, I still have Friday's and didn't get a new one
[09:45] <LocutusOfBorg1> sent again :)
[09:51] <pitti> LocutusOfBorg1: got it
[09:52] <LocutusOfBorg1> wonderful!
[10:13] <xnox> rsalveti: yes. sorry about that. In essence there was a branch with changes "~xnox/upstart/systemd-bridge" however I've used silo to land the upload.
[10:13] <xnox> and it was manual dput, and separate branch
[10:14] <xnox> and at cleanup I did not push the branch at the same time.
[10:14] <xnox> sorry about that. Usually lp:ubuntu/upstart is up to date, or has staged changes to be uploaded next time.
[10:40] <ari-tczew> xnox: ping
[10:40] <xnox> ari-tczew: yo
[10:44] <ari-tczew> xnox: question about esys-particle package. you've added a couple of files like /debian/test/* in release 2.2.u2-2ubuntu4, but Debian has applied only one file debian/test/box30.0.geo. however, Debian approved also autopkgtest.
[10:44] <ari-tczew> xnox: can we sync that package?
[10:46] <xnox> i did not intentionally add things to debian/test dir.
[10:47] <xnox> do check if there is any delta left, and do test build in vivid before syncing
[10:49] <ari-tczew> xnox: just FYI: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/esys-particle/vivid/revision/13
[10:50] <ari-tczew> xnox: ok, delta is approved in debian and I'm building package right now.
[10:52] <tseliot> infinity: hi, do you know if this fix has ever been included in glibc? https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/967149
[12:34] <Madkiss> hey there.
[12:34] <Madkiss> is ppa.lp.net down?
[12:38] <ivoks> Madkiss: some network issues... should be over soon, if it's not already
[12:39] <Madkiss> ah, alright, thanks
[12:51] <dholbach> slangasek, who can help with the following merge proposals?
[12:51] <dholbach> https://code.launchpad.net/~ubuntu-mate-dev/debian-cd/ubuntu-mate/+merge/246189
[12:51] <dholbach> https://code.launchpad.net/~ubuntu-mate-dev/ubiquity/ubquity-mate-fixed/+merge/246079
[12:51] <dholbach> https://code.launchpad.net/~ubuntu-mate-dev/livecd-rootfs/livecd-rootfs-ubuntu-mate/+merge/244446
[13:52] <xnox> dholbach: i've tried mvo , infinity is a good one to try as well
[13:52] <xnox> i can do ubiquity myself, but at the moment my ubuntu time is focused on the hardest stuff i can work on (i.e. upstart->systemd)
[14:17] <cyphermox> xnox: thanks, I'm aware. I'll upload the fix in a bit
[14:45] <mlankhorst> what's gmsh?
[14:50] <mitya57> mlankhorst: http://launchpad.net/ubuntu/+source/gmsh — "Three-dimensional finite element mesh generator"
[14:51] <mlankhorst> I'm more curious how it blocks mesa..
[14:52] <mitya57> oh, an autopkgtest failure
[14:52] <mitya57> That seems to be a random segfault as it succeeded on amd64 and failed only on i386
[14:52] <mitya57> Perhaps pitti can retry it.
[14:53] <mlankhorst> oke
[14:53] <mlankhorst> pitti: ^ ?
[14:53] <pitti> (already at it..)
[14:53] <mlankhorst> thanks
[14:53] <pitti> err no, it's not random
[14:53] <pitti> https://jenkins.qa.ubuntu.com/job/vivid-adt-gmsh/?
[14:53] <pitti> it has never succeeded
[14:54] <pitti> i. e. it has always failed on i386, and succeeded on amd64
[14:54] <mlankhorst> ok could you override mesa then?
[14:54] <pitti> jibel: do you know why http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#mesa happens even though gmsh never succeeded?
[14:54] <pitti> jibel: https://jenkins.qa.ubuntu.com/job/vivid-adt-gmsh/?
[14:55] <pitti> mlankhorst: I will, but we shoudl investigate this first ^; I think I've seen it on other occasions
[14:56] <mlankhorst> maybe because amd64 passes?
[14:58] <jibel> pitti, looking
[15:20] <shadeslayer> is there a way to get pull-lp-source to download from vivid instead of vivid-proposed?
[15:21] <pitti> shadeslayer: just add "vivid" as the second argument
[15:21] <shadeslayer> pitti: doesn't work :(
[15:21] <pitti> shadeslayer: or "precise", "trusty-proposed", etc.
[15:21] <shadeslayer> try doing it for firefox
[15:21] <pitti> shadeslayer: sorry, "vivid-release"
[15:21] <shadeslayer> it downloads 36 here
[15:21] <shadeslayer> ah
[15:21] <shadeslayer> yep, that does the trick, thanks
[15:23] <rbasak> You can also just use the exact version string you want as the second argument.
[15:24] <rbasak> (assuming you know it already and don't have to go look it up)
[15:40] <xnox> shadeslayer: vivid-release
[15:41] <xnox> oh, sorted
[15:41]  * xnox is slow
[15:41] <shadeslayer> xnox: yeah :D
[15:46] <shadeslayer> btw firefox 35 never migrated to the release pocket in vivid?
[15:48] <xnox> shadeslayer: you should know how to check that yourself by now.
[15:49] <xnox> shadeslayer: using docs at https://wiki.ubuntu.com/ProposedMigration
[15:49] <shadeslayer> xnox: yeah, I'm just curious if someone is looking into that? or no ff 35 for vivid?
[15:49] <shadeslayer> rmadison says only 34 is available in -release and 36 in proposed, and 35 in proposed for architechtures that 36 didn't build on
[15:50] <xnox> shadeslayer: yeah, so what?
[15:50] <shadeslayer> xnox: so vivid users don't get FF 35
[15:50] <xnox> shadeslayer: 35 ftbfs on armhf, 36 ftbfs on arm64/powerpc/ppc64el. but only a complete set is ever considered for migration.
[15:50] <shadeslayer> they'll just go from 34-36?
[15:50] <shadeslayer> right, so no 35 for vivid then
[15:50] <xnox> shadeslayer: read ProposedMigration page....
[16:00] <slangasek> dholbach: cyphermox is your man
[16:00] <cyphermox> howdy!
[16:00] <dholbach> ah ok, thanks
[16:01] <dholbach> cyphermox: I just askef for flexiondotorg_ who could review his MPs:
[16:01] <dholbach>  https://code.launchpad.net/~ubuntu-mate-dev/debian-cd/ubuntu-mate/+merge/246189
[16:01] <dholbach>  https://code.launchpad.net/~ubuntu-mate-dev/ubiquity/ubquity-mate-fixed/+merge/246079
[16:01] <dholbach>  https://code.launchpad.net/~ubuntu-mate-dev/livecd-rootfs/livecd-rootfs-ubuntu-mate/+merge/244446
[16:01] <dholbach> s/askef/asked
[16:01] <cyphermox> yep, just opened them from scrollback
[16:01] <cyphermox> I'll review
[16:02] <LocutusOfBorg1> thanks pitti :)
[16:03] <cyphermox> flexiondotorg_: if you're around, I noticed there's a typo in your change to tools/add_live_filesystem for debian-cd; if you want to fix that while I continue the review.
[16:04] <slangasek> cyphermox: thanks :)
[16:13] <brainwash> we would like to push a micro release update for xfdesktop4, but it's stuck in trusty-proposed since 2 months. this bugfix update does not resolve one of the several issues completely (it's triggered less often), and therefore the verification has been marked as FAILED. however, people did not notice any regressions or new bugs.. so, can I mark the verification as DONE?
[16:13] <brainwash> it's bug 1365965
[16:42] <mitya57> Laney, hi, can you top-approve https://code.launchpad.net/~mitya57/ubuntu-themes/wncktask/+merge/245292 please? It has been approved by larsu but he can't set the status.
[16:43] <Laney> he should get in the team
[16:43] <Laney> who is Frank Schoep?
[16:43] <Laney> but yes, fine
[16:44] <mitya57> Laney: thanks
[16:47] <ari-tczew> cyphermox: congrats on get network-manager merged! I think it was a huge job.
[16:47] <bdmurray> pitti: Is it time to enable apport reporting to launchpad for Vivid?
[16:47] <cyphermox> ari-tczew: you have no idea ;P
[16:48] <ari-tczew> cyphermox: well, s/I think/I guess :P
[16:48] <cyphermox> heh. there was a test regression I hadn't quite squashed properly though, so there's an update still waiting to get to proposed; depwait due to libndp
[16:49] <pitti> bdmurray: after alpha-2 is kind of the traditional time; at some point we wanted to phase this out in favor of just errors.u.c., but I guess until we have the more elaborate "additional plugin to collect more information" powers, we should keep LP for devel?
[16:49] <ari-tczew> cyphermox: yeah, I'm looking now on bug 1392385
[16:50] <pitti> hallyn, stgraber: new systemd uploaded with the lxc cgroup ownership fix, works great now!
[16:50] <bdmurray> pitti: I think so yes
[16:50] <stgraber> pitti: great, thanks!
[16:51] <pitti> it'll be stuck in -proposed for a fair while though; powerpc builders are clogged, and arm64 too
[16:51] <stgraber> pitti: so I guess that means LXC no longer is a blocker for the switch to systemd
[16:51] <hallyn> pitti: cool, thanks
[16:51] <pitti> stgraber: indeed not; it's pretty much down to maas and juju now (for !touch)
[16:51] <pitti> hey stgraber -- did you arrive in one piece this time, without further cancellations?
[16:52] <hallyn> he hasn't left :)
[16:52] <hallyn> safely hasn't left
[16:52] <pitti> ah
[16:52] <stgraber> pitti: leaving for the airport in ~4 hours
[16:52] <stgraber> arriving at 1pm tomorrow (instead of the original 8am)
[16:57] <pitti> bdmurray: uploaded
[17:00] <pitti> infinity: are adare and ross down deliberately, or is teh "no route to host" a glitch?
[17:34] <pitti> stgraber, hallyn: oh, does the new lxc release include the fix for bug 1350947? it got committed upstream months ago, so I figure it did?
[17:35] <pitti> ah yes, it does
[17:35] <pitti> \o;
[17:35] <pitti> ouch -- \o/
[17:41] <hallyn> "doc it hurts when I do this:  \o;".  "don't do that then"
[18:19] <slangasek> mlankhorst: hi, so I notice trusty already has llvm-3.5 binary packages, from llvm-toolchain-snapshot; instead of adding a new llvm-toolchain-3.5 package in SRU, can we just use the existing llvm-toolchain-snapshot source package name?
[18:37] <infinity> pitti: Not sure what the state of ross and adare are right now, but we also haven't been using them for months.
[18:51] <doko> slangasek, mlankhorst: yes in theory, but haven't checked for packaging changes. and the llvm-toolchain-snapshot package is now blacklisted. not sure if this is relevant for trusty
[18:52] <slangasek> doko: packaging changes shouldn't matter, really?  whatever's in utopic for llvm-3.5, we would take as part of the HWE stack, this would just be taking over the llvm-toolchain-snapshot source name to reduce the archive inconsistency
[19:19] <infinity> rbasak: Any progress on LP: #1412830 ?
[19:19] <infinity> rbasak: I just realised I've been rejecting some mail because of it. :/
[19:19] <flexiondotorg_> cyphermox, Thanks for reviewing my merge proposals.
[19:20] <flexiondotorg_> cyphermox, I'll prepare re-submissions based on your feedback.
[19:20] <cyphermox> flexiondotorg_: cool; let me know and I'll merge what I can :)
[19:24] <flexiondotorg_> cyphermox, https://code.launchpad.net/~ubuntu-mate-dev/ubiquity/ubquity-mate-fixed/+merge/247641
[20:59] <bluefoxxx> Anyone else on 14.10 experiencing this?
[20:59] <bluefoxxx> http://pastebin.com/NVAv2Rrf
[21:00] <bluefoxxx> 15:59:54 up 2 days, 22:53,  3 users,  load average: 1.87, 0.72, 0.52
[21:00] <bluefoxxx> I'm using Chromium browser, Virtualbox, and Gnome-3.  /home is a separate hard disk entirely.
[21:00] <bluefoxxx> Nothing in particular going on, it's just a desktop.
[21:01] <bluefoxxx> Obviously, there are some 34GB of deleted files.  I reclaimed about 1GB by SIGHUP'ing update-manager (it was holding open deleted partial package downloads)
[21:07] <rbasak> infinity: I asked kickinz1|afk to look at it but he had to take this afternoon off. I'll follow up tomorrow.
[21:07] <infinity> rbasak: Kay.  It's pretty critical for people who haven't noticed yet. :/
[21:08] <infinity> rbasak: Once I realised the problem, was easy enough to comment out the bits, but I'm sure there are lots of people out there silently dropping mail on the floor without knowing, which sucks.
[21:08] <infinity> (Which was me, up until my brother complained a few hours ago)
[21:08] <bluefoxxx> why oh why isn't there an open-deleted-file histogram tool
[21:08] <bluefoxxx> that needs to be an option in ncdu
[21:09] <bluefoxxx> I'm having no luck tracking this down with lsof :|
[21:10] <infinity> bluefoxxx: Not to be facetious or ruin your fun, but if you're putting that much effort into hunting down open handles on deleted files to try to fix them, why not just reboot and be done with it?
[21:10] <bluefoxxx> infinity, the system has been up for 2 days and done nothing special
[21:11] <bluefoxxx> Am I to believe Ubuntu simply bloats space usage with deleted files as normal, accepted behavior, and will use dozens of gigabytes of space and need a reboot every couple days?
[21:11] <bluefoxxx> 13GB of files, 47GB of used space
[21:11] <infinity> bluefoxxx: No.  And that's not "normal" here.
[21:11] <bluefoxxx> that's my issue
[21:11] <bluefoxxx> nobody told me there was a 100GB / partition requirement to run this system
[21:11] <infinity> bluefoxxx: So whatever non-special thing you aren't doing, I'm not doing it harder. :P
[21:12] <bluefoxxx> wait.  it's btrfs.
[21:13]  * bluefoxxx squints really hard.
[21:13] <jrwren> ha! btrfs strikes again.
[21:13] <bluefoxxx> oh haha.
[21:14] <bluefoxxx> Can you guess what happened?
[21:15] <bluefoxxx> http://pastebin.com/Z6v1e7e5
[21:16] <infinity> bluefoxxx: That doesn't look like it "suddenly" happened over 2 days. :P
[21:16] <bluefoxxx> infinity, I said it's been up for 2 days
[21:17] <bluefoxxx> I didn't say i ever looked before
[21:17] <bluefoxxx> also, holy crap, snapshots have been automatic since quantal
[21:20] <bluefoxxx> well, that got me down to 35G.  :|
[21:20] <bluefoxxx> I'll continue my investigation.
[21:24] <flexiondotorg_> cyphermox, Thank you!
[21:28] <cyphermox> flexiondotorg_: np. maybe by tomorrow we can merge things, I need to wait for mvo and cjwatson for some questions and some buttons I can't push  ;)
[21:29] <flexiondotorg_> cyphermox, No probs. Thanks for helping.
[21:44] <infinity> utlemming: Can you look at LP: #1414752 and reassign, fix, close as appropriate?
[21:45] <utlemming> infinity: ack, looking now
[22:13] <smoser> does anyone else belive that update-initrramfs gets called during 'apt-get upgrade|isntall' more than its supposed to?
[22:13] <utlemming> *\
[22:13] <infinity> smoser: Yes, Andy and I have a plan.
[22:14] <sarnold> infinity: yay :)
[22:14] <smoser> infinity, is there a bug ?
[22:15] <infinity> smoser: There may be, but we're not tracking one that I know of.
[22:15] <infinity> smoser: It's a fundamental rewrite of how initramfs-tools and the kernel interact for triggers, not a simple "oh, this is a bit broken" bugfix.
[22:16] <infinity> pitti: Don't suppose you're still around?
[22:53] <infinity> mlankhorst: Minor complaint (which I'm not rejecting for, but should be fixed).  Many of the lts-X packages have a symlink to usr/share/bug/xserver-xorg-core/script which isn't being placed in the right renamed spot.