[01:13] <ScottK> chilicui1: Packages with Ubuntu unique changes in them are not automatically sync'ed.  Those need human intervention.
[01:35] <chilicui1> ScottK: mm, and that's called 'merge' isn't?.., so, It seems like there is no danger if I work in a package that has other ubuntu changes...
[01:36] <ScottK> Yes.
[01:36] <ScottK> Also Debian is in pre-release freeze right now, so the rate of general upload there is relatively low.
[01:36] <ScottK> I wouldn't worry about it too much either way.
[01:38] <chilicui1> wow, thanks for the information ScottK
[01:46] <TheLordOfTime> ScottK, since you're active, can you point me to sample bugs or documentation for filing a sync request bug?
[01:47] <TheLordOfTime> can't use Ubuntu to file it with the scripts, since my partition went and died.
[01:47] <ScottK> I'd search LP for one then and model it's format.
[01:47] <TheLordOfTime> could probably go clone the format of the older ZNC sync request bugs, since its the same package.
[01:47] <TheLordOfTime> i know i filed a few of those over time...
[01:48]  * TheLordOfTime diffs the control files for current and the one he wants synced.
[01:48] <TheLordOfTime> i don't want any build-dep changes :P
[01:50] <TheLordOfTime> those were pre-oneiric i think, though.
[01:50] <TheLordOfTime> not sure if the format for the bugs've changed...
[01:50] <TheLordOfTime> ... oops, i broke my server again
[02:12] <TheLordOfTime> ScottK, who should I subscribe for a sync-request bug for something in Universe, MOTUs or sponsors or someone else?
[02:12] <TheLordOfTime> again i'm not working with the autofiler script :P
[02:12] <ScottK> TheLordOfTime: ubuntu-sponsors
[02:13] <TheLordOfTime> mmkay, i'm going to load a VM first and test the package, it should work as-is without any changes, but i cant build-test on Windows :P  (I can test the binaries on one of my servers though)
[02:50] <TheLordOfTime> ScottK, i'm build-testing in my PPA.  Do you recommend subscribing sponsors before or after i build-test, and should the sync request bug be "Wishlist" importance (if so, i can set that if there's no objection, due ot bugcontrol)
[02:51]  * TheLordOfTime doesnt do anything when the package being synced FTBFS.
[02:51] <ScottK> TheLordOfTime: subscribe sponsors when you are ready for a sponsor to take action (so after).  Yes, wishlist.
[02:51] <ScottK> How about fix the FTBFS?
[02:51] <TheLordOfTime> assuming it FTBFS
[02:51] <TheLordOfTime> it shouldnt after digging around in the sources
[02:51] <TheLordOfTime> but, i don't trust pbuilder locally, its been wonky :P
[03:18] <TheLordOfTime> ScottK, all done, thanks.  :)  https://bugs.launchpad.net/ubuntu/+source/znc/+bug/1081399
[07:47] <dholbach> good morning
[12:41] <Laney> slow reverse-depends is slow
[13:09] <Laney> can we haz codesearch.ubuntuwire.org please?
[13:12] <Zhenech> do not stealz precious servicez from derbian
[13:13] <Laney> but it's so sweet
[13:16] <geser> Laney: can you check if the python-keyring SRU fixed the password issue when using syncpackage and similar tools?
[13:16] <Zhenech> btw, laney, could you sru monkeystudio while I am at work? the exact diff between quantal and raring minus version should be fine (https://bugs.launchpad.net/ubuntu/+source/monkeystudio/+bug/1074845)
[13:17] <geser> I suspect is might be https://bitbucket.org/kang/python-keyring-lib/issue/71/cryptedfilekeyring_unlock-does-not-return which mdeslaur fixed too in his python-keyring uploads :)
[13:17] <Laney> Zhenech: not right now, maybe later. geser ^?
[13:17] <Laney> i'll test the SRU in exchange for you doing that
[13:18] <Laney> geser: seems to work
[13:18] <Laney> didrocks: ^^^ that's the bug you pinged me about the other day
[13:18] <Laney> seems fixed in SRU
[13:19] <didrocks> Laney: oh excellent, please keep me posted
[13:19] <didrocks> Laney: so, we found a workaround this morning
[13:19] <didrocks> which is exporting a keyfile for setting unencrypted key
[13:20] <didrocks> but if there is a better solution… :)
[13:21] <Laney> didrocks: yes, upgrade to the packages in -updates
[13:22] <geser> Laney: thanks for testing. I'm at work right now myself and couldn't test it (don't have chroot here to easily reproduce/test it)
[13:22] <Laney> happy to
[13:22] <Laney> I'm just happy not to have to type my keyring password three times in a row now
[13:22] <Laney> I got quite used to it
[13:25] <geser> at least your password is now in your muscle memory :)
[15:28] <bdrung> dholbach: what does the lintian-ubuntu-only script do?
[15:28] <dholbach> bdrung, you give it a lintian tag and it will parse the ubuntuwire-lintian log to find which ubuntu-only packages are affected and which issues would be better targetted in Debian
[15:31] <bdrung> dholbach: nice.
[15:31] <dholbach> It helped a lot with the bugfixinginitiative page :)
[15:31] <bdrung> that's what i thought
[15:32] <bdrung> it would be nice to have a tool that you give a source package name and it spits out the ubuntu-only lintian tags (-> you introduces these lintian tags)
[15:34] <dholbach> that might be an idea as well
[15:35] <dholbach> so I just checked, we can directly link to Harvest opportunity lists (ie: http://harvest.ubuntu.com/opportunities/?opp.list=bitesize&pkg= gives you all bitesize bugs)
[15:36] <dholbach> if we could agree on a list of "trivial", "easy", "medium", ... lintian tags (which would be useful to get fixed), we could have Harvest aggregate them for us and we wouldn't have to list them on the wiki any more
[15:36] <dholbach> I think I'll start a discussion on the mailing list about it
[15:42] <mspencer> Hi, I'm new to developing for Ubuntu and am interested in working on the Contributor Console (https://wiki.ubuntu.com/ContributorConsole). Is this something a beginner could do? So far I've worked on bug fixes.
[16:07] <alo21> hi
[19:36] <jtaylor> do you use debuild -v against what is in proposed or what is in release?
[19:37] <micahg> I would think proposed
[19:37] <micahg> (so that bugs are closed properly)
[19:38] <jtaylor> makes sense, thx
[23:01] <dlynch> jtaylor, I installed Debian testing today in VirtualBox and Rapid Photo Downloader runs fine on it
[23:16] <bkerensa> I'm merging a package but it says certain files still have conflicts even though I have resolved them... How can I remove this flag?
[23:17] <jtaylor> bzr resolved file
[23:17] <RAOF> bkerensa: You've run “bzr resolve”?
[23:17] <jtaylor> I think
[23:18] <bkerensa> jtaylor: ahh :) I kept trying "bzr resolved"
[23:23] <bkerensa> RAOF: thx