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

Problems with writeManifest for RODBC due to latest having R version 4 dependency #431

Closed
hollywoof opened this issue Jun 1, 2020 · 2 comments

Comments

@hollywoof
Copy link
Contributor

I'm encountering an issue with writing manifest files for RStudio Connect at present.

I think this is due to the latest RODBC requiring R version 4 - which means that the current version is unavailable in my current R version (3.6.3).

I think the writeManifest call is having problems due to the available.packages call on

repo.packages <- available.packages(contriburl = contrib.url(repos, type = "source"), type = "source")

It causes a warning "Unable to find repository URL for package RODBC" and causes the manifest to output as:

    "RODBC": {
      "Source": "CRAN",
      "Repository": null,
      "GithubRepo": null,

which then causes the deployment to fail in RSConnect (via git deployment)

My workaround for this at present is to set options(available_packages_filters = character()) before calling writeManifest - but it feels like writeManifest should somehow handle this problem internally - maybe by setting the filters in the call to available.packages or maybe by searching in
the archives for each repo.

hollywoof added a commit to hollywoof/rsconnect that referenced this issue Jun 1, 2020
See rstudio#431 - this change supports packages where an old version is installed and where a current version is not available
hollywoof added a commit to hollywoof/rsconnect that referenced this issue Jun 1, 2020
See rstudio#431 - this change supports packages where an old version is installed and where a current version is not available
@hollywoof
Copy link
Contributor Author

Apologies for the double commit - http timeout issue (dodgy broadband)

@hadley
Copy link
Member

hadley commented Feb 21, 2023

Looks like this was fixed in #432.

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

2 participants