Re: Bug#908908: turn lvm2-dbusd Architecture: all
Hi Bastian,
On Sun, Jul 26, 2020 at 01:38:02PM +0200, Bastian Blank wrote:
> On Sat, Sep 15, 2018 at 09:01:02PM +0200, Helmut Grohne wrote:
> > * There is a longer dependency cycle between lvm2 (via systemd) through
> > python3. Turning lvm2-dbusd Architecture: all means that all of the
> > python depends can be moved to Build-Depends-Indep solving the cycle.
>
> There is a clear build-dep cycle between lvm2 and systemd, via
> cryptsetup. Not sure what a possible cycle via python3 would be.
Yes, there is. However, systemd has a build profile to break that
particular cycle.
We do bootstrap without python these days. Cross building Python
extensions is still too unreliable to rely on during architecture
bootstrap. Most of the relevant packages have split out their python
bindings via build profiles or b-d-i. lvm2 needs this at least for the
cross bootstrap even after resolving any remaining cycles.
Even then, the python3-dbus dependency is a deal-breaker. dbus-python
Build-Depends on python3-gi and gobject-introspection doesn't work for
cross compilation. This is not going to be fixed any time soon. You
cannot have gobject-introspection in the bootstrap set.
Beyond that, https://bootstrap.debian.net/botch-native/amd64/stats.html
reports src:lvm2 -> python3-pyudev as a strong bridge.
Trust me, the python bindings need to be droppable for lvm2. I gave you
a simple solution. I fear using build profiles will be slightly more
complex. Do you prefer that?
I also note that I am a little unsatisfied with the combination of your
response time for patches and your NACK-time for NMUs. Please bring them
closer together.
Helmut
Reply to: