On Wed, Nov 16, 2022 at 09:26:42PM +0100, Paul Gevers wrote: > Dear LXQt maintainers, > > On 10-11-2022 07:56, plugwash wrote: > > It appears a liblxqt transition has started, possiblly inadvertantly. > > > > Back in June, Simon Quigley prepared an update of the lxqt stack. He > > announced > > that he intended to update the stack in unstable, but only actually did so > > in > > experimental. > > > > Part of this update was a transition from liblxqt0 to liblxqt1. The dev > > package > > has also been renamed from liblxqt0 to liblxqt1-dev, so this transition > > requires > > sourceful uploads of all reverse dependencies. > > > > In late October, Andrew Lee uploaded the new versions liblxqt and > > lxqt-session > > to unstable, but did not upload the rest of the stack. > > > > liblxqt has migrated to testing thanks to "smooth updates", leaving the lxqt > > stack in testing in violation of "packages must be buildable within the same > > release". > > Can you please comment on this and also elaborate how you intent to fix the > situation. At this moment we have a whole bunch of packages [1] that can't > be rebuild in testing due to this, which means all those packages are RC > buggy. The LXQt stack is part of the key package set, so the packages are > not trivial to remove. We only have slightly under 2 months until the first > bookworm freeze, I'd like to see this issue solved ASAP.
Sorry for the mess. Our current plan is to package 1.1.0 first. I will spend some time this week to work on these packages. > > Paul > > [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html -- ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org http://czchen.info/ Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
