> bzr (bazaar) FTBFS and is orphaned. > > I have a Python 3 replacement called breezy (brz) ready, but it has some > problems with remote repositories on Python 3.8, so I was not ready to build it, > obsolete bzr and have a broken alternative. > > However, bzr now also fails to install, so it cannot be any more broken than it > already is. I intent to build and ship half-broken breezy to obsolete > fully-broken bazaar sometimes this week. Shouldn't this be a change so it can be more easily found for issues etc than just on devel@ list and go through the right process? > I'm working with upstream of breezy to fix the problem. > > Links: > > FTBFS https://bugzilla.redhat.com/show_bug.cgi?id=1734995 > FTI https://bugzilla.redhat.com/show_bug.cgi?id=1758870 > breezy https://bugzilla.redhat.com/show_bug.cgi?id=1754964 > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
