Gábor Csárdi

Thanks! The second issue seems like a bug indeed. Wrt. to the first, that unfortunately won't work, because you cannot unlock the keyring from the app. Shiny server would need...

That is unfortunate, but I am not sure if can do much about it. Comparing our output to CRAN's output will probably produce a lot of false positives, I am...

> * "old" has issues > * "new" has issues > * but the log of the R CMD checks does not show the same error. revdepcheck should show this...

> This is not reported as a package with problem in problems.md because I think revdepcheck only report by default new broken packages. Yes, but that is calculated by comparing...

> It won't compare the log of the error. I was not clear on that maybe. Sorry. Yeah, that is a bug indeed, we need to compare the whole thing.

It is not a super common situation, but I can take a look at this before the release.

Hi, which version of gitcreds is this? I think the most recent version prints the output from git at least. Also, what was your git version before the upgrade?

gitcreds 0.1.1 prints the output of git, I believe.

This is what I get for git 1.7.7: ``` Error in new_git_error("git_error", args = args, stdout = out, status = attr(out, : System git failed: git: 'credential' is not a...

Checking the git version programmatically seems hard, because the git version strings are quite creative. E.g. my 1.7.7 prints this: ``` > system("git --version") git version 1.7.7.GIT ``` So I...