[08:45] <geser> Laney: bug #1004845 or a different one?
[10:15] <Laney> geser: yes, I found that
[10:23] <tumbleweed> great python-crypto is about to migrate to debian testing. /me files an RC bug
[10:24] <tumbleweed> oh, it has
[10:44] <geser> looks like the fix for bug #997464 made the IV madatory (unlike optional as mentioned in the documentation)
[10:54] <tumbleweed> geser: looks like the commit intended to make it mandatory for CFB https://github.com/dlitz/pycrypto/commit/411f60f58cea79f7e93476ba0c069b80a2a4c1a0
[10:54] <tumbleweed> which makes sense. CFB uses an IV
[10:55] <geser> and using an IV matches the example in the python file but not the documentation
[10:56] <geser> https://github.com/dlitz/pycrypto/blob/761eb61d2eee8e18e63812ac207d671b2a026eca/lib/Crypto/Cipher/AES.py
[10:57] <geser> https://www.dlitz.net/software/pycrypto/api/current/Crypto.Cipher.AES-module.html#new
[11:13] <geser> l3on: are you planing to merge grass?
[11:16] <geser> a crash in dh_python2? can someone familiar with dh_python2 take a look at https://launchpadlibrarian.net/106081123/buildlog_ubuntu-quantal-amd64.magics%2B%2B_2.14.11-1_FAILEDTOBUILD.txt.gz
[11:20] <tumbleweed> geser: nice
[11:21] <jtaylor> noo magics++ that thing takes hours to build :(
[11:22] <geser> 30min on the buildds till that crash
[11:23] <jtaylor> ok 30 min, its still so long I don't really want to look at it :)
[11:23] <geser> start your pbuilder and go eat (or do something else) :)
[11:24]  * tumbleweed takes a guess as to the casue, while waiting for the build
[17:20] <tumbleweed> geser: the magics++ issue is that it calls dh_python2 twice
[17:20] <tumbleweed> and the second time it encounters the broken symlink that it left behind after the first run
[17:20] <tumbleweed> yay for maintainers who can't drive dh
[17:20] <jtaylor> dh_python2 shouldn't crash if run twice
[17:21] <jtaylor> or leave behind broken symlinks
[17:21] <tumbleweed> I don't think anything requires dh_ tools to be idempotent
[17:21] <tumbleweed> it's fairly common to do mv in builds
[17:21] <tumbleweed> it leaves behind a broken symlink becasue it renames .so.0.0.0 to .so
[17:22] <tumbleweed> (autotools doesn't know that python extensions aren't usefully versioned)
[17:22] <tumbleweed> but yes, it probably should cleanup the .so.X too
[17:22] <jtaylor> it doesn't happen in debian due to python2.6?
[17:23] <tumbleweed> haven't actually figured out why it doesn't happen on debian yet. /me plays some more
[17:45] <dupondje> The Developer Membership Board will consider a maximum of two applicants per meeting — if the agenda already lists two applicants for the next meeting, please attend the next free date (meetings are held every two weeks).
[17:46] <dupondje> https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda
[17:46] <dupondje> looks like there are 2 applications already ...
[17:46] <dupondje> but is it 2 or 3 now ? :)
[17:56] <tumbleweed> dupondje: correct. jbicha and negronjl got there first
[18:01] <dupondje> and no date for next meeting it seems
[18:01] <dupondje> gotto wait a bit then :)
[18:03] <tumbleweed> dupondje: add 2 weeks
[18:54] <dupondje> hmz crap, thats the 18'the, then i'm abroad :s
[19:04] <tumbleweed> dupondje: + 2 weeks again?
[19:25] <Rcart> #join ubuntu-classroom-es
[19:25] <Rcart> sorry  :X
[22:31] <bobweaver> hello there are there any plans for Ubuntu Developer Week coming up later on this year ? I looked at the wiki and I can not seem to find anything thanks as always for your time :)
[23:53] <geser> bobweaver: there is usually one around each release. dholbach might know when the next UDW is