[06:09] <tumbleweed> jtaylor: a bugfix release sounds worth taking
[08:03] <dholbach> good morning
[08:04] <benonsoftware> Hello dholbach
[08:05] <dholbach> hey benonsoftware
[16:17] <takamarou> Hi all - I'm looking to get started doing some dev/bug fixes for Ubuntu, and am getting a bit confused as I browse through triaged bugs..  I see quite a few bugs that are labeled triaged, but when you click into them you see a "Fix Commited" and a "Triaged" entry.  Does this mean that the fix is committed by the original package devs, or does that mean it is still open to fixing?  Example: https://bugs.launchpad.net/ubuntu/+s
[16:17] <takamarou> P.S. Sorry for the dumb question :/
[16:19] <dholbach> takamarou, there's no dumb questions :)
[16:19] <dholbach> takamarou, can you paste the full link to the bug? it seems it was cut off
[16:19] <takamarou> dholbach, hmm, not cut off on my screen..  let me try it on its own line
[16:19] <takamarou> https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/807861
[16:20] <dholbach> ah, that was a good question! :)
[16:20] <dholbach> can you see the two lines in the middle of the page, one "fix committed" and the other one "triaged"?
[16:20] <takamarou> Yep
[16:20] <dholbach> they are what we call 2 bug tasks
[16:21] <dholbach> we identified that the problem is in "inkscape (Ubuntu)" and "inkscape"
[16:21] <dholbach> which means as much as: we need to fix it in inkscape, the Ubuntu package
[16:21] <dholbach> and also in inkscape the upstream project
[16:21] <takamarou> Which is "inkscape" as in the original straight from inkscape, and "inkscape (Ubuntu)" as in the Ubuntu repo version... right?
[16:21] <takamarou> oh
[16:21] <takamarou> OK
[16:21] <dholbach> so it seems like the fix is committed (but not in a release , which would be 'fix committed') upstream
[16:22] <dholbach> and in Ubuntu the bug is triaged, which means that the problem is understood and has all necessary information
[16:22] <dholbach> one possible solution would be to grab the fix from upstream and fix the ubuntu package this way
[16:22] <dholbach> or wait until a new release is rolled upstream and we upgrade to the new upstream version
[16:23] <takamarou> Gotcha.  And what is the usual procedure with that kind of thing?  Wait for the new release, or do it yourself?
[16:23] <dholbach> as it's a typo, I would assume it's safe to wait for the next upstream release
[16:23] <takamarou> OK
[16:23] <dholbach> if it's something urgent like a common crasher, it might be better to just grab the fix, apply it and not block on upstream finding the time to roll a new release
[16:24] <takamarou> So little things like typos are probably going to be a bad choice for getting my feet wet in bug fixing, as they will be fixed upstream
[16:24] <dholbach> no, if you want to start out by fixing a typo, do it - but in a lot of cases it makes sense to submit the fix to the upstream authors
[16:24] <takamarou> OK
[16:24] <dholbach> unless it's something really visible and irritating :)
[16:25] <takamarou> Gotcha
[16:25] <dholbach> it's impossible to know all of this from the very beginning
[16:25] <dholbach> so keep the questions coming
[16:26] <dholbach> also if you haven't heard already, next week is Ubuntu Developer Week, which might interest you: https://wiki.ubuntu.com/UbuntuDeveloperWeek
[16:26] <takamarou> I will - still in the process of upgrading to 11.10, so I don't know all the questions yet.  But I will soon!
[16:27] <dholbach> :-)
[16:27] <takamarou> Sweet.  All the classes are during my work hours, but perhaps I'll keep IRC open in the background
[16:27] <takamarou> Thanks!
[16:33] <takamarou> OK - got another question.  Looking at another bug (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/723864) in Unity.  It's got 4 bug tasks, Unity (ubuntu), Unity, Unity Foundations, and Ayana Design.  I understand the first three, but what the heck is Ayana Design (and also, why is there more than one upstream?).  I've seen this Ayana in a couple places now.
[16:38] <dholbach> takamarou, also we'll put up logs later on
[16:38] <dholbach> takamarou, I'm not 100% sure, but I could imagine that in this case it's a way to get multiple teams aware of the bug
[16:38] <dholbach> not 100% sure though
[16:39] <dholbach> sometimes you can have lots more than 2 tasks
[16:39] <dholbach> ie: https://bugs.launchpad.net/ubuntu/+source/audiofile/+bug/922036
[16:39] <dholbach> in this case it's a matter of fixing the same problem in many different packages
[16:41] <takamarou> OK
[21:34] <TiMiDo> Hi people
[21:35] <TiMiDo> if i want to help around the MoTU  i need to create my self, a PPA, so i can upload new bugs fixes and much more?
[21:38] <micahg> TiMiDo: you can use a local sbuild or pbuilder instance to test
[21:38] <TiMiDo> oh OK i was reading. online on the wikis
[21:39] <TiMiDo> so i can package,
[21:39] <TiMiDo> question do i need my GPG so be sign before uploading. the new changes?
[21:40] <micahg> TiMiDo: upload rights are a different story, they come later (https://wiki.ubuntu.com/UbuntuDevelopers)
[21:41] <TiMiDo> let's see
[21:42] <micahg> TiMiDo: until then, you can get sponsored: https://wiki.ubuntu.com/SponsorshipProcess
[21:42] <TiMiDo> nice.
[21:42] <TiMiDo> I'll get a sponsor later on but anyways i can still upload to lp
[21:43] <TiMiDo> so I'll do that with bzr
[21:44] <micahg> TiMiDo: once you propose a merge into the lp:ubuntu/* branch, it lands in teh sponsorship queue, no sponsor hunting necessary
[21:44] <TiMiDo> oh nice
[21:44] <TiMiDo> i was fixing some bug
[21:44] <TiMiDo> on php5
[21:45] <TiMiDo> do you guys have any packages that need help to be packaging or to check the rules?
[21:47] <TiMiDo> i meant if ubuntu has orphaned packages
[22:17] <blair> ub https://bugs.launchpad.net/bugs/920284 a commenter wrote "Could you progress the ones that require merges, and check how precise
[22:17] <blair> looks after all of this has built and published?"  what am i supposed to do?
[22:17] <blair> s/ub/in/
[22:20] <micahg> blair: check and see what's left to be done to sync maven (i.e. what other build/runtime dependencies need to be sync'd/merged)
[22:21] <blair> micahg, i think the person who has done the syncs has listed it pretty well already
[22:21] <blair> there's nothing for me to do on the ones that require merges from debian, is there?
[22:22] <micahg> blair: propose the merge?
[22:22] <blair> unless i need to open tickets requesting a merge/sync?
[22:22] <micahg> blair: you should ask the person who touched it last first though
[22:25] <blair> there's only really one package that debian has a newer upstream than ubuntu and it was synced, the rest are debian package updates, which i don't think are really needed
[22:25] <blair> for maven working, that is
[22:26] <blair> what does MIR mean here: "synced, but will require MIR of libcommons-parent-java"
[22:27] <micahg> Main Inclusion Request
[22:27] <blair> that means, move it from universe to main?
[22:27] <micahg> yes
[22:29] <blair> why does he say that, i dont' see a direct dependency from libcommons-logging-java onto libcommons-parent-java?
[22:32] <blair> is there a tool to propose merges, like requestsync?
[22:32] <blair> apport?
[22:33] <micahg> sorry, I have to go, will be back UTC early sunday
[22:33] <blair> micahg, ok, have a good one