I'm following instructions from https://firebase.google.com/docs/crashlytics/get-started-ios?hl=es-419
At this point:
$ pod repo add crashlytics git#github.com:crashlytics/SpecsEAP.git
I'm getting this error:
Cloning spec repo `crashlytics` from `git#github.com:crashlytics/SpecsEAP.git` [!] /usr/bin/git clone git#github.com:crashlytics/SpecsEAP.git -- crashlytics
Cloning into 'crashlytics'... ERROR: Repository not found. fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
I've checked the connection to GitHub:
$ ssh -T git#github.com
Hi Username! You've successfully authenticated, but GitHub does not provide shell access.
I've also checked I have a valid SSH key:
$ ssh-add -l -E md5
4096 MD5:b0:26:2f:78:55:57:51:0f:71:17:6d:93:15:dd:67:a8 myemail#gmail.com (RSA)
What am I missing?
Check the english version of the docs, those do not mention any of those repo-adding commands: https://firebase.google.com/docs/crashlytics/get-started?platform=ios
Looks like the spanish translation is outdated.
Related
I'm trying to push my files to my GitHub, but I'm getting the following error:
error: cannot run rpostback-askpass: No such file or directory
fatal: could not read Username for 'https://github.com': Device not configured
Details:
I'm using MAC
My git version: git version 2.32.1 (Apple Git-133)
I'm linking my project to GitHub with HTTP protocole
I ran git config --global user.name and user.mail in the terminal in Rstudio
I tried to use the solution of running git push -u origin main and when I type in my credentials, it gives me the error: "authentication failed". I never changed my password to GitHub, I checked it today to enter the website, it works.
I tried using ssh protocol instead but it seems to be giving me even more errors even though I created my ssh key and added it successfully to my GitHub. Specifically when I click on create new project and add the ssh link Rstudio says:
Cloning into 'data-science-hw'...
ssh_askpass: exec(rpostback-askpass): No such file or directory Host key verification failed.
fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
I went through all the possible suggestions I could find on the internet but none of them worked. I also tried linking a token generated by git, but it work either.
I would be very happy if anybody has any idea what else I could try..
I'm running Vagrant version 2.2.19 with VirtualBox version 6.1 on Mac OS Monterey version 12.3.1.
When running vagrant up or vagrant up --provision, I'm receiving the following error:
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Upon checking the logs, in provisioner-utility-source-core.log I can see the following log:
[0;38;5;2m ▷ Running the [0m[1m[0;38;5;5m'utility-source-core'[21m[0;38;5;2m provisioner...[0m[0m[0m
[0m[39m[2m* Updating the "core" utility on the "master" branch...[21m[0m
fatal: unsafe repository ('/srv/provision/utilities/core' is owned by someone else)
To add an exception for this directory, call:
git config --global --add safe.directory /srv/provision/utilities/core
[0;38;5;9m ! The [0m[1m[0;38;5;5m'utility-source-core'[21m[0;38;5;9m provisioner ran into problems, the full log is available at [0m[1m[0;38;5;5m'/var/log/provisioners/2022.04.18_18-32-31/provisioner-utility-source-core.log'[21m[0;38;5;9m. It completed in [0m[1m[0;38;5;5m0[21m[0;38;5;9m seconds.[0m[0m
In the above, can see a fatal error:
unsafe repository ('/srv/provision/utilities/core' is owned by someone else)
However, I cannot see any resources online to solve the above fatal error.
What I've tried:
Running vagrant halt then vagrant destroy and then vagrant up to create the box again, and then running vagrant up to see if it solves things (get the same error)
Added Git SSH (using this guide) in case it was a Git error
Uninstalled and then reinstalled VirtualBox
Cleared out IPs from /etc/hosts/hosts, and then ran vagrant up again, to see if there were any conflicts.
Have tried running git config --global --add safe.directory /srv/provision/utilities/core, then re-ran vagrant up --provision - but it does nothing.
Note: I have allowed oracle permissions via security and privacy and have rebooted my machine so it's in effect.
Is there any way to get VVV running again?
This is a known issue that was fixed in newer versions of VVV. Update to at least VVV 3.10.1 and re-provision.
If it is still happening despite updating to newer VVV, raise a GitHub issue.
I'm the VVV project lead, usually when we see these issues we fix them, this isn't something you should need to fix yourself. But if you use stackoverflow to report bugs we don't see it. Either raise a GitHub issue or ask in the VVV slack.
https://github.com/Varying-Vagrant-Vagrants/VVV/issues/new/choose
Currently using install_git() to install from a repo protected by Azure Active Directory results in an error:
> devtools::install_git("https://myteam.visualstudio.com/MyProject/_git/MyAwesomeRPackage")
Downloading git repo https://myteam.visualstudio.com/MyProject/_git/MyAwesomeRPackage
Installation failed: Error in 'git2r_clone': Unable to authenticate with supplied credentials
even though the AAD credentials are stored in the git credential manager. For example, calling this from the command line works just fine:
git clone https://myteam.visualstudio.com/MyProject/_git/MyAwesomeRPackage
is there any way to have R use the credentials from the git credential manager for this install?
Try the git parameter, e.g., git = "external".
I'm using Salt (SaltStack) to install packages in Ubuntu 18.04. I want to install a formula for docker, for example. When I apply docker state, I get an error that a package can't be installed, because the package repository that is used in a formula isn't signed.
ID: docker package
Function: pkg.installed
Name: docker-engine
Result: False
Comment: An error was encountered while installing package(s): E: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-bionic/InRelease 403 Forbidden [IP: 13.33.98.216 443]
E: The repository 'https://apt.dockerproject.org/repo ubuntu-bionic InRelease' is not signed.
Same happens when I'm using another formula.
I found out that if I would install a package manually through a command-line, I would use a --allow-unauthenticated option.
But what is the way to solve this issue while using Salt and salt-formulas? How can I install a package from a not signed repository?
Disabling package verification is a very bad idea in any scenario. The Docker repository is perfectly compliant with Ubuntu package signing standards and publishes a GPG key to verify them. It can be added to the system manually:
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
But this is not the primary problem here - it's that the Salt rule you're referring to is outdated and sets an incorrect Docker repo URL - in recent installation script they've changed it from https://apt.dockerproject.org/repo to https://download.docker.com/linux/ubuntu/ and while the old mirror seems to be working, the signature files for new releases don't seem to be available there, which confuses apt.
So using Ansible (sorry, I don't know Salt):
- apt_key:
url: https://download.docker.com/linux/ubuntu/gpg
- apt_repository:
repo: 'deb https://download.docker.com/linux/ubuntu/ bionic stable'
- apt: name=docker-ce
You can use skip_verify to avoid GPG verification check (e.g., --allow-unauthenticated, or --force-bad-verify),
httpd:
pkg.installed:
- fromrepo: mycustomrepo
- skip_verify: True
So, I'm a noob to Artifactory. I downloaded and installed the dockerized version of Pro - demo license, set up my first repository as a place to push internal packages we've developed for our ubuntu users.
However, when I upload a package and try to sudo apt-get update after adding a new ".list" file to my /etc/apt/sources.list.d, I get this message back:
W: The repository 'https://10.202.13.218/artifactory/ubuntu-dev-local xenial Release' does not have a Release file.
Do I have to gpg sign the packages? That seems like it would be a different error.
You can force artifactory to recreate the release.key file with the following API call:
curl -u admin:topsecret -X POST http://localhost:8081/artifactory/api/deb/reindex/debian-local