Due to a glitch in their release process, bzr 1.15 does not contain any of the C files used to accelerate Bazaar's performance critical sections. [It's something to do with them not having run pyrex to generate this C code by accident before rolling this tarball. Meanwhile I do have pyrex installed but our ebuild (quite reasonably) doesn't seem to invoke it. I'm not sure if that's something we should look into; if there habbit is normally to generate such code themselves and ship it, then I don't think we need to mess with it] I encouraged them to do an immediate micro release; Martin agreed promptly that this would be appropriate, but they have a civilian volunteer doing their release management and a bugfix tarball hasn't happened yet. So I recommend =dev-util/bzr-1.15 be package.masked; we'll have to wait for 1.15.1 to be released unfortunately. That should be fine for ~arch as soon as it's out, but in the mean time people should stick with 1.14.1 AfC
Thank you for report Andrew. Masked for now.
FWIW, bzr-1.15.1 was released today <http://article.gmane.org/gmane.comp.version-control.bazaar-ng.announce/227>. It's also in my overlay. IMHO though, I'm not sure that the lack of .c files should be considered a package.mask-able offense. The package doesn't *break* if the C files aren't there, it's just slower.
Thank you, Mark. Well masking does no harm too but forces out users use faster package. In any case new version added to the tree.
