-
Notifications
You must be signed in to change notification settings - Fork 2
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
Continuing on CRAN? #14
Comments
Hi James, Thank you for reaching out, I was unaware that phylosignal was removed from CRAN. I want to keep it there of course. The issue is that adephylo, an essential dependency for phylosignal, has been removed, so I need to figure out what's going on with the maintainer first. I will keep you updated here. |
Update: I have contacted the maintainers of adephylo. They are working on a resubmission to CRAN. |
phylosignal is back on CRAN. |
Thanks for the quick effort! I'll re-add to phylosem on next update.
…On Thursday, October 12, 2023, François Keck ***@***.***> wrote:
phylosignal is back on CRAN.
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AL62VMTN36OELFEJQ3KONW3X7AAH7ANCNFSM6AAAAAA43GL2MI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
James Thorson (he/him)
Alaska Fisheries Science Center, NMFS
Affiliate Faculty, University of Washington
|
Hi all,
I have
phylosignal
as a SUGGESTS for new CRAN packagephylosem
(for phylogenetic structural equation models). However,phylosem
just failed CRAN checks, perhaps becausephylosignal
is now removed from CRAN.Are y'all planning on updating to pass CRAN checks, or should I proceed assuming that
phylosignal
is now unavailable on CRAN?And of course: sorry about any difficulties and trouble! I'm new as a CRAN package maintainer (previously just using GitHub for package distribution) and please tell me if I'm missing some preferred way to discuss dependency issues.
The text was updated successfully, but these errors were encountered: