Moving Bugzilla to git?

Gervase Markham gerv at
Fri Oct 25 12:08:25 UTC 2013

On 24/10/13 21:09, Frédéric Buclin wrote:
> for your information, we stopped using CVS and moved to bzr for GCC
> Bugzilla only *5 months* ago, see
> It wasn't because I
> didn't want to move to bzr earlier, but because I *technically*
> couldn't.

Reading that bug, it looks like the issue was that the server couldn't
run bzr because the Python version was too old. (There were also issues
with upgrading Bugzilla, but those are separate - a VCS change should
IMO be done between two copies of Bugzilla which are identical.)

Do we know what dependencies git has, and whether it runs OK on older
Linux distros? Can someone produce a statically-linked git binary that
runs everywhere?

> Now the migration is done, GCC Bugzilla is running 4.4.1, and
> I don't expect to have to move to git to upgrade to another 4.4.x
> release.

I realise that moving to git is some work, but why do you link it to
upgrading to another release? Using instructions like: , you could
move "sideways" to the same version but on git, in not too much time.
Couldn't you?

dev-apps-bugzilla mailing list
dev-apps-bugzilla at

More information about the developers mailing list