-
Notifications
You must be signed in to change notification settings - Fork 17
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
Bug from CRAN core #12
Comments
yeah I got this email today. I notice that you guys have been working on the package a lot, so I don't want to jump ahead, change it and submit it if it's not ready for primetime. So let me know, I can either do anything that might be needed for the package, submit the current github version as is (after editing the license), or if I should change the last submitted commit and send that. Cheers! |
Can you/we work on the items in the 0.2 milestone and then push? |
See #2 for changing license if you agree to go with MIT that is |
sounds good, I'll try to get to all the milestone issues by tomorrow |
maybe we have enough to close this milestone and send the version with the fixed license now, since there is a deadline, and work on the httr/rcurl thing for v0.3 |
Sure, that sounds good |
@rmaia Yeah, go ahead. It passes all checks for now and should be good to go. We can easily help get the httr version completed before the end of the month. |
so in wrapping up I got this note:
I'm not sure what was changed that required / stopped requiring "assertthat", I think this just slipped in, but figured I'd check before removing it. Are any functions currently using it? Can I just remove? |
I don't see |
I'm likely the one that added it in the |
OK I'm having trouble building & releasing the package. winbuild went ok, but I think Mavericks messed something up on my xcode devtools. when trying to build for release, I get the following error:
I tried following the instructions here but when I run
I tried waiting a couple days and from different connections (fearing it was my university firewall or something), but still, no luck. Any ideas? |
hey @rmaia sorry about that. I had the same problem a while back with the |
Yeah, weird it hasn't been fixed on devtools by now. I did the symbolic link too even though it is not the recommended way. |
ok that worked, version 0.1.1 is on CRAN now |
The text was updated successfully, but these errors were encountered: