[00:12] <bkerensa> micahg: So are we cherry picking changes from debian for the chromium-browser main branch? If not does someone know the workflow
[00:12] <micahg> bkerensa: no, we'll start by getting the stable channel up to date and then work backwards
[00:20] <bkerensa> micahg: ok :) do you think we might be fresher in 13.04?
[00:21] <micahg> bkerensa: hopefully :), current stable should get an update as well, unfortunately, I don't have a timeframe yet
[00:22] <micahg> (as it won't be me doing the work for this)
[07:46] <mohamedalaa98> hello
[07:47] <mohamedalaa98> I want to push a fix to quantal-proposed
[07:47] <mohamedalaa98> https://code.launchpad.net/~m-alaa8/ubuntu/quantal/im-switch/fix-for-621204/+merge/128037
[07:47] <mohamedalaa98> how can I do that?
[07:58] <mohamedalaa98> can you please tell me how I can push a fix to quantal-proposed?
[08:18] <tumbleweed> bdrung: I don't get the logic behind https://bazaar.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk/revision/1182
[08:20] <bdrung> tumbleweed: that was probably not the correct solution for fixing an issue with syncing to -proposed
[08:23] <tumbleweed> ok, probably reverting those bits, then
[08:24] <bdrung> yes
[09:05] <Laney>                    source                   |         version          |     release
[09:05] <Laney> --------------------------------------------+--------------------------+-----------------
[09:05] <Laney>  xml-core                                   | 0.13+nmu2                | raring-proposed
[09:09] <ajmitch> Laney: looks like an autosync?
[09:09] <ajmitch> depwait on newer debhelper
[09:10] <micahg> there was an autosync
[09:11] <mohamedalaa98> Hello :)
[09:11] <mohamedalaa98> can you please help me in this propose https://code.launchpad.net/~m-alaa8/ubuntu/quantal/im-switch/fix-for-621204/+merge/128037
[09:12] <mohamedalaa98> how I can submit bugfix to quantal-proposed?
[09:12] <mohamedalaa98> thanks in advance
[09:13] <micahg> mohamedalaa98: it was suggested that it shouldn't go to quantal-proposed, but rather raring
[09:14] <mohamedalaa98> so I have to reupload this branch to raring?
[09:15] <micahg> mohamedalaa98: yeah
[09:15] <mohamedalaa98> micahg: ok thank you very much :)
[09:19] <tumbleweed> Laney: thanks. I found a good test case, transcode
[09:20] <mitya57> Laney: hi, do you know why there was no "accepted to -proposed" comment in bug 1068208?
[09:20] <mitya57> and should we add a verification-done tag?
[09:20] <tumbleweed> mitya57: I guess someone used the wrong tool
[09:21] <Laney> ajmitch: I was just demoing
[09:21] <micahg> mitya57: wasn't accepted yet
[09:22] <mitya57> micahg: and what is https://launchpad.net/ubuntu/+source/lintian/2.5.10.2ubuntu2.1?
[09:22] <micahg> mitya57: nevermind, E_NOTENOUGHCAFFEINE
[09:22] <mitya57> :)
[09:23] <mitya57> the fix is trivial, so I think I can add a tag myself
[09:23] <Laney> if you verified it
[09:23] <Laney> i'm sure someone else here could do that
[09:26] <mitya57> By the way — what's now the preferred thing to put into changelogs — raring or raring-proposed?
[09:26] <tumbleweed> I'd say raring
[09:27] <Laney> yes
[09:27] <mitya57> OK. And I've verified it, yes.
[09:47] <mitya57> Hm, the reports vs reqorts issue is still not fixed...
[13:27] <Laney> ScottK: done
[13:27] <Laney> (opendkim)
[13:39] <ScottK> Laney: Thanks.
[14:36]  * micahg is wondering why the sync he did didn't show up on raring-changes
[14:38] <micahg> it syncd and shows up for the person I sponsored, just didn't seem to hit raring-changes
[16:48]  * Logan_ waves to micahg 
[16:48] <micahg> hi Logan_
[16:49] <Logan_> micahg: question - when will merge requests start being considered for Raring?
[16:49] <micahg> Logan_: now
[16:49] <Logan_> oh, awesome :)
[16:49] <Logan_> I have a good number ;P
[17:38] <Laney> micahg_mobile: coming down now! sorry!
[17:55] <highvoltage> laney / tumbleweed: plans yet?
[17:55] <highvoltage> and where sre you?
[17:58] <highvoltage> ah coolbhavi says you left already
[21:38] <alo21> hi all
[21:39] <alo21> I saw a package without a maintainer (https://launchpad.net/ubuntu/+source/kaa-metadata)
[21:39] <alo21> why?
[21:44] <maxb> nothing odd there
[21:45] <maxb> ask a clearer question
[21:46] <alo21> maxb: I sent an email in ML.
[21:50] <maxb> alo21: Why do you think it's maintainerless?
[21:53] <alo21> maxb: because I am new... but now I realized that here is the team (http://qa.debian.org/developer.php?login=pkg-freevo-maint@lists.alioth.debian.org)
[21:53] <maxb> It has received an update in Debian this year. Granted, that's months ago now, but I don't know how active this project is
[21:55] <alo21> maxb: As I wrote, I fixed a bug... how can I contact them to submit the fix?
[21:56] <alo21> maxb: seems that this bug affects Ubuntu only
[21:56] <maxb> As the package is currently imported into Ubuntu unmodified from Debian, the first step should be to .... ah
[21:57] <maxb> OK, in that case, it will depend on whether the bug is something that needs to be fixed only in Ubuntu, or is something that could be sent to the upstream project or to Debian, but only matters for Ubuntu
[21:59] <alo21> maxb: in this case I have to modify the packahe in Ubuntu only and send it for 13.04. Right?
[21:59] <alo21> package*
[22:01] <maxb> Well, it depends. Possibly. But if the potential exists to forward the change to Debian and not carry a different in Ubuntu forevermore, Ubuntu developers would prefer you looked into that
[22:02] <alo21> maxb: so I should contact kaa-metadata debian maintainers and talk with them. right?
[22:05] <maxb> alo21: Very probably. But you haven't said what the bug is, so I can't attempt to suggest whether it's truly Ubuntu-specific or not
[22:06] <alo21> maxb: this one is the bug (https://bugs.launchpad.net/ubuntu/+source/kaa-metadata/+bug/553827) and here is (http://qa.debian.org/developer.php?login=pkg-freevo-maint@lists.alioth.debian.org) the package overview
[22:10] <maxb> That doesn't sound Ubuntu-specific at all, rather a general failure in guessing encodings from locale names, so it's definitely something best pursued with the upstream kaa-metadata project and Debian first
[22:12] <alo21> maxb: thanks a lot... how did you check that this bug in not ubuntu only?
[22:15] <maxb> I didn't, I just made an educated guess that it is highly unlikely that locale and character set processing in Python are sufficiently different in Ubuntu compared with Debian or other Linuxes
[22:17] <alo21> maxb: right
[22:17] <alo21> thanks again