Bug#1023787: transition: liblxqt
Hi ChangZhuo, On 03-12-2022 17:19, ChangZhuo Chen (陳昌倬) wrote: On Tue, Nov 29, 2022 at 07:33:11PM +0100, Paul Gevers wrote: Do we need to submit transition for lxqt-globalkeys [0], which is totally covered by liblxqt transition? What we need is coordination, which is why transition bugs need to be filed before the transition starts in unstable. We don't need a transition bug report per source package if they are combined anyways provided that the information about that is in the bug report. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1023787: transition: liblxqt
On Tue, Nov 29, 2022 at 07:33:11PM +0100, Paul Gevers wrote:
> Hi ChangZhuo,
>
> On 29-11-2022 06:29, ChangZhuo Chen (陳昌倬) wrote:
> > Please help to
> > migrate libfm-qt in new queue [0] so that we can prepare the migration.
>
> That's not under our control. You'll need to talk to ftp-master (typically a
> note with explanation on IRC helps).
Hi Paul,
Do we need to submit transition for lxqt-globalkeys [0], which is
totally covered by liblxqt transition?
[0] https://release.debian.org/transitions/html/auto-lxqt-globalkeys.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
Bug#1023787: transition: liblxqt
Hi ChangZhuo, On 29-11-2022 06:29, ChangZhuo Chen (陳昌倬) wrote: Please help to migrate libfm-qt in new queue [0] so that we can prepare the migration. That's not under our control. You'll need to talk to ftp-master (typically a note with explanation on IRC helps). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1023787: transition: liblxqt
On Mon, Nov 28, 2022 at 08:07:14PM +0100, Paul Gevers wrote:
> Hi,
>
> On 28-11-2022 17:50, ChangZhuo Chen (陳昌倬) wrote:
> > On Tue, Nov 22, 2022 at 09:58:48PM +0100, Paul Gevers wrote:
> > > Hi,
> > >
> > > On 21-11-2022 01:05, ChangZhuo Chen (陳昌倬) wrote:
> > > > All affected packages have been uploaded to unstable. Sorry for the
> > > > mess.
> > >
> > > Thanks. Let's see if they can migrate on their own to testing in the
> > > following days.
> >
> > They do not migrate after 8 days, do we need to do anything?
>
> Yes, bug 1024687 needs fixing.
In that case, we also need to finish libfm-qt migration. Please help to
migrate libfm-qt in new queue [0] so that we can prepare the migration.
[0] https://ftp-master.debian.org/new/libfm-qt_1.2.0-2.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
Bug#1023787: transition: liblxqt
Hi, On 28-11-2022 17:50, ChangZhuo Chen (陳昌倬) wrote: On Tue, Nov 22, 2022 at 09:58:48PM +0100, Paul Gevers wrote: Hi, On 21-11-2022 01:05, ChangZhuo Chen (陳昌倬) wrote: All affected packages have been uploaded to unstable. Sorry for the mess. Thanks. Let's see if they can migrate on their own to testing in the following days. They do not migrate after 8 days, do we need to do anything? Yes, bug 1024687 needs fixing. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1023787: transition: liblxqt
On Tue, Nov 22, 2022 at 09:58:48PM +0100, Paul Gevers wrote:
> Hi,
>
> On 21-11-2022 01:05, ChangZhuo Chen (陳昌倬) wrote:
> > All affected packages have been uploaded to unstable. Sorry for the
> > mess.
>
> Thanks. Let's see if they can migrate on their own to testing in the
> following days.
They do not migrate after 8 days, do we need to do anything?
--
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
Bug#1023787: transition: liblxqt
Hi, On 21-11-2022 01:05, ChangZhuo Chen (陳昌倬) wrote: All affected packages have been uploaded to unstable. Sorry for the mess. Thanks. Let's see if they can migrate on their own to testing in the following days. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1023787: transition: liblxqt
On Fri, Nov 18, 2022 at 11:17:34PM +0800, ChangZhuo Chen (陳昌倬) wrote:
> On Wed, Nov 16, 2022 at 09:26:42PM +0100, Paul Gevers wrote:
> > Dear LXQt maintainers,
> >
> > 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
All affected packages have been uploaded to unstable. Sorry for the
mess.
--
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
Bug#1023787: transition: liblxqt
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
Bug#1023787: transition: liblxqt
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. Paul [1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html OpenPGP_signature Description: OpenPGP digital signature
Bug#1023787: transition: liblxqt
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition 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". An automatic transition tracker has been set up at https://release.debian.org/transitions/html/auto-liblxqt.html -- System Information: Debian Release: 10.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 4.19.0-18-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
