[00:03] <lfaraone> micahg: I see. (I'm 17.2y myself)
[00:04]  * ScottK thinks jpds was youngest when he became a MOTU.
[00:10] <micahg> sponsoring page is broken
[00:10]  * micahg will file a bug report
[00:11] <micahg> bug 636692 if anyone's interested
[00:33] <chrisccoulson> lfaraone, wow, you make me feel so old ;)
[00:33] <lfaraone> chrisccoulson: I try. :)
[01:23] <nhandler> lfaraone, micahg: I was 16 when I became a MOTU, but I'm currently 18
[01:35]  * wgrant was 15, but is pretty sure that jpds was the youngest.
[02:17] <micahg> nhandler: ah, sorry :)
[03:57] <Laibsch> cjwatson: can you point me to the lucid package for bug 632280?
[03:57] <Laibsch> lucid-proposed doesn't seem to have it
[03:58] <micahg> Laibsch: there's one in -updates
[03:58] <Laibsch> is there?
[03:58] <Laibsch> I see
[03:58] <Laibsch> I was waiting for it over in -proposed
[03:58] <micahg> Laibsch: must have migrated
[03:58] <micahg> well, 4.1 is in -updates
[03:59] <Laibsch> I have to say that a locally compiled package with the patch didn't fix the issue :-(
[03:59] <micahg> Laibsch: ah, nm, 4.2 is in unapproved
[03:59] <Laibsch> micahg: that one fixes a different issue
[04:00] <Laibsch> yes
[04:00] <Laibsch> 4.2 is what I'm waiting for
[04:33] <lucidfox> Okay, I'm stupid
[04:33] <lucidfox> I linked the screenshot in my download manager post to my home PC
[04:34] <lucidfox> so predictably, it was offline the whole time I was asleep
[04:50] <blackmatter> LF mentor
[04:55] <micahg> blackmatter: do you need help with something?
[07:18] <bilalakhtar> tumbleweed: Thanks for the comment, well I would like to point out one thing here about the skim merge
[07:19] <bilalakhtar> tumbleweed: I had originally requested a merge, and you commented on the bzr merge proposal that a sync would be better
[07:19] <bilalakhtar> THEN I requested sync, thinking you know better
[07:19] <bilalakhtar> BUT bdrung pointed out a few change that would be dropped, and then you realised your mistakes and merged
[07:20] <bilalakhtar> SO
[07:20] <bilalakhtar> It was your fault, but in the comment it appears it was mine!
[08:06] <tumbleweed> bilalakhtar: hmm, I think you're right. I remembered something like that but couldn't see it in the history (I think there was a previous merge proposal which got deleted)
[08:06] <bilalakhtar> tumbleweed: yes of course, it got deleted
[08:06] <bilalakhtar> but I remember the whole story
[08:06] <bilalakhtar> and
[08:07] <bilalakhtar> you later accepted it to be your fault :(
[08:08] <tumbleweed> bilalakhtar: yeah, my previous e-mail to you said that much
[08:09]  * bilalakhtar is sure he won't become MOTU now
[08:09] <tumbleweed> bilalakhtar: I'm editing the endorsement :P
[08:09] <bilalakhtar> tumbleweed: bdrung's comment was stale, and he forgot a recent merge@
[08:09] <bilalakhtar> !
[08:10] <bilalakhtar> he took the mail I sent him for the UUC application, and instead wrote that stuff for my MOTU application
[08:10] <bilalakhtar> so
[08:10] <bilalakhtar> he forgot the recent sponsorships and wrote the old fflowed ones
[08:10] <bilalakhtar> *flawed
[08:12] <tumbleweed> bilalakhtar: you can explain that at the meeting
[08:12] <bilalakhtar> I will also have to defend ari-tczew's commenyt
[08:13] <bilalakhtar> too much for me! well, I took this application to be just a try
[08:14] <tumbleweed> bilalakhtar: one can't win every time :) but let's wait and see...
[08:15] <micahg> tumbleweed: are you up for another SRU?
[08:18] <tumbleweed> micahg: sure
[08:18] <micahg> tumbleweed: bug 576991
[08:28] <bilalakhtar> Thanks tumbleweed @
[08:32] <tumbleweed> micahg: O: libgjs0: binary-or-shlib-defines-rpath ./usr/lib/libgjs-gi.so.0.0.0 /usr/lib/xulrunner-1.9.2.3
[08:32] <micahg> ugh :(
[08:35] <cjwatson> Laibsch: it's in the unapproved queue.  you can't see it yet
[08:35] <Laibsch> I see
[08:35] <Laibsch> Thank you
[08:35] <cjwatson> I'm not about to go approving my own uploads there
[08:35] <Laibsch> hehe
[08:35] <Laibsch> ;-)
[08:35] <cjwatson> there'll be a message on the bug when it's accepted
[08:35] <Laibsch> OK
[08:36] <Laibsch> I'll wait for it
[08:36] <Laibsch> FWIW, I recompiled my own package including the patch
[08:36] <Laibsch> and it did NOT fix the issue
[08:36] <micahg> tumbleweed: where do you see that?
[08:36] <Laibsch> cjwatson: Is your dsc publicly available?
[08:37] <micahg> Laibsch: I could've given you that hours ago :)
[08:37] <tumbleweed> micahg: in my build. Want logs?
[08:37] <Laibsch> micahg: I was asleep hours ago ;-)
[08:37] <Laibsch> but thanks, I'll remember
[08:37] <Laibsch> you can give it to me now
[08:37] <Laibsch> Please?
[08:38] <hrw> morning
[08:38] <hrw> Laibsch: hi
[08:38] <Laibsch> good morning hrw
[08:38] <hrw> can someone help me with this? https://edge.launchpad.net/ubuntu/+source/armel-cross-toolchain-base/1.46/+build/1955387 - package got build but failed to upload
[08:38] <tumbleweed> micahg: it looks like you should call chrpath on libgjs-gi as well as libgjs
[08:38] <micahg> Laibsch: https://edge.launchpad.net/ubuntu/lucid/+queue?queue_state=1&queue_text=
[08:39] <Laibsch> hrw: I assume you inspected the upload log?
[08:39] <hrw> Laibsch: 'duplicated ancestry' says nothing for me
[08:39] <Laibsch> OK
[08:39] <Laibsch> same here ;-)
[08:39] <Laibsch> maybe ask in #launchpad?
[08:39] <hrw> I will
[08:39] <Laibsch> or #soyuz
[08:39] <Laibsch> or whatever component that is ;-)
[08:40] <micahg> tumbleweed: I don't see that lib
[08:40] <Laibsch> I can never make sense of the LP-related names
[08:40] <Laibsch> hrw: is a simple upload of a 0ubuntu2 package an option?
[08:40] <Laibsch> skipping 0ubuntu1
[08:41] <Laibsch> sometimes that resolve "duplicate"-related problems
[08:41] <Laibsch> micahg: thank you
[08:41] <micahg> Laibsch: np
[08:41] <tumbleweed> micahg: gnome-shell: I don't see this: "Drop binary depends on pkg-config"
[08:43] <micahg> tumbleweed: looks like I messed up that debdiff (forgot to add xulrunner as well :-/)
[08:43] <hrw> Laibsch: it is sponsored package
[08:43] <micahg> tumbleweed: unsubscribed sponsors, it obviously needs work, thanks
[08:43] <bilalakhtar> tumbleweed: could you please check bug #636884 ?
[08:43] <micahg> tumbleweed: feel free to comment in the bug
[08:44] <micahg> bilalakhtar: the package was never removed, it hasn't been added yet
[08:45] <bilalakhtar> micahg: It was removed, do a rmadison
[08:45] <bilalakhtar> micahg: oops, correct
[08:45] <micahg> bilalakhtar: :)
[08:46] <micahg> bilalakhtar: I haven't had a chance to talk to the debian-java folks about it yet, it's a circular dependency that needs some kind of help
[08:46] <bilalakhtar> so I will need to change the changelog message, the rest is fine
[08:47] <cjwatson> Laibsch: probably noot
[08:47] <cjwatson> not
[08:47] <bilalakhtar> micahg: done
[08:47] <cjwatson> oh, well, if you can see micahg's URL then that works
[08:47] <micahg> bilalakhtar: if you have time, maybe talk to #debian-java on OFTC to see if they have any ideas how we can get all the circular dependencies in maverick (obviously if the release team approves :))
[08:48]  * micahg has to go to sleep
[08:49] <Laibsch> cjwatson: well, it's not dget'able, but I think I can probably download all files one by one
[08:49] <bilalakhtar> tumbleweed: :) Refresh the merge page, I have made a change in the changelog message
[08:49] <cjwatson> you could just grab the patch from git, linked in the bug
[08:50] <tumbleweed> bilalakhtar: can we try to sort out the circular dependancy first?
[08:50] <cjwatson> it's not like I did anything more than a trivial backport
[08:50] <bilalakhtar> tumbleweed: but , FF, UIF, and now Final F?
[08:51] <bilalakhtar> tumbleweed: That is the preferred way, but , what do you think? This fix does fix the FTBFS
[08:51] <bilalakhtar> as it prevents the build of those sections
[08:52] <micahg> bilalakhtar: there are many FTBFS currently due to this circular dependency
[08:53] <bilalakhtar> micahg: yes i know
[08:53] <bilalakhtar> tumbleweed: perhaps get this one in for the meantime and I will check with the debian-java folks?
[08:54] <bilalakhtar> tumbleweed: fine, this one now bug #636883
[08:54] <tumbleweed> bilalakhtar: you have a patch. It can wait a few days. Esp if you are now going to do something about the springgraph loop
[08:54] <tumbleweed> (and I know you want to get some FTBFS fixes in quickly now :) )
[08:55] <micahg> bilalakhtar: there are still another few weeks to fix that package
[08:55] <bilalakhtar> tumbleweed: :)
[08:55]  * bilalakhtar joins OFTC
[08:55]  * micahg really goes to bed now :)
[08:56] <hyperair> happy programmers' day!
[08:59] <Laibsch> god, Chinese internet sucks
[08:59] <Laibsch> tsocks to the rescue ;-)
[08:59] <jpds> Laibsch: I think that's the design.
[08:59] <hyperair> doesn't tor suck even more?
[08:59] <Laibsch> hyperair: tsocks, not tor
[09:00]  * jpds goes to find some tea bags.
[09:00] <Laney> geser: Do you know of any reason why we can't switch to using the production API in u-d-t?
[09:00] <Laney> p.s. morning folks
[09:00] <hyperair> ehh what's tsocks?
[09:01]  * Laibsch invites hyperair to private chat
[09:04] <AnAnt> Hello
[09:12] <geser> Laney: no reason, it would be probably good to use production for u-d-t versions in Ubuntu releases and edge in trunk to catch changes to the API earlier
[09:13] <Laney> well we specify an API version too so shouldn't get caught out by changes dropping on us
[09:13] <Laney> I'll make this change — last night there were performance problems on edge which made me look into it (production was fine)
[09:13] <Laney> (thanks to lifeless)
[09:14] <bilalakhtar> tumbleweed: Anyway, that *-packages wasn't necessary, it could have been done without, the way I did it. right?
[09:14] <bilalakhtar> but we would deviate from debian]
[09:15] <bilalakhtar> so it isn't a roadblock, but a suggestion!
[09:16] <bilalakhtar> tumbleweed: done
[09:18] <tumbleweed> bilalakhtar: it's how I would fix it :) (and it results in a patch that makes sense to forward to debian and a more helpful changelog entry)
[09:23] <bilalakhtar> tumbleweed: but, my patch would work, right?
[09:23] <bilalakhtar> That's what I meant!
[09:24] <tumbleweed> yes
[09:24] <bilalakhtar> (no need to have the would here, since I tested it in pbuilder)
[09:25] <tumbleweed> :)
[09:31] <kklimonda> good morning
[09:32] <bilalakhtar> tumbleweed: forwarded
[09:32] <popey> bug 631103 could do with some attention, simple packaging error, would be a shame for it to miss the release. Is there a good way to get someone to look at it?
[09:33] <bilalakhtar> popey: me!
[09:33] <superm1> popey, perhaps a decent bribe would do?
[09:33] <popey> :)
[09:34] <popey> I'm guessing the offer of a free Ubuntu cd isn't sufficient
[09:34] <sladen> does it have to be a recent one?
[09:34] <superm1> is it shiny?
[09:34] <sladen> bit scratched
[09:34] <popey> I've been collecting the set
[09:34] <popey> still missing a couple
[09:35] <sladen> which?
[09:35] <sladen> not now---but find out and I'll have a lookie
[09:35] <popey> dont recall off the top of my head, the early dual-cd ones iirc
[09:35] <popey> cool, ta
[09:35] <popey> oh, hang on, i had a wiki page for this..
[09:37] <bilalakhtar> popey: poke a core-dev in -devel
[09:37] <iulian> popey: It doesn't need ubuntu-release's approval.  Find a core-dev to review and upload it.
[09:37] <popey> ok, ta
[09:37] <iulian> Maybe siretart?
[09:38] <iulian> IIRC, he's the one maintaining ffmpeg in Debian.
[09:38]  * siretart notices a highlight
[09:39] <siretart> oh, I remember a bugreport that had a patch that looked like it had already been fixed in ubuntu but it wasn't
[09:39] <iulian> popey: ^
[09:39] <popey> thanks
[09:41] <AnAnt> Hello, is it possible to stimulate a button press in xvfb-run ?
[09:41] <siretart> AnAnt: have a look at dogtail
[09:42] <AnAnt> siretart: is that a package ?
[09:42] <AnAnt> superm1: thanks
[09:42] <siretart> AnAnt: yes, it is
[09:43] <AnAnt> siretart: ah, python-dogtail
[09:45] <AnAnt> assistive technology ?
[09:48] <AnAnt> siretart: can that be used in a Debian package ?
[09:48] <AnAnt> I mean used for preparing a package, I recall I seen a package doing something with xvfb-run during build
[09:49] <AnAnt> but this dogtail, seems to have some requirements
[09:53] <Laibsch> Can I prepare an SRU with versions 0.6.2-0ubuntu1lucid1 and 0.6.2-0ubuntu1karmic1?  I find that more readable than 0.6.2-0ubuntu1.10.04.1.
[09:54] <Laibsch> or are the numbers a strict requirement?
[09:54] <siretart> AnAnt: no idea
[09:54] <Rhonda> numbers sort better, there were at some point not completely straight forward alphabetical releases.
[09:54] <Laibsch> current version in both karmic and lucid is obviously 0.6.2-0ubuntu1
[09:55] <Laibsch> Rhonda: there's still some way to Z ;-) and eventually we may hit 99, too ;-)
[09:55] <Rhonda> Right, but after 99 comes 100 :)
[09:56] <Laibsch> which may give you trouble to sort
[09:56] <Rhonda> And I don't expect to live by that time anymore.
[09:56] <Rhonda> Why should it?
[09:56] <Rhonda> Why should 100 sort before 99?
[09:56] <Laibsch> you know the option -n to sort?
[09:56] <Rhonda> I know, but how is that of matter here?
[09:56] <Rhonda> How dpkg sorts is relevant.
[09:56] <Laibsch> 100 may sort before 99
[09:57] <Rhonda> $ dpkg --compare-versions 99 \< 100 && echo "yes"
[09:57] <Rhonda> yes
[09:57] <Laibsch> anyway, lets's not get too far off-topic
[09:57] <Rhonda> Laibsch: No, it may not.
[09:57] <Rhonda> Not within dpkg.
[09:57] <Laibsch> I understand your preference
[09:57] <Rhonda> And that's the only relevant thing with respect to package versions.
[09:57] <Laibsch> my question is only if numbers are a must
[09:57] <Rhonda> It's not my preference, it's how the system works. :)
[09:58] <Laibsch> your preference for numbers instead of characters
[09:58] <Laibsch> I prefer characters here despite the limitation you correctly mentioned
[09:58]  * directhex gives everyone a free warthog
[09:58] <Laibsch> computers vs humans
[09:59] <Rhonda> directhex: I doubt that there will be a 0.6.2-0ubuntu1 warthog update. :)
[09:59] <directhex> boo! discrimination against older pcs!
[09:59] <Rhonda> warthog is EOLed, too.
[09:59] <directhex> booooo!
[10:00] <Rhonda> Laibsch: Currently it wouldn't matter from what I can see. All current releases do sort alphabetically properly.
[10:00] <Laibsch> great
[10:00] <Laibsch> characters it'll be then :-P
[10:00] <Laibsch> ;-)
[10:00] <Rhonda> But then, I'm still not a person for an authorative answer. :)
[10:01] <Rhonda> I just can tell you that it wouldn't cause any troubles _now_ as things are.
[10:02] <directhex> personally i dislike both options
[10:02] <directhex> (there should be a + or ~ there IMHO)
[10:02] <directhex> but i'm odd like that
[10:04] <Rhonda> Hmm, wait, yes.
[10:05] <Rhonda> A ~ is definitely missing.
[10:05] <Rhonda> Laibsch: 0.6.2-0ubuntu1~karmic1 and 0.6.2-0ubuntu1~lucid1 because otherwise it would be considered a higher version number than 0.6.2-0ubuntu1 in maverick.
[10:06] <Laibsch> well, that's desired
[10:06] <Rhonda> ?
[10:06] <Laibsch> it should of course be higher than the current version
[10:06] <Rhonda> It's desired to not be able to upgrade properly from older versions to latest?
[10:06] <Rhonda> ??!
[10:06] <Laibsch> ???
[10:06] <Rhonda> Why so?
[10:07] <Laibsch> (16:54:51) Laibsch: current version in both karmic and lucid is obviously 0.6.2-0ubuntu1
[10:07] <Rhonda> Ah, higher than that, yes.
[10:07] <Laibsch> 0.6.2-0ubuntu1 is not in maverick
[10:07] <Rhonda> But it still has to be lower than what's in maverick.
[10:07] <directhex> what is the target version you want in the SRU?
[10:07] <Rhonda> Good. If you would have mentioned a package name that would have helped too, btw. :)
[10:08] <directhex> SRU version is based on target version, not the original
[10:08] <Laibsch> how else would you be able to SRU?
[10:08] <Laibsch> I think it's gnome-scan
[10:08] <directhex> simple-scan?
[10:08] <Laibsch> directhex: what do you mean, target version?
[10:09] <Laibsch> let me check
[10:09] <Laibsch> I'll give you the bug number
[10:09] <Laibsch> bug 482618
[10:09] <directhex> Laibsch, i mean if 0.6.2-0ubuntu1 is in karmic/lucid, why are you trying to upload 0.6.2-0ubuntu1 again? surely you want a newer version?
[10:10] <Laibsch> I'm SRUing/backporting a simple fix
[10:10] <directhex>  gnomescan | 0.6.2-0ubuntu1 | karmic/universe | source, all
[10:10] <directhex>  gnomescan | 0.6.2-0ubuntu1 | lucid/universe | source, all
[10:10] <directhex>  gnomescan | 0.6.2-0ubuntu2 | maverick/universe | source, all
[10:10] <Laibsch> of course
[10:10]  * Laibsch hides ;-)
[10:10] <Laibsch> oh, wait
[10:10] <Laibsch> no need to
[10:10] <directhex> Laibsch, so it's a fix which is not in 0.6.2-0ubuntu2 in maverick, and not relevant in maverick?
[10:10] <Laibsch> and it can't be any other way, really
[10:10] <Laibsch> directhex: why do you think that?
[10:11] <Laibsch> it's essentially the diff between 0ubuntu2 and 0ubuntu1, but backported
[10:11] <Laibsch> SRUd
[10:11] <directhex> right. okay. that took 20 minutes more than it should have done
[10:11] <Laibsch> not really my fault, I think
[10:11] <Laibsch> I was only asking if characters are OK
[10:12] <Laibsch> which apparently they
[10:12] <Laibsch> are
[10:12] <Laibsch> the rest was more or less you guys' curiousity
[10:27] <hrw> ok, my package is now pbuilding to test recent updates so I can get back to business
[10:28] <hrw> in this/next week I plan to start procedure of becoming ubuntu developer. currently there is one package in archive which I maintain (armel-cross-toolchain-base), and there are two which I maintained in past, also submitted lot of improvements to few core components (gcc/eglibc/binutils/linux) and 3 my packages are on a way to maverick (got FFe for them).
[10:30] <hrw> according to https://wiki.ubuntu.com/UbuntuDevelopers there are few types of developers in Ubuntu. which kind should I start with? Universe contributor? motu? core-dev?
[10:33] <hrw> Laibsch: hints?
[10:33] <Laibsch> I kind of failed to understand this myself ;-)
[10:33] <Laibsch> I went for becoming a DM (and maybe DD in the future) myself
[10:34] <Laibsch> I guess the most powerful would be core-dev
[10:34] <geser> hrw: Universe contributors gives you only Ubuntu membership
[10:34] <Laibsch> universe contributor and motu are the same AFAIU
[10:34] <tumbleweed> Laibsch: no, MOTU can upload to universe and multiverse
[10:34] <Laibsch> but these things have been changing quickly in the past
[10:34] <Laibsch> I see "universe contributor" seems to be a new creation then
[10:34] <geser> Laibsch: yes, core-dev can upload everthing, MOTU only universe/multiverse and Universe contributor can't upload (only Ubuntu membership)
[10:35] <Laibsch> These groups are being faster than I can keep up with
[10:35] <hrw> Laibsch: after reading ubuntu wiki I also got a feeling that becaming UD by becaming DD first is nicer way but takes more time I think
[10:35] <Laibsch> contributing to Ubuntu can be more than a full-time job just keeping up with the red tape ;-)
[10:36] <Laibsch> hrw: My experience (and frustration) lately is that Debian is very responsive.  I've come to loathe (profoundly I may add) many Ubuntu processes.
[10:36] <geser> hrw: an other option for you might be PPU (Per-package upload rights) for the package you maintain
[10:36] <Laibsch> I say that as someone who hasn't touched a Debian system for at least 5 years
[10:37] <hrw> the fun is that working for Canonical means also that my code lands in Ubuntu sooner or later. and as my 3 packages lands there soon (one landed) I think that I need to get kind of UD status to get control on them without playing with sponsors
[10:37] <Laney> you don't get control
[10:37] <hrw> Laney: control as "right to do dput mypackage_newversion.dsc"
[10:41] <hrw> Laney: I think that such kind of control exists in ubuntu
[10:41] <Laney> upload rights? sure
[10:42] <Laney> doesn't give you any more right to work on a package than anyone else though
[10:42] <hrw> and yes, I remember my old phrase "Debian has maintainers, Ubuntu has developers"
[10:42] <Laibsch> Laney: it sure does
[10:42] <Laibsch> you can upload freely
[10:42] <Laibsch> most people cannot do that
[10:42] <Laibsch> but I think lately it's more going to "peer review"
[10:42] <hrw> Laibsch: but any od UD can do upload too if they think it has a sense
[10:43] <Laibsch> yes
[10:43] <Laibsch> Ubuntu devs are more powerful than DD
[10:43] <Laibsch> in that sense
[10:43] <Laibsch> although even in Debian it's more of a social than a technical barrier
[10:44] <hrw> yes
[10:45] <hrw> I prefer Debian way more as it allows me to add few persons to Uploaders: field and be free to go for holidays without worrying that personX will break it. but ubuntu rules tries to keep such breaks away
[10:46] <micahg> hrw: team packageset ownership is encouraged for that reason
[10:46] <hrw> thx micahg
[10:46] <Laney> that doesn't give you any control either
[10:46] <Laney> (yet)
[10:46] <micahg> Laney: what do you mean by control?
[10:47] <Laney> packageset teams don't own packages
[10:47] <Laney> hrw: nothing stops you maintaining your package in debian
[10:48] <micahg> Laney: well, true, but they have upload rights, and the team can be set as the maintainer in some cases
[10:48] <hrw> Laney: it is ubuntu package - making it workin in debian is one of my objectives for next 6 months
[10:48] <geser> hrw: even in Debian other DD have the option for an NMU a package
[10:49] <hrw> Laney: since UDS I touched each toolchain components. gcc packaging got few thousands LOC size patches from me (all merged)
[10:49] <Laney> ok...
[10:49] <geser> hrw: even if every MOTU/core-dev (depending on where you package is) has the right to upload your package most will coordinate with you before uploading
[10:49] <hrw> geser: I know. used NMU way for my own local changes
[10:50] <hrw> geser: my packages goes for universe
[10:50] <micahg> Laney: did the new sqlite help with banshee?
[10:50] <Laney> somewhat
[10:50] <Laney> still some problems though
[11:06] <jpds> Laney: Keeps crashing at the end of songs here.
[11:06] <Laney> I doubt that's a sqlite problem, but please file an upstream bug (assuming you are running 1.7.5)
[11:07] <Laney> banshee --debug will give you a trace
[11:07] <jpds> It's a native code error.
[11:07] <Laney> could be gst
[11:29] <AnAnt> Hello
[14:16] <bilalakhtar> lucidfox: Steadyflow is good! Is there anything in which I can help?
[14:16] <jetienne> q. i would like to do a script which is called on "apt-get purge mypackage"... there is prerm but it has a bunch of commands... which one is the good one ?
[14:17] <lucidfox> bilalakhtar> Certainly! You can translate, test and file bugs and feature requests, give feedback on the UI, or contribute code
[14:17] <bilalakhtar> lucidfox: I mean contributing code, but what should I begin with, when contributing code?
[14:18]  * bilalakhtar bzr branches lp:steadyflow
[14:18] <lucidfox> bilalakhtar> Would you like to have commit access, or you'd prefer just submitting patches and/or branches?
[14:18] <bilalakhtar> lucidfox: I mean, what is needed right now? feature addition or bug fixing?
[14:18] <bilalakhtar> lucidfox: I prefer contributing patches rather than having access
[14:19] <lucidfox> Right now, features. Just a moment, I'll add a TODO file :)
[14:23] <iulian> What is steadyflow?
[14:24] <bilalakhtar> iulian: https://edge.launchpad.net/steadyflow
[14:25] <iulian> Ah, download manager.
[14:26] <bilalakhtar> lucidfox: since its Vala I might not be able to help a lot
[14:26] <lucidfox> Hey, Vala is easier than C!
[14:26] <bilalakhtar> that's why I preferred the 'patch' method
[14:26]  * lucidfox nods
[14:26]  * bilalakhtar never worked on Vala
[14:27] <lucidfox> Have you written C# or Java?
[14:27] <bilalakhtar> lucidfox: none
[14:27] <lucidfox> :(
[14:27] <bilalakhtar> C/C++ instead, lucidfox
[14:27] <bilalakhtar> My languages include Python, PHP, C/C++, (web languages)
[14:28] <bilalakhtar> lucidfox: np, I can learn languages very easily. I learnt python 'just like that'
[14:28] <bilalakhtar> by just looking at applications written in it
[14:32] <lucidfox> bilalakhtar> same :)
[14:41] <lucidfox> bilalakhtar> pull to get TODO and a little source tree documentation
[14:56] <bilalakhtar> lucidfox: done, thanks for the TODO!
[14:57]  * bilalakhtar will now be off
[15:29] <kklimonda> ari-tczew: so my second patch doesn't work - have you managed to get a straceback? and what about the patch attached to bug report? also, can you still reproduce the issue with g-s-d from the archive?
[15:29] <ari-tczew> kklimonda: just tested patch from LP.
[15:30] <ari-tczew> kklimonda: yes, from archive is still affected
[15:30] <ari-tczew> kklimonda: not managed a straceback. I forgot, that it's important for you.
[15:32] <kklimonda> ari-tczew: hmm.. do I have to do something to make kolourpaint4 use g-s-d?
[15:32] <ari-tczew> kklimonda: perhaps not. I only install kolourpaint4
[15:33] <ari-tczew> kklimonda: btw. it's causes by edit file from print screen (clipboard)
[15:33] <kklimonda> how do you put a screenshot in the clipboard?
[15:34] <ari-tczew> kklimonda: I'm clicking on keyboard and push the button 'PrtSc'
[15:34] <ari-tczew> then save on desktop (automatically window), then saved file open through kolourpaint4
[15:40] <kklimonda> hmm, I got it to crash once..
[15:46] <kklimonda> ari-tczew: in the meantime the stacktrace with debug symbols would be great ;)
[15:48] <ari-tczew> kklimonda: ok but now I'm busy
[16:15] <hrw> https://wiki.ubuntu.com/MarcinJuszkiewicz/DeveloperApplicationForUniverseContributer - does it look ok or should I change something there?
[16:20] <kklimonda> ari-tczew: I can't crash g-s-d with the patch attached to bug 626379 and I have figured out how to reproduce it..
[16:20] <DktrKranz> directhex: mind paste me latest ACCEPT mail for your monodevelop-database_2.4+dfsg-2 upload, if you still have it?
[16:21] <geser> hrw: try to get some endorsements from the persons you work with.
[16:21] <directhex> Subject: 	monodevelop-database_2.4+dfsg-2_amd64.changes ACCEPTED into unstable ?
[16:21] <kklimonda> ari-tczew: and that's not the same patch I have sent you some time ago.
[16:22] <hrw> geser: sure, thats the goal for next few days
[16:22] <directhex> DktrKranz, http://paste.debian.net/89553/
[16:25] <DktrKranz> yay
[16:25] <DktrKranz> dak is finally fixed
[16:25] <DktrKranz> thanks :)
[16:25] <directhex> DktrKranz, you mean no more ['foo'] in "uploaded to" message?
[16:25] <DktrKranz> yes
[16:30] <geser> hrw: you might also want to check if you already fulfill "sustained and significant contributions" which is a requirement for membership. "While there is no precise period that we look for, it is rare for applications to be accepted from people contributing for less than 6 months" (from https://wiki.ubuntu.com/Membership)
[16:31] <ScottK> ajmitch_: Could you have a look at the pythonmagick FTBFS.  I recall you particularly love mixing boost and python.  Needs to get fixed for NBS.
[16:31] <hrw> geser: the questions is: where/how I can test it
[16:33] <geser> hrw: I didn't look at your application in detail (yet) but you should know better than me how long you have contributed directly to Ubuntu and how much (packages, bug fixes, etc.). If in doubt ask your sponsors if they feel that you are "ready".
[16:34] <kklimonda> can package build-depend on language-pack-en-base ?
[16:35] <geser> IIRC some packages use it as replacement for locales-all, so yes
[16:36] <hrw> geser: my direct ubuntu changes started in May 2010. My sponsor (Steve Langasek, who is also my manager) confirmed that I should start for getting Ubuntu Developer status.
[16:37] <kklimonda> hrw: so you are a Pole, you work for Canonical and we don't know you? Your LoCo involvement leaves a lot to be desired! ;)
[16:37] <ari-tczew> hrw: you should start working on stricte Ubuntu development - merges, syncs, SRUs, security updates. but now we are around FinalFreeze and only bugfixes are upload-able
[16:38] <ari-tczew> yea, next Polish contributor. sounds good
[16:39] <geser> ari-tczew: I don't know on which tasks hrw works for Canonical so he might have got exceptions for the work he is doing
[16:40] <hrw> kklimonda: I am more developer then social type
[16:40] <hrw> and my work takes most of my time
[16:42] <ScottK> hrw: If your view is "I do what I get paid to do and that's enough", you're likely to be disappointed.
[16:43] <ScottK> The fact that your manager wants you to be an Ubuntu developer means precisely nothing with regards to your becoming one.
[16:45] <ari-tczew> hrw: do you want be a volunteer?
[16:46] <hrw> ScottK: not quite that. I do have few years of experience with fixing ftfbs problems and this is one of things where I plan to go. from time to time I do changes in packages which I use, sometimes I do package things not present in archive for my own use.
[16:47] <ScottK> hrw: OK.  That's good to hear.
[16:47] <hrw> kklimonda: Szczecin does not have any visible group of Ubuntu users
[16:48] <hrw> ScottK: sure thing is that most of my work on ubuntu will be job related. but it will be spread on many packages during natty development I hope.
[16:48] <ScottK> OK.
[16:48] <hrw> ScottK: for maverick I did few thousands of lines in patches for gcc/eglibc/linux/binutils packaging rules.
[16:49] <kklimonda> hrw: that was said mostly as a joke - Poland has no LoCo to talk about. But still it's not going to get better if we all hide on english speaking channels :)
[16:49] <ScottK> hrw: One piece of advice I will give you is not to rely exclusively on the fact that it's easy to get sponsored by your fellow Canonical co-workers and make a point of participating with the broader community.
[16:49] <hrw> kklimonda: I am on 4 irc networks and have 16 open windows now. just one channel is Polish speaking
[16:50] <hrw> ScottK: I know
[16:50] <ScottK> OK
[16:52] <tumbleweed> hrw: yeah, get endorsements from the people you've worked with, but also do more work with the wider community (i.e. put non-urgent things in the sponsor queue and get to know some other sponsors)
[16:54] <hrw> mkey
[16:54] <tumbleweed> best way to get endorsments is to have many people who've sponsored your work
[16:55] <ari-tczew> hrw: ATM we have one sponsor from Poland, but maybe it will be changed soon :)
[16:59] <kklimonda> nice, another python 2.6 release that breaks backward compatibility..
[17:05] <hrw> have a nice rest of day
[17:33] <micahg> SpamapS: re mongodb, go ahead and update the merge if you like, I won't get to it until later tonight at the earliest
[17:34] <SpamapS> micahg: its updated already isn't it?
[17:34] <micahg> SpamapS: oh, you wanted to know about adding something else
[17:34] <SpamapS> micahg: I submitted upstream too.. might as well get them to include the wrapper too.
[17:35] <SpamapS> micahg: this wrapper business feels really dumb though. We're just putting off one failure for another if we expect ABI incompatibility.
[17:35] <micahg> SpamapS: oh, I wanted to chat with you about that, but not now, the wrapper is only good in Ubuntu or its derivitives
[17:38] <SpamapS> micahg: Right, they seem to have a bunch of ubuntu specific stuff in their build process.
[17:41] <micahg> SpamapS: k, ttyl
[18:48] <achiang> hello, i'm trying to modify a package (x11proto-fixes). i grab it, unpack it, and check the output of what-patch, which says "quilt". although i don't see a debian/patches/ directory, my impression is that i can just say: quilt new foo.patch ; quilt add bar.c ; vi bar.c ; quilt refresh. i modify the changelog appropriately and then build the package. however, after installing it in a chroot, i don't see my changes. did i do something obviously wro
[18:48] <achiang> ng?
[18:58] <achiang> or would perhaps #ubuntu-packaging be a better place to ask the above?
[19:00] <ScottK> achiang: Did you export QUILT_PATCHES=debian/patches ?
[19:01] <achiang> ScottK: not in my chroot. but otherwise, yes. i mean, after doing a quilt refresh, i see debian/patches/ appear, there's a series file, and my patch exists and looks sane
[19:01] <achiang> ScottK: i guess when i build, i don't see any text about my patch getting applied though
[19:02] <ScottK> It's already applied, isn't it?
[19:02] <achiang> hm, i think i pop all the patches before i build
[19:02] <ScottK> Sounds like you are doing things right, so I'm not sure.
[19:02] <achiang> i did rm the .pc directory that gets created
[19:04] <Sarvatt> achiang: check out debian/README.source, X packages are a bit different and use xsfbs. basically you need to add a  $(STAMP_DIR)/patch dependency to the first target in the rules and the clean target needs to have a dependency on xsfclean, then just create debian/patches/, drop your patch in that directory and add to the series
[19:05] <achiang> Sarvatt: interesting. now that you mention it, looking in debian/rules, i do see include debian/xsfbs/xsfbs.mk. does that mean that what-patch lied to me?
[19:06] <achiang> Sarvatt: nm, i will read more before asking further stupid questions.
[19:07] <Sarvatt> http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-ati.git;a=blobdiff;f=debian/rules;h=5c87ec5bcef3458a952fbcb24304054fcc7288e0;hp=06e2f6b13a1cc173044f42a9b7b3d31325451b23;hb=83cfc16d7321f9cce38d0e04a18f5a31ea6681a9;hpb=016a84478f32b7edcb6c1dc9c2d55ec8130d82c3  -- thats basically a reverse example of what ya need to do besides adding quilt the build deps
[19:09] <achiang> Sarvatt: thanks so much. it would have taken me a long time to figure that out.
[19:16] <c_korn> does someone have an idea how to write a watch file for the release version of snowglobe? http://wiki.secondlife.com/wiki/Snowglobe the problem is that the download link for the dev or release version does not contain the information whether it is a release or dev version.
[19:17] <directhex> c_korn, write a wrapper in php or similar which can do the job for you
[19:18] <directhex> c_korn, i.e. "screen scrapes page, looks for non-development version, presents URL which watch file can use"
[19:18] <c_korn> directhex: I already thought of this. but I did not yet find a free php webhoster which allows f_open with URLs or fsockopen
[20:50] <bilalakhtar> ari-tczew: ping
[20:52] <bilalakhtar> angelabad: hello there!
[20:52] <ari-tczew> bilalakhtar: pong
[20:52] <bilalakhtar> ari-tczew: a late pong :)
[20:52] <bilalakhtar> ari-tczew: Did you read the memos I sent you?
[20:52] <bilalakhtar> ari-tczew: /msg MemoServ read new
[20:53] <angelabad> hello!
[20:54] <ari-tczew> bilalakhtar: no?
[20:54] <ari-tczew> bilalakhtar: [21:50] <bilalakhtar> ari-tczew: ping
[20:54] <bilalakhtar> ari-tczew: I have experience, you could ask the people here
[20:54] <bilalakhtar> ari-tczew: The memos!
[20:54] <ari-tczew> bilalakhtar: nothing
[20:55] <bilalakhtar> ari-tczew: okay, lemme explain manually
[20:55] <bilalakhtar> ari-tczew: I saw your comment on my MOTU application about the experience thing
[20:55] <ari-tczew> cool
[20:55] <bilalakhtar> ari-tczew: I agree I should work in more areas, but I am talking about the first point
[20:55] <bilalakhtar> ari-tczew: there are a few MOTUs who know I have enough experience
[20:56] <bilalakhtar> ari-tczew: if it was because I told you to run dh get-orig-source I would like to tell you that will also work
[20:56] <ari-tczew> bilalakhtar: my opinion is you don't have expierence. you started work since maverick and I remember not long ago your mistakes - review by dholbach
[20:56] <bilalakhtar> dh forwards all unknown calls to debian/rules
[20:56] <bilalakhtar> ari-tczew: that was long ago!
[20:56] <bilalakhtar> ari-tczew: FYI I have been involved with Debian before
[20:56] <ari-tczew> bilalakhtar: oh, the time is running quickly
[20:57] <bilalakhtar> move to ubuntu very recently
[20:57] <bilalakhtar> so most of my errors were about ubuntu packaging, apart from that
[20:57] <bilalakhtar> my knowledge in debian packaging is very good
[20:57] <ari-tczew> bilalakhtar: so maybe you should apply to DD?
[20:57] <bilalakhtar> ari-tczew: not that much as well :)
[20:58] <ari-tczew> bilalakhtar: what's the sense of this discussion? remove/change my comment?
[20:58] <bilalakhtar> ari-tczew: yup, I just want to say, your point 1 is not valid anymore
[20:58] <bilalakhtar> you may not remove it I have no problem
[20:58] <bilalakhtar> but if during the meeting they ask
[20:59] <ari-tczew> bilalakhtar: I won't do this - this is my opinion. everyone can edit your wiki application and write opinion
[20:59] <bilalakhtar> ari-tczew: its your choice, I just wanted to ask it
[20:59] <bilalakhtar> ari-tczew: I know
[20:59] <bilalakhtar> ari-tczew: but just wanted to tell you
[20:59] <bilalakhtar> ari-tczew: You have more experience than me, look at your own application, 20+ comments
[20:59] <bilalakhtar> wow
[20:59] <bilalakhtar> ari-tczew: I don't want to get it removed, I just want to get the fact cleared in you
[21:00] <ari-tczew> bilalakhtar: well, after my comment you're looking for my mistakes to show them to me?
[21:01] <bilalakhtar> ari-tczew: ah, lol, no way!
[21:01]  * bilalakhtar doesn't plot plans against others
[21:02] <ari-tczew> bilalakhtar: take it easy
[21:02] <bilalakhtar> ari-tczew: well, thanks for the comment
[21:03] <ari-tczew> bilalakhtar: it's my pleasure
[21:03]  * ari-tczew is going watch dr house
[21:14] <ajmitch_> ScottK: now what were you trying to foist off onto me?
[21:15] <ScottK> ajmitch_: Look at the build log for pythonmagick on i386 and enjoy.
[21:17] <ajmitch_> interesting that it worked on amd64
[21:18] <ScottK> Yeah.
[21:18] <ScottK> It looked like just your pile of pain.
[21:19] <ajmitch_> it looks like too much c++ for me to be comfortable
[21:19]  * ajmitch_ will need to dig around for an i386 pbuilder
[22:03] <ScottK> lfaraone: Still waiting for your new turtleart upload.
[22:11] <lfaraone> ScottK: right, the maintainer said he'd get to it today.
[22:12] <ScottK> lfaraone: OK.
[22:12] <ScottK> tick tock.  tick tock.
[22:24] <ajmitch_> ScottK: it's a little frustrating that the patches in there are the ones included in pythonmagick 0.9.2, and are the ones said to fix such an error
[22:24]  * ajmitch_ is not a fan of c++
[22:24] <ScottK> Weird.
[22:24] <ScottK> So maybe it's a boost problem?
[22:25] <ajmitch_> or maybe it's unrelated to boost
[22:26] <ajmitch_> though with that pile of ..., who knows?
[22:26] <ScottK> Yeah.
[23:07] <ari-tczew> angelabad: what about this branch? https://code.launchpad.net/~angelabad/ubuntu/maverick/gnome-bluetooth/gnome-bluetooth-fix-631126
[23:08] <angelabad> ari-tczew, this was to fix the 631126, I forgot remove it
[23:08] <angelabad> i will remove, thanks
[23:36] <ari-tczew> nice ^