`bzr ci --fixes blah-blah`: how it supposed to work?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexander Belchenko wrote:
> I starting to use trac for my bzr-controlled projects.
> One thing that I don't understand, and documentation
> don't tell me anything useful is the '--fixes' flag
> of bzr commit command. And `bzr help bugs` is not
> very useful, as well ;-)
> 
> I try to imagine why for it might be useful, but I don't
> understand how it supposed to work?
> For launchpad bugs the string lp:12345 is works,
> as I remember.
> 
> But, what I do wrong in following session:
> 
> $ bzr ci --fixes=trac:15
> bzr: ERROR: Unrecognized bug trac:15. Commit refused.
> 
> ?
> 
> [µ]

You have to set things up so that it knows what URL you mean when you say "trac:".

So in ~/.bazaar/bazaar.conf you set up something like:

trac_project_url = http://my/project/trac/

And then you use:

bzr ci --fixes=project:15

Which is related to
http://my/project/track/ticket/15

I do agree that the documentation should be improved.

I went ahead and created a bug:
https://bugs.launchpad.net/bzr/+bug/120050

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGbsBaJdeBCYSNAAMRAiIiAJ43TX2zCXfr6R0HUkyK1yS2wrULdQCeIqxp
x8SHv/Com9nL0ewi/Pnid0Y=
=NsbK
-----END PGP SIGNATURE-----