> Would you apply this patch? Uploaded...
> (I realise that you want db4.8 to go away, but it's still a > build-dependency of python2.6 and python2.7, which means that it still > shows up in many interesting cross-build chains. It would be nice if you have some spare cycles to help me find why the python2.7 build is failing when updated to db5.1. We ran some tests in the experimental to build with db5.1 on all archs and several architectures had a problem. Unfortunatelly I don't have a time to debug it now and may have a time in few months. So if you f.e. will have time after oneiric is out, it would be great help if you could help me with that. > db doesn't have this particular problem, but has a different one; > I'll need to investigate that separately.) Thanks for that. O. -- Ondřej Surý <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
