In such cases it is usually best to bump version number, and do a fresh upload to lunar-proposed such that it is higher than any of (kinetic, lunar).
Might make sense to still upload no change rebuild of dbus into lunar-proposed. On Tue, 22 Nov 2022, 18:45 Sebastien Bacher, <seb...@ubuntu.com> wrote: > Hey there, > > Le 22/11/2022 à 18:21, Paride Legovini a écrit : > > The dbus package has now need force-migrated from lunar-proposed to > > -release (currently pending publication). This should fix the issue. > > I've stated that via chat but I still disagree that was the right thing > to do. Without tests result how are we confident that the update isn't > bringing a regression (one other update in lunar could create issue for > the dbus in proposed)? Why didn't we fix the autopkgtest setup to use an > lunar image or enable proposed to allow the tests to be correctly tried > instead? > > Also are we confident that they aren't other packages in the same > situations? > > Cheers, > Sebastien > > > -- > ubuntu-devel mailing list > ubuntu-devel@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel >
-- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
