Re: Migration to testing of optimir is blocked - why?
Hy Dylan,
On Wed, Jul 17, 2019 at 02:51:25PM +0200, Dylan Aïssi wrote:
> The migration of optimir [1] to testing was blocked during the freeze
> for Buster. But since the freeze is over, optimir never moved to
> testing and I don't know why. He has some dependencies which are
> available only in amd64, so could this be a problem for the migration?
> Should I restrict the arch of optimir to amd64 only to unblock its
> from unstable? Or the problem is from somewhere else?
The Excuses link[2] is your friend. The Architecture all package
expects to be able to run on *all* architectures but it can't since some
Depends are only available on amd64 this is a problem. I try to
remember what the solution was. I think in some cases we used the ugly
hack to make the package Architecture: any and
Build-Depends: bowtie2, python3-pysam
which provides the package only where those dependencies exist. But
that's not a nice solution. I think we did not do this trick for
metaphlan2 but if I remember correctly that needed a manual hint from
release team to propagate. Sorry, I simply forgot - may be you check
the list archive for a proper solution?
Thanks for your work on this
Andreas.
> [1] https://tracker.debian.org/pkg/optimir
[2] https://qa.debian.org/excuses.php?package=optimir
--
http://fam-tille.de
Reply to: