Your message dated Fri, 31 May 2024 09:08:22 +0300
with message-id <zllpvvrkgktsg...@mitya57.me>
and subject line Re: Bug#1061179: transition: qtbase-abi-5-15-13
has caused the Debian Bug report #1061179,
regarding transition: qtbase-abi-5-15-13
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 ow...@bugs.debian.org
immediately.)


-- 
1061179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
Control: block -1 by 1060761 1060802

Dear Release team,

I have skipped Qt 5.15.11 release and would like to upgrade to 5.15.12
which was published in December. Qt WebEngine will be upgraded from 5.15.15
to 5.15.16. The transition is prepared in experimental.

There are two blockers, lomiri-ui-toolkit and stellarium, but I can NMU them.

I have submitted a merge request with the ben file:
https://salsa.debian.org/release-team/transition-data/-/merge_requests/47

--
Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
On Fri, May 24, 2024 at 07:30:40PM +0200, Emilio Pozuelo Monfort wrote:
> btw not sure what to do about qtbase-opensource-src's reverse
> autopkgtests[1]. Looks like they are having some trouble installing the
> right dependencies from unstable. Perhaps they hadn't been rebuilt yet when
> the tests were scheduled. Paul, do you have any ideas?

And it migrated! \o/

Thanks to Paul for helping me with retrying tests.

--
Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to