[12:21] <geser> bdrung: was the only reason you changed the lp: #xxx in debian/changelog to LP to look equal to the other entries? (u-d-t commit 874)
[12:21] <bdrung> geser: yes
[12:27] <bdrung> geser: should i setup a daily build of ubuntu-dev-tools?
[12:28] <bdrung> tumbleweed: ^
[12:40] <tumbleweed> bdrung: yeah why not (now that we have a test suiet, that'd be great)
[12:40] <bdrung> tumbleweed: the question is where who should own the PPA?
[12:41] <bdrung> tumbleweed: ubuntu-dev?
[12:41] <tumbleweed> that doesn't sound ideal. I have no problem with you owning it, otherwise a dedicated team?
[12:42] <bdrung> tumbleweed: didicated team? proposals?
[12:43] <tumbleweed> udt-dailies / udt-developers
[12:44] <find> do u know what can i join ubuntu term?
[12:46] <ari-tczew> find: join what?
[12:48] <find> translate
[12:55] <dpm> find, which language do you want to translate into?
[12:55] <dpm> you can find the team for your language here:
[12:55] <dpm> https://translations.launchpad.net/+groups/ubuntu-translators
[12:56] <tumbleweed> dpm: whois suggests china. find: https://wiki.ubuntu.com/Translations/Contact/Teams (#ubuntu-cn-translators?)
[12:56] <dpm> ubuntu-l10n-zh-cn
[12:56] <find> OK,i go to see it,thank u very much
[12:57] <dpm> find, np, you can go to https://launchpad.net/~ubuntu-l10n-zh-cn and you'll find how to contact them there
[13:00] <bdrung> tumbleweed: {debupstream}~~bzr{revno} as debian version?
[13:00] <tumbleweed> ~~ seems overkill but fine.
[13:01] <find> i am find it already,thank u very much
[13:02] <bdrung> tumbleweed: it should be lower than {debupstream}~maverick and {debupstream}~ppa
[13:02] <bdrung> ok, changing to one ~
[13:03] <tumbleweed> I tend to use ~daily+bzr{revno}
[13:03] <bdrung> tumbleweed: let's see if it works: https://code.edge.launchpad.net/~udt-developers/+recipe/daily
[13:04] <bdrung> tumbleweed: that's even better
[13:09] <happyaron> Should I file sync request when Debian has a new version of a package?
[13:10] <Laney> it will be autosynced if the package is a) not modified in Ubuntu and b) has been uploaded to unstable
[13:10] <Laney> otherwise yes sync if it can and should be synced
[13:11] <coolbhavi> happyaron, yes but make sure you follow https://wiki.ubuntu.com/SyncRequestProcess
[13:11] <happyaron> thank you, :)
[13:46] <sagaci> so if one wanted to get a new package into ubuntu, the most sensible way (in the majority of cases) is to go through Debian, right?
[13:47] <sagaci> and ubuntu packaging is mostly maintaining stuff rather than introducing new packages, in a nutshell
[13:49] <Laney> yes that is fair to say
[13:50] <sagaci> thanks, trying to get my head around some of it
[13:51] <happyaron> AFAIK, debian ftp-master says they won't accept new package from NEW before squeeze is out.
[13:51] <Laney> not true
[13:52] <happyaron> they randomly accept some packages, but no guarantee.
[13:53] <Laney> there are never guarantees, but i have asked for several packages to be accepted and they always have
[14:40] <bdrung> tumbleweed: shouldn't ubuntutools/test/test_help.py be in ubuntutools/test_help.py?
[14:42] <bdrung> tumbleweed: why should we add 'a1' to the version number if the target is UNRELEASED?
[14:43] <bdrung> tumbleweed: http://paste.debian.net/103007/
[14:48] <tumbleweed> bdrung: you could say that about all te test suites. a1 is like ~1 in python terms. Aah nice. BTW if you run it with python2.7 it'll tell you when it's skipping things.
[14:50] <bdrung> tumbleweed: you still don't explain why you add 'a1'? why should the version modified?
[14:52] <tumbleweed> off-topic for that branch, I just saw that code and thought, if we are determining the version from the changelog, we should differentiate prereleases. Doesn't really matter at all, though.
[14:54] <bdrung> tumbleweed: i am against this change. the daily will have an other version anyway
[14:56] <tumbleweed> bdrung: reverted
[14:58] <bdrung> tumbleweed: get-build-deps runs sudo
[14:58] <tumbleweed> as do a few others
[14:59] <bdrung> tumbleweed: that let's the test fail and shouldn't be for --help
[15:00] <tumbleweed> yes. I've blacklisted most of the others, I'll sort it out now.
[15:06] <surfzoid> Hi folk
[15:06] <surfzoid> is "grub-reboot" have an GUI/FE ?
[15:07] <surfzoid> because i just finish to wrote one :-) http://surfzoid.free.fr/freevbsoft/RebootInFE/
[15:14] <aboudreault> hi, is Karmic still supported for security updates?
[15:18] <bdrung> aboudreault: yes
[15:18] <aboudreault> it's 2 years the non-lts support?
[15:19] <ebroder> 18 months
[15:19] <aboudreault> I see
[15:20] <aboudreault> thanks
[15:53] <bdrung> tumbleweed: 404main: sys.exit(0) only if sys.argv[1] in ('help', '-h', '--help')
[15:53] <bdrung> merge-changelog:sys.exit(0) -> sys.exit(exit)
[16:16] <lostern> What are the environment variables that are used to search include and lib dirs?
[16:19] <lostern> Never mind, I should have looked in the gcc man page first.
[16:20] <RoAkSoAx> dude!! /win 3
[16:21] <RoAkSoAx> lol
[16:55] <hakermania1> 199 people in room :)
[16:58] <bdrung> hakermania1: and 299 in #ubuntu-dev
[16:59] <bdrung> #ubuntu-devel
[17:00] <hakermania1> bdrung: Haha, coincidence :)
[17:01] <udienz> Dang.. my bad.. i've uploaded dsc reather than debdiff :)
[17:02] <coolbhavi> udienz, saw that this morning :)
[17:02] <bdrung> tumbleweed: please let me know once one of your two branches is ready for merge
[17:03] <udienz> coolbhavi, hehehe, i'm so sleepy this day.. and also my connections is very bad
[17:04] <coolbhavi> udienz, :)
[17:05]  * udienz uploading now
[17:05] <udienz> bug 692457
[17:07] <ebroder> apw: --verbose
[17:07] <bdrung> udienz: you could drop ".dcs" from the debdiff name next time
[17:10] <udienz> bdrung, ok, my bad.. :) i was very confused this day, last "dsc" files uploaded 5 times transfered to lp with 3kbps :(
[17:10] <udienz> all errors
[17:12] <hakermania1> udienz: You take several errors: http://revu.ubuntuwire.com/p/ttf-indonesian Why you let it like this and you don't correct them?
[17:12] <udienz> hakermania1, license problem.
[17:13] <udienz> upstream author doesn't reply my emails
[17:13] <hakermania1> udienz: :/
[17:15] <udienz> hakermania1, how about your package?
[17:15] <hakermania1> udienz: Waiting for 3rd review :)) No errors at all :)
[17:23] <bdrung> udienz: you should subscribe ubuntu-sponsors again.
[17:24] <udienz> bdrung, Done
[17:31] <tumbleweed> bdrung: thanks, btw you changed indentation of line 117 of 404main during the tab -> space conversion. I guess I'd better look for more of those
[17:34] <bdrung> tumbleweed: thanks for detecting
[17:34] <tumbleweed> code after an exit() is suspicious :P
[17:35] <bdrung> tumbleweed: fix pushed
[17:37] <bdrung> tumbleweed: can you get your config-681693 branch ready for merge?
[17:41] <tumbleweed> bdrung: looking at it. test-help should be mergeable, waiting for your ACK
[17:42] <bdrung> tumbleweed: merge-changelog:sys.exit(0) -> sys.exit(exit)
[17:42] <tumbleweed> add-patch needs manpage, setup.py + copyright entries, and a BLACKLIST entry
[17:43] <bdrung> tumbleweed: tell that mvo
[17:43] <tumbleweed> thanks
[17:44] <bdrung> tumbleweed: can setup.py create symlinks?
[17:45] <tumbleweed> well, it's python, it can do anything. Don't know of any distribute mechanism for doing them though.
[17:46] <ari-tczew> could someone look on bug 540514 ? I really don't understand what's the problem
[17:47] <bdrung> ari-tczew: you can ask for build log or the malformed control file
[17:48] <coolbhavi> bdrung, +1 and isnt the original maintainer field in source stanza?
[17:49] <ari-tczew> bdrung: why? Version: 2.4.8-2ubuntu1
[17:58] <tumbleweed> bdrung: I pushed a fix. config-681693 looks ok to me. There's also import-bfd-681693 (the beginning of one branch per script)
[18:00] <bdrung> tumbleweed: pushed?
[18:00] <tumbleweed> bdrung: test-help r886
[18:01] <bdrung> k, got it now
[18:09] <bdrung> tumbleweed: merged (not yet pushed)
[18:10] <tumbleweed> thanks. I'll be picking away at more scripts
[18:20] <bdrung> tumbleweed: pushed
[18:21] <tumbleweed> bdrung: aah, thanks. I forgot about the related BD changes
[18:23] <bdrung> tumbleweed: re config branch: my three points are still open: 1) what speaks against using Logging.warning instead of printf?
[18:24] <tumbleweed> bdrung: oh, didn't push r914, pushed.
[18:27] <bdrung> tumbleweed: you use logger instead of ubuntutools.logger
[18:29] <bdrung> tumbleweed: can we please use only one?
[18:29] <tumbleweed> now I understand the confusion last night, I thought you meant logging :P
[18:29] <bdrung> tumbleweed: i failed in configuring logging to look like  ubuntutools.logger
[18:31] <tumbleweed> yeah no need to build of logging if it's more complex than reinventing it
[19:16] <bdrung> tumbleweed: so you can throw logging out again and use ubuntutools.logger
[19:16] <bdrung> (which doesn't require to be initialised)
[19:17] <tumbleweed> bdrung: yeah I'm busy with it
[19:17] <bdrung> tumbleweed: btw, our daily build is up and running: https://code.edge.launchpad.net/~udt-developers/+archive/daily
[19:25] <tumbleweed> bdrung: ok, there we are (r916). BTW I looked at add-patch, it's not ready to be install (breaks with quilt, haven't tried anything else). I'll prod mvo when he turns up
[19:29] <ari-tczew> could anyone look on changes in https://launchpad.net/ubuntu/+source/libhdhomerun/20100828-0ubuntu1
[19:29] <ari-tczew> for me it looks like horrible bad sponsorship
[19:30] <ari-tczew> d/copyright changed, lack of mention in d/changelog
[19:33] <tumbleweed> ari-tczew: looks like it went from an ubuntu-only package to a debian sync, and back to the ubuntu one
[19:33] <ebroder> Probably means the sync was wrong
[19:34] <ari-tczew> omg...
[19:34]  * ari-tczew guess that procedures and policies are only for community, not stricte Canonical developers.
[19:35] <ari-tczew> tumbleweed, ebroder: what's next with that package? merge is available.
[19:36] <tumbleweed> ari-tczew: if the fork is intended to be permanent, it should be sync black-listed.
[19:37] <ari-tczew> I see very good flow of information...
[19:40] <ebroder> ari-tczew: It looks like superm1 is the primary maintainer for that package. Which makes sense since he does a lot of Mythbuntu stuff. Maybe you should try to get in touch with him since he seems to have fairly clear intentions around the package
[20:36] <bdrung> tumbleweed: merged and pushed
[20:38] <tumbleweed> bdrung: two more scripts in separet branches, I'll do a couple more now.
[20:41] <bdrung> tumbleweed: these tools needs to be converted to PEP8: requestsync, ubuntu-build, ubuntutools/lp/udtexceptions.py, ubuntutools/requestsync/*.py - do you want to do it?
[20:41] <bdrung> tumbleweed: pushed again
[20:46] <tumbleweed> ack-sync looks good. OK I'll convert those.
[20:47] <bdrung> tumbleweed: you can do it directly in trunk
[20:50] <bdrung> tumbleweed: BACKPORTPACKAGE_LPINSTANCE in import-bfd branch
[20:56] <tumbleweed> the cost of getting distracted
[20:57] <tumbleweed> both pushed
[20:59] <bdrung> tumbleweed: merged import-bfd
[21:03] <bdrung> tumbleweed: the indentation of optParser should be improved (lp-set-dup)
[21:03] <tumbleweed> bdrung: the alternative is to split long strings (line length)
[21:04] <bdrung> tumbleweed: what do you prefer?
[21:06] <tumbleweed> bdrung: I change style as appropriate (also see the heavily-indented bits of the config-parsing code.
[21:11] <bdrung> tumbleweed: the lines are too long even with the short indentation.
[21:12] <bdrung> tumbleweed: the scripts need PEP8 conversion
[21:15] <tumbleweed> bdrung: can you clarify both of those? Which lines, which scripts?
[21:15] <bdrung> tumbleweed: the script you where you converted tabs to spaces
[21:15] <bdrung> http://www.python.org/dev/peps/pep-0008/
[21:16] <bdrung> tumbleweed: see Maximum Line Length example
[21:16] <tumbleweed> bdrung: yes, my editor is configured to highlight long lines. I just did a pure tab-to-space conversion.
[21:17] <tumbleweed> I decided to tidy them up in a second pass
[21:18] <bdrung> tumbleweed: k, that's a good idea (too see the tidy process)
[21:56] <hakermania> if any reviewer has time please take a look at wallch at REVU thx in advance! http://revu.ubuntuwire.com/p/wallch
[22:00] <superm1> ari-tczew, afaik everything should be documented in bzr for changes
[22:05] <bdrung> tumbleweed: pushed
[22:06] <bdrung> tumbleweed: "debian_srcpkg = ubuntutools.requestsync.mail.getDebianSrcPkg" -> wrong indented
[22:08] <tumbleweed> bdrung: least bad option
[22:09] <tumbleweed> pylint can drive you mad btw, it always complains about *something* :)
[22:13] <bdrung> tumbleweed: i know. i fix only some of the complains
[22:39] <bcurtiswx> would someone be able to explain this error to me? src/Makefile.am: object `empathy-accounts-dialog.$(OBJEXT)' created both with libtool and without
[23:00] <bdrung> tumbleweed: merged lp-set-dup-681693
[23:08] <RAOF> bcurtiswx: I've not seen that error before, but it *looks* like you've got a rule which generates empathy-accounts-dialog.(o? so?), which libtool will also be generating, and it's complaining.
[23:09] <bdrung> tumbleweed: should i move libapt-pkg-perl, libwww-perl, python-magic, python-soappy from recommends to depends?
[23:09] <RAOF> I'd guess therefore that something is defining a rule for empathy-accounts-dialog.so, since that's what libtool should be generating.
[23:10] <bcurtiswx> RAOF, hmm, weird, because one of my patches requests a function from it and doesn't see it, so i added it to recognize it
[23:11] <RAOF> bcurtiswx: Care to pastebin the Makefile.am?
[23:11] <bcurtiswx> RAOF, yeah I can.  Gimme a sec
[23:14] <bdrung> tumbleweed: we should write the dependencies for every script directly into the scripts
[23:26] <bcurtiswx> RAOF, seems ive found some other things.  I will get back to ya later :)
[23:26] <RAOF> bcurtiswx: Heh.  No problem.
[23:46] <tumbleweed> bdrung: I think recommends is probably correct for them. Of course it's helpful if scripts can print what they are missing rather than die horribly, but that's a biggish job.