[05:07] <Rhonda> paultag: Thanks, but that's just the official mail about it, it's not like I just started yesterday …  :)
=== medberry is now known as med_out
[06:10] <dupondje> tumbleweed: about the shorewall-lite, seems like debian maintainer already tagged the bug as 'pending upload'
[06:10] <dupondje> so will indeed be fixed quite fast
[07:25] <dholbach> good morning
[07:57] <benonsoftware> Hello all
[07:58] <benonsoftware> msg ChanServ Hi
[07:58] <ronin___> hello
[07:58] <benonsoftware> Sorry about the msg ChanServ Hi. Forgot to add the / at the start :(
[08:40] <benonsoftware> Hi all
[08:44] <ronin___> hi
[08:45] <benonsoftware> ronin___: Hay
[08:46] <ronin___> benonsoftware: hi, how do you do?
[08:47] <benonsoftware> ronin___: Fine thanks, you?
[08:47] <ronin___> benonsoftware: good, thank you
[08:48] <benonsoftware> ronin___: You into programming?
[08:49] <ronin___> benonsoftware: actually at this time I configure my machine for begin
[08:49] <benonsoftware> ronin___: To begin what sorry?
[08:50] <ronin___> benonsoftware: programming
[08:50] <benonsoftware> Oh ok. What langugage fo you use? Python?
[08:50] <ronin___> I love Python
[08:50] <ronin___> and sometimes try to use C and Assambly
[08:50] <ronin___> and sometimes try to use C and Assembly
[08:51] <benonsoftware> ronin___: Know any where I could start with Python from startch?
[08:51] <ronin___> Of course use Python from Google Code
[08:52] <ronin___> Let me I search and send link to you
[08:52] <benonsoftware> ronin___: Thanks
[08:52] <ronin___> It's really fantastic
[08:53] <wzssyqa> https://launchpad.net/ubuntu/+source/ns3  how to rebuild it ?
[08:53] <wzssyqa> somebody can help me?
[08:54] <ronin___> benonsoftware: http://knol.google.com/k/python-tutorials#
[08:54] <ronin___> benonsoftware: http://www.4shared.com/file/O66XysNF/Python_Web_training_site_offli.html
[08:55] <benonsoftware> ronin___: Thanks. For that.
[08:55] <benonsoftware> ronin___: Are you a MOTU?
[08:56] <ronin___> benonsoftware: http://www.4shared.com/dir/FKj6FkgN/Python_Trainings.html
[08:56] <benonsoftware> Thaks
[08:57] <benonsoftware> ronin___: You a MOTU?
[08:57] <ronin___> benonsoftware: no
[08:58] <benonsoftware> ronin___: Trying to be one?
[08:58] <ronin___> benonsoftware: actually be a linux kernel developer
[08:58] <benonsoftware> ronin___: I want to be a MOTU.
[08:59] <ronin___> benonsoftware: I think first step must be a MOTU
[08:59] <ronin___> benonsoftware: good
[08:59] <benonsoftware> ronin___: For kernel dev?
[08:59] <ronin___> benonsoftware: what
[08:59] <benonsoftware> ronin___: You said first step must be a MOTU. What did you mean?
[09:00] <ronin___> benonsoftware: for be kernel developer in first place must be a MOTU
[09:00] <ronin___> benonsoftware: you must read a lot
[09:00] <benonsoftware> ronin___: What do you mean read a lot?
[09:00] <ronin___> benonsoftware: It's hard but enjoyable
[09:01] <ronin___> benonsoftware: I read lot's of wiki page in ubuntu.com
[09:01] <ronin___> benonsoftware: debian.org
[09:06] <benonsoftware> ronin___: I know. I spend all day on wiki.ubuntu.com or launchpad.net searching stuff
[09:06] <ronin___> benonsoftware: It's really hard
[09:07] <ronin___> benonsoftware: all the people are busy and can't help
[09:07] <benonsoftware> ronin___: I have read just about every page on wiki.ubuntu.com at least a couple of comes.
[09:08] <benonsoftware> ronin___: I know. I ask on IRC. Answer: Sorry please go to wiki.ubuntu.com/MOTU we're very busy now.
[09:08] <benonsoftware> ronin___: Or even. Busy. at work
[09:08] <ronin___> benonsoftware: Do you know how can get a code and try to fix a bug?
[09:09] <benonsoftware> ronin___: For what?
[09:10] <ronin___> benonsoftware: e.g. mozilla firefox
[09:10] <mok0> dholbach: Saw your name in an article on Ars
[09:10] <mok0> :-)
[09:10] <dholbach> mok0, oh really?
[09:10] <dholbach> I hope it wasn't anything embarrassing? :)
[09:10] <benonsoftware> ronin___: I think you can with bazaar
[09:11] <ronin___> but i got error
[09:11] <mok0> dholbach: http://arstechnica.com/gadgets/news/2011/07/hands-on-google-mobile-client-for-android-and-huddle-group-messaging.ars
[09:12] <benonsoftware> ronin___: What type of error?
[09:12] <dholbach> mok0, phew - I'm glad it wasn't anything worse :)
[09:12] <dholbach> that was in sunny Dublin last week :)
[09:13] <ronin___> Warning: Permanently added 'bazaar.launchpad.net,91.189.90.11' (RSA) to the list of known hosts.
[09:13] <ronin___> bzr: ERROR: Transport operation not possible: readonly transport
[09:14] <dholbach> ronin___, what did you try to do? push to a branch?
[09:15] <ronin___> bzr branch lp:testdrive
[09:16] <dholbach> that's a bit weird
[09:16] <mok0> dholbach: heh
[09:16] <dholbach> ronin___, maybe you can ask in #launchpad - they should know for sure
[09:17] <dholbach> I'm not sure if you have to   bzr launchpad-login
[09:17] <ronin___> yes I'm login
[09:18] <mok0> dholbach: looking forward to checking out Google+ myself
[09:19] <benonsoftware> ronin___: Try either #launchpad like dholbach said or #bzr
[09:19] <dholbach> mok0, it's a shame it's only opened so slowly
[09:19] <tumbleweed> bdrung_: Here's an attempt to tidy 3.0 (quilt) branches before pushing lp:~stefanor/ubuntu-dev-tools/sponsor-patch-quilt I tested it with opendrim-lmp-systemmemory and am waiting to see if the importer likes it or not
[09:20] <ronin___> whar do you mean?
[09:20] <mok0> dholbach: I think that's a part of the whole scheme... when something's restricted, it generates an enormous interest...
[09:20] <dholbach> mok0, on the other hand you might lose interest if you have to wait too long :)
[09:20] <mok0> dholbach: well, there w
[09:21] <mok0> illl be a strong wish to follow the first movers
[09:21] <mok0> FB started the same way, remember? Myspace used to be bigger
[09:22] <dholbach> I was very late to the party the last few times :)
[09:22] <mok0> dholbach: heh, me too. Still am...
[09:49] <ronin___> dholbach: for getting code, must be member of the Testdrive?
[09:50] <benonsoftware> ronin___: I think so.
[09:50] <dholbach> ronin___, no
[09:50] <dholbach> just branching should be possible for all branches in LP
[09:51] <dholbach> (unless it's a private project, but that's only a small minority)
[09:54] <ronin___> Is it good idea for send mail to Dustin?
[09:55] <ronin___> and ask from him?
=== hannesw__ is now known as hannesw
=== dholbach_ is now known as dholbach
[11:09] <bdrung_> tumbleweed: can you write an online test for it?
[11:18] <tumbleweed> bdrung_: it didn't work anyway, I need to play more
=== xeros_ is now known as xeros
[11:41] <didrocks> jtaylor: hey, can you forward your patch for https://code.launchpad.net/~jtaylor/ubuntu/oneiric/qtemu/fix-756221/+merge/67153 upstream?
[11:43] <jtaylor> didrocks: can do, but upstream seems pretty dead
[11:43] <didrocks> jtaylor: well, better to still try, even if there is no activity, at least, other distro can look at their bugtracker and pick the patch if needed
[11:43] <didrocks> jtaylor: meanwhile, I'm build testing and merging, thanks :)
[11:43] <jtaylor> its forwarded to debian
[11:44]  * jtaylor forwarding up
[11:50] <jtaylor> https://sourceforge.net/tracker/?func=detail&aid=3357677&group_id=184796&atid=910689
[11:52] <didrocks> jtaylor: excellent, thanks :)
[13:28] <jtaylor> sourcehighlight-qt segfaults with the new boost
[13:28] <jtaylor> and it can't use the old one as it has a dependency which needs the new one
[13:45] <jtaylor> ah no was just a library conflict
[13:45] <jtaylor> can someone shedule a rebuild of source-highlight so it picks up the new boost?
[13:47] <jtaylor> 8 {,r}deps
[14:05] <tumbleweed> jtaylor: according to the transition tracker, source-highlight-qt should be done first, and that won't rebuild without changes
[14:05] <tumbleweed> oh, other way around
[14:05] <jtaylor> it won't rebuild before libsource-highlight
[14:05] <jtaylor> I'm just preparing a branch that fixes the add needed problem
[14:08] <jtaylor> where is the boost transition tracker?
[14:09] <tumbleweed> http://people.canonical.com/~ubuntu-archive/transitions/boost1.46.html
[14:09] <jtaylor> thx
[14:09] <jtaylor> branch pushed
[14:10] <jtaylor> again a bit more extensive than usual, but its an ubuntu only package
[15:20] <aonyx> I am thinking of wetting my feet with some of the packaging bugs from the sprint
[15:20] <aonyx> found here http://corelli.tumbleweed.org.za/ubuntu-qa/bugjam/
[15:20] <tumbleweed> ohi aonyx
[15:20] <aonyx> hello
[15:20] <aonyx> that was very quick
[15:22] <aonyx> so a question I have is if the bug is fixed in Debian whether there is any point in fixing it in ubuntu
[15:22] <tumbleweed> if it's fixed in debian, we probably want to sync the package over from debian
[15:23] <aonyx> aha, so I should look then for bugs that have not been fixed in Debian right?
[15:25] <tumbleweed> if it's actually been *fixed* (i.e. uploaded) in debian, then we want to check if it builds in oneiric, and file a sync request
[15:26] <tumbleweed> if the package doesn't fail to build in debian (e.g. --as-needed issues), there's little incentive for the package maintainer in debian to move quickly, and it's worth fixing in Ubuntu first
[15:26] <aonyx> ok, cool.
[15:26] <tumbleweed> that said, the --as-needed issues will affect debian in the future, so one might as well file the patch in debian first, and see if the maintainer bites
[15:28] <aonyx> okydokes, it was just that all the triaged bugs on the page seem to have been fixed over in debian already.
[15:28] <aonyx> I did manage to find something not fixed there, which I am going to take a shot at now.
=== JanC_ is now known as JanC
[18:38] <jtaylor> hm what are the timeouts for builds which are hanging in ppas?
[18:38] <jtaylor> my ipython testsuite crashed and blocks :(
[18:39] <geser> 150 min with no output
[18:40] <jtaylor> so long :O
[18:42] <geser> some larger files needs some time for compilation especially on the slower archs
[18:42] <geser> or some programs working for some time (e.g. converting) without any output
[18:44] <jtaylor> what would happen if I upload a new revision now? would it kill the build?
[18:44] <geser> no
=== pfifo_ is now known as pfifo
[19:14] <aonyx> tumbleweed: may I bug you for a second? :)
[19:20] <psusi> normally SRU procedure requires that a bug be fixed in the development release before being SRU'ed.  Natty had a regression where it duplicated entries on the battery menu when (un)plugging mains.  Since the battery icon has not been working at all in Oneiric, I can't even confirm that it suffers from the problem, let alone that it needs the same fix.  Is there a way to override the requirement that it be fixed in oneiric first?
[19:21] <geser> psusi: talk to the SRU team?
=== yofel_ is now known as yofel
[20:08] <aonyx> so tumbleweed seems to be busy, in  which case I shall try asking the rest of you
[20:08] <aonyx> he said that you were all very helpful :)
[20:09] <aonyx> so I am trying to understand some changes that he helped me to make on a makefile for tabix
[20:09] <aonyx> makefile is here http://pastebin.com/CCze660P
[20:10] <aonyx> on line 41 we have libraries referred to: m and z, by "-lz" and "-lm" where could these libraries possibly be?
[20:10] <aonyx> as you can probably see I am quite new to this :)
[20:11] <jtaylor> aonyx: that expand to: libz.so and libm.so
[20:11] <jtaylor> lib prepended and extension added (.so or .a)
[20:12] <jtaylor> they are searched in gcc -print-search-dirs
[20:13] <jtaylor> the most important is /usr/lib and /usr/lib/`dpkg-architecture -qDEB_HOST_MULTIARCH`
[20:15] <aonyx> jtaylor: thanks
=== med_out is now known as medberry
=== Quintasan_ is now known as Quintasan
[23:59] <psusi> TheMuso, re bug #675108 I have not even been able to confirm that the problem exists on oneiric yet because the battery indicator does not show up at all, and I suspect that the problem was due to an ongoing transition that likely will resolve itself on oneiric.  Given that, is it not possible to go ahead with fixing the regression in natty for now, and come back to oneiric later if it is even an issue?