Package: kraken Version: 0.10.5~beta-4 Severity: serious Hi folks,
As of version 0.10.5~beta-3, kraken now declares a dependency on jellyfish (specifically, jellyfish1). However, kraken builds for all architectures, but jellyfish and jellyfish1 are available only on amd64. This makes the built kraken packages uninstallable on all architectures except for amd64, and will block the updated package from reaching Debian testing. There are three ways that this can be resolved: - if jellyfish can be built for all archs, its debian/control should be fixed to be Architecture: any instead of Architecture: any-amd64. - if you know jellyfish will never be portable to other architectures, you can update kraken to also list itself as Architecture: any-amd64. - if you know jellyfish won't be built for all archs now, but aren't sure if it would be built for other architectures later, you can add jellyfish as a build-dependency to kraken so that it will not be built on architectures where it won't be installable. At a glance, I see that jellyfish uses x86 assembly, so probably one of the last two options is appropriate here. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
