Re: OTB

[Sebastiaan Couwenberg <sebastic@xs4all.nl>]

On 18-12-15 15:59, Sebastiaan Couwenberg wrote:
> Also note that otb build depends on libinsighttoolkit4-dev provided by
> insighttoolkit4 which is currently prevented from migrating to testing
> and only available for amd64 & i386:
> 
>  https://tracker.debian.org/pkg/insighttoolkit4
> 
> This makes maintenance of otb much easier because you don't have to
> worry about the ports. But it also makes otb unavailable on the other
> architectures, and it's a bit of a shame to not also have it on the
> modern arm* architectures at least.

Because only amd64 & i386 are able to build otb, you don't have to
upload new release to experimental first if you update the symbols for
both architectures. You don't have to collect the symbols from buildd
logs for the other architectures.

@Rashad, if you don't have one already, create an i386 chroot in
addition to (native) amd64 chroot you already have:

 sudo cowbuilder --create --distribution=sid --architecture=i386 \
                 --basepath=/var/cache/pbuilder/base-sid-i386.cow

You can then build the package in the i386 with git-buildpackage with:

 gbp buildpackage --git-pbuilder --git-arch=i386

Creating architecture specific chroots is also documented in the team
policy:

 http://pkg-grass.alioth.debian.org/policy/packaging.html#git-pbuilder

As is building the package for other distributions & architectures:

 http://pkg-grass.alioth.debian.org/policy/packaging.html#git-build-package

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1