Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1205376 .
FWIW, part of the reason I've been using tortoisehg is that it used to
make bzexport work, when it didn't work on Windows with the hg that
shipped with mozillabuild. It's a little ironic that it's now
(apparently!) the other way around, especially that we broke what used
to work.
~ Gijs
On 16/09/2015 16:44, Gregory Szorc wrote:
I am pretty sure this is due to running hg from a py2exe based Mercurial
distribution on Windows. This is pretty much any hg on Windows that isn't
MozillaBuild 2.0. This includes TortoiseHg.
Things have or will break unless running MozillaBuild 2.0.
Please file a Developer Services product bug with the command output with
--traceback added to the args so we can track failing more gracefully.
On Sep 16, 2015, at 05:02, Gijs Kruitbosch <gijskruitbo...@gmail.com> wrote:
On Windows I still get "No module named Cookie!" after using ./mach
mercurial-setup to update vcs-tools.
~ Gijs
On 15/09/2015 22:52, Jeff Walden wrote:
The Mercurial extensions to interact with Bugzilla -- bzexport and the like --
have been updated to handle 2fa details. No need to add API key support
yourself, or use some sketchy dude's user-repo fix for the issue! ;-) (As at
least three people have considered, two people have actually done, tho only one
ended up landed upstream.)
Just run |./mach mercurial-setup| to pick up the new version with API key
support. Then add:
[bugzilla]
username = your-bugzilla-email-addr...@example.com
apikey = 0123456789ABCDEF0123456789ABCDEF01234567
to your ~/.hgrc, where the hex number is a Bugzilla API key generated on the
relevant Bugzilla prefs page, and pushes should work again.
("Mercurial had it first...")
Jeff
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
