Re: subread: limit architectures
- To: Debian Med Project List <debian-med@lists.debian.org>
- Subject: Re: subread: limit architectures
- From: Andreas Tille <andreas@fam-tille.de>
- Date: Sat, 16 May 2015 07:28:20 +0200
- Message-id: <[🔎] 20150516052820.GG27760@an3as.eu>
- In-reply-to: <55564F77.5050700@biotec.tu-dresden.de>
- References: <5556013D.3040401@biotec.tu-dresden.de> <20150515181058.GC27760@an3as.eu> <55564F77.5050700@biotec.tu-dresden.de>
Hi Alex,
On Fri, May 15, 2015 at 09:56:39PM +0200, Alex Mestiashvili wrote:
>
> The problem is that the code builds but tests fail in some strange way.
Well, if I understand things correctly the test is part of the package
build process and thus in the case of a failed test no package is build,
right?
> I think in order to fix that, one would need to understand the algorithm..
> I even can not form the question to narrow the possible field of problem...
I admit I have a bit strange gut feeling about algorithms that work on
some but not all architectures.
> So I personally would go with setting the Architecture field to working
> ones.
This sounds sensible for the moment.
> I assume that because the package had never been uploaded for the
> failing architectures I can simply set the Architecture and upload it to
> unstable.
> I guess there is no need in removal requests or something similar?
Yes.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: