Source: vkd3d
Version: 1.2-13
Severity: serious
Justification: ftbfs

Dear maintainer,

Your package currently doesn't get build on ppc64el because it
build-depends on the to-be-build version of libvkd3d-headers, but the
version available on ppc64el is the previously built version.

Your trick seems to have worked on other architectures, but it's a
race condition (and doesn't work elsewhere).

I just discussed this on #debian-ftp

<elbrus> does anybody have a clue where to look why libvkd3d-headers (arch:all) 
isn't available on ppc64el causing ppc64el to not build vkd3d
-*- elbrus stares at https://buildd.debian.org/status/package.php?p=vkd3d
<waldi> because -13 is the current version on ppc64el, but it wants -14
<waldi> how can this work?=
<waldi> it can't
<elbrus> of course
<waldi> but it's an interesting idea: build-depending on itself, just another 
architecture
<elbrus> sorry, I should have spotted that
-*- elbrus will file a bug
<waldi> thx
<elbrus> worked elsewhere
<waldi> dak is supposed to export only arch-all packages of the matching 
version. maybe this does not work always or what
<waldi> aka if a source got arch-any with version 1 and arch-all with version 1 
and 2, only the version 1 should be available in the Packages files
<jrtc27> maybe that doesn't extend to incoming?
<jrtc27> ie there's a ~6h window where you *can* pull in the arch:all version
<jrtc27> the header dependency is !i386 !amd64 and the arm64 build picked it up 
from incoming
<waldi> right, incoming. yes that makes sense then

Paul

Reply via email to