[03:15] <EpikVision> is anyone available?
[03:19]  * hyperair is semi-available
[03:19] <hyperair> oh he disapeared.
[03:39] <psusi> I'm married and have a kid... definitely not available.
[03:40] <EpikVision> ok
[07:40] <bobweaver> Hello there I am haveig trouble when building it is my control file it is here http://paste.ubuntu.com/981264/  just wondering what I am doing wrong thanks for your time. Oh and the email address are in the control file I just took out for the paste. error is here http://paste.ubuntu.com/981275/
[07:41] <bobweaver> thanks again
[07:43] <geser> bobweaver: add a 2nd whitespace at the start of lines 2-7
[07:43] <bobweaver> thanks
[07:44] <bobweaver> I always get that mixed up if it is one or two spaces
[07:44] <bobweaver> thanks again
[07:48] <_ruben> that file could use some spellchecking and whitespace fixing :)
[07:59] <bobweaver> I am on it thanks _ruben
[09:04] <nigelb> Can someone grant nomination on this bug? https://bugs.launchpad.net/ubuntu/+source/sphinx/+bug/997891
[09:05] <nigelb> geser: you around? :)
[09:11] <geser> nigelb: sort of, why?
[09:11] <nigelb> geser: I was wondering if you had the magical powers to ack the nomination on that bug.
[09:11] <geser> should have as a MOTU
[09:14] <nigelb> geser: Can you? :)
[09:14] <geser> nigelb: sorry, I can't. It's either because it's in main or some other team membership is needed
[09:14] <nigelb> AH.
[09:15] <nigelb> I wonder if it needs release team.
[09:17] <elky> https://launchpad.net/sphinx/trunk suggests it wants stub
[10:12] <iulian> nigelb, elky: Done.
[10:13] <elky> iulian, woot thanks
[13:15] <CareBear\> hm
[15:56] <highvoltage> hmm, where's the motu crowd, I'd thought you'd be in tha archive-reorg room by now :)
[15:58] <highvoltage> (ah here you are)
[15:59] <broder> i got really good at timing how long the drive would take
[15:59] <broder> been inching my alarm later and later all week
[15:59]  * ajmitch made it in time...
[16:00] <ajmitch> starting to feel the effects of too many sleepless nights though :)
[16:24]  * ScottK thinks being at a local UDS would be rough.
[16:24] <broder> not getting a room at the hotel was a mistake, i think :)
[16:25] <ajmitch> broder: at least you get to sleep in your own bed
[16:25] <broder> yes, although i don't get to sleep in it for nearly long enough
[16:44] <EpikVision> can someone help me in the package guide?
[16:51] <broder> Laney: ping (one sec...)
[16:52] <broder> if you're testing manual backporting, let me give you my patch to include an lp closer
[16:52] <broder> (even though it will be ingored by lp, i feel moderately strongly hat we should have it there to capture history)
[16:52] <Laney> push it to udt?
[16:53] <Laney> also it looks like it doesn't pass -v
[16:54] <broder> will land momentarily
[16:54] <broder> i think that's mostly deliberate - we don't want to, e.g., close sru tasks
[16:54] <Laney> would it?
[16:54] <broder> well, if there was a closer in the history between current archive version and backported version
[16:55] <broder> and an sru task on that bug
[16:56] <vibhav> EpikVision: What do you want help with?
[16:56] <tumbleweed> EpikVision: no need to ask to ask. Please just ask your question
[16:56] <EpikVision> hahah
[16:56] <EpikVision> ok
[16:56] <broder> Laney: pushed
[16:56] <EpikVision> http://developer.ubuntu.com/packaging/html/fixing-a-bug.html
[16:57] <EpikVision> I'm going through "Work on a fix"
[16:57] <broder> Laney: hmm. actually, the real reason to include the lp closer is for the sake of AA review
[16:57] <EpikVision> vibhav: I've done all the steps to this point
[16:57] <vibhav> EpikVision: What are you working on?
[16:57] <EpikVision> Fixing a bug.
[16:58] <EpikVision> from the packaging guide
[16:58] <vibhav> I mean, which package
[16:59] <EpikVision> tomboy
[16:59] <vibhav> EpikVision: Whcih bug?
[17:01] <EpikVision> vibhav: I don't think the guide goes through any bug.
[17:01] <EpikVision> but i was just following the steps, up to the section "Work on a fix"
[17:01] <EpikVision> I don't get why $ patch -p1 < ../bugfix.patch
[17:01] <EpikVision> is giving me an error.
[17:02] <vibhav> EpikVision: You need to fing a bug to work on
[17:02] <EpikVision> alright then.
[17:02] <EpikVision> vibhav: I'm totally new to the scene.
[17:02] <EpikVision> and the package guide is confusing me.
[17:02] <vibhav> IF no bug, no fix = NO changes in source
[17:02] <EpikVision> alright
[17:02] <vibhav> EpikVision: Which part?
[17:04] <EpikVision> vibhav: "Work on a fix"
[17:06] <EpikVision> up to the code ($ edit-patch 99-new-patch), everything went fine
[17:06] <EpikVision> but I can't get past $ patch -p1 < ../bugfix.patch
[17:07] <EpikVision> vibhav: when I put that command, I keep getting
[17:07] <EpikVision> bash: ../bugfix.patch: No such file or directory
[17:08] <EpikVision> I cd-ed to tomboy/tomboy.dev
[17:09] <vibhav> EpikVision: bugfix.patch needs to be the name of the patch
[17:09] <vibhav> you made to fix the bug
[17:09] <EpikVision> ok
[17:10] <EpikVision> so how do I work on the fix, if it were necessary?
[17:10] <EpikVision> for this tutorial specifically?
[17:10]  * EpikVision scratches his head
[17:12] <tumbleweed> EpikVision: what are you fixing in tomboy?
[17:12] <EpikVision> vibhav: as mentioned earlier, I was just following the package guide
[17:13] <EpikVision> ohh
[17:13] <EpikVision> hold on.
[17:14] <EpikVision> tumbleweed:  I was just following the package guide
[17:15] <tumbleweed> EpikVision: right, but that's the point where you need to fix something
[17:15] <EpikVision> tumbleweed: really?
[17:15] <tumbleweed> I mean, edit some source code
[17:15] <tumbleweed> well, sure, that's the point of that guide, right? :)
[17:15] <EpikVision> ok, do you any bitesized bug for tomboy that I should try?
[17:15] <tumbleweed> you can find a bunch on harvest.ubuntu.com
[17:17] <EpikVision> tumbleweed: i'm at harvest, but I'm having trouble filtering the list to tomboy.
[17:17] <tumbleweed> EpikVision: http://harvest.ubuntu.com/opportunities/package/tomboy/
[17:18] <EpikVision> alright.
[17:18] <EpikVision> https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/386893
[17:18] <EpikVision> wait a min
[17:18] <EpikVision> nvm this one.
[17:19] <EpikVision> tumbleweed: is it courtesy to tackle a bug with no current assignee?
[17:21] <tumbleweed> that person has been assigned for over a year
[17:21] <EpikVision> whoa
[17:21] <tumbleweed> let's assume that they aren't going to do it
[17:21] <EpikVision> hahaha
[17:22] <EpikVision> ok
[17:23] <EpikVision> tumbleweed: so now that I'm at "Work on a fix" at this point
[17:23] <EpikVision> how can I delve into the source code?
[17:24] <EpikVision> I found the problem, figured out that the package could be looked through, and I branched the source package.
[17:24] <EpikVision> now how can I start with a fix?
[17:25] <tumbleweed> EpikVision: there's a patch in the linked gnome bug that you should try
[17:26] <tumbleweed> note that the patch author mentions it wasn't perfect yet
[17:27] <EpikVision> should, I should replace gnome-bug with myself?
[17:27] <tumbleweed> what is 'gnome-bug'
[17:28] <EpikVision> the assignee
[17:28] <EpikVision> were you referring to the linked page I sent you earlier?
[17:28] <tumbleweed> no. that's a linked bug. click on it
[17:28] <EpikVision> ohhh
[17:29] <EpikVision> ok, i clicked it.
[17:30] <EpikVision> what should I do?
[17:30]  * EpikVision feels slightly bewildered.
[17:32] <tumbleweed> download the most recent patch and see if it applies?
[17:33] <EpikVision> ok, according to the package guide, what step am I at?
[17:34] <EpikVision> http://developer.ubuntu.com/packaging/html/fixing-a-bug.html
[17:34] <tumbleweed> you are going to use patch patch, not edit patch
[17:34] <EpikVision> alright.
[17:34] <tumbleweed> err patch, not edit-patch
[17:35] <EpikVision> it gives me (err: command not found.)
[17:36] <tumbleweed> then install it :)
[17:37] <EpikVision> so, I should patch patch tomboy?
[17:37] <EpikVision> I cded to /tomboy/tomboy.dev
[17:37] <tumbleweed> "patch patch" was a typo of mine
[17:38] <EpikVision> what is the syntax i need to patch tomboy?
[17:38] <EpikVision> I'm guessing (err patch <insert app name>)
[17:39] <tumbleweed> no, the packaging guide shows you the right syntax
[17:39] <tumbleweed> where ../bugfix.patch is the name of the patch
[17:39] <jtaylor> quilt import <patch> should also work
[17:40] <tumbleweed> sorry, yes that,s the best approach
[17:40] <jtaylor> then: quilt push
[17:40] <Laney> from within a quilt shell (which I assume edit-patch uses)?
[17:40] <EpikVision> I wrote (quilt import ../bugfix.patch)
[17:41] <EpikVision> but it gives me (Patch ../bugfix.patch does not exist.)
[17:41] <EpikVision> :(
[17:43]  * micahg is curious what manual backport testing is
[17:44] <EpikVision> ../bugfix.patch doesn't exist in my folder...
[17:44] <jtaylor> you need to download it from the bug first
[17:44] <Resistance> and secondly:
[17:45] <Resistance> <tumbleweed> [05/11/12 12:39:22] where ../bugfix.patch is the name of the patch
[17:45] <Resistance> it might not be *named* bugname.patch
[17:45] <Resistance> so you'll need to know (1) where you downloaded the patch to, and (2) what that patch's name is
[17:45] <Laney> micahg: it means us uploading it instead of archive admins using the script
[17:45] <Resistance> EpikVision:  after you download it from the bug
[17:46] <EpikVision> https://bugzilla.gnome.org/show_bug.cgi?id=588730
[17:47] <EpikVision> Resistance: I'm trying to tackle this bug, but I can't work on a fix.
[17:47] <EpikVision> How do I download it from here?
[17:47]  * Resistance looks
[17:48] <jtaylor> is it a good idea to add a patch that is not upstream?
[17:48]  * Resistance seems to be missing backlogs
[17:48]  * EpikVision is a new at this.  
[17:48] <Resistance> what's the package the bug is in?
[17:48] <jtaylor> tomboy
[17:49] <EpikVision> yup. I got the source code from a branch.
[17:49]  * Resistance reads the bug, and reads the equivalent LP bug
[17:49] <EpikVision> I'm following the outline provided by the Package guide
[17:49] <EpikVision> If I succeed, this would be the first bug I ever fixed.
[17:51] <Resistance> EpikVision:  did you check the upstream bug to confirm that the patch(es) that fix LP Bug 386893 (linked to the upstream bug) are *committed* upstream, and not just proposed?
[17:51] <Resistance> upstream, there's two bugs on there
[17:51] <jtaylor> unfortunatly I don't think this particular bug should be fixed in ubuntu
[17:51] <Resistance> s/bugs/patches/
[17:52] <Resistance> jtaylor:  i'm in agreement, it needs to be fixed upstream
[17:52]  * Resistance is on BugSquad, and is giving his opinion on this one
[17:52] <Resistance> perhaps the fix(es) will show up in Quantal at some point?
[17:53] <Resistance> after fixed upstream
[17:53] <EpikVision> ok then.
[17:53] <EpikVision> Resistance: what do you mean by "checking">
[17:54] <Resistance> EpikVision:  i.e. go to the upstream bug, check both of the submitted patches and figure out which one is needed to fix the issue listed on that bug
[17:54] <Resistance> there's two patches submitted to that upstream bug
[17:54] <Resistance> one which was committed already and the other which is proposed
[17:54] <EpikVision> oh ok
[17:55] <Resistance> having said this, i believe it needs upstream fixing.
[17:55] <Resistance> jtaylor:  any objection to me voicing my opinion on that on this bug?
[17:55] <Resistance> (the LP bug)
[17:56] <PaoloRotolo> Hi all!
[17:56] <EpikVision> Resistance: what's the link to go to the upstream bug?
[17:57] <Resistance> its linked to the LP bug.
[17:57] <Resistance> https://bugzilla.gnome.org/show_bug.cgi?id=588730
[17:58] <EpikVision> should I choose a committed one or a proposed one?
[17:58] <Resistance> <jtaylor> unfortunatly I don't think this particular bug should be fixed in ubuntu
[17:58] <Resistance> rather it needs to be fixed upstream
[17:58] <Resistance> which means that it needs to be fixed in the program itself and applied for whatever version that gets included into
[17:59] <EpikVision> ah
[17:59] <Resistance> and while it may be nice to really have in Ubuntu, it should ideally be fixed upstream
[17:59] <EpikVision> what's the downstream then?
[17:59] <Resistance> i'm going to concur with jtaylor on this, it doesn't need fixing in ubuntu
[17:59] <EpikVision> alright.
[17:59] <EpikVision> perhaps, I'll find another one.
[17:59] <EpikVision> since I'm new, i need to tackle a bite-sized bug.
[17:59] <Resistance> there's a list of bite-sized ones, isnt there?
[18:00]  * Resistance could have SWORN there was one
[18:00] <jtaylor> http://harvest.ubuntu.com/
[18:01] <Resistance> jtaylor:  any objection to me stating your opinion (which is also my opinion) that this does not need fixing in ubuntu (but rather upstream) on the corresponding LP bug?
[18:01] <jtaylor> no
[18:01]  * EpikVision hopes to fix at least one bug today.
[18:02]  * EpikVision thanks Resistance and jtaylor for helping.
[18:02] <EpikVision> https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/395001
[18:02] <EpikVision> Is this a good one?
[18:03] <jtaylor> judging from the amount of comments probably not
[18:04] <jtaylor> also that again looks like an upstream issue
[18:04] <Resistance> jtaylor: can you poke the LP people and see whether LP is having a comms issue with gnome-bugs' upstream tracker?
[18:04] <EpikVision> https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/395001
[18:04] <Resistance> LP suggests that it is having a comms error
[18:04] <EpikVision> Resistance: maybe this is better.
[18:05] <Resistance> EpikVision:  FYI: jtaylor's higher up in the chain than I am, i'm pretty comfortable immediately trusting his assessment of bugs
[18:05] <EpikVision> https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/395001
[18:05] <Resistance> EpikVision:  posting three times gets annoying
[18:05] <Resistance> and in some cases is floody
[18:05] <EpikVision> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/828359
[18:05] <EpikVision> I meant to get this one. I'm orry
[18:06] <Resistance> might i suggest, EpikVision, that you not assign yourself to bugs willy-nilly?
[18:06] <Resistance> just a small suggestion, is all
[18:06] <EpikVision> willy-nilly?
[18:06] <EpikVision> alright.
[18:06] <Resistance> i'm noticing on 395001 you assigned yourself then removed yourself from assignee after jtaylor pointed out its an upstream bug
[18:06]  * Resistance looks at 828359
[18:06] <EpikVision> sorry about that.
[18:07] <Resistance> this one's marked as incomplete
[18:07] <EpikVision> I think I would like to be assigned a decent bug to start with.
[18:07] <EpikVision> I have poor judgment and choice.
[18:08] <EpikVision> :(
[18:08]  * Resistance quickly runs off for a cup of coffee
[18:10]  * EpikVision stares at the computer screen.
[18:11] <Resistance> jtaylor:  tumbleweed:  sorry for interjecting and stealing your thunder, there
[18:12] <Laney> broder: can we have it API close the bug with -c à la syncpackage?
[18:12] <tumbleweed> Resistance: no problem I ran off to the canonical shop in UDS between sessions :)
[18:13] <Resistance> :P
[18:13] <ajmitch> tumbleweed: got a bunch of goodies?
[18:13]  * Laney need to get something
[18:13] <Laney> got a voucher
[18:13] <tumbleweed> ajmitch: yar, a new backpack and a hoodie
[18:13]  * ajmitch has a hoodie & fleece jacket
[18:13] <tumbleweed> plus some special orders for people in ZA :)
[18:14]  * Resistance should make an effort to attend UDS in the future.
[18:15]  * EpikVision had much fun at UDS.
[18:15] <Resistance> the past two UDS, i've been showing up remotely, although i did a lot of lurking this one
[18:17] <tumbleweed> I love that we have remote participation, but it's really hard to actually participate when you aren't there in person
[18:18] <Resistance> mhm
[18:18]  * tumbleweed is glad to be here
[18:18] <Resistance> i should point out, though, that when people actually talk loudly enough to be heard over the live audio streams, it makes life easier
[18:18]  * Resistance stopped by the MOTU BoF session yesterday
[18:18] <Resistance> (remotely of course)
[18:18] <tumbleweed> some people seem incapable of speaking up :)
[18:19] <Resistance> mhmn
[18:19] <Resistance> having said this, i could have said "Turn up the volume", but that crinkling noise was already too loud xD
[18:19] <Resistance> (there was crinkling somewhere near the mic)
[18:19]  * ajmitch blames highvoltage 
[18:21] <EpikVision> https://bugs.launchpad.net/unity-2d/+bug/813041
[18:21] <EpikVision> guys, I think this one is ok.
[18:22] <tumbleweed> the most useful thing you can do there is to provide a patch
[18:22] <Resistance> mhm
[18:22] <EpikVision> providing a patch?
[18:22] <Resistance> aw, man, how is it i can just down a cup of coffee without realizing it...
[18:22]  * Resistance goes off to get another cup
[18:22] <EpikVision> haha
[18:22]  * EpikVision laughs
[18:23] <EpikVision> I should use http://developer.ubuntu.com/packaging/html/udd-patchsys.html
[18:28] <Resistance> that bug'd need a patch at the most, that's the best you can do, its triaged upstream (with the Unity project)
[18:28] <EpikVision> tumbleweed:
[18:28] <EpikVision> tumbleweed: since you are UDS, can you lend a prospective developer a hand?
[18:28] <EpikVision> *are at
[18:28] <Resistance> EpikVision:  UDS is a busy time for devs :P
[18:28] <Resistance> i think you'll need some patience ;P
[18:28] <EpikVision> perhaps so...
[18:28]  * Resistance is intentionally not bugging the MOTUs much during UDS, even though their attention is necessary for a sync request from Debian for Quantal
[18:29] <tumbleweed> EpikVision: what are you needing a hand with?
[18:29] <EpikVision> determining what is a proper bug to fix.
[18:29] <EpikVision> how to recognize a easy bug from a hard bug
[18:29] <EpikVision> etc.
[18:29] <EpikVision> lol
[18:29] <tumbleweed> bitesize tag is an esay way to find an easy bug
[18:30] <EpikVision> some bitesize ones aren't meant to be fixed, I noticed during this discussion.
[18:30] <EpikVision> or a starter can't try them.
[18:30] <Resistance> probably because they're already merged/committed upstream
[18:30] <tumbleweed> right, so for each bug we make a decision on where we want to fix it
[18:31] <Resistance> for the first one you did, the one i came in on, that was already filed upstream and merged upstream with a fix
[18:31] <Resistance> so that didn't need fixing in Ubuntu
[18:31] <EpikVision> ahh ok
[18:31] <Resistance> i didnt look at that second one very well
[18:31]  * Resistance was too busy focusing on the need for coffee
[18:31] <EpikVision> oh my
[18:31] <tumbleweed> but if it's serious enough, we can apply the patch in Ubuntu rather than wait for the new version from the upstream that fixes the bug
[18:31] <Resistance> mhm
[18:32] <EpikVision> i c.
[18:32] <EpikVision> starters should try simple bugs then.
[18:32] <EpikVision> like typos
[18:32] <Resistance> yep.
[18:32] <Resistance> well, even then, minor fixes arent always accepted
[18:33] <EpikVision> btw, does anyone know alejandro's irc name?
[18:33] <tumbleweed> user-visible typos are a great thing to start with
[18:33] <Resistance> i agree
[18:33] <EpikVision> alrighty then, where and how can I find a bunch of them?
[18:34] <tumbleweed> search for spelling / typo on bugs.launchpad.net/ubuntu ?
[18:34] <Resistance> the easy-to-fix stuff is good, including the bitesize bug i took up / filed against php5 to use unix sockets instead of TCP sockets, which was accepted upstream and exists in 5.4 in some debian repo :P
[18:34] <Resistance> that was a very easy to fix one ;P
[18:34] <Resistance> yeah, what tumbleweed suggested would work
[18:34] <Resistance> (default setup, on that php5 bug/wishlist request, btw ;P)
[18:34] <Resistance> speaking of which...
[18:35] <Resistance> tumbleweed:  who do i need to prod about server packages, such as php5 and whether they'll update to whatever the latest is in debian for Quantal?
[18:35] <EpikVision> Resistance: can you give an overview of the way of the developer?
[18:35] <Resistance> the ubuntu server team?
[18:35] <Resistance> i *should* be honest and point out that my duties with bugs primarily are deciding what's triage-worthy, and then filing it upstream as necessary
[18:35] <Resistance> nowadays i dont usually patch/fix bugs
[18:35] <Resistance> unless they're in the nginx project's PPAs, because i'm the manager of that ppa's lucid packages... :P
[18:36] <EpikVision> wow, that's awesome.
[18:36] <Resistance> OW!  hot coffee!
[18:36]  * highvoltage kind of stumbles in
[18:36] <Resistance> but to be honest, most bugs for that are fixed upstream, or have patches upstream that get included in the package
[18:37] <highvoltage> (eek I've missed a lot)
[18:37] <Resistance> (in regards to nginx's ppas which are more up to date than the repos)
[18:37] <Resistance> highvoltage:  meh, that's what scrollbacks and ubuntu logs are for :P
[18:37] <tumbleweed> Resistance: the last person who touched it is responsible for merging it from Debian
[18:38] <Resistance> tumbleweed:  ah, i see.
[18:38] <Resistance> how do i determine who was responsible for merging from debian?
[18:38] <Resistance> changelog entries?
[18:38] <broder> Laney: eh...i'm a bit iffy on that one - it has the same problem as syncpackage but worse since the upload hits unapproved
[18:38] <Laney> yes
[18:38] <tumbleweed> merges.ubuntu.com (which is currently a little out of date)
[18:38] <Laney> I would just leave it open though
[18:38] <Laney> I think most backporters are capable of doing that :-)
[18:39] <broder> huh?
[18:39] <Laney> what?
[18:39] <Laney> just don't press yes until it gets accepted
[18:39] <broder> ....that could take days, though
[18:40] <Laney> it could
[18:40] <Laney> the one i just did took 12 minutes
[18:40] <broder> that's because cjwatson and i were sitting next to each other and testing manual backporting
[18:40] <Laney> you are always free to quit and not do it
[18:40] <Laney> fine.
[18:40] <broder> i'm fine with adding the option
[18:43] <broder> bah. connection fail. in any case, colin and i came up with a list of changes we want to see in backportpackage before we start using it for heavy-duty backporting
[18:43] <broder> i will add bug closing to that list
[18:44] <Laney> ty
[18:45] <broder> in case you're curious, the changes are: switching from ~precise1 to ~ubuntu12.04.1 and passing -v because (a) that's what was always done and (b) it won't close bugs
[18:45] <broder> (the -backports pocket is special cased to never be able to close bugs)
[18:46] <Laney> interesting
[18:46] <Resistance> broder:  mind if i pick your brain about requesting a package sync?
[18:47] <broder> Resistance: i'm about to go afk for a while. asking the channel would probably be better
[18:47] <Resistance> if i use requestsync to request a sync from Debian unstable to Quantal, do i put quantal or something else for the target release?
[18:47] <Resistance> simple question, just a question of what to put in for target release
[18:47] <jtaylor> bug 997201 is weird
[18:47] <jtaylor> how can that happen?
[18:48] <broder> Resistance: yes, quantal is correct
[18:48] <Resistance> just wanted to make sure, thanks.
[18:48] <broder> though you shouldn't have to specify anything - it should default to the current devel release
[18:50] <Resistance> broder:  reminder that i'm on natty still (waiting for a replacement drive to come in), i'd rather not chance it ;P
[18:50] <broder> requestsync will ask you to confirm what it's doing before it does anything
[18:51] <Resistance> yeah, well i'm in the habit of putting information into the fields just to make sure it has the right info
[18:51]  * Resistance made the mistake of not doing that before when packaging things, and ran into all sorts of crap from pbuilder when it locally-build the package he was building
[18:51] <Resistance> locallybuilt*
[18:51] <Resistance> bah, stupid keyboard
[18:52] <Resistance> https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/998195  <-- in case someone can take a look at this
[18:52] <Resistance> (it builds in Quantal, i tested locally, and in a Quantal VM)
[18:53] <Resistance> bah, more firefox updates >.>
[19:05] <Rhonda> How brave would it be to upgrade from maverick directly to precise?
[19:07] <Rhonda> Huhm, I guess I should redirect myself to #ubuntu :)
[19:07] <Laney> probably it should display an "I uploaded this, please wait for it to be approved" message too
[19:07] <Laney> syncpackage could also do this during freezes ^o)
[19:08] <tumbleweed> or we should have a separate tool that looks at recent syncs / backports uploaded by you that have open bugs nad closes them
[19:09] <Laney> i'm thinking of Fix Committed which the same tool could/should do
[19:09] <Laney> for Fix Released, maybe closemybugsd would be nicetm
[19:09] <Laney> ™
[19:10] <Laney> well, maybe not backportpackage unless that is driving dput for you
[19:10] <Rhonda> wow, 500mb ram and 380mb swap. this is going to be fun :)
[19:10] <Laney> huh, what machine is this?!
[19:11] <Rhonda> two cores atom 1.6 ghz, hmmm
[19:11] <Rhonda> an aspire one netbook
[19:12] <Rhonda> I think it was one which had ubuntu preintalled back then
[19:12] <Rhonda> the display is broken, and there are some keys missing (I am typing on the rubber thingies mostly ;)
[19:13] <Rhonda> It's the best I could get as a quick replacement for my hp laptop that doesn't want to charge anymore
[19:13] <Laney> sounds like an enjoyable piece of hardware :-)
[19:13] <Rhonda> Didn't know you are also into masochism like me, Laney ;)
[19:14] <Laney> heh
[19:15] <Rhonda> Reminds me of the days when the m key on my compaq notebook b0rked.
[19:15] <Rhonda> I tweaked the keyboard bindings and even managed to get used to have the m above the tab key.
[19:18] <Rhonda> sfvbm right alt menu and right windows key, also right shift key, those are the keys that are missing the regular plastic above the rubber thingy
[19:19] <Rhonda> also, for additional fun, they keyboard layout is some qemrtz
[19:19] <Rhonda> anyone got a clue which language uses qemrtz?
[19:19] <Rhonda> italian potentially?
[19:30] <Resistance> if i've filed a sync request for a bug on LP in which the package that is being synced to Quantal closes that bug, should I set the bug that the sync request will close  to  "In Progress" (and assign the bug to someone involved with getting that sync request completed)?
[19:31] <Resistance> assuming the bug has "confirmed" as its current status
[19:33] <tumbleweed> Resistance: mention all the bugs that this will close in the sync request
[19:33] <tumbleweed> (assuming they aren't closed in the changelog)
[19:33] <Resistance> they are closed in the changelog
[19:34] <tumbleweed> perfect
[19:34] <Resistance> but the LP bug that's being closed, does it need "In Progress" set to its status with the sync request having been filed?
[19:35] <tumbleweed> you can, if you are worried that someone else is going to look at them
[19:36] <Resistance> now i assume i just wait for someone on the sponsors team to see the sync request?
[19:36] <tumbleweed> yes
[19:36]  * Resistance has all the patience in the world, then, on that one :)
[21:39] <bobweaver> hello there I am trying to find information about " Traditional Packaging "  is it like   make upstream  make make or autotolls/whatever  then start the debian package with dh_make -e <email> -c < license  -f foo.tar      then make all your debian/*  then make tar ball foo.orig.tar.gz  then build package with fakeroot and dpkg-buildpackage -F  ?
[21:40] <bobweaver> This is why I ask  http://developer.ubuntu.com/packaging/html/traditional-packaging.html
[21:49] <ScottK> bobweaver: In very general terms yes.
[21:50] <Laney> That packaging guide is using "traditional packaging" to mean packaging without using UDD.
[21:50]  * Laney tries to say "packaging" some more
[21:58]  * ScottK thinks of it more as "way that works reliably" than "traditional".
[21:59]  * Laney looks forward to reviewing that patch to the guide
[21:59] <bobweaver> ahh cool so like a hardened package ? or like very sound package
[22:00] <bobweaver> quilt is verry confusing for new comer like me and that guide if that helps at all
[22:00] <ScottK> Quilt is confusing to a newcomer period.
[22:00] <bobweaver> :)
[22:01] <ScottK> I don't recall exactly why, but I had a lot of trouble with it.
[22:01] <ScottK> Now I've gotten past it, but it's definitely a barrier to entry.
[22:05] <bobweaver> thanks ScottK
[22:06] <bobweaver> there was also something in the ,manual about RCD or something like that and I do not know what that is either I am looking for it now.
[22:06] <bobweaver> I can not belive that I deleted my Quesytions file then again it was 4 am
[22:11] <bobweaver> ok so I found it it is under the section Limitations of UDD¶What is  RCS on top of RCS.  ?
[22:12] <tumbleweed> bobweaver: RCS = revision control system
[22:12] <tumbleweed> both bzr and quilt are RCSs
[22:13] <bobweaver> ahh thanks that should be in maunal ? I should file bug ?
[22:13] <bobweaver> or shouldd I just add that and push my branch ?
[22:14] <tumbleweed> either works. If you're adding an explanation, that's great, that's what matters
[22:14] <bobweaver> will do now
[22:15] <bobweaver> thanks for the info everybody !
[22:19] <ScottK> tumbleweed: Quilt isn't really an RCS.
[22:20] <ScottK> dpkg tries to treat it that way, but that's dpkg's fault.
[22:21] <tumbleweed> ScottK: yeah, it's more a patch management tool
[22:21] <ScottK> Yes
[22:21] <tumbleweed> which is a job taken on by modern RCS tools
[22:22] <ScottK> Sort of.
[22:29] <bobweaver> hello again is there any tips that you could give too a new comer that wants to learn but also wants too learn from your mistakes. Like one for me is learn debconf before you try to write a postinst script or you do not have too package something eachtime you make a change, Thanks again I know that that is a loaded question but any tips help thanks
[22:36] <ScottK> Learning debconf is an advanced task.  Save it for later (until you find you need it).
[22:36] <ScottK> Find a bug that bothers you and see if you can figure out how to fix it.  Then package the fix.
[22:36] <ScottK> That's the best way to learn.
[22:41] <bobweaver> Thanks ScottK  !
[23:01] <bobweaver> I just got great news !
[23:05] <bobweaver> for bringing devs into motu. If you know what the newboston that is great if not it is a place too watch tutorials online about programing and all sorts of other stuff. his python video #1 of like 60 or something has over 288,000 hits and watches on youtube  and that is just the pyhton videos. He has said yes that he would put any video tutorials from motu on his site. I think that this would bring a lot of people in not sure if this is
[23:05] <bobweaver>  good or not what do you think  ?
[23:10] <bobweaver> sorry I was wrong about the numbers on that video it has 399,246 views
[23:10] <bobweaver> most have at least 100,000 per 1st video