Your message dated Thu, 30 Apr 2020 20:35:42 +0000
with message-id <e1jufui-0001fd...@fasolo.debian.org>
and subject line Bug#958515: fixed in diamond-aligner 0.9.32-2
has caused the Debian Bug report #958515,
regarding diamond-aligner breaks proteinortho autopkgtest on arm64: Error: 
wrong fromat
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
958515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diamond-aligner, proteinortho
Control: found -1 diamond-aligner/0.9.31-1
Control: found -1 proteinortho/6.0.14+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of diamond-aligner the autopkgtest of proteinortho
fails on arm64 in testing when that autopkgtest is run with the binary
packages of diamond-aligner from unstable. It passes when run with only
packages from testing. In tabular form:

                       pass            fail
diamond-aligner        from testing    0.9.31-1
proteinortho           from testing    6.0.14+dfsg-1
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of diamond-aligner
to testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=diamond-aligner

https://ci.debian.net/data/autopkgtest/testing/arm64/p/proteinortho/5105579/log.gz

autopkgtest [14:23:33]: test run-unit-test: [-----------------------
*****************************************************************
Proteinortho with PoFF version 6.0.14 - An orthology
detection tool
*****************************************************************
Detected 32 available CPU threads (adjust this with -cpus), Detected
'blastp+' version 2.9.0+
Checking input files.
Checking test/C.faa... ok
Checking test/C2.faa... ok
Checking test/E.faa... ok
Checking test/L.faa... ok
Checking test/M.faa... ok

**Step 1**
Generating indices anyway (forced).
Building database for 'test/C.faa'      (109 sequences)
Building database for 'test/E.faa'      (72 sequences)
Building database for 'test/L.faa'      (40 sequences)
Building database for 'test/M.faa'      (40 sequences)
Building database for 'test/C2.faa'     (2 sequences)

**Step 2** using blastp+



Running blast analysis: 0% (0/10)


Running blast analysis: 100% (10/10)


Running blast analysis: 80% (8/10)


Running blast analysis: 10% (1/10)


Running blast analysis: 20% (2/10)


Running blast analysis: 30% (3/10)


Running blast analysis: 40% (4/10)


Running blast analysis: 50% (5/10)


Running blast analysis: 60% (6/10)


Running blast analysis: 70% (7/10)


Running blast analysis: 90% (9/10)


Running blast analysis: 100% (10/10)
[OUTPUT] -> written to test_blastp.blast-graph

**Step 3**
Clustering by similarity (Proteinortho mode) using up to 96343.5 MB of
memory (75% of total memory) and 32 cpu core(s). Adjust this behaviour
with the -mem option.
Reading test_blastp.blast-graph
5 species
113 paired proteins
148 bidirectional edges


Clustering: 85.84%

Clustering: 89.38%

Clustering: 93.81%

Clustering: 95.58%

Clustering: 100.00%
Done
[OUTPUT] -> Orthologous groups are written to test_blastp.proteinortho.tsv
You can extract the fasta files of each orthology group with
'proteinortho_grab_proteins.pl -tofiles test_blastp.proteinortho.tsv
test/C.faa test/E.faa test/L.faa test/M.faa test/C2.faa'
 (Careful: This will generate a file foreach line in the file
test_blastp.proteinortho.tsv).
[OUTPUT] -> Orthologous pairs are written to test_blastp.proteinortho-graph
[OUTPUT] -> Summary is written to test_blastp.proteinortho-graph.summary
[OUTPUT] -> Orthologous groups are written to test_blastp.proteinortho.html

All finished.
*****************************************************************
Proteinortho with PoFF version 6.0.14 - An orthology
detection tool
*****************************************************************
Detected 32 available CPU threads (adjust this with -cpus), Detected
'blastp+' version 2.9.0+
Checking input files.
Checking test/C.faa... test/C.faa       109 genes       ok
Checking test/C2.faa... test/C2.faa     2 genes ok
Checking test/E.faa... test/E.faa       72 genes        ok
Checking test/L.faa... test/L.faa       40 genes        ok
Checking test/M.faa... test/M.faa       40 genes        ok

**Step 1**
Generating indices anyway (forced).
Building database for 'test/C.faa'      (109 sequences)
Building database for 'test/E.faa'      (72 sequences)
Building database for 'test/L.faa'      (40 sequences)
Building database for 'test/M.faa'      (40 sequences)
Building database for 'test/C2.faa'     (2 sequences)

**Step 2** using blastp+ with : synteny



Running blast analysis: 0% (0/10)


Running blast analysis: 100% (10/10)


Running blast analysis: 80% (8/10)


Running blast analysis: 10% (1/10)


Running blast analysis: 20% (2/10)


Running blast analysis: 30% (3/10)


Running blast analysis: 40% (4/10)


Running blast analysis: 50% (5/10)


Running blast analysis: 90% (9/10)


Running blast analysis: 60% (6/10)


Running blast analysis: 70% (7/10)


Running blast analysis: 100% (10/10)
[OUTPUT] -> written to test_synteny.blast-graph

**Step 3**
Clustering by similarity (Proteinortho mode) using up to 96343.5 MB of
memory (75% of total memory) and 32 cpu core(s). Adjust this behaviour
with the -mem option.
Reading test_synteny.blast-graph
5 species
113 paired proteins
148 bidirectional edges


Clustering: 85.84%

Clustering: 89.38%

Clustering: 93.81%

Clustering: 95.58%

Clustering: 100.00%
Done
[OUTPUT] -> Orthologous groups are written to test_synteny.proteinortho.tsv
You can extract the fasta files of each orthology group with
'proteinortho_grab_proteins.pl -tofiles test_synteny.proteinortho.tsv
test/C.faa test/E.faa test/L.faa test/M.faa test/C2.faa'
 (Careful: This will generate a file foreach line in the file
test_synteny.proteinortho.tsv).
Adding singles...
[OUTPUT] -> Orthologous pairs are written to test_synteny.proteinortho-graph
[OUTPUT] -> Summary is written to test_synteny.proteinortho-graph.summary
[OUTPUT] -> Orthologous groups are written to test_synteny.proteinortho.html

Clustering by gene-order (POFF mode)
Reading test_synteny.ffadj-graph
5 species
106 paired proteins
105 bidirectional edges


Clustering: 17.92%

Clustering: 61.32%

Clustering: 81.13%

Clustering: 83.02%

Clustering: 84.91%

Clustering: 86.79%

Clustering: 88.68%

Clustering: 90.57%

Clustering: 92.45%

Clustering: 98.11%

Clustering: 100.00%
Done
[OUTPUT] -> Orthologous groups are written to test_synteny.poff.tsv
You can extract the fasta files of each orthology group with
'proteinortho_grab_proteins.pl -tofiles test_synteny.poff.tsv test/C.faa
test/E.faa test/L.faa test/M.faa test/C2.faa'
(Careful: This will generate a file foreach line in the file
test_synteny.poff.tsv).
Adding singles...
[OUTPUT] -> Orthologous pairs written to test_synteny.poff-graph
tput: No value for $TERM and no -T specified
[STDERR] Error: wrong fromat... Please make sure you only provide
*.blast-graph or *.proteinortho-graph files as input...
Died at /usr/bin//proteinortho_summary.pl line 117, <$FH> line 2.
[OUTPUT] -> Summary is written to test_synteny.poff-graph.summary
USAGE: proteinortho2html.pl <myproject.proteinortho> (<fasta1> <fasta2> ...)
the first argument points to the proteinortho output (tsv)-file. Any
further (optional) files should be fasta files, for conversion of the
identifier to a proper gene name/ describtion. The HTML output is
printed to stdout, use '>' to write the html output to a file.
[OUTPUT] -> Orthologous groups are written to test_synteny.poff.html

All finished.
*****************************************************************
Proteinortho with PoFF version 6.0.14 - An orthology
detection tool
*****************************************************************
Detected 32 available CPU threads (adjust this with -cpus), Detected
'diamond' version 0.9.31
Checking input files.
Checking test/C.faa... ok
Checking test/C2.faa... ok
Checking test/E.faa... ok
Checking test/L.faa... ok
Checking test/M.faa... ok

**Step 1**
Generating indices anyway (forced).
Building database for 'test/C.faa'      (109 sequences)
Building database for 'test/E.faa'      (72 sequences)
Building database for 'test/L.faa'      (40 sequences)
Building database for 'test/M.faa'      (40 sequences)
Building database for 'test/C2.faa'     (2 sequences)

**Step 2** using diamond



Running blast analysis: 0% (0/10)
Parameter-vector :
(version=6.0.14,step=0,verbose=1,debug=1,exactstep3=0,synteny=0,duplication=2,cs=3,alpha=0.5,connectivity=0.1,cpus=32,evalue=1e-05,purity=1e-07,coverage=50,identity=25,blastmode=diamond,sim=0.95,report=3,keep=0,force=1,selfblast=0,twilight=0,singles=0,clean=0,blastOptions=,nograph=0,xml=0,desc=0,tmp_path=./proteinortho_cache_test_diamond/,blastversion=unknown,binpath=,makedb=diamond
makedb
--in,blast=,jobs_todo=10,project=test_diamond,po_path=/usr/bin/,run_id=,threads_per_process=3,useMcl=0,freemem=-1)


[Error]  diamond failed.
The most likely  errorsources of this are:
- no space left on device error.
- outdated diamond, please update diamond or consider another -p algorithm.
- the databases are missing. Maybe you ran --step=1 and removed the
databases afterwards? Please rerun 'proteinortho --step=1 --force
/path/to/fastas'
- maybe the fasta files are mixed nucleotide and aminoacid sequences or
just not suited for diamond? (For example diamond only processes protein
sequences) Try 'proteinortho --step=1 --check --force /path/to/fastas'.


(If you cannot solve this error, please send a report to
incoming+paulklemm-phd-proteinortho-7278443-iss...@incoming.gitlab.com
including the parameter-vector above or visit
https://gitlab.com/paulklemm_PHD/proteinortho/wikis/Error%20Codes for
more help. Further more all mails to lech...@staff.uni-marburg.de are
welcome)


Perl exited with active threads:
        31 running and unjoined
        0 finished and unjoined
        0 running and detached
autopkgtest [14:23:55]: test run-unit-test: -----------------------]

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: diamond-aligner
Source-Version: 0.9.32-2
Done: Andreas Tille <ti...@debian.org>

We believe that the bug you reported is fixed in the latest version of
diamond-aligner, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 958...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille <ti...@debian.org> (supplier of updated diamond-aligner package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 30 Apr 2020 21:43:33 +0200
Source: diamond-aligner
Architecture: source
Version: 0.9.32-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 
<debian-med-packag...@lists.alioth.debian.org>
Changed-By: Andreas Tille <ti...@debian.org>
Closes: 958090 958515
Changes:
 diamond-aligner (0.9.32-2) unstable; urgency=medium
 .
   * Fixed different build issues
     Closes: #958515, #958090
   * Upstream says diamond-aligner does not run on 32bit systems
     https://github.com/bbuchfink/diamond/issues/347#issuecomment-622051316
Checksums-Sha1:
 1973d1e038a0d934e902775e7d456a2b595ae00e 2202 diamond-aligner_0.9.32-2.dsc
 e1a7c7a86f1ba85a8818e3e4c5c29b895242e62f 131260 
diamond-aligner_0.9.32-2.debian.tar.xz
 ed9d0afd750d5d13809ce3d3c36b5a70539a28ca 6823 
diamond-aligner_0.9.32-2_amd64.buildinfo
Checksums-Sha256:
 da8eec3012c3c001633a9f744fbcbe57ee633f6a6ce43b0bc504c59176244537 2202 
diamond-aligner_0.9.32-2.dsc
 c2fd3b38a8a7f2bbf49a1f540c83c1a84d6603ca97b17e8bb8227e7ecf2c3c2f 131260 
diamond-aligner_0.9.32-2.debian.tar.xz
 0876234037fac5f589249caa65c8fe6a2f4e4b0f2ec9390e982e472a22a69abb 6823 
diamond-aligner_0.9.32-2_amd64.buildinfo
Files:
 769a315f5986f88d58b7c91b7298fe5f 2202 science optional 
diamond-aligner_0.9.32-2.dsc
 ae1353df8b261f1c334f94cffd162d90 131260 science optional 
diamond-aligner_0.9.32-2.debian.tar.xz
 03feaffbf0da20107ad3c916e1313f65 6823 science optional 
diamond-aligner_0.9.32-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl6rLhsRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGpzxAAi3tKZ2Ah74aHr9E8mvvewt0BCfZfuxt2
KT2hwUc7eSZ9DB/KQRId87i4ssgAstNiJ232gPks0ugNxqgHgIDhkJxPH27cy4y5
Cs0T1LbZXQEg+KJAw2H4IsFRx0hnxF/SK88gfLnPJAdScbso8VEsu1ksuqN2N0ND
YHDMLdhkHSeExru8/QuJsBrxrR7PR7SQGqYkzwCidNJRBoK7Qu5w7iF6hiqANneH
lZE59TMdyLouBqk3LC7AE+z3ccZx+QHrcCsmS9A/3Vyh1S6W+g/h2zVf1T6SUISc
r6vMf8uYinOiSyyGsTBHVLGeChwsXgLnbUrCq+AYFCowUtpxu9++HRLpCbYpKed2
CDZ3oGzq6Q+cZ68krgfC8tCatLLtK1w/EU3aKngf0oWpPwJWS5FNlYugU8krB5gC
VnkbvB7w+9wKrHIDkMqWXy+NwjBl0igeZLVLrdbS20/a75RlXUl3T2JAO/BydqEy
ew/dylkiK6UJ9r7iLCIXwTsVUqjq2IETxdEcaefBJHANWdKzavpRaraMyTQTHGXS
PbqAuS1I5BwQqWFR43BWUlmOkgVwQCMI4NksWre8HF9UoK4SFJMzk1JpeUX7M/lG
2wob4rPa7iKT+7D6229YsWqVVPMIziulrT+/lydzaWjm49mslsdpUsD5kYCPhgPf
RdmUiN6zMZk=
=x7XR
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to