-
Notifications
You must be signed in to change notification settings - Fork 46
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
citr currently not available from CRAN #75
Comments
Likewise, but I installed on my desktop yesterday after updating to 4.0.3, but it failed after updating on my laptop today. devtools::install_github("crsh/citr") yields: Downloading GitHub repo crsh/citr@HEAD |
Hi everyone, thanks for reaching out. Currently, remotes::install_github("ropensci/RefManageR")
remotes::install_github("crsh/citr") |
Thank you! Yep: https://cran.r-project.org/web/packages/RefManageR/ says "Archived on 2020-10-27 for policy violation. " Nothing to do with that election, I hope! |
Thanks crsh. Fixed the problem for me too. |
This was very helpful. Thank you. |
RefManageR is on CRAN again since 2020-11-13. Could citr reappear there too? |
Thanks for reaching out. I'll try to resubmit before the end of the week. |
Thanks crsh. The paper I'm working on at the moment is in Word (lit review) but the next will be in RMarkdown so the timing is perfect. |
Hi, I just stumbled on this problem myself, and was relieved to find this issue and see that |
Thanks |
Could you elaborate on that? What error message are you seeing? |
Dear Frederik, first of all: Thank you for maintaining the wonderful citr-package. I probably have the same issue as hao203. I have installed citr on RStudio 1.4.1106 and R 4.0.5. running
returns the following error:
I hope that this helps to debug. Sincerely yours |
Hi, I ran into the same error message as JohannPopp, I wonder if there is any way to fix it? Thanks! |
Hi folks,
Maybe I am missing something but I can't citr for the current version of R. Is this coming? Is there anything I can do to help?
Cheers,
-LA
The text was updated successfully, but these errors were encountered: