[03:00] <mfisch> robert_ancell: do you know why gnome-control-center wasn't updated to 3.6?
[03:01] <mfisch> robert_ancell: could be the dozens of patches we're holding I suppose
[03:01] <robert_ancell> mfisch, it has to be done at the same time as gnome-settings-daemon
[03:01] <robert_ancell> and that had some side-effects I believe
[03:01] <robert_ancell> the plan is to do it this cycle though
[03:03] <mfisch> robert_ancell: is there a test PPA that has them updated anywhere?
[03:03] <robert_ancell> mfisch, https://launchpad.net/~ubuntu-desktop/+archive/ppa
[03:04] <TheMuso> @pilot out
[03:04] <mfisch> robert_ancell: what are the odds of me being able to install 3.6 on my dev box and then going back to 3.4 without exploding my system?
[03:04] <robert_ancell> mfisch, there's also a PPA for the gstreamer migration https://launchpad.net/~ubuntu-desktop/+archive/gstreamer1.0
[03:04] <robert_ancell> probably safe?
[03:05] <robert_ancell> (haven't tried it myself)
[03:05] <mfisch> robert_ancell: I'm trying to pick up an upstream fix that affects N7
[03:05] <robert_ancell> ah
[03:05] <mfisch> well, reinstalls are entertaining anyway, so I'll do it
[03:05] <robert_ancell> what's the fix?
[03:06] <mfisch> robert_ancell: well actually I think it's not fixed, https://bugzilla.gnome.org/show_bug.cgi?id=662117
[03:06] <mfisch> robert_ancell: I pulled that into the quantal version of g-c-c and it didn't solve the issue
[03:07] <mfisch> robert_ancell: from what I can tell it was fixed in gnome in 3.4 and the 3.6 tree
[03:07] <robert_ancell> yeah, looks that way
[03:07] <mfisch> "fixed" in quotes
[03:07] <robert_ancell> for some defintion of fixed
[03:07] <mfisch> since the fix doesn't work for me, so I'll try the 3.6 and see since it should have the "fix' also
[03:08]  * robert_ancell fires up his n7
[03:08] <mfisch> robert_ancell: the n7 has 2 issues that I think this "fix" should fix, let me find them
[03:09] <mfisch> robert_ancell: #1077096 and #1077054
[03:10] <robert_ancell> mfisch, btw is it a known problem on the n7 where the input locks up and you can select but not click on anything?
[03:10] <mfisch> robert_ancell: yep, thats our biggest issue
[03:11] <robert_ancell> mfisch, any ideas what it is?
[03:11] <mfisch> but you read the Known Issues section of the wiki, I'm sure, so you already know all about it
[03:11] <mfisch> robert_ancell: #1068994 button1 gets stuck after a while
[03:11] <mfisch> robert_ancell: It's an X issue IIRC
[03:11] <robert_ancell> why of course I did... :/
[03:11] <mfisch> Daniel D'Andrada is working on it
[03:12] <mfisch> robert_ancell: the only solution is to reboot when that happens unfortunately
[03:12] <robert_ancell> yeah, at least it reboots fast!
[03:14] <mfisch> robert_ancell: and the unity greeter looks really good too, no scaling issues
[03:14] <robert_ancell> yeah it's nice
[03:15] <robert_ancell> mahjongg is the best app on the touchscreen
[03:15] <mfisch> okay, rebooting with this new g-s-d
[03:16] <mfisch> I guess a logout will do
[03:22] <robert_ancell> yes
[03:23] <mfisch> robert_ancell: gnome-settings-daemon died :(
[03:24] <robert_ancell> not a good sign
[03:24] <mfisch> my laptop is blindingly bright, better than too dim to read I guess
[03:29] <robert_ancell> mfisch, is it in-scope to modify the theme so the window controls are clickable (i.e. win7 shaped)
[03:29] <mfisch> robert_ancell: close/minimize etc?
[03:29] <robert_ancell> mfisch, yes
[03:30] <mfisch> I think we have a bug filed about that actually.
[03:30] <robert_ancell> I couldn't see it
[03:30] <mfisch> let me find it
[03:31] <mfisch> robert_ancell: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1075470
[03:31] <mfisch> ?
[03:31] <robert_ancell> ah, ta
[03:32] <robert_ancell> was searching for window controls etc
[03:33] <mfisch> robert_ancell: #ubuntu-arm is the designated channel for N7 question, but bugs like these make sense to discuss here too
[03:34] <robert_ancell> oh, I thought I was in #ubuntu-desktop, didn't notice this was #ubuntu-devel
[03:34] <robert_ancell> meh, too many channels anyway :)
[03:35] <mfisch> robert_ancell: regarding that brightness bug, how does one go about testing the "pure gnome" version?
[03:35] <mfisch> or how do you prove that it's not just the fault of the Ubuntu version?
[03:36] <robert_ancell> mfisch, compile it locally. You'd have to replace the existing binary or do some hackery though
[03:36] <robert_ancell> mfisch, with apps it's easy, but lower level stuff much harder. You can compile the package with the patches disabled
[03:37] <mfisch> option B might be easier
[03:37] <robert_ancell> as long as none of the patches are strictly required (which is generally the case)
[03:41]  * robert_ancell just realized he has 5 active screens in front of him
[04:50] <pitti> good morning
[05:30] <hyperair> TheMuso: ping
[05:30] <hyperair> regarding bug #1070631, what else is necessary?
[05:31] <hyperair> TheMuso: the debdiff contains only a debian/changelog entry, and rightly so, because no other changes are needed to backport it.
[05:31] <hyperair> TheMuso: it's sitting there as a debdiff because i can't upload libgpod myself.
[05:33] <TheMuso> hyperair: So its a no-change rebuild in quantal essentially...
[05:33] <hyperair> TheMuso: -proposed.
[05:33] <TheMuso> Yeah well of course.
[05:33] <hyperair> TheMuso: it's a *backport* of -7 which is in raring, into quantal-proposed.
[05:34] <hyperair> not a rebuild of -6 which is in quantal.
[05:34] <TheMuso> urm... Shouldn't you then be pulling the patch from the -7 packaging?
[05:34] <hyperair> yes it's to be applied against -7?
[05:35] <hyperair> don't you see the context lines?
[05:35] <hyperair> it says  libgpod (0.8.2-7) unstable; urgency=low
[05:35] <hyperair>  
[05:35] <hyperair>    * [1c86366] Make -cil packages non-arch-all (Closes: #689054)
[05:35] <TheMuso> Yes I see that, but are you saying you want the entirity of -76 put into quantal-proposed?
[05:35] <hyperair> yes.
[05:35] <TheMuso> *the entire -7 upload
[05:35] <hyperair> yes.
[05:36] <hyperair> do you need a debdiff against -6 for that?
[05:36] <TheMuso> Yes but I see 3 changes there that are not relevant to the SRU.
[05:36] <hyperair> hang on, lemme check that..
[05:37] <hyperair> TheMuso: which 3 changes?
[05:38] <hyperair> oh, okay, should i remove those?
[05:38] <TheMuso> Bump debhelper to 9, the standards version change, and the package section change.
[05:38] <TheMuso> All of which are in -7.
[05:38] <hyperair> TheMuso: they're insignificant changes that don't result in any user-visible changes
[05:38] <hyperair> -6 is already built against dh >=9
[05:39] <hyperair> in quantal, thatis
[05:39] <hyperair> bumping that makes no difference
[05:39] <TheMuso> No, but I have seen the release team raise flags over changes like that that are not relevant to the SRU.
[05:39] <ScottK> Yes, but if you change compat it can change how debhelper processes stuff.
[05:39] <hyperair> ScottK: i didn't change compat.
[05:39] <hyperair> ScottK: it's only bumping the build-dep version.
[05:39] <ScottK> Oh.
[05:39] <hyperair> ScottK: it was already on compat 9, build-depping on >= 8.9~
[05:39] <hyperair> 8.9~ -> 9 = no difference
[05:40] <ScottK> SRU should be minimal.
[05:40] <ScottK> I agree it's not needed.  So it shouldn't be there.
[05:40]  * hyperair sighs
[05:40] <hyperair> fine, i'll strip it
[06:11] <hyperair> TheMuso: alright, i've uploaded the new patch.
[06:31] <TheMuso> hyperair: Ok, I'm taking care of it now.
[06:32] <hyperair> thanks
[07:20] <diwic> @pilot in
[07:25] <diwic> @pilot out
[07:59] <dholbach> good morning
[07:59] <pitti> hey dholbach
[07:59] <dholbach> hi pitti
[08:00] <pitti> dholbach: tu n'est pas dans #ubuntu-quality ?
[08:00] <pitti> dholbach: ah, maintenant!
[08:00] <dholbach> pitti, oui, je suis là
[08:02] <geser> bonjour / good morning / Guten Morgen
[08:03] <pitti> geser: доброе утро!
[08:03] <geser> :)
[08:09] <diwic> @pilot in
[08:11]  * dholbach hugs diwic
[08:11]  * diwic hugs dholbach 
[11:53] <tkamppeter> Seems that I have hit a ghost dependency in apt-get making it impossible to use apt-get again. I have installed "ia32-libs' trying to install some closed-source app and ia32-libs is uninstallable as some i386 library versions did not get built. Now "apt-get install -f" insists on installing the uninstallable libraries, even after removing all :i386 packages
[11:54] <seb128> to be complete tkamppeter would like to "undo" the "those new packages will be installed" and doesn't know how
[11:55] <seb128> installing them fail due to what looks like cairo/avahi multiarch bugs:
[11:55] <seb128> http://pastebin.ubuntu.com/1357786/
[11:55] <seb128> " trying to overwrite shared '/usr/share/doc/libcairo-gobject2/README.gz', which is different from other instances of package libcairo-gobject2:i386"
[11:55] <seb128> bug #1078625
[11:56] <seb128> pitti, I hope that gzip bug is not back
[11:56] <pitti> urgh
[11:56]  * seb128 does like those README.gz being different between arches
[11:56] <seb128> doesn't*
[11:56] <seb128> well, the avahi error in on README (not .gz) so not like that...
[11:58] <tkamppeter> seb128, pitti, I cannot even help myself by uninstalling all :i386 packages (ias32-libs I haver already uninstalled). Then "apt-get -f install" wants to install all :i386 packages again. There seems to be some hard ghost dependency on at least some of the i386 libraries making the broken libraries required.
[11:59] <seb128> tkamppeter, did you try to dpkg -r them?
[11:59] <seb128> hum
[11:59] <seb128> /usr/share/doc/libcairo-gobject2/README.gz -> ../libcairo2/README.gz
[11:59] <seb128> the file which is different is a symlink
[12:01] <seb128> the README.gz in libcairo2 amd64 and i386 have the same md5 it seems (from dpkg-deb the debs)
[12:01] <seb128> wonder if that's a but in dpkg/apt
[12:02] <Laney> that is a tkamppeter upload
[12:02] <seb128> oh, so maybe local build
[12:02] <Laney> I bet he installed his self built deb which has different files
[12:02] <Laney> md5sums*
[12:02] <seb128> Laney, good thinking!
[12:03] <Laney> same for avahi
[12:03] <seb128> tkamppeter, does wget https://launchpad.net/ubuntu/+source/cairo/1.12.2-1ubuntu2.1/+build/3923069/+files/libcairo2_1.12.2-1ubuntu2.1_amd64.deb && dpkg -i it fixes the cairo error?
[12:03] <seb128> Laney, thanks for pointing that ;-)
[12:03] <seb128> it's a "fun" corner case situation
[12:03] <diwic>  @pilot out
[12:03] <diwic> @pilot out
[12:05] <tkamppeter> seb128, pitti, no change: http://pastebin.ubuntu.com/1357813/
[12:05] <seb128> tkamppeter, wget https://launchpad.net/ubuntu/+source/cairo/1.12.2-1ubuntu2.1/+build/3923069/+files/libcairo-gobject2_1.12.2-1ubuntu2.1_amd64.deb and dpkg -i it and try again?
[12:08] <tkamppeter> seb128, now the libcairo error went away and only libavahi stuff is remaining.
[12:08] <Laney> same fix
[12:09] <seb128> tkamppeter, wget https://launchpad.net/ubuntu/+source/avahi/0.6.31-1ubuntu2/+build/3889306/+files/libavahi-common3_0.6.31-1ubuntu2_amd64.deb
[12:09] <seb128> tkamppeter, wget https://launchpad.net/ubuntu/+source/avahi/0.6.31-1ubuntu2/+build/3889306/+files/libavahi-client3_0.6.31-1ubuntu2_amd64.deb
[12:09] <seb128> tkamppeter, dpkg -i those
[12:13] <tkamppeter> seb128, yes, now it works. Thanks.
[12:13] <seb128> tkamppeter, yw!
[12:58] <marga> Hi, I'm trying to mark a bug fixed for quantal but not yet fixed for precise.  I can't seem to find the correct way to do this in launchpad, can anybody please give me a hint?
[13:00] <diwic> marga, you will have to nominate the bug for precise
[13:00] <marga> alright, how do I do that?
[13:00] <marga> I'm talking about the launchpad interface.
[13:00] <diwic> marga, then someone with the correct access (possibly yourself, if you're a developer) can accept the nomination
[13:01] <marga> I've seen this in plenty of bugs, a subitem inside the package (Ubuntu) with a small clock
[13:01] <diwic> "Nominate for series" link
[13:01] <cjwatson> Do you have a "Nominate for series" option just below the bug metadata?
[13:01] <cjwatson> You have to be in a certain team (ubuntu-bugcontrol IIRC) to even see that
[13:01] <marga> I don't.
[13:01] <cjwatson> Then you need to ask somebody who is
[13:01] <diwic> cjwatson, oh, I didn't know that
[13:02] <marga> Ok. Good, I think I was going crazy or something.
[13:02] <marga> s/think/thought.
[13:02] <cjwatson> https://wiki.ubuntu.com/UbuntuBugControl
[13:03] <diwic> marga, is there a specific bug you want me to nominate for you?
[13:03] <marga> https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/834174
[13:03] <marga> It's been uploaded to raring-proposed, but I'd like this to be also fixed in precise.
[13:04] <diwic> marga, done, you should now see a nomination
[13:05] <marga> diwic, thanks
[13:18] <xnox> marga: diwic: and nomination accepted.
[13:18] <marga> tnx
[13:19]  * xnox will play around with this on the weekend, unless somebody beats me to testing it.
[13:19] <marga> I've changed the desc and the debdiff.  Hopefully I've folllowed SRU guidelines now.
[13:21] <xnox> marga: the real test case is that you can ssh in & unlock the drive.
[13:22] <xnox> marga: the bug is that above is not possible due to bugs in discovering / generating initramfs on a system with multiarch
[13:25] <marga> ok, feel free to update my desc :)
[13:33] <sbhw> cjwatson: The Ubuntu Studio team wants to know when will the blender python fix go into raring-main (not -proposed)
[13:37] <xnox> sbhw: it's being transitioned by britney: check the output here http://people.canonical.com/~ubuntu-archive/proposed-migration/
[13:37] <xnox> as to why it's possibly stuck.
[13:38] <xnox> sbhw: so the armhf build has just finished, and not fully published yet for britney to attempt transition to main.
[13:44] <cjwatson> sbhw: Yeah, this is all automatic
[13:44] <cjwatson> sbhw: They should be a bit more patient since I only uploaded it an hour or two ago
[13:45] <cjwatson> And given that none of them fixed it in the multiple days that it was broken ... ;-)
[13:46] <sbhw> cjwatson, can't undetstand the system. They want to know it since that they almost just want to remove it from the seeds.
[13:46] <cjwatson> That's a daft response :)
[13:46] <cjwatson> It'll be fixed in an hour or two
[13:47] <xnox> sbhw: "the bug will be marked fix released at the time it's migrated into the raring-release pocket."
[13:47] <sbhw> yep
[13:54] <scott-work> cjwatson: sorry for the noise, i had commented blender out of our meta to make sure the iso would build and was just curious on an ETA so i had a general approximation of when i needed to uncomment blender
[13:54] <scott-work> again, sorry for the trouble
[13:59] <xnox> scott-work: well, generally it's ~1h after fully built on all arches, that is if it's actually installable and doesn't cause other packages to become uninstallable.... but blender takes a while to build on arm
[14:02] <scott-work> xnox: i'd like to use this as a teachable moment for myself; is -proposed an "in box" or queue for building then pushing into the repos?
[14:03] <scott-work> i realized in uds-q there was discussion about changing how the repos are structured, i am certainly not up to date on this and the processes
[14:03] <xnox> scott-work: it's the same thing as in debian: unstable -> testing transition.
[14:03] <xnox> scott-work: but we _do not_ impose the "10 day delay", nor rc-bugs.
[14:04] <scott-work> ah, okay. thank you :)
[14:04] <xnox> scott-work: we plan to block on failing auto-pkg-test of the package or any of it's reverse-depends.
[14:04] <xnox> scott-work: but that is not done yet.
[14:07] <scott-work> thank you again, xnox
[14:07] <xnox> scott-work: np. blender is in release now, in ~0.5h it should be pushed to the mirrors.
[14:07] <xnox> the storm is over.
[14:12] <pitti> cjwatson: jibel and I would like to meet with you soon to discuss adt/britney integration; when would be a good time for you?
[14:14] <cjwatson> pitti: any time tomorrow would be lovely, if that suits
[14:14] <pitti> cjwatson: yes, it does; how does 10:00 UTC sound?
[14:15] <cjwatson> scott-work: https://lists.ubuntu.com/archives/ubuntu-devel/2012-October/036043.html
[14:15] <cjwatson> pitti: sure
[14:15] <pitti> thanks
[14:15] <cjwatson> just grab me and we can hop on mumble or something
[14:19] <scott-work> oooh, thank you cjwatson , i will definitely read that
[14:45] <rickspencer3> sforshee, wrt my USB dongle, can I run trace-cmd for a long time? it sometimes takes all day before it disconnects
[14:46] <sforshee> rickspencer3, the only risk is the size of the trace.dat file getting very large. You could check it periodically and restart trace command if the file is getting too big. All I'm really interested in is the part of the trace right before the disconnect happens.
[14:47] <rickspencer3> ok sforshee
[14:47] <rickspencer3> thanks
[14:47] <rickspencer3> it's running now
[14:47] <sforshee> rickspencer3, also please grab dmesg after killing trace-cmd so I can try to correlate the two
[14:47] <rickspencer3> sforshee, ack
[14:47] <sforshee> (that is after the disconnect happens)
[15:09] <psusi> why is the util-linux package still source format 1.0 with no patch system?
[15:11] <cjwatson> psusi: ask its maintainer; 3.0 isn't a requirement and some people still like it the old way for one reason or another
[15:12] <cjwatson> Or of course sometimes it's just hadn't-got-round-to-it
[15:14] <Sweetshark> doko_: bug 1017125 should be good for quantal SRU. I also prepared a mpi package. both boost1.49_1.49.0-3.1ubuntu1.1.dsc and boost-mpi-source1.49_1.49.0-3.1ubuntu1.1.dsc waiting on chinstrap.
[15:14] <psusi> I mean I thought we were not supposed to just directly make changes to the upstream source without some sort of patch system?
[15:15] <xnox> psusi: in general yes, but also we are not suppose to diverge from debian way of maintaining the package.
[15:15] <xnox> psusi: sometimes the two conditions conflict with each other, if debian has no patch system.
[15:16] <psusi> yea, but isn't it better to add a patch system than to have the upstream sources mangled?
[15:17] <psusi> and would it be worth while for me to try to update the package to 3.0 (quilt) and submit it to the debian maintainer?
[15:18] <psusi> or just dive in and make changes directly to the upstream source?
[15:23] <xnox> psusi: dive in ;-)
[15:23] <xnox> psusi: that's what we do for all native packages as well....
[15:23] <xnox> psusi: or use the bzr lp:ubuntu/$pkg branches.
[15:24] <xnox> if individual changes are committed you get a normal vcs history.
[15:26] <geser> psusi: if you don't wand to have a mix of directly applied patches and patches from patch system, you would have to ideally transfer those directly applied patches to patch files too (and make the delta even bigger)
[15:27] <geser> often those changes are bigger than the patch you wanted to apply and you have to merge it everytime
[15:27] <geser> but feel free to convince the Debian maintainer to use a patch system
[15:28] <cjwatson> psusi: We should never change the patch system in an Ubuntu delta
[15:28] <cjwatson> That includes adding one
[15:28] <cjwatson> psusi: But as geser says, feel free to try to persuade the Debian maintainer that they want to change
[15:29] <cjwatson> It's not fair to describe the upstream sources as being mangled - that's why we have .orig.tar.gz / .diff.gz
[15:30] <geser> psusi: and you might have a better chance to get you patch included in Debian if you don't change the whole packaging system
[15:31] <cjwatson> Exactly
[15:33] <psusi> yea, but doesn't having them all squashed into the diff.gz make for conflict galore when you update to a new upstream?
[15:33] <doko_> Sweetshark, done
[15:34] <cjwatson> psusi: Not particularly, no
[15:34] <psusi> and since they aren't seaparted out, resolving them is next to impossible?
[15:34] <cjwatson> Sure, you may have to know the package depending on the complexity of the changes
[15:34] <cjwatson> Anyway, this isn't the point
[15:34] <cjwatson> Merging a new Debian version is much more common for us than merging a new upstream directly
[15:34] <cjwatson> We should therefore optimise for not creating huge numbers of conflicts against Debian
[15:35] <cjwatson> (Also, I believe the util-linux maintainer uses git to maintain the packaging against upstream and does not find this to be a particular problem for his workflow; hence why you should talk to him ...)
[15:36] <psusi> hrm... well, I guess I'll just make the change directly then... just thouguht that make merging a pita
[15:40] <cjwatson> Like I say, it's a matter of optimising for merging against Debian vs. upstream
[15:40] <Sweetshark> doko_: awesome, thanks
[15:41] <cjwatson> I mean, we *could* in theory aggressively convert every non-native package in Ubuntu to 3.0 (quilt), but then we'd end up assuming significantly more merge workload
[15:41] <cjwatson> It doesn't make economic sense
[15:42] <cjwatson> And it doesn't make social sense either since a number of the Debian maintainers we'd like to work with would consider that very rude
[15:43] <xnox> doko_: Sweetshark: thanks a lot ;-)
[15:47] <ppawel> hi, I want to update upstream version for a package (geos - from 3.3.3 to 3.3.5)
[15:48] <ppawel> I did 'bzr branch ubuntu:geos', then 'dch -i', updated version to 3.3.5, then bzr bd -S
[15:48] <ppawel> but it complains that "unexpected upstream changes detected" and tries to create a patch
[15:49] <ppawel> when I create it I can't build the package anymore...
[15:49] <ppawel> dpkg-source: error: cannot read geos-3.3.5.orig.ND5giv/debian/patches/update-to-3.3.5: No such file or directory
[15:49] <xnox> ppawel: did you merge the new upstream tarball?
[15:50] <xnox> ppawel: cause following your instructions the diff will have the reverse between 3.3.5 -> 3.3.3
[15:50] <xnox> ppawel: $ bzr merge-upstream ../geos-3.3.5.tar.gz
[15:50] <xnox> ppawel: instead of `dch -i`
[15:50] <ppawel> yeah it doesn't apply to 3.3.3...
[15:50] <ppawel> xnox, thanks, I will try that
[15:51] <xnox> ppawel: but your branch is dirty now, so move it aside and try again.
[15:56] <ppawel> xnox, thanks it works now
[16:28] <mterry> doko_, how do you feel about promoting libboost-filesystem-dev and libboost-system-dev (and associated 1.49 versioned packages)?
[16:28] <mterry> (libunity test suite needs them)
[16:29] <mterry> er, rather nux test suite needs them
[16:30] <doko_> mterry, sure, why not? but I don't see these in component-mismatches yet
[16:31] <mterry> doko_, no, not yet.  was planning ahead.  though, I'm not sure a branch adding these as build-depends will get through the PS landing process unless they are in main.  didrocks?
[16:33] <xnox> doko_: hmm.... componen-mismatches doesn't work that well with everything going via -proposed.
[16:34] <xnox> doko_: e.g. bug 1077484 doesn't show libsemanage in component-mismatches
[16:35] <doko_> hmm
[16:35] <cjwatson> xnox: that's on the to-do lit
[16:35] <cjwatson> *list
[16:36] <cjwatson> I'm asking Ursula to have a look at that
[16:37] <xnox> cjwatson: ok. thanks.
[16:46] <bdmurray> barry: what's next with https://code.launchpad.net/~mvo/ubuntu-release-upgrader/lp1071388/+merge/132851 in your opinion?
[17:01] <didrocks> mterry: so, theorically it can
[17:01] <didrocks> mterry: but as we'll have soon daily upload, it's better to just merge it when we have the build-dep in main
[17:01] <didrocks> doko_: ^
[17:03] <doko_> didrocks, what am I supposed to merge?
[17:04] <didrocks> doko_: we are talking about the merge request for the packaging adding the build-dep
[17:21] <SpamapS> kenvandine: hey, did I hear you right in CPH that you were working on a new Gwibber thing?
[17:21] <kenvandine> yeah
[17:21] <kenvandine> the service has been rewritten
[17:21] <kenvandine> the client still needs to be ported to the new backend
[17:21] <SpamapS> kenvandine: ah, but the frontend is the same.. thing?
[17:21] <kenvandine> but the backend is rocking!
[17:21] <kenvandine> yeah
[17:21] <kenvandine> for now :)
[17:21] <kenvandine> well
[17:22] <SpamapS> negronjl: ^^
[17:22] <kenvandine> there is the unity lens too
[17:22] <kenvandine> for 13.04 we'll be removing the client
[17:22] <kenvandine> and just shipping the lens
[17:22] <SpamapS> ah
[17:22] <SpamapS> removing, or just demoting?
[17:22] <kenvandine> and hopefully expanding the lens functionality a bit
[17:22] <kenvandine> just not seeding it
[17:22] <SpamapS> right, cool
[17:23] <negronjl> nice
[17:32] <barry> bdmurray: nothing, i think.
[17:33] <ppawel> I uploaded a source package to my PPA. will the derivative packages be built for me?
[17:38] <bdmurray> barry: so you think its okay to merge and upload?
[17:41] <barry> bdmurray: check w/mvo.  he said he fixed the couple of things i mentioned, but the diff in the mp doesn't look updated.  not sure he pushed his changes.
[18:06] <mterry> doko, sorry, getting back from lunch.  I think didrocks's point was that it might be easier with the PS process if the archive were ready as we test the branches.  Which means pre-promoting.
[18:07] <didrocks> right ;)
[18:10] <mterry> doko, so I guess the ask is to pre-promote libboost-filesystem-dev and libboost-system-dev (and associated 1.49 versioned packages), assuming they don't need a full MIR
[18:28] <hallyn> slangasek: so using udevadm trigger --subsystem-match=misc --action=change for /dev/kvm, the main downside i'm seeing (beside expectec container weirdness) is that if kvm module is not loaded, but /dev/kvm was manually created, perms on it won't get fixed.  i don't know if we care about that case.
[18:32] <hallyn> mahmoh: any chance you could verify bug 589063 ?
[18:37]  * apw just installed a Q system from scratch and when trying to upgrade it to R i found it was in "LTS only" mode ... is that right?
[18:55] <slangasek> hallyn: why would something manually create /dev/kvm?  Also, if the kvm module is not loaded, isn't /dev/kvm non-functional?
[18:58] <hallyn> slangasek: correct, it wouldn't be functional.  This would be some obtuse test case.
[18:58] <slangasek> hallyn: right; so when the kvm module was loaded, udev would trigger and update the permissions on /dev/kvm anyway
[18:58] <slangasek> hallyn: static /dev is not a configuration we support
[18:59] <hallyn> it's not?  that's too bad :)
[18:59] <hallyn> slangasek: ok, i'l go ahead and push this change.  thanks!
[19:40] <zyga> james_w: does pkgme support python3?
[19:40] <zyga> (as in packaging python3 software)
[19:44] <slangasek> xnox: so llvmpipe on panda is sufficiently horrid that running compiz at all, even just for ubiquity, is almost certain to be unusable.
[19:54] <infinity> slangasek: Has anyone tested that theory this cycle?  ogra was telling me that llvmpipe on his Chromebook is actually pretty usable and the Chromebook, while certainly faster than a Panda, isn't exactly a computing powerhouse.
[19:57] <slangasek> infinity: I haven't tested, but I don't see how a massive port of LLVMpipe to NEON would have magicked itself up overnight
[19:57] <slangasek> feel free to test and prove me wrong :)
[19:58] <infinity> My Panda's somewhat preoccupied with building glibc for 5 distributions.
[19:58] <infinity> When it stops crying, maybe I'll ask it to do GUI things to a monitor.
[19:59] <highvoltage> sad panda is sad
[20:00] <infinity> It's a masochist, it's okay.
[21:12] <chrisccoulson> is armhf busted? https://launchpad.net/ubuntu/+source/firefox/17.0~b6+build1-0ubuntu1/+build/3983790
[21:25] <xnox> slangasek: *sigh* well I have a workitem to implement it and I was hoping panda will be better than VM or old-laptop. I guess i'll use one of those in development, and then smoke test on the panda.
[21:27] <xnox> mterry: did you know about `pull-lp-source $package {$distro,$distro-$pocker,$version}` & `pbuilder-dist $distro {create,update,clean,build,login}` which has support for _all_ ubuntu & debian releases?
[21:27] <xnox> mterry: well the first-one changes to pull-debian-source.
[21:27] <mterry> xnox, you're talking about instead of pbuilder-scripts?
[21:28] <xnox> mterry: yeah. Or what is unique in pbuilder-scripts which is missing in ubuntu-dev-tools.
[21:28] <Laney> SpamapS: where do we stand with copying up SRUs?
[21:28] <Laney> if possible I'd like to avoid uploading webkit twice ...
[21:29] <mterry> xnox, I wrote those scripts when working with OEMs and needing all sorts of custom sources.  So supporting standard ubuntu and debian releases wasn't a big feature
[21:29] <xnox> mterry: There is a request to backport it to precise, but I just don't see what it offers extra / on top of what ubuntu-dev-tools already offer for a very long time including stable releases.
[21:29] <xnox> mterry: so if ubuntu-dev-tools add [easy] support for extra sources it will be match?
[21:29] <xnox> mterry: so if ubuntu-dev-tools adds [easy] support for extra sources it will be match?
[21:29] <xnox> mterry: anything else?
[21:30]  * xnox wants to consolidate tools, scripts, utilities around ubuntu-dev-tools if possible.
[21:31] <slangasek> xnox: even if someone did magic up an LLVMpipe port to NEON, it would still be slower than in kvm
[21:31] <doko> \o/  http://gcc.gnu.org/ml/gcc-cvs/2012-11/msg00455.html  \o/
[21:31] <mterry> xnox, I'm for consolidating.  I'd have to go through and figure out the various features though.  Easy sources is one.  apt-get update before building.  apt-get sourcing using the sources in one of the chroot
[21:31] <xnox> slangasek: ok.
[21:32] <slangasek> chrisccoulson: armhf busted> there was mention about the livefs builder having "tar errors" as well, but I don't have details
[21:33] <slangasek> infinity, ogra-cb: ^^ any ideas? https://launchpadlibrarian.net/123040342/buildlog_ubuntu-raring-armhf.firefox_17.0~b6%2Bbuild1-0ubuntu1_FAILEDTOBUILD.txt.gz
[21:33] <xnox> mterry: i'll open a bug about those three. If there is anything else, feel free to do wishlist bugs against ubuntu-dev-tools.
[21:33] <chrisccoulson> slangasek, thanks
[21:34] <Laney> that's the same kind of error we saw on celbalrai, yeah
[21:36] <mterry> xnox, it also lays out the sources in a certain way & uses that layout to automatically determine which project chroot you want it to operate on (can be overridden).  Not sure if ubuntu-dev-tools can easily support that stle
[21:36] <mterry> style
[21:36] <slangasek> Laney: ok, it was the same bunzip2 problem?
[21:36] <xnox> mterry: hmm... well pbuilder-dist already auto-supports guesing/using multiple combinations of distro's and arches.
[21:36] <Laney> slangasek: I think so
[21:37] <slangasek> infinity: do you have a raring panda handy?
[21:37] <xnox> mterry: the whole point of pbuilder-dist was to allow easily manage chroots for all releases & cross-arches, since it's common for ubuntu developers to build against multiple ubuntu releases (sru/security/backports) and debian releases (for bug verification /forwarding to debian)
[21:38] <infinity> slangasek: I could do, but like I said earlier, my Panda's a bit busy.
[21:38] <xnox> mterry: so I am sure it can be extended to handle sub-types of chroots.
[21:38] <slangasek> infinity: ah, still? thbt
[21:38] <slangasek> ok
[21:38] <slangasek> infinity: well, bzip2 hasn't changed in raring, so I guess I'll open a critical bug against eglibc in the meantime
[21:39] <infinity> slangasek: Also, if this build log ever loads.. If it's bunzip2 spontaenously having a fit, that's been happening on ARM for years.
[21:39] <slangasek> oh, it has?
[21:39] <infinity> Yeah.  Though, it usually manifests before the build starts (when untarring the chroot).
[21:39] <slangasek> I've never heard of it until Laney mentioned it happening on celebrityrye this week
[21:40] <infinity> And it's so wildly unreproducible, no one's managed to hunt it down.
[21:40] <infinity> celbalrai's issues seem unrelated.
[21:40] <slangasek> not according to Laney
[21:40] <Laney> now it has died, but before that we were seeing similar errors
[21:40] <slangasek> Laney: do you have a pointer to such an error?
[21:40] <infinity> Similar, or the same?
[21:40] <Laney> p'raps I have a log which is nonempty
[21:41] <xnox> mterry: adding all of these requests to the wishlist =)))) keep them coming.
[21:41] <slangasek> infinity: similar, because the livefs builder doesn't generally go about unpacking firefox tarballs :P
[21:41] <Laney> yeah that's wishful thinking
[21:42] <infinity> slangasek: Well, yes.  And I would have assumed the errors were just "something from some sort of compression something or other" which is hardly "the same error".
[21:42] <mterry> xnox, :)
[21:42] <xnox> mterry: we are soon gonna get shiny cross-building support ;-)
[21:43] <xnox> mterry: and that will want easy custom repositories as well =)
[21:43] <mterry> nice
[21:43] <xnox> mterry: with and without qemu execution.
[21:43] <slangasek> infinity, chrisccoulson: I've saved off a copy of the logfile, so will retry the build now
[21:44] <mterry> xnox, oh yeah, that's another thing my scripts did is set up qemu
[21:44] <xnox> mterry: pbuilder-dist does it already, since before your script had it ;-)
[21:44] <mterry> xnox, :)
[21:44] <infinity> slangasek: It won't repeat, unless you're very unlucky.
[21:47]  * infinity would like to know why his firefox has suddenly decided he isn't allowed to do things like look at web pages.
[21:48]  * xnox would like to know why my internet decided to give we all but lp.net
[21:48] <xnox> s/we/me/
[21:48]  * xnox now back
[21:51] <xnox> mterry: also any reason why it's based on pbuilder instead of sbuild?
[21:52] <xnox> sbuild supports multiple instances easy, and mk-sbuild allows to easily create them.
[21:53] <mterry> xnox, ah!  you are one of those sbuild evangelists  :)  It was based on pbuilder because that's what I was comfortable with
[21:53] <xnox> mterry: I use all three: pbuilder, cowbuild, sbuild =))))
[21:53] <xnox> mterry: i'm the freak that cannot get enough =))))
[21:54] <mterry> xnox, hah
[22:06] <ogra-cb> slangasek, the last live build logs from celab...thing all have one or the other gunzip error from dpkg unpack
[22:07] <slangasek> gunzip, not bunzip2
[22:07] <slangasek> so that's not the same error at all
[22:07] <ogra-cb> it is definitely not limited to bzip2
[22:07] <slangasek> "limited to" - there's no reason to think the two issues are at all related
[22:07] <slangasek> unless someone knows of a tar bug?
[22:08] <ogra-cb> well, dpkg died with a broken pipe error in all recent builds that still produced logs
[22:09] <ogra-cb> during gunzip
[22:09] <ogra-cb> this one seems to show similar symproms
[22:14] <slangasek> bunzip2 reporting a corrupted stream and dpkg reporting a broken pipe are not meaningfully similar
[22:14] <infinity> slangasek: Given how celbalrai when off the deep end, it looked more like the filesystem corruption (or memory corruption at a more fundamental level, leading to filesystem corruption).
[22:14]  * slangasek nods
[22:14] <kamakwazee> Hey
[22:14] <slangasek> hello
[22:15] <infinity> slangasek: As to the bunzip2 thing we see occasionally, retrying (or, in the case of chroot tarballs, removing the cached copy, then retrying) always "fixes" it, which points at similar potential causes.
[22:15] <infinity> slangasek: Oh, it also seems to sometimes need a reboot to clear up, which is mildly disconcerting.
[22:15] <infinity> s/need/needs/
[22:15] <infinity> But yeah, none of this is new, it's been happening for years.  :/
[22:16] <xnox> stokachu: grub2 diff (i) committed to core-dev branch & (ii) pocket sru team member of the day to commit it into oneiric.
[22:16]  * xnox s/pocket/poked/
[22:16]  * xnox wonders what's with my hands.....
[22:16] <kamakwazee> I was wondering if someone could help me. I downloaded testdrive and synced the raring iso but it boots console. Is that normal?
[22:19] <kamakwazee> Is it normal for my testdrive synced iso to boot into console?
[22:21] <ScottK> kamakwazee: Ask in #ubuntu-testing.  You probably have a better chance of getting an answer there.
[22:21] <kamakwazee> ScootK: Ok. Thanks. I am wanting to learn the source code a little so I can help develop.