Paul Wise

@donnemartin this issue has now come up in [Debian#1005858](https://bugs.debian.org/1005858). It would be great if you could decide on switching to `git some` or keeping `gh`.

Here is an example G++ command-line in case that helps track down the issues: ``` c++ -Ilibots.a.p -I. -I.. -I../include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++11 -g -O2 -fdebug-prefix-map=/build/opentype-sanitizer-8.1.1+dfsg.1=....

From the warnings it sounds like some of the code should use size_t for types instead of int.

@jelmer mentioned on the #breezy IRC channel that most of the changes are to the lower layers of the API. In particular breezy.generate_ids has moved to breezy.bzr.generate_ids so that is...

PS: Breezy itself has a git-remote-bzr script but it is not very compatible with this version and it is not as good as this version. -- bye, pabs https://bonedaddy.net/pabs3/

I have a breezy branch in my fork of git-remote-bzr. I don't remember if it fully works with a version of breezy that supports Python 2 but I expect that...

I did some more porting to the Python 2 version of breezy, but the port isn't yet complete.

Forwarded from https://bugs.debian.org/729768

I am still interested in having this compatibility layer as it would be useful, once git-remote-bzr works again after #27 and #26 are solved. -- bye, pabs https://bonedaddy.net/pabs3/

@jnahmias asked the Debian fonts team to help out with the situation, I'm responding in that capacity. Personally, regardless of the provenance/copyright/license situation, I would always suggest to remove all...