[00:32] <dtchen> maco: want to push http://launchpadlibrarian.net/36042725/lame_3.98.2%2Bdebian-0ubuntu3.debdiff for me, please?
[00:32] <maco> sure
[00:32] <dtchen> thanks
[00:35] <maco> dtchen: "apt-get -t=lucid source lame" isnt happy.=
[00:35] <ajmitch> dtchen: you don't have upload rights yet?
[00:35] <maco> he hasnt in a couple years
[00:35] <maco> gave them up
[00:36] <ajmitch> but he reapplied recently
[00:36] <ajmitch> lame is in multiverse if it helps your apt-getting :)
[00:36] <maco> and cant figure out what the new process is
[00:36] <maco> ajmitch: ah thts it
[00:37] <ajmitch> I suspect a different group of people need to be pinged for upload rights now
[00:37] <maco> its the DMB
[00:37] <dtchen> ajmitch: DMB met this morning, but their meeting times collide directly with my work hours.
[00:37] <ajmitch> dtchen: that's why I was a little surprised, since I saw a number of other people welcomed into the fold
[00:37] <ajmitch> like Amaranth with his compiz crack
[00:38] <Laney> they wanted to do an interview as it was a core-dev application
[00:39] <Amaranth> They wanted to do an interview because he was core-dev in the past
[00:39] <ajmitch> ah well
[00:39] <maco> er...isnt update-maintainer supposed to put 'Ubuntu Developers <ubuntu-devel-discuss...>" in debian/control?
[00:39] <ajmitch> soon, I hope :)
[00:40] <ajmitch> maco: what did it do for you?
[00:40] <maco> put me
[00:40] <maco> pretty sure thats not right
[00:40] <ajmitch> heh
[00:40] <Laney> it does that if it can't find the package in debian
[00:41] <dtchen> which it isn't, since its source is either debian-multimedia or multiverse
[00:41] <ajmitch> thanks, I was just about to say that :)
[00:41]  * ajmitch was just reading through the (short) source for it
[00:41] <maco> i see
[00:41] <maco> so i should put in devel though, right?
[00:41] <dtchen> these are the sorts of things I would have outright rejected in the past for patches, but well, I think we can do better
[00:42] <ajmitch> unless you want to be responsible for it
[00:42] <dtchen> (better -> smoother upgrades)
[00:43]  * Laney doesn't understand the Provides:
[00:43] <dtchen> Laney: upgrades
[00:43] <Laney> and that changelog could be more verbose (why)
[00:43] <Laney> anyway, bed
[00:44] <dtchen> we can't prevent people from using other repositories, but we can handle upgrades from known sources
[00:44] <dtchen> true, I could have put "Allows smooth upgrades"
[00:44] <maco> dtchen: uploading
[00:48] <dtchen> maco: thanks
[00:49] <ajmitch> finally, an up-to-date sid install
[02:07] <Buuntu>  /join #ubuntu-us-oh
[02:26] <Buuntu> nxvl, so do you think I can get a mentor then?
[02:27] <nxvl> Buuntu: can you do a patch by yourself?
[02:28] <Buuntu> nxvl, hmm, a very simple one :D, I was able to build the one provided as an example on the wiki guide :P
[02:28] <nxvl> Buuntu: a mentor is not a teacher
[02:28] <Buuntu> nxvl, well, I just need guidance
[02:29] <nxvl> Buuntu: a mentor will guide you trough the motu process, but not by the hand, you need to be able to do the process by yourself
[02:29] <nxvl> Buuntu: with a little help of a mentor
[02:30] <Buuntu> nxvl, well that will be helpful anyways, I just need someone to guide me at first at least - I'm not exactly sure what to do next besides maybe try to build a few more packages
[02:30] <RoAkSoAx> ;)
[02:30] <nxvl> Buuntu: find a bug that you can fix, try to fix it, and when you have problems ask here
[02:30] <nxvl> a lot of people will be able to helo
[02:33] <nxvl> Buuntu: https://wiki.ubuntu.com/UbuntuDevelopment
[02:34] <Buuntu> nxvl, find a bug? motu deals with bugs?
[02:34] <Buuntu> nxvl, I thought they just packaged what the developers made
[02:34] <nxvl> no
[02:35] <nxvl> we deal with bugs
[02:35] <nxvl> actually most of the work is dealing with bugs
[02:36] <nxvl> the packaging is mostly done in debian
[02:38] <Buuntu> nxvl, lol, what kind of bugs exactly - bugs in packages?  it isn't very clear what MOTU does in the wiki then :P
[02:38] <nxvl> in packages, in packging, etc..
[02:39] <nxvl> we maintain the packages
[02:39] <nxvl> if the packages have bugs, we need to fix them
[02:39] <nxvl> or contact upstream to fix it
[02:39] <Buuntu> nxvl, I don't know how the process works - that's what I need guidance with: where do I get the packages that haven't been approved for example (I'm guessing those are the ones that need fixed)?
[02:39] <Buuntu> nxvl, how do I upload the completed package, etc...
[02:41] <Buuntu> nxvl, do I need to fix bugs in the source package as well?
[02:41] <Buuntu> nxvl, lots of questions I'm confused about... :P
[02:41] <nxvl> questions that you can ask in this channel and someone will answer to them and help you
[02:42] <nxvl> ScottK: around?
[02:42] <nxvl> ScottK: i kinda broke courier :P
[02:43] <Buuntu> nxvl, does motu do the bug finding itself or do we just fix the bugs that have already been found?
[02:43] <nxvl> ScottK: it's complaining about some non-moved files
[02:44] <nxvl> Buuntu: http://qa.ubuntuwire.org/
[02:52] <Buuntu> nxvl, can I really fix any bug with just what that guide taught me?
[02:53] <dtchen> Buuntu: there isn't a substitute for experience, I suppose
[02:54] <Buuntu> so motu is more of a self-taught thing more than anything? I shouldn't expect any guidance?
[02:54] <nxvl> yup
[02:54] <maco> there is much to read, but you can of course ask questions here
[02:54] <nxvl> there isn't a magic recipe that will fix all your problems
[02:54] <nxvl> you need to think
[02:55] <maco> i dont think anyone's going to prevent you from making mistakes and learning from them
[02:55] <Buuntu> T_T
[02:55] <maco> i ask a LOT of questions
[02:55] <nxvl> i'm a MOTU and i do that aswell
[02:55] <nxvl> core-devs ask questions aswell
[02:55] <nxvl> no-one knows all the answers
[02:55] <Buuntu> I think I expected this to be much easier than it is, that's all :P
[02:56] <Buuntu> everything all set up and easy to follow instructions on how to do it etc...
[02:56] <maco> yeah, we could probably use better docs
[02:56] <dtchen> +1
[02:56] <maco> but the good news is that there are a few things you're going to do a lot and once youve done them once or twice, its pretty easy
[02:57] <RoAkSoAx> Buuntu, i'm also a MOTU and I ask a looooooooooooooot of questions on things I do not know
[02:57]  * maco puts a hand over dtchen's mouth so he cant say how many questions i ask
[02:58] <nxvl> yeah, RoAkSoAx drive me crazy all day
[02:58] <nxvl> :D
[02:58]  * nxvl hides
[02:58] <Buuntu> so sorry if this is broad, but how does the process of maintaining work?
[02:58] <nxvl> maco: well, we are on IRC, closing his mouth won't help you
[02:58] <maco> hehe dtchen's my roommate, so none of you see how much i ask him, since i do it offline
[02:58] <nxvl> maco: his hands are still free :P
[02:58] <maco> nxvl: hrm fair point
[02:58] <RoAkSoAx> maco, nxvl and ivoks wanted to kill me once :P
[02:58] <maco> nxvl: no killing MOTUs!
[02:59] <nxvl> maco: you are listed aswell
[02:59] <ajmitch> maco: take away our fun, why don't you
[02:59] <nxvl> maco: so don't blame me :D
[02:59] <maco> nxvl: i thought that was "maco, i am talking to you..."
[02:59] <nxvl> ohhh
[02:59] <nxvl> right
[02:59] <Buuntu> how do you "check a package for bugs"? just review all the important files and maybe run pbuilder on the package see if the dependencies are wrong?
[02:59] <maco> i dont recall wanting to kill RoAkSoAx
[02:59] <nxvl> it can be that aswell
[02:59] <nxvl> :P
[02:59] <nxvl> i do
[02:59] <nxvl> :D
[03:00] <ajmitch> if only finding bugs in a package were that easy :)
[03:00] <maco> Buuntu: pbuilder it, yeah...test installation and removal...upgrade as well if a previous verison exists
[03:00] <ajmitch> that'll catch a few of them, some won't show up until people start using the package
[03:00] <dtchen> piuparts <--
[03:01] <Buuntu> maco, what do you suggest I do first, build a s*** load of packages so I get the hang of how it works?
[03:01] <maco> ok yeah piuparts automates htat install/remove/upgrade thing...i just dont know hwo to use it
[03:01] <maco> ajmitch: i think Buuntu means testing the packaging, not the software
[03:01] <nxvl> that reminds me
[03:01] <maco> Buuntu: find a bug with a patch attached and learn how to patch the pakage
[03:01] <dtchen> I'm pretty sure I sketched out how to use it in a classroom session ;-)
[03:01] <nxvl> dtchen: you weren't on UDS, right?
[03:01] <dtchen> nxvl: correct
[03:01] <maco> dtchen: yeah i have to go read that
[03:01] <ajmitch> maco: but they're so closely related most of the time :)
[03:01] <Buuntu> are packages with bugs all nicely organized already?
[03:01] <maco> Buuntu: bugs.launchpad.net/ubuntu ?
[03:02] <nxvl> dtchen: why?
[03:02] <micahg> ?
[03:02] <maco> Buuntu: you can do a search on there for bugs with patches attached
[03:02] <micahg> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=bitesize
[03:02] <ajmitch> think of MOTU like fighting a forest fire with a leaky bucket of water :)
[03:02] <micahg> bitesize might be good to start with, no?
[03:02] <maco> micahg: i thought bitesize tended to involve having to make a patch of your own?
[03:02] <Buuntu> maco, so when a bug is filed and accepted, it goes to MOTU first?
[03:02] <nxvl> ajmitch: heh
[03:02] <maco> Buuntu: motu deal with stuff in universe & main
[03:03] <maco> but bug squad & bug control go after bugs first
[03:03] <maco> they triage, set importance, etc. ...get the bug into a state where a developer can start writing a patch
[03:04] <micahg> here's the process before it gets to MOTU: https://wiki.ubuntu.com/Bugs/HowToTriage/Charts
[03:04] <maco> micahg: i figured checking that a patch applies, and if it does creating a debdiff would be an easy thing to start with
[03:04] <dtchen> nxvl: much needed respite, work commitments, etc.
[03:04] <Buuntu> maco, ok so first things first.  Where can I find the packages with bugs
[03:04] <Buuntu> micahg, yeah I've read that I believe
[03:05] <micahg> maco: makes sense
[03:05] <maco> Buuntu: finding packages *without* bugs would be harder
[03:05] <maco> Buuntu: almost every bug in bugs.launchpad.net/ubuntu/+bugs is attached to a package
[03:05] <RoAkSoAx> maco, btw... does pkern want to change the localization of gobby source to en_US instead of en_UK?
[03:05] <ajmitch> having bugs which are useful to work on is another matter - the problem described doesn't always have an obvious solution
[03:06] <Buuntu> maco, click on the ones that "Need-packaging"?
[03:06] <ajmitch> that's why the bugsquad goes through & tries to get more info on them
[03:06] <micahg> well, about 97.5%
[03:06] <micahg> but we have 80k+ bugs now
[03:06] <nxvl> dtchen: oh yeah, working sucks
[03:06] <maco> Buuntu: if you want to package from scratch, sure...but doing an "advanced search" for bugs with patches will be easiest to start, i think
[03:06] <ajmitch> micahg: about a thousand bugs each to squash then? :)
[03:07] <maco> RoAkSoAx: gobby source is en_UK by default. ubuntu has no en_US translation team and expects source to be en_US and then we have en_UK langpacks
[03:07] <micahg> ajmitch: with 400 new ones a day :)
[03:07] <ajmitch> we'll give the new bugs to the newest MOTU then
[03:07] <maco> RoAkSoAx: so that means for en_US users to see en_US text, the source needs to be changed to be en_US and an en_UK.po has to be added
[03:07] <nxvl> well, en_US isn't the main language after all
[03:07] <nxvl> :P
[03:07] <RoAkSoAx> maco, yes I saw the bug report, but what I mean is that if you've contacted upstream and ask him to change to en_US?
[03:08] <micahg> ajmitch: actually about half are still new, so they're pre-MOTU
[03:08] <ajmitch> micahg: I was wrong about the number of people in ~ubuntu-dev, LP lists 144 people
[03:08] <Buuntu> maco, bugs with patches, how do I find those?
[03:08] <micahg> except for the 2k needs-packaging bugs
[03:08] <maco> RoAkSoAx: oh, i have not talked to upstream. dpm said that too. im kinda expecting "but en_UK is *REAL* english" as a response. also, that version of gobby is no longer being developed
[03:08] <maco> Buuntu: click advanced search
[03:09] <Buuntu> maco, I'm there
[03:09] <ajmitch> maco: I could argue that en_NZ is real english as well :P
[03:09] <nxvl> Buuntu: http://daniel.holba.ch/harvest/
[03:09] <nxvl> maco: harvest is easier
[03:09] <maco> nxvl: ok
[03:09] <Buuntu> nxvl, are you daniel holba?!
[03:09] <maco> hahah no
[03:10] <maco> daniel is dholbach
[03:10] <ajmitch> no, he doesn't give enough hugs to be dholbach
[03:10] <maco> he'll not be online for 5 more hours or so
[03:10] <Buuntu> lol ok
[03:10] <RoAkSoAx> maco, but cuz I was about to merge the new gobby version in squeeze, but I want to wait to see if upstream changes the default localization... I'll try to convince him too though. It should not be that hard as dpm said
[03:10] <nxvl> Buuntu: hell no!
[03:10] <Buuntu> nxvl, hahaha
[03:10] <maco> RoAkSoAx: the patch i did wasnt for new gobby, just the old unmaintained one
[03:10] <nxvl> maco: daniel? 3 maybe 4 more hours
[03:10] <maco> RoAkSoAx: im not sure how to approach this
[03:11] <maco> nxvl: he gets on when its 3am my time
[03:11] <maco> i know cuz i fell asleep a half hour before he got online this morning :)
[03:11] <ajmitch> heh
[03:11] <nxvl> maco: this time of the year he usually gets on when it's 2 am my time, IIRC
[03:12] <nxvl> i haven't need to wait for him in a while, maybe he changed his schedule
[03:12] <maco> maybe he's sleeping in since UDS?
[03:12] <nxvl> maco: you are on washington, right?
[03:12] <maco> nxvl: yes
[03:12] <nxvl> that reminds me, i need to sleep what i'm owing since UDS, i'm still SO tired
[03:12] <RoAkSoAx> maco, The new upstream release has the same *problem*. I would try to convince pkern to change the localization in the source as dpm recommended :)
[03:12] <nxvl> maco: then you are in my same tz... i think
[03:12] <ajmitch> nxvl: that's why there are weekends
[03:12] <nxvl> maco: 10:12ish?
[03:13] <nxvl> ajmitch: really? aren't they for drinking and partying?
[03:13] <nxvl> :P
[03:13] <maco> RoAkSoAx: is pkern upstream?
[03:13] <maco> nxvl: yes
[03:13] <ajmitch> nxvl: I wouldn't know, I usually sleep through them ;)
[03:13] <RoAkSoAx> maco, yep
[03:14] <nxvl> ajmitch: life is short, sleeping is a waste of time
[03:14] <maco> fudge nuggets
[03:14] <nxvl> ajmitch: i can sleep when i'm dead
[03:14] <RoAkSoAx> nxvl, +1 to weekends for drinking and partying... :)
[03:14] <nxvl> just give me more mountain dews
[03:14] <nxvl> :D
[03:14] <maco> i think he dislikes me after that bug report now :(
[03:14] <nxvl> sadly there is no mtn dew in peru :(
[03:14] <ajmitch> maco: were you slightly flaming upstream in that bug report?
[03:14] <RoAkSoAx> maco, i'll ping him do about this too to find out if he is interested in doing so
[03:15] <maco> no
[03:15] <RoAkSoAx> nxvl, there is
[03:15] <RoAkSoAx> nxvl, go to Plaza Vea :P
[03:15] <maco> ajmitch: no, but i argued with him when he said i broke things. i blamed dpm, as i warned him i would
[03:15] <nxvl> RoAkSoAx: I DON"T WANT TO KNOW!!!
[03:15] <nxvl> to late
[03:15] <nxvl> :(
[03:15] <nxvl> now i will never sleep
[03:15] <maco> ajmitch: because i told dpm i dont do string changes for fear of breaking translations and that if i got in trouble for making the change the way he told me to, id blame him
[03:15] <Buuntu> so most people here went to the UDS?
[03:15] <ajmitch> hah
[03:15] <RoAkSoAx> nxvl, hahaha It's not that bad... it doesn't have any effect on me anyways :P
[03:16] <maco> Buuntu: i think just me and nxvl
[03:16] <ajmitch> Buuntu: a few did, most of us didn't go
[03:16] <maco> as far as who's talking right now
[03:16]  * ajmitch had other small things on, like work
[03:16] <maco> yeah i skipped school
[03:16] <Buuntu> maco, isn't it in California?
[03:16] <maco> it was in dallas
[03:16] <RoAkSoAx> maco, I see here that your upload was for lucid right? so I can drop the patch in the merge
[03:16] <maco> RoAkSoAx: yes
[03:17] <ajmitch> UDS is in a different place each time
[03:17] <maco> north america in fall and usually europe (once oz) in spring
[03:19] <ajmitch> I think wgrant is at uni
[03:19] <nxvl> maco: RoAkSoAx was on UDS aswell
[03:19] <maco> RoAkSoAx: did i meet you?
[03:19] <RoAkSoAx> yep :P
[03:19] <maco> ajmitch: yeah he's like 19, he should be in uni
[03:19] <RoAkSoAx> maco, nope :(
[03:19] <nxvl> heh
[03:19] <RoAkSoAx> maco: but I new who you were
[03:20]  * ajmitch hasn't been to UDS for a little while
[03:20] <nxvl> RoAkSoAx: knew
[03:20] <RoAkSoAx> s/new/knew
[03:20] <maco> RoAkSoAx: there were 20 women. couldnt have been that hard
[03:20] <nxvl> i still remember Prague when there was only ~5 womens
[03:20] <nxvl> glad to see the number is increasing
[03:21] <RoAkSoAx> maco, let's see... I was the one who cjwatson asked the name of in the Future of MOTU sessions  :)
[03:21] <maco> ah ok
[03:21] <ajmitch> how did that session go?
[03:21] <ajmitch> I haven't heard anything from it
[03:21] <maco> i PM'd him and asked "did you just ask 'what's your name, son?'"
[03:21] <maco> (no, it was "sorry?" not "son?")
[03:21] <maco> i think the conclusion was "lets keep the name motu, for hysterical raisins"
[03:21] <nxvl> cjwatson needs to come with subtitles </maco>
[03:22] <ajmitch> the hard part about UDS is trying to track down all the little bits of information that was discussed there
[03:22] <maco> nxvl: not just him
[03:22] <maco> nxvl: but the others need translation subtitles
[03:22] <maco> or i just need to learn a few more languages :)
[03:22] <ajmitch> since it's an effective dividing line between those that were there & know about it, and those who weren't
[03:23] <maco> ajmitch: we came up with a list of what the functions of motu are
[03:23] <maco> and talked about how the "train new devs" thing would be handled (each team should train the people interested in specializing with them, but if someone doesnt have a specialization yet... anyone should still be willing to help)
[03:24] <nxvl> maco: well, i can understan the main ones
[03:24] <nxvl> :D
[03:24] <ajmitch> maco: I'm mostly ranting about the communication in general, I don't like getting surprises a few months down the track & being told "but it was discussed at UDS!" :)
[03:24] <maco> ajmitch: we had a session on that too!
[03:24]  * wgrant has been at uni for a couple of years now.
[03:24] <wgrant> Although I am young.
[03:24] <nxvl> wgrant: how old are you?
[03:24] <wgrant> nxvl: 18 and a little bit.
[03:24] <nxvl> wgrant: around 18?
[03:24] <ajmitch> wgrant: you make the rest of us feel old
[03:24] <nxvl> yeah, that's what i remembered
[03:24] <maco> he made me feel old!
[03:24] <micahg> wow
[03:24] <StevenK> Haha
[03:25] <nxvl> maco: shhh
[03:25] <StevenK> maco: But you're not old!
[03:25] <nxvl> maco: you are young
[03:25]  * micahg wishes Ubuntu was around when I was younger
[03:25] <maco> yeah i know
[03:25] <EzraR> \
[03:25] <ajmitch> don't worry, I know debian developers who are around 70+ :)
[03:26]  * nxvl remembers a comment of ScottK a couple of years ago saying i made him feel too old when i posted about why bugs are called bugs
[03:26] <StevenK> ajmitch: CosmicRay doesn't count :-P
[03:26] <ajmitch> StevenK: nah, this is a local, phil charles
[03:26] <ajmitch> he used to be active in the debian CD team
[03:27]  * RoAkSoAx has to many emails to read after the UDS :(
[03:27] <nxvl> RoAkSoAx: try to check my e-mail after a weekend
[03:27] <nxvl> RoAkSoAx: you will get CRAZY
[03:28] <RoAkSoAx> nxvl, i have 70 unread emails in average in 4 of my accounts :S... and I already got rid of the spam :S
[03:28] <ajmitch> only 70?
[03:28] <lfaraone> maco: hm?
[03:28] <ajmitch> you're not subscribed to debian-devel then, are you?
[03:28]  * lfaraone waves at Buuntu 
[03:28] <nxvl> RoAkSoAx: plz! that's less of what i get in a morning
[03:29] <RoAkSoAx> ajmitch, i mean 70 on each of my 4 accounts
[03:29]  * Buuntu waves back
[03:29] <ajmitch> or the favourite - ubuntu-bugs@l.u.c
[03:29]  * wgrant doesn't count debian-devel in his mail totals.
[03:29] <wgrant> I have > 10000 unread there now.
[03:29] <ajmitch> d-d is a list to be read selectively
[03:29] <StevenK> wgrant: That's a sign you should probably unsubscribe
[03:29] <nxvl> wgrant: heh, yeah, try to subscribe to go-nuts
[03:29] <RoAkSoAx> mine are just emails that I need to reply :( or to care about :(
[03:29] <wgrant> StevenK: But there are amusing/useful threads on there sometimes.
[03:30] <ajmitch> nxvl: sounds interesting
[03:30] <StevenK> wgrant: And the last time that happened was what, 2002?
[03:30] <ajmitch> StevenK: lies, there are interesting threads on there all the time
[03:30] <nxvl> StevenK: well, it depends, if you just read and get amused on how they can fight for nonsenses sometimes, it's recent
[03:31] <wgrant> nxvl: Precisely.
[03:31] <ajmitch> like the recent discussions on the 3.0 (quilt) source format
[03:31] <wgrant> Right.
[03:31] <wgrant> And the GR threat.
[03:31] <StevenK> Meh, I have -private for that
[03:31] <jpds> Hmm.
[03:31] <ajmitch> -private is boring
[03:32] <ajmitch> not that we'll disclose any of the contents :)
[03:32] <StevenK> Heh
[03:32] <StevenK> Except for the Edward Betts incident
[03:34] <ajmitch> can't say I recall that
[03:35] <StevenK> ajmitch: "I drank heavily, passed out, and I woke up my laptop was covered in vomit, so I'm on VAC"
[03:35] <ajmitch> haha
[03:39] <ajmitch> StevenK: coming over for LCA in jan?
[03:41]  * wgrant will be in Wellington the week before, so will probably attend.
[03:41] <jpds> wgrant: Be sure to take boots.
[03:41] <ajmitch> wgrant: great
[03:41] <StevenK> ajmitch: Yup
[03:41] <StevenK> Speaking of, I need to book flights
[03:44]  * ajmitch was just registering this morning & looking for flights
[03:44] <ajmitch> probably only slightly cheaper for me to fly there than for you
[03:46] <StevenK> Really?
[03:46] <ajmitch> well, about $260 NZD for me, return flights
[03:47] <ajmitch> not sure about right now, but you can get to australia for a similar price sometimes
[05:30] <EzraR> why would the lucid build servers have an older version of xulrunner than karmic?
[05:30] <EzraR> xulrunner-dev
[05:35] <StevenK> EzraR: Er, looks okay to me from rmadison
[05:38] <EzraR> what version?
[05:38] <micahg> EzraR: xulrunner-dev is provided by xul-1.9.1
[05:38] <dtchen> looks fine:
[05:38] <dtchen> xulrunner-dev | 1.9.1.5+nobinonly-0ubuntu0.9.10.1 | karmic-security | amd64, i386
[05:38] <dtchen> xulrunner-dev | 1.9.1.5+nobinonly-0ubuntu0.9.10.1 | karmic-updates | amd64, i386
[05:39] <dtchen> xulrunner-dev | 1.9.1.5+nobinonly-0ubuntu1 |         lucid | amd64, i386
[05:39] <EzraR> this package just failed...it was installing stuff into xulrunner-devel-1.9.1.3
[05:40] <EzraR> on my pbuilder it installes into xulrunner-devel-1.9.1.5
[05:41] <dtchen> does the environment have an active deb line for karmic-updates?
[05:42] <EzraR> hmm
[05:42] <EzraR> not sure what you mean
[05:42] <wgrant> Where's the build log?
[05:43] <EzraR> https://launchpad.net/ubuntu/+source/pcmanx-gtk2/0.3.9-2ubuntu1/+build/1364833/+files/buildlog_ubuntu-lucid-armel.pcmanx-gtk2_0.3.9-2ubuntu1_FAILEDTOBUILD.txt.gz
[05:43] <dtchen> err, armel
[05:43] <wgrant> armel
[05:43] <wgrant> Yes.
[05:44] <EzraR> ?
[05:44] <micahg> EzraR: you're not going to want to do that
[05:44] <micahg> I mean explicitely stating the version in the path
[05:45] <wgrant> Horrible applications (like xulrunner) are likely to FTBFS on obscure architectures (like armel), so old versions might be present.
[05:45] <EzraR> that was how it was before the murge i just pointed it to the right place
[05:46] <EzraR> i mean i could start a trend and use a symlink
[05:46] <micahg> EzraR: I suggest you talk to asac in the morning
[05:47] <StevenK> Or you could fix xulrunner to built on armel
[05:47] <EzraR> heh
[05:47] <wgrant> Preferably both.
[05:49] <lifeless> StevenK: so, bacon explosion. Are you in?
[05:49] <wgrant> lifeless: NO.
[05:49] <StevenK> lifeless: I'm happy to try it, but they scare me
[05:49] <StevenK> lifeless: And where has Chewy gone? :-(
[05:50] <fabrice_sp> micahg, you're right about the version. IT can easily be fixed with an * :-/
[05:51] <fabrice_sp> I should have paid more attention before sponsoring (only thought about merges, and not xulrunner version changes)
[05:53] <lifeless> wgrant: whyever not?
[05:53] <lifeless> StevenK: been busy with Life.
[05:53] <wgrant> lifeless: ETOOMUCHBACON
[05:54] <lifeless> wgrant: but but but
[05:54] <StevenK> wgrant: No such thing
[06:04] <EzraR> micahg: who is asac?
[06:05] <micahg> EzraR: head of the mozilla team (maintainer of xulrunner)
[06:05] <lifeless> alexander sach
[06:05] <EzraR> ahh heh..
[06:06] <EzraR> yeah i'll have a chat with him
[06:07] <fabrice_sp> EzraR, I've just uploaded a new version with * instead of 1.9.1.5 in install and rules file.
[06:07] <fabrice_sp> it should be on armel now
[06:08] <fabrice_sp> anyway, speak with asac about the better way to do that
[06:08] <EzraR> fabrice_sp: thnx
[06:09] <EzraR> should i send the idea to debian too? i always feel like a pest contacting debian maintainers
[06:10] <fabrice_sp> EzraR, i think so: sid has 1.9.1.5 also, so they should encounter the same problem
[06:12] <micahg> EzraR: asac is also a DD I think
[06:13] <EzraR> they hardcode the path, is why i say it
[06:13] <micahg> EzraR: debian?
[06:13] <EzraR> ok ill talk to him about it
[06:13] <EzraR> yeah
[06:15] <EzraR> they use the path xulrunner-devel-1.9.1
[06:15] <EzraR> maybe its a symlink?
[06:16]  * EzraR shrugs
[06:16] <EzraR> ill talk to him about it
[06:16] <EzraR> thanks guys
[06:55] <mac_v> hi.. anyone who is involved with the vuze package around? vuze also faces this problem > Bug #403135 , but the bug has somewhat become a master bug... should i file a separate bug for vuze or just add it as an also affects?
[07:14] <LucidFox> Hmm.
[07:14] <LucidFox> How do I update a package in bzr to a new upstream version?
[07:16] <lifeless> bzr merge-upstream path-to-tarball [optional-path-to-branch-of-new-upstream]
[07:22] <LucidFox> bzr: ERROR: unknown command "merge-upstream"
[07:23] <lifeless> LucidFox: you'll want bzr-builddeb installed, and also see James Westby's mail to ubuntu-devel last week or so
[07:39] <LucidFox> bzr: ERROR: Unable to find the tag for the previous upstream version, 0.12.5, in the branch: upstream-0.12.5
[07:43] <siretart`> LucidFox: is that a branch you created yourself or from the package importer?
[07:43] <lifeless> LucidFox: sounds like this isn't  a bzr packaging branch from the importer
[07:43] <LucidFox> What's the package importer?
[07:45] <siretart`> LucidFox: bzr builddeb provides a command 'mark-uploaded' that tags the current revision properly. the branches on launchpad are using james_w bzr-builddeb commands on every import
[07:45] <siretart`> LucidFox: in order to fix your private branch, go back in history and use that command to add your tags.
[07:49] <lifeless> siretart`: upstream tags are different
[07:49] <lifeless> siretart`: they have the pristine-tar data added
[07:49] <lifeless> [on the commit]
[07:50] <siretart`> lifeless: oh, mark-uploaded doesn't add these? it should!
[07:50] <lifeless> siretart`: merge-upstream does
[07:50] <siretart`> hm. ok
[07:50] <lifeless> the error about missing tag is filed as a bug:)
[07:50] <siretart`> k
[07:51] <LucidFox> I can just re-checkout the package "properly", but I don't know where the documentation is.
[07:52]  * ajmitch still finds it a little hard to follow, but hasn't tried any merges yet
[07:52] <ajmitch> is there a wiki page with the current info about the workflow?
[07:53]  * ajmitch guesses wiki.u.c/DistributedDevelopment is it
[07:56] <LucidFox> It's a specification page...
[07:57] <ajmitch> with a documentation link
[08:01] <dholbach> good morning
[08:01]  * LucidFox waves
[08:01] <LucidFox> By the documentation link, do you mean https://wiki.ubuntu.com/BzrMaintainerHowto ?
[08:02] <dholbach> hi LucidFox
[08:02] <ajmitch> no, https://wiki.ubuntu.com/DistributedDevelopment/Documentation
[08:02] <ajmitch> hello dholbach
[08:04] <dholbach> hi ajmitch
[08:07] <ajmitch> dholbach: how are you today?
[08:08] <dholbach> ajmitch: good good - how about you?
[08:09] <ajmitch> good thanks :)
[09:11] <mac_v> hi.. why is the winbind package not installed by default?
[09:11] <mac_v> oops wrong channel!
[10:48] <LucidFox> "These applications have been authorized to access Launchpad on your behalf. If you revoke an authorization, that application will not be allowed to do anything in Launchpad on your behalf."
[10:48] <LucidFox> That's it. Launchpad is the new Facebook. :)
[10:49] <tsimpson> as long as I don't get those "oh, please be my friend" messages, I don't mind
[10:49] <Flannel> tsimpson: Will you please be my friend?
[10:50] <tsimpson> I'll consider it, if you pay me ;)
[11:03] <pmcenery> Hi. Does anyone know how to get a PPA deleted from launchpad? I have added one that I would like to remove? Is it possible?
[11:03] <pmcenery> I.e. one of my own PPAs
[11:04] <noodles775> pmcenery: please ask on #launchpad - but yes, you can file a question requesting it to be deleted (if you've never published to it, otherwise just disabled currently)
[11:04] <pmcenery> noodles775: thanks
[11:39] <akheron> any MOTUs around? http://revu.ubuntuwire.com/p/jansson
[11:50] <LucidFox> akheron> Looking
[11:50] <akheron> thanks
[11:58] <LucidFox> akheron> Commented
[11:59] <akheron> thanks, good points
[12:02] <ScottK> nxvl: Did you get Courier fixed?
[12:30] <LucidFox> So many of the common mistakes on REVU are caused by users leaving dh_make defaults.
[12:31] <akheron> LucidFox: what defaults?
[12:31] <akheron> invoking wrong dh_ programs?
[12:31] <LucidFox> For example, commented out dh_* commands in debian/rules. Or debian/dirs.
[12:31] <akheron> ah, ok
[12:32] <LucidFox> debian/dirs is only needed in very specific cases, it should really be debian/dirs.ex, I think.
[12:34] <tsimpson> you don't include the .ex files, those are examples
[12:35] <LucidFox> I know.
[12:37] <tsimpson> LucidFox: that wasn't directed to you specifically :)
[12:42] <LucidFox> "Choice of Law: This license is governed by the Laws of Pennsylvania, USA."
[12:42] <LucidFox> Huh? How does it work if the user doesn't live there?
[12:42] <wgrant> That's not a terribly rare sort of clause.
[12:44] <LucidFox> So even if I use the software in Russia, its terms of use will still be governed by US law?
[12:51] <LucidFox> http://revu.ubuntuwire.com/p/ubuntu-tweak <-- Software like this bugs me. It's like Automatix, "solving" Ubuntu problems the Windows way - an approach that rarely works.
[12:56] <tsimpson> I doubt it'll make it into the archives
[12:58] <nxvl> ScottK: not still, i'm trying to figure out what's going on
[13:00] <LucidFox> tsimpson> Well, if it technically satisfies the packaging rules, who will have the guts to refuse it just for ideological reasons? :)
[13:01] <tsimpson> harmful packages will not be accepted
[13:01] <LucidFox> On a related note... I've finally moved remaining jaunty packages in REVU to "Needs Work". Only karmic and lucid remaining now.
[13:01] <tsimpson> there was a time that automatix was on revu
[13:02] <LucidFox> And it wasn't accepted because it was "harmful"?
[13:02] <tsimpson> it was a badly written software, so it wasn't ever going to be accepted
[13:02] <tsimpson> and the security team would definitely block it
[13:03] <tsimpson> it was full of "sudo apt-get -y --force-yes ..."
[13:04] <LucidFox> O_O
[13:07] <ScottK> There's no rule that says we have to accept crap.
[13:07] <ScottK> Even if it's packaged correctly.
[13:29] <ghostcube> guys anyone knows the webpage for the nvidia driver packages from ubuntu official
[13:29] <ghostcube> not ppa
[13:29] <ghostcube> its not offcial released
[13:30] <slytherin> ghostcube: What do you mean by webpage?
[13:30] <ghostcube> its an page where you can download the deb packages and install them by dpkg -i
[13:30] <ghostcube> and the heck i dont remember where to search for
[13:31] <ghostcube> i have them on my other machne in bookmarks
[13:31] <ghostcube> :D
[13:31] <ghostcube> its not an repo
[13:31] <akheron> LucidFox: btw, assuming that my package gets to universe some day, is it OK to have the packaging maintained in a GitHub repo?
[13:32] <slytherin> ghostcube: did you search http://packages.ubuntu.com
[13:32] <ghostcube> i found them as i searched for the latest kernels from ubuntu kernel team
[13:32] <ghostcube> yeah
[13:32] <ghostcube> slytherin: if iam at home later i tell you ;)
[13:33] <LucidFox> akheron> I don't know, never used a VCS for packages I maintain by myself.
[13:34] <ScottK> akheron: Once it's in Universe, it'll be team maintained and so you're welcome to maintain packaging in github, but it's unlikely others would push changes there.
[13:35] <akheron> ScottK: ok, I just thought about the Vcs-Browser and Vcs-Git control fields which I have there
[13:36] <ScottK> akheron: I think it's not a problem to have them, but as I said, it's not likely that others will go to github if they change your package.
[13:37] <ScottK> Of course if you keep it up to date and in good shape yourself, that may not come up.
[13:37] <ScottK> akheron: I'd suggest that if you're that interested in the package you should also look at getting it into Debian where you can be the dedicated maintainer.
[13:38] <akheron> I've been thinking about that, but I think I'm more interested in the software itself than in maintaining the package
[13:39] <akheron> getting it to debian too would be great though
[13:41] <ScottK> If you are interested in the software, getting it into Debian helps get it in front of a lot more users (Debian has other downstreams than Ubuntu).
[13:41] <slytherin> akheron: Vcs-* fields are used if the packaging is maintained in a VCS. This usually happends for team maintained packages in Debian.
[13:41] <ScottK> See mentors.debian.net.
[13:44] <akheron> ScottK: I'll have a look, thanks
[13:55] <pmatulis> is pdebuild the way to go if i want to sign a build in order to make a PPA?
[14:05] <jack_> sudo pbuilder create --debootstrapopts --arch --debootstrapopts amd64
[14:06] <jack_> is that the way to build a 64bits chroot on 32bit to build packages for amd64?
[14:07] <jack_> I find info about how to get a 32bit chroot on amd64 but not vice versa
[14:07] <jack_> is that for a reason?
[14:07] <ScottK> AFAIK you can't build 64 bit binaries with a 32 bit system.
[14:08] <jack_> ScottK, mmh
[14:09] <jack_> ScottK, are u sure?
[14:09] <jack_> maybe someone can confirm this?
[14:11] <Hobbsee> fairly sure he's right
[14:12] <Hobbsee> (Scottk, that is)
[14:12] <Laney> yeah, you can't do it like that
[14:12] <jack_> ok thanks
[14:13] <jack_> other ways?
[14:14] <geser> you need a 64bit kernel to run 64bit binaries (applies also to those run in a chroot)
[14:18] <Laney> I dunno if you can emulate it
[14:19] <soren> Well, if you run it in qemu, you can, but it's very, very slow.
[14:25] <slytherin> pmatulis: you can use any of the build tools available (pdebuild, pbuilder, sbuild etc). Signing is not dependent on build tool used.
[14:26] <pmatulis> slytherin: should i be using sudo to run pdebuild, i get errors otherwise.  then i get the error "Could not find a signing program (pgp or gpg)"
[14:27] <pmatulis> slytherin: i needed sudo to create my initial pbuilder (base.tgz)
[14:28] <Laney> to upload to a ppa you just need a signed source package
[14:30] <slytherin> pmatulis: gpg is not installed? What kind of setup are you using?
[14:30] <slytherin> pmatulis: You can also create a source package with dpkg-buildpackage. You do not need root access for that.
[14:31] <pmatulis> slytherin: yes, it's installed.  i'm using pbuilder and i would like to stick to as few tools as possible
[14:31] <pmatulis> slytherin: i would rather use pbuilder/pdebuild for everything
[15:01] <slytherin> ttx: any idea if the jasper compiler included in tomcat is the only jsp compiler available in repos?
[15:02] <ttx> slytherin: no idea. There should be one in jetty, I suppose
[15:03] <slytherin> ttx: ok. I will check
[15:10] <bddebian> Heya gang
[15:11] <xim_> im new to ubuntu dev, can software written in java be integrated into the ubuntu repos?
[15:12] <bddebian> No Java is Evil and therefore not allowed.. ;-P
[15:12] <dholbach> xim_: don't listen to bddebian
[15:12] <dholbach> xim_: there's a bunch of java applications in Ubuntu already
[15:12] <bddebian> hehe
[15:13] <bddebian> xim_: Just make sure it works with gcj and/or openjdk
[15:13] <xim_> ah ok thx
[15:14] <dholbach> and there's https://wiki.ubuntu.com/JavaTeam/KnowledgeBase
[15:14] <xim_> im about to start writing yet another alarmclock since none of the available ones do what I want, and id like to make it available so I wanted to ask before I got started on it if only native code was accepted
[15:15] <xim_> but schweet
[15:15] <pmcenery> Is there a list of packages that people would like to see packaged anywhere? I'm looking to get some packaging practice...
[15:15] <bddebian> pmcenery: Launchpad should have request for packaging bugs or you can check Debian's WNPP for RFP
[15:16] <dholbach> pmcenery: personally I'd recommend starting work on existing packages
[15:16] <slytherin> bddebian: gcj is old. Nobody uses it these days. :-)
[15:16] <dholbach> https://wiki.ubuntu.com/MOTU/GettingStarted has links to all the important documentation
[15:16] <bddebian> xim_: If you package your own, try to make sure you don't include any binary jar files, it should be able to be built from the existing java stuff in Debian/Ubuntu
[15:16] <dholbach> xim_: meet slytherin
[15:16] <dholbach> slytherin: meet xim_ :)
[15:16] <bddebian> slytherin: Well I was trying to be "nice" :)
[15:17] <sebner> heya dholbach bddebian :)
[15:18] <dholbach> hi sebner
[15:18] <bddebian> Hi sebner
[15:18] <xim_> gotcha
[15:19] <slytherin> bddebian: Even Debian switched to openjdk as default. :-)
[15:21] <slytherin> xim_: I would suggest work on existing packages. Many of them need fixing/updating. But I leave the decision to you.
[15:22] <bddebian> slytherin: I know I've been "helping" the debian-java team some :)
[15:22] <slytherin> I know. Was just teasing you. :-P
[15:25] <bddebian> slytherin: Even though I forget to credit people some times.. :(  :)
[15:25] <slytherin> Ok. We are past that already. I told you it was not a bug issue.
[15:25] <slytherin> s/bug/big
[16:10] <MTecknology> How do translations work as far as in the package? Is there any magic voodoo that goes on so if somebody pulls the package from ppa lp will give them the package with the translations in it?
[16:16] <dpm> MTecknology, could you please specify what you are trying to do, so someone can try to help you? In general, PPA packages have got no integration with LP, as far as translations go.
[16:16] <MTecknology> dpm: I don't understand how translations are used
[16:25] <jpds> MTecknology: Translation files in packages are strip from them on build and put into language packs, IIRC.
[16:25] <jpds> stripped*
[16:25] <MTecknology> oh
[16:26] <dpm> MTecknology, that's quite a general question :) Are you working on a particular package? In general, for Ubuntu packages inside the package (generally those from upstream) are imported into Launchpad. Ubuntu translators complete them using the web UI and those are then exported in special packages called language packs
[16:26] <ScottK> jpds: But only for Main and this is #ubuntu-motu
[16:26] <MTecknology> that makes more sense; thanks
[16:26] <MTecknology> I just didn't have any understanding of it at all
[16:27] <jpds> ScottK: For now....
[16:27] <dpm> MTecknology, but have also in mind what ScottK is mentioning. For the packages in universe translations are left in the package as they are
[17:43] <pmatulis> is there an easy way to discover what release & arch the current pbuilder is using?
[17:44] <AlanBell> hi, can someone point me in the direction of some information about how the partner repo is maintained?
[17:45] <ScottK> AlanBell: You need to ask Canonical about that.  It's nothing to do with the Ubuntu community.
[17:45] <AlanBell> thanks ScottK, do you know any contact point for it?
[17:45] <AlanBell> there are not many packages in it for Karmic
[17:45] <ScottK> Generally this is the case.
[17:46] <AlanBell> what is generally the case?
[17:46] <ScottK> Not a lot of packages.
[17:46] <AlanBell> ah, indeed, there are not lots
[17:46] <ScottK> Also Partner usually starts to get packages at release time.
[17:47] <AlanBell> but there were many more in the Jaunty repo
[17:47] <AlanBell> I asked about it a few times during the karmic beta and was told to wait for the release
[17:47] <AlanBell> but only symphony got added
[17:48] <AlanBell> http://archive.canonical.com/ubuntu/dists/jaunty/partner/binary-i386/Packages vs http://archive.canonical.com/ubuntu/dists/karmic/partner/binary-i386/Packages
[17:48] <AlanBell> the one I want is alfresco-community
[17:48] <ScottK> My generaly understanding is that being in the Partner repo involves a contractual relationship between Canonical and the entity wanting the package there.
[17:48] <ScottK> generaly/gneral
[17:49] <ScottK> Urgh.  Just imagine all my spelling was perfect.
[17:49] <AlanBell> so I guess someone stopped paying the bills then
[17:50] <ScottK> That'd be my guess.  Or negotiations are still in progress.
[17:50] <ScottK> No way to know.
[17:51] <AlanBell> ok, thanks for your help, I will go digging elsewhere . . .
[17:57] <waver_> I have a small problem, my postinst and prerm is no more working after installing/removing the package
[17:57] <waver_> Old one: http://pastebin.com/d11a9f00b
[17:57] <waver_> New one: http://pastebin.com/d6f42ca6e
[17:58] <waver_> any idea ?
[18:34] <timmie> hello fellow packagers
[18:34] <timmie> I need some advice on changing an already uploaded package
[18:35] <timmie> anyone with time to help?
[18:36] <av`> timmie, go ahead :)
[18:38] <timmie> Thanks.
[18:38] <timmie> A package I created using the Ubuntu guide for Python.
[18:38] <timmie> After a successful upload, the build did not succeed
[18:39] <timmie> then I modified the debian/control file
[18:39] <timmie> run dput again.
[18:39] <timmie> and the package got rejected.
[18:39] <timmie> what do I need to do to replace the one in the PPA / REVU?
[18:40] <av`> timmie, wait... PPA is not an alternative for REVU
[18:40] <timmie> know. I first send it to a PPA. Then to REVU.
[18:41] <av`> and anyway you are using a wrong versioning
[18:41] <av`> did you bump the version after the change on control?
[18:41] <timmie> But let's get the correct package on the PPA first and then see what we do with REVU.
[18:42] <av`> do you know that when you upload an X package version 1.0-1 into PPA, the next X package upload should have the version bumped?
[18:42] <timmie> > did you bump the version after the change on control?
[18:42] <timmie> What do you mean? I edited the control and send the file after running debuild
[18:42] <av`> that's wrong
[18:42] <av`> you need to add a new changelog entry for that
[18:42] <timmie> and increment the version number?
[18:43] <av`> yes exactly
[18:43] <av`> the debian revision number not the upstream one
[18:43] <av`> pay attention to this detail
[18:44] <timmie> I see that the part "making changes to your  package" needs more attention in the guide.
[18:44] <timmie> So whenever I edit control or rules I would need to change the chnagelog file as well?
[18:45] <av`> you need to document what you change
[18:45] <av`> otherwise no one will ever know why you changed something
[18:46] <av`> this happens when you have uploaded a certain revision already
[18:46] <timmie> could you give me an example of a debian version number ?
[18:46] <av`> if not you should have a changelog entry available to modify already
[18:46] <av`> let's say I'm packaging a foo package upstream version 1.0
[18:46] <timmie> yes.
[18:46] <av`> the first revision will be 1.0-1
[18:46] <av`> where 1 is the debian revision and 1.0 the upstream one
[18:47] <av`> you do some changes, you make up a new changelog entry and you'll have 1.0-2
[18:47] <av`> :)
[18:47] <av`> I don't go further explaining you other strange versioning stuff since I see you are learning
[18:48] <timmie> would I need to change the version of the source tarball as well?
[18:48] <av`> anyway please use something like ~ppa1 when you upload to PPA
[18:48] <av`> or something like that
[18:48] <av`> no
[18:48] <av`> the tarball has the upstream versioning only in it
[18:48] <timmie> so I now have
[18:48] <timmie> spyder (1.0.1-1) karmic; urgency=l
[18:48] <av`> foo_1.0.orig.tar.gz for istance
[18:48] <timmie> I should change into
[18:48] <timmie> spyder (1.0.1-2) karmic; urgency=l
[18:48] <timmie> correct?
[18:48] <av`> then will be 1.0.1-2
[18:48] <av`> yes
[18:49] <av`> add ~ppa1
[18:49] <av`> or ~timmie1
[18:49] <av`> :)
[18:49] <av`> so it will be 1.0.1-2~ppa1 or 1.0.1-2~timmie1 :)
[18:50] <av`> that's nice to do, if not people will have problems updating packages that come from the archive
[18:50] <timmie> nice, will try that.
[18:50] <timmie> could you also help me with lintian?
[18:51] <av`> yes
[18:51] <timmie> here is a buildlog:
[18:51] <timmie> http://revu.ubuntuwire.com/revu1-incoming/spyder-0911251542/lintian
[18:51] <timmie> What had happened there?
[18:52] <av`> watch file is missing, but that's your choice to have it or not
[18:52] <av`> standards are outdated, not really a problem since it will go into a PPA
[18:52] <av`> you miss the python dep, this is different if your package uses pycentral or pysupport
[18:54] <timmie> > standards are outdated, not really a problem since it will go into a PPA
[18:54] <timmie> at the end I wouldlike to send it to REVU and not to a PPA.
[18:54] <timmie> therefore, how do I set the correct standards?
[18:55] <av`> latest standards available are 3.8.3
[18:55] <av`> so just update them
[19:11] <timmie> I don't understand this:
[20:30] <fabrice_sp> jdong, sru for Bug #458171 ?
[20:39] <fabrice_sp> bigon, ping
[20:49] <jdong> fabrice_sp: you're acked.
[20:50] <fabrice_sp> thanks jdong :-)
[20:50] <jdong> sure thing
[23:21] <\sh> micahg, zend-framework 1.9.6 is reaching lucid just now ... you can start to do some test backports for karmic, jaunty, intrepid and hardy :)
[23:23] <micahg> \sh: it'll probably be tomorrow sometime before I get to it, is that ok?
[23:23] <micahg> probably early morning
[23:26] <micahg> actually, maybe I'll do karmic now
[23:31] <micahg> is there a backporting script?
[23:43] <\sh> micahg, nope...normally I'm doing all those manually...
[23:46] <micahg> ok
[23:48] <micahg> \sh: just dch -e and modify the version and target?
[23:52] <\sh> micahg, right :)
[23:53] <micahg> \sh: ok, looks like it's still making it's way into lucid, I'll check back a little later
[23:54] <\sh> micahg, no rush...
[23:54]  * \sh goes back to his rollout of new software