> Steve Langasek wrote on 01/11/2022:
> > I have set the flag now for lunar as it came up in discussion with
> > Foundations. The question of whether to change this for stable series is
> > still open (now with some further series that are stable) but can be
> > discussed separately.
>
> I very much welcome this change, but I think we're now missing an easy
> way to build (sbuild) packages with -proposed fully enabled. schroots
> created by mk-sbuild and sbuild-launchpad-chroot may have -proposed in
> sources.list, but that's not going to be used in >= Lunar. On Launchpad
> some extra pinning is done to fully enable -proposed [1].
>
> One way to re-enable easy builds with full -proposed could be modifying
> sbuild-launchpad-chroot (/etc/schroot/setup.d/90apt-sources) to do the
> same pinning that Launchpad does [1]. Once we have a way to sbuild with
> -proposed enabled I think enabling NotAutomatic for the stable releases
> would be a good idea: other than helping with SRU verification, the
> change will keep the -proposed behavior uniform across releases.
>
> Paride
>
> [1]
> https://git.launchpad.net/launchpad-buildd/commit/?id=c2ebcb6752af496166a5fffd9df3a4d6df6048ef
Gianfranco pointed out that there are dbus installability problems in
the lunar autopkgtests. For instance:
https://autopkgtest.ubuntu.com/packages/c/cinnamon-control-center/lunar/amd64
libdbus-1-dev : Depends: libdbus-1-3 (= 1.14.0-2ubuntu2) but
1.14.0-2ubuntu3 is to be installed
dbus 1.14.0-2ubuntu3 is built and I think it was published correctly
but it hasn't migrated out of lunar-proposed yet.
Is the breakage fallout from the changes to how proposed is handled for lunar?
Thank you,
Jeremy Bicha
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
