transition of packages into testing where Build-Depends can't be fulfilled for some architecture
Hello,
for some time I'm working on the package kicad [1] to help the current
maintainer Georges Khaznadar. Georges told me he currently haven't the
needed time to get kicad fully prepared for the Stretch release and
thankfully he gave me upload rights.
So I worked on the latest release of KiCad v4.0.5 and prepared the
upload and changes for a Debian release.
KiCad is using a lot of the Boost libraries, so the package
libboost-context-dev is also needed.
As I've now have seen boost changed [2] the supported platforms for this
package in 1.58.0.2 and only the platforms any-i386 any-amd64 armel
armhf arm64 mips mipsel powerpc ppc64el are now provided with a package
of libboost-context-dev.
Thus kicad isn't build able on mips64el and s390x [3]. And some other
non RC platforms as well. So, now to my question, is this behavior
preventing kicad to migrate into testing after the delay?
Need I to change the Architecture field for the arch related packages of
kicad then accordingly? As we are going on to the 26th January I would
solve this issue before we would need to call for unblocking later.
Or would kicad enter testing automatically and no further action is need
for kicad?
Thanks!
[1] https://tracker.debian.org/pkg/kicad
[2]
http://metadata.ftp-master.debian.org/changelogs/main/b/boost-defaults/unstable_changelog
https://sources.debian.net/src/boost-defaults/1.62.0.1/debian/control/#L200
[3] https://buildd.debian.org/status/package.php?p=kicad
--
Regards
Carsten Schoenert
Reply to: