Re: Please give back ncbi-blast+ on mipsel and ppc64
Philipp Kern writes: > Looks like this already happened. FWIW with self-service giveback you > need to URL encode the plus but I confirmed that this works. Yes, looks all good now, thanks! As for not using self-service, it was more a matter of having more or less forgotten that it was an option nowadays, and then proceeding to overlook the brief directions on using it. Sorry for the noise. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Re: Please give back ncbi-blast+ on mipsel and ppc64
On 2/19/2020 8:40 PM, Aaron M. Ucko wrote: > As such, could we please try for another automated build? > > gb ncbi-blast+_2.9.0-4 . mipsel Looks like this already happened. FWIW with self-service giveback you need to URL encode the plus but I confirmed that this works. Kind regards Philipp Kern
Please give back ncbi-blast+ on mipsel and ppc64
[Please keep me copied; I don't follow debian-med closely, or the port lists at all.] Greetings. The latest automatic mipsel build of ncbi-blast+ failed due to an apparent toolchain glitch: /tmp/cch4xoEA.s: Assembler messages: /tmp/cch4xoEA.s: Internal error in emit_inc_line_addr at ../../gas/dwarf2dbg.c:1247. Today, I performed a manual build on a porterbox (eller) with the plan of then exploring workarounds, only to find that it succeeded as is. As such, could we please try for another automated build? gb ncbi-blast+_2.9.0-4 . mipsel Thanks! P.S.: The m68k and ppc64 failures don't appear to be ncbi-blast+'s fault either, but I'll let them slide for now because they don't affect testing migration and the latest changes should all be formalities on those architectures. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
