This morning I ran my weekly update and encountered the error "bzr.eclass could not be found by inherit()" for several of my ebuilds. I managed to track the problem down to a specific commit from a few days ago: https://gitweb.gentoo.org/repo/gentoo.git/commit/eclass?id=79a3d7f7c3ca5f1af64f0d5e60cd490ca62f3c05 I would like to request that this commit be reverted. Personally I have several live ebuilds that require this eclass due to the upstream source only being available via Bazar VCS. This is also the VCS used by Ubuntu and Launchpad, so anyone creating an ebuild that pulls from there would also require it. At the end of the day, Bazar is a VCS that exists (even if Gentoo specifically doesn't use it) so I feel that removing functionality just because it is "unused" is not a great idea.
From Gentoo ebuild repo POV, this bug is resolved/invalid. Last-rites mail sent more than 30 days ago and eclass declared @DEAD at the same time, no consumers, especially, it does not do anything since dev-vcs/bzr package is gone as well. It was a broken, unmaintained, stuck-with-py27 package and it is not coming back. And no one bothered to package breezy, what supposedly was a py3 fork of bzr.
I guess if we want to keep this bug open it should depend on the corresponding New Package request.
Reassigning to myself (as previous maintainer of the eclass). (In reply to Andreas Sturmlechner from comment #2) > I guess if we want to keep this bug open it should depend on the > corresponding New Package request. Right. This bug isn't actionable unless we'll have a package (and a maintainer) for the Bazaar replacement.
Eclass posted to gentoo-dev-mailing list: https://archives.gentoo.org/gentoo-dev/message/31562e4d48322cacdde73bbc08c7419d
Eclass reinstated. Closing.
