-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ned Deily wrote:
> In article <[email protected]>, > Phil Dobbin <[email protected]> wrote: >> I've just run selfupdate & got, amongst other things: >> >> `mercurial 2.2.3_0 < 2.3_0` >> >> so I ran upgrade outdated but now when I cd into my hg vim repo & run >> `hg pull` it throws the error: >> >> `$ hg pull >> abort: No module named repo!` > > hg 2.3 is working fine for me. Check your ~/.hgrc file and any > repo-specific .hg/hgrc files for the stray use of the word "repo", for > example in the [extensions] section. And make sure you don't have any > PYTHON* environment variables set (like PYTHONPATH) that might be > causing a problem. Thanks, Ned. It was `hggit/gitrepo.py` (the hggit extension) that was causing the problem. In fact, it's been a problem more than once on several different occasions. Cheers, Phil... - -- But masters, remember that I am an ass. Though it be not written down, yet forget not that I am an ass. Wm. Shakespeare - Much Ado About Nothing -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQHfqfAAoJEKuJdOaOnmMJOJ4IAKSGT/YX34GQ0WhRduThGcsK VSDcXBt/DbWub8psKcVXZy982V5z7lEHfkUxTVkpeeBO0Zd2h0lZV0roBLm5rGr1 JDX0KGp74WZtwcnuky+/jUB4WUabho6g/EMM/eP+nbXfBBuupxZR8i/cgCn5abkI 1vRcsGYSmI0FA7yvi6AfHfOHl9JCLvGZ8JpbmbkKCtgM/EbrQCzrwVKDpP/9tb3y NbQALP/R7PQMAG14Wwkagdh85H7fUxWZRL2vWTrNo1KGTgJB0nvmJ42PgU8blPPb 8rP5PLo7LF/BKRvZjye5FZKaBT1QUyIadtWBXy2bb5Y8cdURroCUunb7Xy8rSA4= =4R11 -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-users
