[00:26] <kees> infinity: any chance you can upload those eglibc patches? I'd like to commit changes to the qa regression test suite
[00:27] <infinity> kees: Oh, you actually wanted people to run that code?
[00:28] <infinity> kees: (I just got home from HK, and today's been a PlusOneMaint firefighting day, I'll toss you feedback and/or an upload by tomorrow)
[01:37] <TheMuso> D/c
[01:41] <bkerensa> cyphermox_: anything I can do to get this bug looked at and perhaps fixed? https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/972063
[02:10] <nemo> Sooo, just FYI, libcairo2-1.11 completely broke libreoffice on my SO's computer. menus unreadable
[02:10] <nemo> forcing install of 1.10 seems to have fixed things
[02:10] <nemo> lost some of my cairo dev libs in the process, ah well
[02:11] <nemo> I tried forcing 1.12 - that did not seem to help though. as screwed up as ever. perhaps due to some related deps, dunno.
[02:11] <nemo> anyway. 1.10, all better.
[02:36] <bernie> micahg: is there a specific channel where i could find compiz developers to help diagnose a bug interactively?
[02:37] <bernie> oh, i found #compiz
[02:38] <bernie> and #ubuntu-unity
[03:14] <kees> infinity: sweet, thanks! let me know if I can help further. :)
[03:42] <pitti> Good morning
[03:42] <pitti> slangasek: hm, perhaps I misremembered then; although 750 MiB and 800 MB isn't too far apart anyway
[03:43] <pitti> slangasek: 750 MiB seems fine, too
[04:15] <vibhav> micahg: Confragtulations!
[04:15] <vibhav> Congratulations*
[04:15] <micahg> vibhav: what did I do?
[04:15] <infinity> micahg: You know, but whatever it was, you obviously did it well.
[04:15] <infinity> s/You know/Who knows/
[04:16] <infinity> Brain:finger disconnect.
[04:16] <vibhav> micahg: You are in the Membership Board, right?
[04:16] <micahg> vibhav: ah, yes, thanks
[04:17] <infinity> Hasn't that been true for a while?
[04:17] <micahg> infinity: non-devs this time :)
[04:17] <vibhav> I only came to know about it today
[04:17] <infinity> Oh.  Too many boards.
[04:17] <infinity> So confusing.
[04:18] <micahg> well, the RMBs were collapsed into a single team now
[04:25] <TheMuso> /c/c
[05:15] <slangasek> pitti: yeah... see ubuntu-release@ for my follow-up question :)
[05:16] <slangasek> one way or the other we should lock this down so nusakan stops telling us our images are oversized ;)
[05:17] <pitti> slangasek: right, already replied there
[05:17] <slangasek> ok cool :)
[05:18]  * pitti votes for 700 Ububytes and Kububytes, units which will grow by 50 MB every year
[05:18] <pitti> which are shamefully missing from http://xkcd.com/394/
[05:19] <slangasek> heh
[05:20]  * infinity nearly has a beverage->monitor incident over "kububytes".
[06:09] <ScottK> xnox: pyopencl both needs a rebuild for the boost transition and a merge from Debian.  I'm technically TIL on the merge due to a previous rebuild, but don't anticipate getting to it, so if you could do it or find someone, that'd be great.
[07:02] <dholbach> good morning
[08:31] <seb128> RAOF, slangasek, SpamapS, bdmurray: is there anything blocking the unity SRU to move to -updates?
[08:31] <seb128> the bugs are all verified and it's in proposed for 11 days
[08:32] <seb128> the bamf one should be verified as well, the one non-green bug can't be opened, launchpad timeout on it
[09:47] <RAOF> seb128: Bug #772063 seems to show a regression during testing? Specifically, https://bugs.launchpad.net/unity/+bug/772063/comments/29
[09:49] <ogra_> "resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing anything."
[09:49]  * ogra_ wonders why thats an error ... should be a warning 
[09:50] <ogra_> (or even "info")
[09:53] <morphis> ogra_: heyho, do you mind if I ask you something in private?
[09:54] <ogra_> well, is it something the community shouldnt see ?
[09:54] <ogra_> :)
[09:56] <seb128> RAOF, hum, I doubt that's a regression, that's the only user who mentioned something like that and there was no change around the super handling code nor the dash
[09:56] <seb128> RAOF, seems rather a local random issue for that user
[09:57] <seb128> RAOF, he also didn't reply to my comment asking to open a new bug
[09:58] <RAOF> Ok. I'll give that a shove.
[10:00] <RAOF> Ah, right.  And didrocks is currently fighting -0ubuntu2 to get it to build.
[10:01] <seb128> RAOF, correct
[10:14] <seb128> RAOF, thanks!
[10:14] <seb128> ;-)
[10:34] <seb128> could somebody set https://code.launchpad.net/~gunnarhj/ubuntu/precise/ubuntu-docs/missing-links/+merge/103121 to merged?
[10:35] <seb128> (it was targetting the wrong vcs, the fixes got merged into the correct one)
[11:58] <matanya> why do I get : bzr dh-make hello-2.7 hello-2.7.tar.gz  bzr: ERROR: command 'dh-make' requires argument TARBALL
[12:50] <ahasenack> hello, good morning/afternoon/evening!
[12:50] <ahasenack> could someone from the sponsors team take a look at my upload please? #1004678
[12:50] <ahasenack> thanks!
[13:04] <geser> ahasenack: the Standards-Version field is pure documentatory and doesn't get use anywhere. So you can update it (after checking the changes between the policy versions and if they apply to your package) to a current version (instead of adding a useless lintian-override)
[13:05] <ahasenack> geser: isn't the right thing to do to keep it at the lower version I need? Lucid, in this case?
[13:06] <geser> no need to
[13:06] <ahasenack> geser: the same debian source package builds on lucid all the way up to quantal
[13:06] <ahasenack> geser: adjusting dependencies at build time when needed
[13:07] <geser> the Standard-Versions is used at build (or anywhere, perhaps only for statistics)
[13:08] <geser> you could take a package from quantal with current Standard-Versions and backport it to lucid if you wanted (and only care about build-dependencies and build tools like dh_python)
[13:09] <ahasenack> geser: where do I find the differences in the standards, and what they mean?
[13:13] <Adri2000> ahasenack: /usr/share/doc/debian-policy/upgrading-checklist*, debian-policy package
[13:14] <ahasenack> geser: so your review point is to bump that and get rid of the override, right?
[13:14] <ahasenack> Adri2000: thanks
[13:14] <geser> yes
[13:14] <ahasenack> geser: anything else or still looking?
[13:17] <ahasenack> geser: that's a lot of versions to check, do you have a suggestion? That document is long and is full of details
[13:23] <geser> ahasenack: it's nothing urgent, so you can leave it for now at that versions and review it for the next upload. Most of the changes of that new policy versions probably don't affect your package at all
[13:23] <ahasenack> geser: ok, I'll file a bug for it
[13:26] <geser> ahasenack: another small upgrade for the furture: as lucid has already debhelper7 you could upgrade debian/compat (and the build-dependency on debhelper) to 7 if you want
[13:26] <geser> otherwise the changes to debian/* look ok
[13:27] <ahasenack> geser: yeah, and I would love to have a simpler rules file too, but I inherited that package as is and am proceeding carefully with the debian/* changes
[13:27] <ahasenack> I personally prefer to use override targets in the rules file when I have an exception
[13:28] <ahasenack> geser: not too long ago that package had to build on dapper, I guess that was the main reason
[13:31] <ahasenack> geser: ok, that's done in our trunk branch (debhelper 7)
[13:31] <ahasenack> so next upload will have it
[13:31] <ScottK> geser: Since compat 5 is not deprecated, there's really no reason not to leave it.
[13:32] <ahasenack> right, but we don't have reason to keep 5 anymore since we don't build this for old releases anymore
[13:34] <geser> ScottK: true, but is there a reason to not slowly upgrade the package to current "versions" (if possible)?
[13:35] <ScottK> As long as you don't need features from newer debhelper, it seems like not a very productive use of time.
[13:35] <ScottK> There's no reason not to, but there's no particular benefit either.
[13:37] <ahasenack> I plan to move this rules file to more dh 7 features
[13:39] <xnox> ScottK: I will get to it =) I'm doing it in alphabetical order, NMUs/uploading patches etc =)
[13:39] <ScottK> xnox: OK.  I'll leave it to you.
[13:39] <ScottK> ahasenack: In that case, have at it.
[13:39] <xnox> stop of Debian Imports stalls it a bit, due to alpha 1
[13:42] <ahasenack> geser: so, what happens now?
[13:42] <ahasenack> geser: are you a sponsor, or did you just take a look?
[13:44] <geser> ahasenack: I just took a look, can't sponsor it as I'm not a core-dev (can't upload to main)
[13:44] <ahasenack> geser: ok, thanks even so
[13:51] <cr3> hi folks, I use mk-build-dep to generate a package for the build dependencies when working on the source of a project. might there be a way to also generate a package for the run dependencies, not just for the build but to actually run the project?
[14:04] <ScottK> geser: You should fix that.
[14:09] <tseliot> pitti: any ideas about this? http://paste.ubuntu.com/1025080/
[14:14] <pitti> tseliot: are you running this straigth out of trunk?
[14:14] <pitti> tseliot: without building the pacakge first?
[14:14] <pitti> tseliot: my bet is that "./setup.py egg_info" will fix it
[14:15] <tseliot> pitti: yep. I'm doing PYTHONPATH=.. ./run from master
[14:15] <pitti> tseliot: I guess run should check if the egg is present and point that out
[14:16] <tseliot> pitti: yes, that wouldn't be such a bad idea
[14:17] <tseliot> pitti: all of the tests passed. I had to test my changes to the xkit code. I'd like to fix the other packages before uploading my new xkit
[14:17] <tseliot> pitti: shall I push my changes without uploading?
[14:18] <tseliot> (leaving it UNRELEASED)
[14:18] <pitti> tseliot: sure, as we are currently frozen
[14:18] <sconklin> @pilot in
[14:19] <tseliot> pitti: ok then
[14:27] <rdz> hi all. there is a package that a team of which i am a member of host in debian, that is currently broken in ubuntu 12.04. what's the best way to get fix pushed to ubuntu? i'm not familiar with the ubuntu processes, but i am a ubuntu user myself
[14:27] <rdz> the package in question is pd-readanysf
[14:28] <rdz> there is wrong linking order in the Makefile which unfortunately leads  to totally broken binary in ubuntu 12.04
[14:28] <rdz> (unfortunately it works in debian unstable), otherwise we would have captured the error earlier
[14:34] <geser> rdz: see https://wiki.ubuntu.com/StableReleaseUpdates
[14:36] <rdz> geser, thanks
[14:41] <rdz> "Check that the bug is fixed in the current development release" <- this would be ubuntu 12.10, right?
[14:42] <rdz> geser, so if I apply to the changes to debian, they would automatically "drop" to the current development release and then the process could be proceeded to include the fix in ubuntu 12.04?
[14:54] <jwendell> hi, folks. why does the precise kernel have the 3.2.0 numbering instead of follow upstream 3.2.x schema?
[14:58] <Adri2000> rdz: yes, fixed in the development release currently means fixed in quantal, and if a working package is in debian it should get synced automatically (though I'm not sure if we are auto-syncing from unstable or testing now). that is a prerequisite for uploading a fix in ubuntu 12.04
[14:58] <Adri2000> jwendell: maybe ask in #ubuntu-kernel
[14:59] <jwendell> Adri2000, thanks
[15:13] <bdmurray> dobey: bug 981255 is missing some SRU information
[15:13] <bdmurray> dobey: otherwise the other bugs look good
[15:16] <dobey> bdmurray: added, though it makes no sense for that bug really. :)
[15:34] <bdmurray> dobey: a couple of the ubuntuone-control-panel bugs don't have fix released quantal tasks… did they just not get updated?
[16:14] <dobey> bdmurray: oh?
[16:16] <bdmurray> dobey: bug 966283
[16:16] <bdmurray> and bug 865688
[16:18] <dobey> bdmurray: looks like maybe the ubuntu task on those was added after the upload to quantal, so they didn't get automatically marked
[16:18] <dobey> bdmurray: fixed it now anyway so they are fix released in q
[16:19] <bdmurray> dobey: okay thanks.  by the way could you look at my new lptools merge proposal?
[16:21] <dobey> bdmurray: as soon as i can.
[17:16] <Bluefoxicy> where do core dumps go
[17:16] <Bluefoxicy> Segmentation fault (core dumped)
[17:17] <nemo> depends on whether you have core dumps enabled
[17:17] <Bluefoxicy> oh
[17:17] <nemo> ulimit
[17:17] <Bluefoxicy> because VLC crashes constantly on trying to play dvd
[17:17] <nemo> Bluefoxicy: although if you can reproduce it. just use gdb
[17:17] <nemo> much easier
[17:17] <Bluefoxicy> bluefox@icebox:~$ ulimit
[17:17] <Bluefoxicy> unlimited
[17:17] <nemo> man ulimit
[17:17] <nemo> gdb vlc
[17:17] <Bluefoxicy> nemo what do I do with gdb
[17:17] <nemo> run
[17:18] <nemo> I'm surprised that wasn't trapped though, and submitted using ubuntu's error reporting dæmon
[17:18] <nemo> well. dæmon or widget or whatever it is :)
[17:18] <Bluefoxicy> Program received signal SIGSEGV, Segmentation fault.
[17:18] <Bluefoxicy> [Switching to Thread 0x7ffff1efe700 (LWP 21354)]
[17:18] <Bluefoxicy> 0x00007fffedbbc76c in dvdnav_describe_title_chapters ()
[17:18] <Bluefoxicy>    from /usr/lib/libdvdnav.so.4
[17:19] <Bluefoxicy> well then :)
[17:19] <nemo> Bluefoxicy: bt for backtrace - but you'll get more useful backtrace by installing -dbg versions of the libraries
[17:19] <Bluefoxicy> it's a bug in libdvdnav4 :)
[17:19] <nemo> Bluefoxicy: then, file a bug w/ the appropriate project
[17:19] <nemo> Bluefoxicy: I suspect if you are using a very old ubuntu version, they'll want you to test w/ a more recent version of their lib
[17:19] <bdmurray> seb128: might you know anything about the sru for bug 1006701?
[17:20] <Bluefoxicy> i'm on 12.04 amd64
[17:20] <Bluefoxicy> and just updated evrytihng a few hours ago
[17:23] <Bluefoxicy> nemo:  more interesting, I'm trying to watch a DVD and the default movie player (Totem) is horrible.
[17:23] <Bluefoxicy> The DVD appears interlaced, as alternate scanlines flicker one pixel up and down constantly
[17:23] <Bluefoxicy> VLC has a "deinterlace" feature that fixes this, while Totem just stabs you in the eyes for 2 hours D:
[17:24] <Bluefoxicy> (yes it's extremely noticeable looking at the ripped copy pulled from the DVD with Thoggen)
[17:27] <nemo> I've never found Totem's DVD playing adequate
[17:31] <Bluefoxicy> well, most people aren't stupid enough to encode their content interlaced
[17:31] <Bluefoxicy> Disney obviosuly doesn't share in this collective intelligence
[17:32] <Bluefoxicy> oh
[17:32] <Bluefoxicy> I thought you said 'annoying,' not 'adequate' :P
[17:34] <Bluefoxicy> nemo:  http://sphotos.xx.fbcdn.net/hphotos-ash3/521345_3614750160740_372269247_n.jpg btw :3
[17:34] <nemo> ah. I have that
[17:36] <nemo> Bluefoxicy: if you want to play, and vlc is being annoying.
[17:36] <nemo> Bluefoxicy: you might be able to navigate the chapter structure in vlc without triggering the bug. otherwise, you can always do mplayer dvd://1
[17:38] <seb128> bdmurray, what about it?
[17:39] <seb128> bdmurray, the launchpad page seems to have all the details I would provide, do you have a specific question?
[17:42] <bdmurray> seb128: the diff contains a change I'm not clear on
[17:42] <bdmurray> --- oneconf-0.2.8/oneconf/version.py    2012-04-10 13:11:34.000000000 +0000
[17:42] <bdmurray> +++ oneconf-0.2.8.1/oneconf/version.py  2012-06-04 11:48:14.000000000 +0000
[17:42] <bdmurray> -RELEASE='12.04'
[17:42] <bdmurray> +RELEASE='12.10'
[17:46] <seb128> bdmurray, hum, I'm unsure about it, can you ask on the bug for Didier?
[17:46] <bdmurray> seb128: yes, thanks for looking
[17:46] <seb128> yw!
[17:51] <Bluefoxicy> nemo:  it doesn't even start.
[17:51] <Bluefoxicy> nemo:  vlc that is
[17:52] <Bluefoxicy> tbh Totem wouldn't be terribly terrible if it would de-interlace
[17:52] <Bluefoxicy> sure it's not the most awesome DVD emulator ever, but it'll get you to the feature film with no real trouble.
[17:52] <Bluefoxicy> but when the feature film *vibrates*?
[18:04] <Bluefoxicy> nemo: mplayer interrupted with signal 11 in open_stream when trying to open dvd with menus
[18:04] <Bluefoxicy> I assume that means libdvdnav4 is broken o_o  mplayer dvd://16 works but I can't seek through the video etc.  No UI
[18:05] <nemo> Bluefoxicy: figured.
[18:06] <nemo> Bluefoxicy: that's why I was suggesting by number as a workaround
[18:06] <nemo> Bluefoxicy: you can still seek in the video using keyboard nave in mplayer
[18:06] <nemo> left/right pageup/pagedown
[18:06] <nemo> nav
[18:07] <Bluefoxicy> oh, update manager is telling me VLC crashed
[19:48] <seb128> slangasek, could you review https://code.launchpad.net/~nathwill/ubuntu/precise/pam/lp-110287/+merge/100282 if you have some free time (I see you were piloting yesterday, not sure if you saw it or not but it's in the queue for a while)
[19:53] <seb128> zul, could you review https://bugs.launchpad.net/ubuntu/+source/nova/+bug/989241? it's in the sponsoring queue for a while
[19:53] <zul> seb128: yep
[19:53] <seb128> roaksoax, hey, you sponsored https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/959218, could you get the fix in q?
[19:53] <seb128> zul, thanks
[19:54] <stgraber> seb128, roaksoax: though after alpha1 please, we're in softfreeze and lvm2 is seeded :)
[19:57] <seb128> stgraber, skaet email suggested uploads could happen as usual to proposed during the freeze, what happened to that?
[19:57] <stgraber> seb128: proposed is fine indeed
[19:57] <seb128> stgraber, ok, so when you mean "after alpha1 please" you mean "don't forget to use proposed"?
[19:57] <roaksoax> seb128: sure
[19:58] <seb128> roaksoax, thanks
[19:58] <roaksoax> :)
[19:58] <stgraber> seb128: right, I should have said, don't upload anything seeded to the release pocket until post-alpha1 (unless it's release critical and #ubuntu-release is aware of it)
[19:59] <seb128> stgraber, there should be no need to say that, people know we are frozen and read the announce email, but thanks for watching what happens... ;-)
[20:00] <stgraber> seb128: haha, good one :) you'd be surprised how many people we have to remind to subscribe and READ -announce during the DMB meetings...
[20:01] <seb128> stgraber, well anyway let's not spend too much time on whether you need to remind others what they need to do or not and assume those who didn't notice it was a1 week know now ;-)
[20:02] <seb128> zul, https://bugs.launchpad.net/ubuntu/+source/nova/+bug/989242 as well ;-)
[20:02] <zul> seb128: ack
[20:02] <seb128> thanks ;-)
[20:09] <slangasek> seb128: well, I was scheduled to pilot yesterday but never got a chance :(  I will look at that merge, yes
[20:10] <seb128> slangasek, thanks
[20:10] <seb128> slangasek, yeah, lot of people seem to be scheduled and get busy with other things, I still use the opportunity that they were supposed to pilot to bounce stuff at them :p
[20:10] <slangasek> heh :)
[20:10] <seb128> it's only fair ;-)
[20:11] <seb128> especially in a week where dholbach called for helped because we had a backlog > 100 items in the queue
[20:11] <seb128> -ed
[20:15] <barry> pitti: are you still around?
[20:53] <ahasenack> hi, could someone review/sponsor my proposed upload to quantal? #1004678? Thanks
[21:13] <kees> stgraber: I've uploaded the first pass of libseccomp to debian. it'll be in NEW soon...
[21:17] <stgraber> kees: cool!
[21:39] <bdmurray> hyperair: all the bugs associated with alarm-clock-applet in precise-proposed (bug 977110 for example) are missing SRU information
[22:00] <sconklin> @pilot out
[22:45] <barry> james_w: ping
[23:47] <bdmurray> any ideas about what is going on in bug 1001904?
[23:47] <bdmurray> dpkg: error processing /var/cache/apt/archives/sysvutils_2.86.ds1-14.1ubuntu45_amd64.deb (--unpack)
[23:47] <bdmurray> why would that be tried to install?
[23:53] <infinity> bdmurray: On the one hand, it looks like there's a missing Replaces there, on the other hand, I have no idea why he's trying to install hardy packages on precise.
[23:57] <infinity> bdmurray: Ah-ha.  His DpkgHistoryLog gives a hint.
[23:57] <infinity> bdmurray: He added hardy sources to install ancient versions of java.
[23:58] <infinity> bdmurray: And then his next dist-upgrade pulled in hardy Essential packages.
[23:58] <infinity> bdmurray: I'm going to go out on a limb here and say that's really not a supported configuration.
[23:58] <bdmurray> infinity: how do you see that he added hardy sources?
[23:59] <infinity> bdmurray: I don't, per se, but the previous two commands (apt-get install sun-java5 and sun-java6) pulled in a version of sun-java5 that's only available in hardy.  Indeed, we haven't shipped it *since* hardy, which is likely why he added the sources.