On Tue, Feb 22, 2011 at 03:19:52PM -0700, Michael Chaffin wrote: > On Tue, Feb 22, 2011 at 3:13 PM, W. Trevor King <[email protected]> wrote: > > What is the output of `be --full-version`? Specifically, you'll want > > a revision that contains the patch, currently either > > 0d9ec7c727ff624ee1905831e806cab8c9e65537 > > or > > 1ab82c10019f16a24fe93aae85dc44e99c5b85d5 > > ... > C:\XXX>be --full-version > 1.0.0 > revision: 0d9ec7c727ff624ee1905831e806cab8c9e65537 > ...
Hmm, that is indeed the patched version. On Tue, Feb 22, 2011 at 02:57:09PM -0700, Michael Chaffin wrote: > I then tried to install again and still received the same error. The goal of that patch was to not execute the failing code, so something strange is going on here. Could you post the full traceback with the new BE? Could you also post the output of `bzr version`. These will probably be pretty boring, but until I can reproduce your error I can't do much to fix it... Thanks, Trevor -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgpXzPS6aFk2x.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
