circular build dependency between ubuntu-release-upgrader and update-manager

[anarcat]

trying to build ubuntu-release-upgrader from scratch on another debian platform gives an impossible build dependency:

Source: ubuntu-release-upgrader
Section: admin
Priority: optional
Maintainer: Ubuntu Developers <email address hidden>
Build-Depends: debhelper (>= 9),
               python3-all,
               python3-distutils-extra,
               python3-apt (>= 0.8.5~),
               lsb-release,
               python3-update-manager,
               apt-clone (>= 0.2.3~ubuntu2)

Source: update-manager
[...]
Package: python3-update-manager
Architecture: all
Section: python
Replaces: update-manager-core (<< 1:0.163)
Breaks: update-manager-core (<< 1:0.163)
Depends: ${python3:Depends},
         ${misc:Depends},
         python3-apt (>= 0.8.5~),
         python3-distupgrade,
         python3-launchpadlib,
         lsb-release

python3-distupgrade is a binary package of ... ubuntu-release-upgrader! so to build ubuntu-release-upgrader, one needs python3-update-manager, which cannot be installed because it depends on the python3-distupgrade binary package, provided by the ubuntu-release-upgrader source package..

it seems to me the DistUpgrade library could be moved to python3-update-manager or python3-apt, to resolve this loop.

[Ark74 (ark74)]

I'm new to building, and packaging and I have noticed this too, is this a bug or some advance method to achieve this?

@anarcat did you ever got this sorted out?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[anarcat (anarcat)]

> @anarcat did you ever got this sorted out?

No, I gave up on this project.