[11:41] <wgz> hi AuroraBorealis.
[11:42] <AuroraBorealis> sup
[11:43] <wgz> if you've got some time, can you try some debug things on meliae?
[11:43] <AuroraBorealis> sure!
[11:44] <wgz> okay, what's your current diff on the meliae install?
[11:44] <wgz> I want to go back and work out why the IO wasn't functioning without the hack first.
[11:45] <AuroraBorealis> that might be difficult cause i downloaded the tarball
[11:45] <AuroraBorealis> any suggestion on how to do it? o.o
[11:47] <AuroraBorealis> can i somehow diff it against the original tarball?
[11:48] <wgz> hm.
[11:49] <wgz> maybe step one should be working out why your setup is borked so you can't branch lp projects then.
[11:49] <AuroraBorealis> i think i can do that now
[11:50] <AuroraBorealis> its just that one day launchpad was being iffy
[11:50] <wgz> okay, branch a fresh lp:meliae and delete the currently installed one from Python27\Lib\site-packages\meliae
[11:51] <wgz> I've got the hacks here anyway so we can re-apply them as needed :)
[11:52] <AuroraBorealis> k did that
[11:54] <wgz> okay, run setup.py on that, then the testsuite bit we got to crash and see if that's still happening.
[11:56] <AuroraBorealis> what was the command to build the test suite again?
[11:59] <wgz> http://irclogs.ubuntu.com/2011/10/02/%23bzr.html#t11:57
[12:00] <wgz> there's actually a script to run the tests I realised after, but what we did before works too.
[12:01] <AuroraBorealis> yeah crashes python still
[12:02] <wgz> okay, great.
[12:03] <wgz> well, not great, but you get the idea.
[12:03] <AuroraBorealis> yes!
[12:07] <wgz> okay, instructions: <http://paste.ubuntu.com/704848/>
[12:07] <wgz> ....I should have wrapped some lines
[12:07] <wgz> ask if anything doesn't make sense
[12:08] <AuroraBorealis> k
[12:08] <wgz> otherwise, paste me things as you go
[12:09] <AuroraBorealis> where is python.dll?
[12:11] <wgz> possibly in C:\Windows\system32\python27.dll but adapt for win64
[12:11] <wgz> something like process explorer will tell you exactly which dll files get loaded if you run python the import meliae.scanner
[12:11] <AuroraBorealis> yeah its in SysWOW64
[12:12] <wgz> if that has different C runtimes loaded it's a sign something's gone wrong
[12:13] <wgz> ^*then import
[12:13] <AuroraBorealis> hmm
[12:13] <AuroraBorealis> "link.exe: the program can't start becamse mspdb80.dll is missing"
[12:14] <AuroraBorealis> let me google this...
[12:15] <wgz> you probably need to run your vcvars bat file first
[12:17] <wgz> though the fact that says 80 not 90 makes me worry.
[12:17] <AuroraBorealis> well
[12:17] <AuroraBorealis> that was with the 9.0 sdk
[12:18] <AuroraBorealis> ok that worked
[12:18] <wgz> I have Microsoft Visual Studio 8\Common7\IDE\mspdb80.dll - which isn't the right VS version for Python 2.7
[12:18] <AuroraBorealis> with running 9.0's vcvarsall
[12:18] <wgz> cool.
[12:19] <wgz> wait, I also have it in  Microsoft Visual Studio 9, no worries.
[12:19] <AuroraBorealis> python's dumpbin
[12:19] <AuroraBorealis> http://paste.ubuntu.com/704851/
[12:20] <wgz> you need the /IMPORTS flag
[12:20] <wgz> dumpbin /IMPORTS python27.dll
[12:27] <AuroraBorealis> scanner dump: http://paste.ubuntu.com/704853/
[12:27] <AuroraBorealis> pythondll: http://paste.ubuntu.com/704854/
[12:28] <wgz> okay, you see our problem there? :)
[12:29] <AuroraBorealis> compiling with 10 instead of 9?
[12:29] <wgz> yeah, _scanner is linked against a newer C runtime
[12:30] <wgz> really distutils shouldn't let that happen, but I'm guessing we can work around it easily enough
[12:30] <AuroraBorealis> can i force a version?
[12:30] <AuroraBorealis> cause the microsoft sdk installed both 9 and 10
[12:31] <wgz> yup, just looking to see how.
[12:31] <wgz> so, running meliae `setup.py build_ext --help" gives a bunch of options
[12:34] <AuroraBorealis> does build_ext actually put it in the sitelib folder?
[12:36] <wgz> by default it puts its output in a subfolder of ./build
[12:36] <wgz> then install moves the stuff to site-packages
[12:36] <wgz> so, start by deleting meliae from site packages again, and deleting the build folder under meliae
[12:37] <wgz> in fact, it may be worth clearing out all of site-packages and re-installing if every built extension has this problem
[12:38] <wgz> you can double-check by running dumpbin on other pyd files.
[12:38] <AuroraBorealis> k, let me check..
[12:42] <wgz> I wonder if the hacks we needed to get distutils to work in the first place were entirely correct
[12:43] <wgz> can you pastebin the contents of ..\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd maybe?
[12:44] <wgz> and run meliae `setup.py build_ext` and paste me the contents so we can see where it's linking the wrong thing
[12:44] <AuroraBorealis> http://paste.ubuntu.com/704860/ thats setenv.cmd
[12:46] <wgz> okay yeah, that's referencing "Microsoft Visual Studio 10.0"
[12:46] <AuroraAustralis> hmm
[12:47] <wgz> is there another .cmd as well? because that one isn't right.
[12:49] <wgz> would be annoying if it required actually installing an older SDK.
[12:50] <AuroraAustralis> this is setup.py build_ext
[12:50] <AuroraAustralis> let me look for another cmd
[12:50] <AuroraAustralis> and that seems to be the only .cmd file in that folder
[12:55] <AuroraAustralis> did i somehow make it use the 10 compiler?
[12:55] <wgz> well,
[12:56] <wgz> either that's just the wrong SDK version, and we need an older one
[12:56] <wgz> or we just need it to not set the paths to point at VS 10
[12:56] <AuroraAustralis> well i have a Microsoft Visual Studio 9.0 folder
[12:57] <wgz> yup, but running that SDK script makes distutils look at VS 10 instead, which it shoudln't
[12:57] <wgz> so, start by undoing the addition to vcvarsamd64.bat which added the call to that .cmd
[12:58] <wgz> we can then manually set the LIB, LIBPATH, and INCLUDE if needed
[12:59] <wgz> I suggest:
[13:00] <wgz> start a new cmd window, call that problematic cmd and do `echo %LIB%` and the same for LIBPATH and INCLUDE, and paste it
[13:01] <wgz> then we can copy that with corrections straight into a distutils conf file rather than messing the vcvarsamd64 at all.
[13:02] <AuroraAustralis> i dont seem to have a lib, libpath or include env variable as it just prints out %libpath% or whatever
[13:03] <wgz> hm, maybe run vcvars pre-edit and try?
[13:05] <AuroraAustralis> http://paste.ubuntu.com/704870/
[13:06] <AuroraAustralis> ran the vcvars in the 9.0 folder
[13:09] <wgz> hm, and if you then run the v7.1\Bin\SetEnv.cmd file?
[13:12] <AuroraAustralis> with calling the vccars64.bat file (which calls SetEnv.cmd) http://paste.ubuntu.com/704876/
[13:12] <wgz> okay.
[13:13] <wgz> so, if you have the 9.0 equivalent of those paths, we can just change the versions
[13:13] <wgz> eg C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\Lib\amd64 -> C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\Lib\amd64
[13:14] <wgz> and we can set them in setup.cfg rather than editing bat files
[13:14] <AuroraAustralis> there is a lib folder but no amd64 folder inside of it
[13:15] <wgz> meh, then this is our problem, and short of building python itself against 10.0 I'm not sure what the fix is.
[13:15] <AuroraAustralis> why did installing visual studio install 64 bit of 10 but not 64 bit of 9
[13:16] <wgz> this I don't know.
[13:18] <wgz> okay, I need to do some cooking, work out a way of getting the 64bit versions of the msvc9 runtimes, that would solve things.
[13:19] <AuroraAustralis> yeah
[13:19] <AuroraAustralis> i need to get to bed, i'll google around and see if i can get those
[13:37]  * AuroraAustralis reinstalls the windows 7 sdk
[13:37] <AuroraAustralis> hoping for magic
[13:46] <AuroraAustralis> the reinstall has defeated me
[13:46] <AuroraAustralis> going to bed, night
[16:56] <Pilky> is there anyone around with any experience getting bzr to work with Jenkins/Hudson for CI? I'm using the plugin they list but I'm getting errors when I try a build that says it can't find bzrlib
[17:06] <wgz> vila would be your man but he's not around currently.
[17:11] <Pilky> wgz: thanks
[18:29] <lifeless> Pilky: the plugin shells out to bzr
[18:30] <lifeless> Pilky: so if its not working, your bzr isn't installed correctly (e.g. you've installed it to ~/bin but PYTHONPATH isn't export) or something like that
[18:32] <Pilky> yeah, I had to mess around with the location as bzr is in /usr/local/bin on my machine as I used the Mac installer
[18:32] <Pilky> I think I might have got it now though, just required some messing around with settings
[19:53] <jelmer> 'morning
[19:53] <Noldorin> hi jelmer
[19:54] <jelmer> hi Noldorin
[20:01] <wgz> ...is it jelmer?
[20:02] <jelmer> 'evening wgz :)
[20:03] <wgz> are you somewhere far away currently? :)
[20:05] <jelmer> ah, heh
[20:05] <jelmer> no, I'm at home
[20:06] <jelmer> I'm used to saying 'morning around this time of day since thats when the Ozzies and Kiwis show up :)
[20:12] <fullermd> In my mind, it's always morning...
[21:25] <wgz> jelmer: did you get anything exciting back from PQM?
[21:25] <wgz> see the comment at the end of <https://code.launchpad.net/~gagern/bzr/bug869915-mkdir-quiet/+merge/78601>
[21:26]  * wgz bops ubot5 on the head