Skip to content
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

Update r-tmae to 1.0.2 #31069

Closed
wants to merge 6 commits into from
Closed

Update r-tmae to 1.0.2 #31069

wants to merge 6 commits into from

Conversation

c-mertes
Copy link
Contributor

@c-mertes c-mertes commented Oct 16, 2021

We moved the main git developer repo to https://github.com/gagneurlab/tMAE.

In addition, this update makes #30957 obsolete.

closes gh-31072, gh-30957

c-mertes and others added 4 commits October 17, 2021 15:10
Also remove from run deps since it's implicitly added by openssl's run_exports.
HDF5Array.so is also directly linked to OpenSSL:
> readelf -d lib/R/library/HDF5Array/libs/HDF5Array.so | grep libcrypto
>  0x0000000000000001 (NEEDED)             Shared library: [libcrypto.so.1.1]
@@ -28,6 +28,7 @@ requirements:
- bioconductor-DESeq2
- bioconductor-IRanges
- bioconductor-GenomicRanges
- bioconductor-hdf5array
Copy link
Member

@mbargull mbargull Oct 23, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why only in host but not run? bioconductor-hdf5array does [edit]not[/edit] define any run_exports and as such won't be added to run implicitly.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think its a bug, and was a proof of concept. The DAG is not properly build if you do not specify the direct dependencies.
https://app.circleci.com/pipelines/github/bioconda/bioconda-recipes/54750/workflows/ddf69ab9-9bf4-4a6c-adfe-2e09fc7f8f75/jobs/173070?invite=true#step-106-18
Now it build in the right order.

I will create a issue.

Copy link
Member

@mbargull mbargull Oct 23, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you mean to write indirect dependency? If it's a direct dependency, then it has to be listed (i.e., only in that case the way the DAG can and should be created that way).

Copy link
Member

@mbargull mbargull Oct 23, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(if it is an indirect dependency, we should split this PR in two and have the *hdf* packages be built beforehand.)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So hdf5* is an indirect dependency of t-mae. I assume that this still gets picked up by the DAG. No? Then we have to split it. See #31185

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure why the DAG wasn't created as expected. Possibly because it didn't look at dependency chains that includes non-to-be-built packages? I can't remember how the DAG is built, TBH.

Yes, please open another PR. (I'll be AFK for the rest of the day, but can approve/merge tomorrow if no one else beats me to it.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And with that other PR then merged you can remove the indirect dependency from the requirements list again (because we actually don't want to directly depend on indirect deps.)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I will do this. Thanks for the help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bioconductor-hdf5 incompatibility with other packages due to new openssl 3
2 participants