Hi Release Team, 2 packages of mine, primarily due to demanding resources for build (c++ with heavy use of templating) and testing (I do prefer to do build-time testing and they use realistic data) always were somewhat problematic to be built across architectures; thus they were removed from wheezy (while in testing) whenever new FTBFS were detected. Both are highly specialized to the field of neuroimaging. Both are old versions (see below) but relatively popular as for a specialized software.
ants ---- Slightly updated snapshot version than then one in squeeze Fresh upstream version requires fresh ITK (in experimental) popcon ~100 FTBFS atm on mips, mipsel, s390 imho due to insufficient resources and might be tricky to make them build reliably openmeeg -------- The same upstream version as in squeeze -- minor additional patching (gcc 4.7) + enabled build time unittests Fresh upstream requires fresh libmat (in experimental) popcon ~200 FTBFS atm on mips only, and could be resolved simply through disabling build time unittesting I wondered, than even if I manage to overcome FTBFS on those -- would they be allowed to come back to wheezy? Thanks in advance -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
