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

Bug#1034037: marked as done (unblock: qt6-tools/6.4.2-1)

Your message dated Thu, 20 Apr 2023 10:50:50 +0200
with message-id <02e94816-7b21-cb35-08f5-4ad5820a761c@debian.org>
and subject line Re: Bug#1034037: unblock: qt6-tools/6.4.2-1
has caused the Debian Bug report #1034037,
regarding unblock: qt6-tools/6.4.2-1
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.)


-- 
1034037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034037
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: unblock
X-Debbugs-Cc: deltaone@debian.org

Please unblock package qt6-tools

[ Reason ]
Qt 6.4.2 was released in January 2023. In order to get the transition done in time,
we received pre-release tarballs from The Qt Company to prepare the packaging and we
completed the transition in time.
Since those were pre-release tarballs, we marked the version as 6.4.2~rc1. After the
release, it turned out that the pre-release tarballs were identical to the official
6.4.2 tarballs. We then reuploaded every package and marked the packages as version
6.4.2 to reflect this.
The rc1 version of qt6-tools is in bookworm, but the "official" 6.4.2 is not yet.
It was uploaded in January, but its migration has been blocked by llvm-toolchain-15.

We'd like to request an unblock such that qt6-tools 6.4.2-1 can migrate to testing 
once llvm-toolchain-15 has migrated.

[ Impact ]
The impact is minimal as this is merely a cosmetic change.

[ Tests ]
No additional tests have been run.

[ Risks ]
The risks are minimal as it is the same tarball simply rebuilt.
The checksums for both tarballs are identical, see
https://tracker.debian.org/news/1402882/accepted-qt6-tools-642rc1-1-source-into-experimental/
and
https://tracker.debian.org/news/1414695/accepted-qt6-tools-642-1-source-into-unstable/

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
-

unblock qt6-tools/6.4.2-1

diffstat for qt6-tools-6.4.2~rc1 qt6-tools-6.4.2

 changelog |    7 +++++++
 1 file changed, 7 insertions(+)

diff -Nru qt6-tools-6.4.2~rc1/debian/changelog qt6-tools-6.4.2/debian/changelog
--- qt6-tools-6.4.2~rc1/debian/changelog	2022-12-30 16:59:08.000000000 +0100
+++ qt6-tools-6.4.2/debian/changelog	2023-01-29 00:54:45.000000000 +0100
@@ -1,3 +1,10 @@
+qt6-tools (6.4.2-1) unstable; urgency=medium
+
+  [ Patrick Franz ]
+  * Switch to the official 6.4.2 tarball, the tarball is the same.
+
+ -- Patrick Franz <deltaone@debian.org>  Sun, 29 Jan 2023 00:54:45 +0100
+
 qt6-tools (6.4.2~rc1-2) unstable; urgency=medium
 
   [ Patrick Franz ]

--- End Message ---
--- Begin Message --- 
Hi,

On 07-04-2023 19:16, Paul Gevers wrote:
That's fine, but I don't expect llvm-toolchain-15 to migrate before the bookworm release, and I don't think this cosmetic issue warrants the tpu dance. So I think we'll just have 6.4.2~rc1-2 as the bookworm version. 

llvm-toolchain-15 is confirmed unlikely to migrate. So let's close this bug.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: