-
Notifications
You must be signed in to change notification settings - Fork 66
Issues: r-lib/pak
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
local_install_*
does not work with archive
bug
#756
opened Mar 14, 2025 by
eitsupi
Install an unexpected problem or unintended behavior
citeproc
instead of pandoc-citeproc
when latter required
bug
#755
opened Mar 13, 2025 by
jamesmbaazam
Auth:
Aborted setting keyring password
error in pak when also using the keyring
package on Linux
#751
opened Mar 5, 2025 by
glin
Auth: Make requirement to have username in repo URL optional? Or more doc examples
#750
opened Mar 4, 2025 by
glin
Auth: pak requires non-standard ports to be specified in
.netrc
, unlike curl
#749
opened Mar 4, 2025 by
glin
Failure to unzip when UNC path in use, leading to package installation failure in pak::pkg_install
#745
opened Feb 28, 2025 by
awong234
pak::pkg_install fails to install gihtub-hosted package with remote dependency in subdirectory?
#740
opened Feb 10, 2025 by
d2gex
Respect the environment variable
DOWNLOAD_STATIC_LIBV8
when determining system requirements
#736
opened Jan 13, 2025 by
jranke
Fails to install when there is a parent library path and do not recognize parent libsPath
#732
opened Jan 7, 2025 by
latot
Add support for installing packages from authenticated repositories, with
keyring
support
#729
opened Dec 20, 2024 by
atheriel
conflicting remotes set for packages installed from r-universe via url
#727
opened Dec 17, 2024 by
kevinushey
pak install fails when Bioconductor is inaccessible even if CRAN is
#726
opened Dec 17, 2024 by
Moohan
Previous Next
ProTip!
Follow long discussions with comments:>50.