control: reopen -1 control: found -1 ganeti/2.16.0-5 On 2019-01-28 15:08, Apollon Oikonomopoulos wrote: > Source: ganeti > Source-Version: 2.16.0-4
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Format: 1.8 > Date: Mon, 28 Jan 2019 11:37:36 +0200 > Source: ganeti > Binary: ganeti ganeti-2.16 ganeti-haskell-2.16 ganeti-htools > ganeti-htools-2.16 ganeti-doc python-ganeti-rapi python3-ganeti-rapi > ganeti-testsuite > Architecture: source > Version: 2.16.0-4 > Distribution: unstable > Urgency: medium > Maintainer: Debian Ganeti Team <gan...@packages.debian.org> > Changed-By: Apollon Oikonomopoulos <apoi...@debian.org> > Description: > ganeti - cluster virtualization manager > ganeti-2.16 - cluster virtualization manager - Python components > ganeti-doc - cluster virtualization manager - documentation > ganeti-haskell-2.16 - cluster virtualization manager - Haskell components > ganeti-htools - cluster virtualization manager - tools (stand-alone) > ganeti-htools-2.16 - cluster virtualization manager - tools for Ganeti 2.16 > ganeti-testsuite - cluster virtualization manager - test suite > python-ganeti-rapi - cluster virtualization manager - RAPI client library > python3-ganeti-rapi - cluster virtualization manager - RAPI client library > (Python 3) > Closes: 918374 920685 920686 > Changes: > ganeti (2.16.0-4) unstable; urgency=medium > . > * Fix FTBFS with sphinx 1.8 (Closes: #918374) > * Bump Standards-Version to 4.3.0; no changes needed > * Detect arch-dependent libc/linux header values (Closes: #920685, #920686) We finally upgraded one of our ppc64el ganeti machine, and we ended up having this issue again. After investigation, it happens that the constants are now correctly detected at build time, however /usr/share/ganeti/2.16/ganeti/_constants.py is shipped in ganeti-2.16 which is arch:all. As we build arch:all on amd64, the constants are the amd64 ones. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
signature.asc
Description: PGP signature
