[Debian-med-packaging] r9070 - trunk/packages/insighttoolkit/wrapitk/python/trunk/debian

Andreas Tille andreas at an3as.eu
Wed Dec 21 08:44:17 UTC 2011


Hi,

I#m a bit confused about the changelog entry:

On Wed, Dec 21, 2011 at 05:39:19AM +0000, Steven Michael Robbins wrote:
> Author: smr
> Date: 2011-12-21 05:39:19 +0000 (Wed, 21 Dec 2011)
> New Revision: 9070
...
> --- trunk/packages/insighttoolkit/wrapitk/python/trunk/debian/changelog	2011-12-20 15:29:12 UTC (rev 9069)
> +++ trunk/packages/insighttoolkit/wrapitk/python/trunk/debian/changelog	2011-12-21 05:39:19 UTC (rev 9070)
> @@ -1,3 +1,10 @@
> +wrapitk-python (3.20.1.3) unstable; urgency=low
> +
> +  * control.in: Build only on architectures with sufficient computing
> +    power.
...
> --- trunk/packages/insighttoolkit/wrapitk/python/trunk/debian/control	2011-12-20 15:29:12 UTC (rev 9069)
> +++ trunk/packages/insighttoolkit/wrapitk/python/trunk/debian/control	2011-12-21 05:39:19 UTC (rev 9070)
> @@ -16,7 +16,7 @@
>  
>  Package: python-insighttoolkit3
>  Section: python
> -Architecture: any
> +Architecture: amd64 arm i386 ia64 mips powerpc sparc


For me this implicitely means that kfreebsd* and hurd* might not feature
sufficient computing power even if running on powerful processors.  I've
also always assumed that s390 would be a powerful architecturs.  I do
not question your specific selection of architectures - however, this
does not logically fit the explanation in the changelog.

My guess is that there were some FTBFS errors on certain architectures
and I'd regard it more logical to provide a negative list of
architectures that failed rather than a positive list which is OK but
might exclude some archs for no real reason.

Kind regards

        Andreas.

-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list