Cant build snaps with bazaar/breezy on core22

[Sameer Sharma]

Although i had reported this in breezy nothing good came out, as asked in breezy bug tracker i did upgrade to latest breezy using pip and virtual env but still launchpad build service use older breezy or bazaar variant are crashing thus failing the snap builds, i hope this looked upon and i believe fixes must be backported to jammy since using latest breezy from pip has no effect whatsoever.

Build log--> https://launchpadlibrarian.net/677508910/buildlog_snap_ubuntu_jammy_amd64_xdman_BUILDING.txt.gz

Also snapcraft remote-build is surprisingly ok ? i believe its adopting the latest breezy natively installed ?

[Sameer Sharma (sameersharma2006)]

Bug in breezy, got reply suggesting to use latest breezy, did but has no effect --> https://bugs.launchpad.net/brz/+bug/2027888

[Sameer Sharma (sameersharma2006)]

Things to consider:

1) Completely Removed breezy installed from jammy repo locally along with its libs.

2) Using latest breezy via pip and virtual env

3) Snap build fails only if using launchpad build service.

4) snapcraft remote-build works fine.

5) Pushed breezy commits to launchpad inside the virtual env.

[Colin Watson (cjwatson)]

This would have to be fixed in Ubuntu's breezy package. Launchpad builds just install it from Ubuntu - we don't control anything else about it.

snapcraft remote-build creates a temporary git repository under the covers, which is why it's unaffected.

[Jelmer Vernooij (jelmer)]

FWIW breezy 3.3.4 has the fix