pi#raspberrypi:~ $ sudo apt-get update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Ign:3 https://raspbian.snips.ai/buster stable InRelease
Err:4 https://raspbian.snips.ai/buster stable Release
404 Not Found [IP: 143.204.15.89 443]
Reading package lists... Done
E: The repository 'https://raspbian.snips.ai/buster stable Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
configuration details.
The question is answered here: https://askubuntu.com/questions/732985/force-update-from-unsigned-repository
You can either shut off the security for repo updating or exclude those repos from security checks.
Related
Cross posting to try to get some assistance, github has not yielded any comment yet.
https://github.com/kaltura/platform-install-packages/issues/707
After adding in the kaltura repos per instruction, the following errors appear on Focal.
Any ideas on getting around the signature problems?
root#kaltura:~# apt update
Hit:1 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:2 http://installrepo.kaltura.org/repo/aptn/focal propus InRelease [1,426 B]
Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease
Err:2 http://installrepo.kaltura.org/repo/aptn/focal propus InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DE7AA37623C65ECB
Hit:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Reading package lists... Done
W: GPG error: http://installrepo.kaltura.org/repo/aptn/focal propus InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DE7AA37623C65ECB
E: The repository 'http://installrepo.kaltura.org/repo/aptn/focal propus InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
I'm running the following in a Docker container (in a Gitlab CI/CD pipeline) with the python:3 image. I installed git using the following command:
apt-get update
apt-get install -y git
Based on the output, this wasn't even necessary because git was already installed. Unfortunately, I got the following output that states that the "git" command was not found even though the "git" command was used earlier in the script. Does anyone have any idea what's going on here?
$ apt-get update
Get:1 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]
Get:2 http://deb.debian.org/debian bullseye InRelease [116 kB]
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]
Get:4 http://security.debian.org/debian-security bullseye-security/main amd64 Packages [109 kB]
Get:5 http://deb.debian.org/debian bullseye/main amd64 Packages [8183 kB]
Get:6 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [2592 B]
Fetched 8494 kB in 1s (6639 kB/s)
Reading package lists...
$ apt-get install -y git
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.30.2-1).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
$ git --version
git version 2.30.2
$ git config --global user.email "${GIT_USER_EMAIL:-$GITLAB_USER_EMAIL}"
$ git config --global user.name "${GIT_USER_NAME:-$GITLAB_USER_NAME}"
$ regex="^report\/[^\/]*\/([^\/]*)\/(.*)"
$ [[ $CI_COMMIT_BRANCH =~ $regex ]]
$ CUSTOMER="${BASH_REMATCH[1]}"
$ PATH="${BASH_REMATCH[2]}"
$ RELPATH=$(.ci/scripts/find_relative.py "${CI_PROJECT_PATH}" "${PATH}")
$ git submodule add ${RELPATH} ${CUSTOMER}
/scripts-530-146123/step_script: line 151: git: command not found
ERROR: Job failed: command terminated with exit code 1
In this line:
PATH="${BASH_REMATCH[2]}"
you alter the PATH variable. I suspect it no longer has /usr/bin (or wherever git is) in the new path.
I know there are many answers to this but i already tried many solutions on internet but not a single one worked for me .
Im using Ubuntu 19.04 in an Oracle virtual Box.
ather#ather-VirtualBox:~$ sudo apt-get update
[sudo] password for ather:
Ign:1 http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 InRelease
Ign:2 http://security.ubuntu.com/ubuntu disco-security InRelease
Err:3 http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 Release
404 Not Found [IP: 195.135.221.134 80]
Ign:4 http://in.archive.ubuntu.com/ubuntu disco InRelease
Ign:5 http://in.archive.ubuntu.com/ubuntu disco-updates InRelease
Err:6 http://in.archive.ubuntu.com/ubuntu disco Release
404 Not Found [IP: 43.255.166.254 80]
Err:7 http://in.archive.ubuntu.com/ubuntu disco-updates Release
404 Not Found [IP: 43.255.166.254 80]
Err:8 http://security.ubuntu.com/ubuntu disco-security Release
404 Not Found [IP: 91.189.91.39 80]
Reading package lists... Done
E: The repository 'http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://in.archive.ubuntu.com/ubuntu disco Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://in.archive.ubuntu.com/ubuntu disco-updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.ubuntu.com/ubuntu disco-security Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Software Configuration is like this
Ubuntu 19.04 is out-dated. So all packages for Ubuntu 19.04 is found in old-release section.
This may cause this 404 error.
You can refer this post to solve error.
I tried to install Ruby with version specified 2.5.1 (the version is just example), and tried following script, but I got an error as follows. Is it possible to install Ruby with a version using apt installing so I can deal with Ruby version dependency issue?
$ sudo apt update ; sudo apt install ruby-full=2.5.1
Hit:1 http://dl.google.com/linux/chrome/deb stable InRelease
Get:2 https://download.docker.com/linux/ubuntu bionic InRelease [64.4 kB]
Hit:3 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Hit:4 http://ppa.launchpad.net/kelleyk/emacs/ubuntu bionic InRelease
Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:7 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:8 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease
Hit:9 http://ppa.launchpad.net/teejee2008/timeshift/ubuntu bionic InRelease
Fetched 64.4 kB in 2s (41.9 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
40 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '2.5.1' for 'ruby-full' was not found
You can install rbenv which is a Ruby Environment and then you can install the version of Ruby you want over it.
Refer to this answer.
The specific version of ruby you want to install has to be a package available in your Ubuntu distro's package repository. A quick way to check this is using apt list | grep ruby-full or apt list | grep ruby.
If you don't find the version you're looking for, you can add a repository and download it from there. Brightbox is a widely used repository maintaining several ruby version packages. Their installation docs should help you.
Note: I still recommend that you use a ruby version manager like rbenv or rvm.
I have a kubuntu 16.04 on my computer and when i want to do a apt update it get a 403 forbidden error. I visited a lot of web page on the internet and they didn't helped me. how can i fix this issue.
every time i do apt-get update i get these results:
Ign:1 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial InRelease
Err:2 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial Release
Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
Ign:3 http://security.ubuntu.com/ubuntu xenial-security InRelease
Err:4 http://security.ubuntu.com/ubuntu xenial-security Release
503 Service Unavailable
Ign:5 http://archive.ubuntu.com/ubuntu xenial InRelease
Ign:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Err:7 http://archive.ubuntu.com/ubuntu xenial Release
503 DNS error for hostname archive.ubuntu.com: Temporary failure in name resolution. If archive.ubuntu.com refers to a configured cache repository, please check the corresponding configuration file.
Err:8 http://archive.ubuntu.com/ubuntu xenial-updates Release
503 DNS error for hostname archive.ubuntu.com: Temporary failure in name resolution. If archive.ubuntu.com refers to a configured cache repository, please check the corresponding configuration file.
Reading package lists... Done
E: The repository 'cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.ubuntu.com/ubuntu xenial-security Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://archive.ubuntu.com/ubuntu xenial Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://archive.ubuntu.com/ubuntu xenial-updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.