[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1023787: marked as done (transition: liblxqt)

Your message dated Thu, 8 Dec 2022 18:10:21 +0100
with message-id <Y5IafbJspvCYS/Zc@ramacher.at>
and subject line Re: Bug#1023787: transition: liblxqt
has caused the Debian Bug report #1023787,
regarding transition: liblxqt
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1023787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023787
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@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

--- End Message ---
--- Begin Message --- 
On 2022-11-10 06:56:41 +0000, plugwash wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@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

The old binary packages got removed from testing. Closing.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: