[Bug 988296] Re: bzr check awfully slow checking repository in valid_repo

2012-04-26 Thread Per Ångström
** Description changed: After upgrading from Ubuntu 10.10 to 11.04 I'm having trouble running meld on some repositories: meld seems to freeze up while bzr runs at 100 % CPU until I kill it. After some digging I find that it's the invocation of brz check that seemingly runs into an endless

[Bug 988296] Re: bzr check awfully slow checking repository in valid_repo

2012-04-26 Thread Per Ångström
OK, I have updated the bug description and created a packaging branch for natty: lp:~autark/ubuntu/natty/meld/meld-fix-988296 I have not yet proposed for merging. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 988296] Re: bzr check awfully slow checking repository in valid_repo

2012-04-25 Thread Per Ångström
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988296 Title: bzr check awfully slow checking repository in valid_repo To manage notifications about this bug go to:

[Bug 988296] Re: bzr check awfully slow checking repository in valid_repo

2012-04-25 Thread Julian Taylor
I'm guessing with revision 29 you mean the packaging branch, meld itself uses git. So this is fixed in ubuntu precise. If you want you can create a packaging patch for natty and oneiric, please follow this procedure: https://wiki.ubuntu.com/StableReleaseUpdates I can assist if you need help in

[Bug 988296] Re: bzr check awfully slow checking repository in valid_repo

2012-04-25 Thread Per Ångström
Adding a minimal patch to solve this bug for natty, taken from precise. ** Patch added: patch-988296-natty-updates.diff https://bugs.launchpad.net/ubuntu/+source/meld/+bug/988296/+attachment/3103755/+files/patch-988296-natty-updates.diff -- You received this bug notification because you are

[Bug 988296] Re: bzr check awfully slow checking repository in valid_repo

2012-04-25 Thread Julian Taylor
it would need to be a patch to the package and the bug description needs to be filed out appropriately. I consider it low importance as it only affects bzr on larger repositories and can be worked around. Please see https://wiki.ubuntu.com/PackagingGuide/Recipes for some guides on how to create