[Pkg-ganeti-devel] New upload & arch specs
Apollon Oikonomopoulos
apoikos at gmail.com
Fri Aug 2 08:38:26 UTC 2013
Hi all,
Ganeti currently has an RC bug (#718553 - my fault, sorry!) which will
require a new upload. While we're at it, there is another important
problem that has to be resolved for it to migrate to testing:
https://buildd.debian.org/status/package.php?p=ganeti&suite=sid
Currently 2.7 fails to build on armel, armhf, mips, mipsel, s390 and
s390x, while 2.5.2 was previously built there, flagging ganeti
out-of-date. This is because the newer Haskell components make use of
Template Haskell, which in turn requires GHCi at compile time. GHCi
itself is not available on all platforms:
http://ghc.haskell.org/trac/ghc/wiki/Platforms
IOW, there is no way ganeti-haskell will build on these architectures in
the near future, unless it stops using TH. So, apart from requesting
removal from unstable for these arches, AFAICT we have 3 options:
1. Leave the package as-is, stating that if GHCi is ever available for
an arch, we'd like to have ganeti-haskell built for it. In that case
we should also Recommend qemu-system-${Arch}.
2. Change ganeti-haskell's arch field to 'i386 amd64 powerpc sparc' to
reflect platforms with GHCi availability (ugly).
3. Consider dropping non-x86 architectures completely.
Currently there is support in the Linux kernel for KVM on PPC, s390,
MIPS and ARM, but I don't think ganeti has ever been tested on them.
In theory 2.7 should work if the user sets the kvm:kvm_path parameter
to /usr/bin/qemu-system-<arch> and uses the kvm:kvm_extra parameter
if appropriate.
Personally I'd go for option 1, but I'm not sure how ftp-master will
react to us requesting removal while maintaining arch: any. If OTOH
upstream states that they clearly *don't* support non-x86 arches, we
should go for 3. Opinions?
Thanks,
Apollon
More information about the Pkg-ganeti-devel
mailing list