Bug#983018: qdbus: Needs package downgrade from Buster to Bullseye (missing epoch in transitional package)
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,
On Thu, Feb 18, 2021 at 09:08:46AM +0100, Axel Beckert wrote:
> 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
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
Reply to: