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

install_bitbucket fails when dependencies are private #86

Closed
tidy-bot opened this issue Aug 2, 2017 · 3 comments
Closed

install_bitbucket fails when dependencies are private #86

tidy-bot opened this issue Aug 2, 2017 · 3 comments

Comments

@tidy-bot
Copy link

@tidy-bot tidy-bot commented Aug 2, 2017

Issue by moosilauke18
Wednesday Jun 29, 2016 at 19:38 GMT
Originally opened as r-lib/devtools#1245


So, I have a repo in bitbucket which is private the depends on another private repo. As of the latest devtools version (1.12.0), it fails with a 401 unauthorized. I'm using dependencies=TRUE and sending auth_user and password in install_bitbucket.

Also, the dependency I can install no problem first, so it's an issue when the dependency is private.

@tidy-bot
Copy link
Author

@tidy-bot tidy-bot commented Aug 2, 2017

Comment by thercast
Thursday Jun 30, 2016 at 12:24 GMT


Just wanted to mention that I'm experiencing the same issue with private GitHub repositories that depend on packages in other GitHub private repositories. I installed the dependency package from the other private repo first and the install went through without a hitch. But during the installation of the main package from the private GitHub repo it still tries to install the dependency package even though it is already available. FWIW I am using packrat with this project.

@tidy-bot
Copy link
Author

@tidy-bot tidy-bot commented Aug 2, 2017

Comment by filipsch
Saturday Jul 09, 2016 at 16:47 GMT


I'm also seeing this issue. Exact same situation that @moosilauke18 mentions, but for private packages on GitHub.

jimhester added a commit to jimhester/remotes that referenced this issue Aug 28, 2018
We now pass all authentication arguments and build arguments to remotes
and dependencies. This means you can supply the authentication
in in the top level `install_()` call and have that same authentication
be used in downstream Remotes.

This also should propagate upgrade to dependencies appropriately, so
setting `upgrade = FALSE` should disable upgrading for all dependencies,
even grandchildren.

Fixes r-lib#86
Fixes r-lib#53
jimhester added a commit to jimhester/remotes that referenced this issue Aug 28, 2018
We now pass all authentication arguments and build arguments to remotes
and dependencies. This means you can supply the authentication
in in the top level `install_()` call and have that same authentication
be used in downstream Remotes.

This also should propagate upgrade to dependencies appropriately, so
setting `upgrade = FALSE` should disable upgrading for all dependencies,
even grandchildren.

Fixes r-lib#86
Fixes r-lib#53
jimhester added a commit to jimhester/remotes that referenced this issue Aug 28, 2018
We now pass all authentication arguments and build arguments to remotes
and dependencies. This means you can supply the authentication
in in the top level `install_()` call and have that same authentication
be used in downstream Remotes.

This also should propagate upgrade to dependencies appropriately, so
setting `upgrade = FALSE` should disable upgrading for all dependencies,
even grandchildren.

Fixes r-lib#53
Fixes r-lib#86
Fixes r-lib#87
jimhester added a commit to jimhester/remotes that referenced this issue Aug 28, 2018
We now pass all authentication arguments and build arguments to remotes
and dependencies. This means you can supply the authentication
in in the top level `install_()` call and have that same authentication
be used in downstream Remotes.

This also should propagate upgrade to dependencies appropriately, so
setting `upgrade = FALSE` should disable upgrading for all dependencies,
even grandchildren.

Fixes r-lib#53
Fixes r-lib#86
Fixes r-lib#87
jimhester added a commit to jimhester/remotes that referenced this issue Aug 29, 2018
We now pass all authentication arguments and build arguments to remotes
and dependencies. This means you can supply the authentication
in in the top level `install_()` call and have that same authentication
be used in downstream Remotes.

This also should propagate upgrade to dependencies appropriately, so
setting `upgrade = FALSE` should disable upgrading for all dependencies,
even grandchildren.

Fixes r-lib#53
Fixes r-lib#86
Fixes r-lib#87
jimhester added a commit that referenced this issue Aug 31, 2018
We now pass all authentication arguments and build arguments to remotes
and dependencies. This means you can supply the authentication
in in the top level `install_()` call and have that same authentication
be used in downstream Remotes.

This also should propagate upgrade to dependencies appropriately, so
setting `upgrade = FALSE` should disable upgrading for all dependencies,
even grandchildren.

Fixes #53
Fixes #86
Fixes #87
@nataliagalant
Copy link

@nataliagalant nataliagalant commented Aug 20, 2019

I'm still getting an error unless dependencies = FALSE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants