-
Notifications
You must be signed in to change notification settings - Fork 11
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
Cannot submit to CRAN #30
Comments
(Saw your post on Mastodon. Apologies if the below is something you've already thought about.) I was able to replicate this error on my machine (Debian 12, Intel) when cloning the repo and running I don't think (though I've not maintained a package on CRAN for a couple of years now) that CRAN will generate documentation on the fly, so is there a chance that the |
Thanks for the hint @dill. I checked it manually when submitting, but maybe I missed something or did something wrong. I'll double-check on the next submit. |
Happy to test out your submission on my machine if that helps! :)
…On Thu, 30 Nov 2023, at 08:26, Timothy Wolodzko wrote:
Thanks for the hint @dill <https://github.com/dill>. I checked it
manually when submitting, but maybe I missed something or did something
wrong. I'll double-check on the next submit.
—
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAPIKXSBMLGSJRL2FTF7LYHA7NDAVCNFSM6AAAAAA77BRCM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGMYDMOJSGE>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@dill thanks, but I was able to submit it, so no help needed anymore. |
I cannot submit v 1.10.0 to CRAN because their checks throw:
Which doesn't seem to be true, but I have no idea how to "fix" it for now.
The text was updated successfully, but these errors were encountered: