Dear Peter,
we will re-create this problem with a new database in our instance, (to be sure
on the reproducibility) and then raise an issue.
Mit freundlichen Grüßen
Matthias Enders
---
[cid:image001.png@01D03960.8254BEE0]
You may have found a new Galaxy bug then :(
Could you log an issue here:
https://github.com/galaxyproject/galaxy/issues
(From what you've said, I don't think that this is a problem in the
BLAST+ wrappers themselves)
Peter
On Wed, Jul 11, 2018 at 3:20 PM, Matthias Enders <
Dear Peter,
the reloading of the blast *.loc files did not solve the Problem. Actually only
a complete restart of the container solved the problem for us.
Mit freundlichen Grüßen
Matthias Enders
---
Good. So is everything resolved now?
Peter
On Wed, Jul 11, 2018 at 3:08 PM, Matthias Enders <
m.end...@german-seed-alliance.de> wrote:
> Dear Peter,
>
>
>
> yes we did reload the Blast *.loc files using the admin interface. Our
> Version is 18.05 (based on the Galaxy – Docker image).
>
>
>
>
Is there anything in the Admin's interface to let you reload the BLAST
*.loc files?
If yes, did you try it but it didn't work?
What version of Galaxy do you have?
Peter
On Tue, Jul 10, 2018 at 3:11 PM, Matthias Enders <
m.end...@german-seed-alliance.de> wrote:
> Dear Peter,
>
>
>
> up to our
Hi - We have been trying to clean up the Galaxy tool deps ... have this
interesting log as a result. Getting a lot of these:
"DependencyException: Conda dependency seemingly installed but failed to build
job environment."
I am curious about the way files play in different locations in Galaxy:
