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

trouble installing goseq in R v4.4 Bioconductor v3.2 #4

Open
D-Metzger opened this issue Jun 5, 2024 · 4 comments
Open

trouble installing goseq in R v4.4 Bioconductor v3.2 #4

D-Metzger opened this issue Jun 5, 2024 · 4 comments

Comments

@D-Metzger
Copy link

After updating to the latest version of R v4.4 I have not been unable to install a working copy of goseq which has been my preferred go enrichment tool for some time. Would it be possible to update goseq or could you direct me to who I should contact to enquire about goseq updates?

@nadiadavidson
Copy link
Owner

Hi @D-Metzger ,

@federicomarini will be taking over maintenance of goseq and may be able to help you get it running in R v 4.4.

All the best,
Nadia.

@federicomarini
Copy link
Contributor

Hi @D-Metzger, as of now the goseq package could not build on the Bioc machines, because one of its dependencies was not building (geneLenDataBase).
I currently provided a fix for that, and now geneLenDataBase is building correctly again. Still, the Bioc builds did not complete the operation of re-building the goseq package.

For now, you should be able to install the devel version from github via

devtools::install_github("federicomarini/geneLenDataBase")
devtools::install_github("federicomarini/goseq")

This should be fixed tomorrow according to the build schedule on the Bioc machines - in the meantime, hope the fix I just posted does the job 😉

@D-Metzger
Copy link
Author

Thanks @federicomarini ! No luck with the Bioc build yet but the fix you posted is working great!

@federicomarini
Copy link
Contributor

you can imagine that this fix is likely going to be already included in the soon-to-be-happening build round, so as of friday (saturday if in European time zones, likely 😬 ) the workaround should not be needed any more.
I would tend to leave this issue open for a couple of more days, in case someone passes by with a similar issue.
Afterwards, I would add the link to my forked repo into the codebase of goseq to redirect the traffic about it over there.

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

No branches or pull requests

3 participants