Hi,

on one system I wondered why qdbus is still on Qt4. Then I noticed that
the version of the Qt4 qdbus package from Buster is higher (!) than the
version of the Qt5 qdbus package in Bullseye:

$ apt-cache policy qdbus
qdbus:
  Installed: 4:4.8.7+dfsg-18+deb10u1
  Candidate: 4:4.8.7+dfsg-18+deb10u1
  Version table:
 *** 4:4.8.7+dfsg-20 100
        100 /var/lib/dpkg/status
     5.15.2-3 990
        900 https://debian.ethz.ch/debian bullseye/main i386 Packages

From what I can see, the proper fix is to prepend at least an epoch of
"4" to (only) the transitional package, i.e. to make the version of
qdbus in Bullseye "4:5.15.2-…" instead of just "5.15.2-…".

Even the BTS gets it partially wrong probably because of this and still
thinks the current qdbus package is built from the qt4-x11 source
package:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=qdbus;dist=unstable
(Note that it displays the correct version number, but the wrong source
package.)

Hello,

Bug #983018 in qttools-opensource-src reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/qt-kde-team/qt/qttools/-/commit/3f30e1424052ebb926ec506f1fda8294c49f0434
Closes: #983018.
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/983018

clone -1 -2
reassign -2 ftp.debian.org
retitle -2 dak: version checks for binaries not enforced when binary changes from any to all
severity -2 normal
tags -2 - pending

Hi,

The current situation:

qdbus      | 5.15.2-3                             | testing      | all
qdbus      | 5.15.2-3                             | unstable     | all
qdbus      | 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 | oldoldstable | amd64, armel, armhf, i386
qdbus      | 4:4.8.7+dfsg-11                      | oldstable    | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
qdbus      | 4:4.8.7+dfsg-18+deb10u1              | stable       | amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x

Normally, version checks should prevent an upload to unstable of a binary that
has a lower version than in stable or testing. However, this is checked per
architecture, and it seems the check wasn't done because the binary changed
from arch: any to arch: all at the same time. This case should probably be
checked in dak as well (obviously also for arch: all to arch: any).

Cloning the bug to track the issue in dak.

Cheers,

Ivo