Bug#1023919: marked as done (transition: astc-encoder)

2022-11-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Nov 2022 23:46:55 +0100 with message-id and subject line Re: Bug#1023919: transition: astc-encoder has caused the Debian Bug report #1023919, regarding transition: astc-encoder to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1023948: marked as done (transition: hmat-oss)

2022-11-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Nov 2022 23:46:34 +0100 with message-id and subject line Re: Bug#1023948: transition: hmat-oss has caused the Debian Bug report #1023948, regarding transition: hmat-oss to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1024178: RM: pypy-stem/1.8.0-3.1

2022-11-16 Thread Hefee
Hey, > Migration of python-step is currently blocked as removal of pypy-stem > would render vanguards uninstallable. So what's the plan regarding > vanguards? The pypy-stem was already a broken package and not functional it broke the autopkgtests see #1022111. Vanguards should be ported to

Bug#1023787: transition: liblxqt

2022-11-16 Thread Paul Gevers
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

Bug#1023787: State of Debian LXQt in 2022

2022-11-16 Thread Simon Quigley
Dear Debian Release Team, or whoever this may concern, Let me provide some context for the current state of LXQt in Debian, and where the shortcomings exist in our current process, leading to a situation like this. Lubuntu, an officially recognized flavor of Ubuntu, has used LXQt for our