Bug#1053866: marked as done (transition: jpeg-xl)

2024-06-14 Thread Sebastian Ramacher
Hi On 2024-06-14 08:10:56 +0200, Mathieu Malaterre wrote: > Emilio, > > On Fri, May 31, 2024 at 12:40 PM Emilio Pozuelo Monfort > wrote: > > > > Control: reopen -1 > > > > On 31/05/2024 12:36, Debian Bug Tracking System wrote: > > > jpeg-xl (0.8.2-4) unstable; urgency=medium > > > . > > >

Bug#1053866: marked as done (transition: jpeg-xl)

2024-06-14 Thread Mathieu Malaterre
Emilio, On Fri, May 31, 2024 at 12:40 PM Emilio Pozuelo Monfort wrote: > > Control: reopen -1 > > On 31/05/2024 12:36, Debian Bug Tracking System wrote: > > jpeg-xl (0.8.2-4) unstable; urgency=medium > > . > > * Upload 0.8.2-4 to unstable. Closes: #1053866 > > Uploading to unstable

Processed: Re: Bug#1053866: marked as done (transition: jpeg-xl)

2024-05-31 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1053866 {Done: Mathieu Malaterre } [release.debian.org] transition: jpeg-xl 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as

Bug#1053866: marked as done (transition: jpeg-xl)

2024-05-31 Thread Emilio Pozuelo Monfort
Control: reopen -1 On 31/05/2024 12:36, Debian Bug Tracking System wrote: jpeg-xl (0.8.2-4) unstable; urgency=medium . * Upload 0.8.2-4 to unstable. Closes: #1053866 Uploading to unstable doesn't close the transition bug. There are still things to do here, such as binNMUs, and

Bug#1053866: marked as done (transition: jpeg-xl)

2024-05-31 Thread Debian Bug Tracking System
Your message dated Fri, 31 May 2024 10:34:08 + with message-id and subject line Bug#1053866: fixed in jpeg-xl 0.8.2-4 has caused the Debian Bug report #1053866, regarding transition: jpeg-xl to be marked as done. This means that you claim that the problem has been dealt with. If this is not