-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] New release to fix bugs in package manager installations #70
Comments
Yes ! @bneron it would be great if you could find the time to release the fix. It impacts users of DefenseFinder, and also users of software using defensefinder in their pipeline (e.g. weisberglab/beav#1). Thanks |
Just wanted to add my voice as well. It would be super nice to have the fix in a new release for all of the downstream pipelines. Thanks for all of the hard work! |
Hi all, glad to know I'm not the only one having trouble with profiles. |
this bug has been already fixed 27ee21c. just use the master version. |
Hi @bneron, I appreciate that the master version is updated and thank you very much for the fix. However, I just wanted to reiterate that (as mentioned also by Jean and Marco), using the master version is not a viable option for downstream softwares, pipelines or SOPs that use macsyfinder as a dependency (e.g. through pip or conda). Thank you again! |
I wil do a new release at the end of february but I haven't any time right now to do it. |
In the meantime, we released defensefinder (v1.2.2) with a previous version of macsyfinder that did not have the bug. We'll make another release when macsyfinder will be released. |
I just released a new version of MacSyFinder ( https://github.com/gem-pasteur/macsyfinder/releases 2.1.4) that fix this bug |
Is your feature request related to a problem? Please describe.
The current release contains bugs that have been fixed in the main branch, e.g. #69.
Describe the solution you'd like
Creating a new minor release.
Describe alternatives you've considered
Either downloading from GitHub or fixing the code in the environment, none of which are suitable within workflow managers or SOPs.
Thank you
The text was updated successfully, but these errors were encountered: