On April 28, 2016 05:54:57 PM you wrote: > Source: cableswig > Version: 0.1.0+git20150808-2 > Severity: serious > Control: block 818848 by -1 > > Dear maintainer, > > gccxml is scheduled for removal, but cableswig build-depends on it. > Please port your package to castxml.
Actually, cableswig should also be removed. It was only in the archive to support the old insighttoolkit builds; but insighttoolkit is to be removed c.f. #795019. Nothing else depends on cableswig -- see dak output, below. What's your preferred workflow here? Shall I close this bug and open a removal for cableswig? Or will you just go ahead and remove cableswig and gccxml now? GCC-XML is dead upstream and my attempt at a wrapper around CastXML was not a success so IMHO it's better to remove it sooner than later. Its other dependencies have already switched to CastXML (e.g. pygccxml) or they will soon or they are also dead. Cheers, -Steve dak rm -Rn cableswig" Will remove the following packages from unstable: cableswig | 0.1.0+git20150808-2 | source, amd64, arm64, armel, armhf, hurd- i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x libcableswig-dev | 0.1.0+git20150808-2 | amd64, arm64, armel, armhf, hurd- i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x Maintainer: Steve M. Robbins <s...@debian.org> ------------------- Reason ------------------- ---------------------------------------------- Checking reverse dependencies... # Broken Build-Depends: insighttoolkit: cableswig (>= 0.1.0+cvs20110226) Dependency problem found.
signature.asc
Description: This is a digitally signed message part.
