I am trying to install MongoDB 4.4 on a Raspberry Pi 4 model B running Raspberry Pi OS 64 bits.
I would like to know the proper way to add the depository:
https://repo.mongodb.org/apt/debian/dists/buster/mongodb-org/4.4/
I believe it should be inserted in this folder:
/etc/apt/sources.list.d/
But I can't find the correct manner to do it.
I tried a few options, one being creating a file mongodb-org-4.4.list in the /etc/apt/sources.list.d directory containing this:
deb https://repo.mongodb.org/apt/debian/ buster main
But nothing worked. I always get some error message when running:
apt update
Something like:
Reading package lists... Done
E: The repository 'https://repo.mongodb.org/apt/debian buster 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.
........
Further information:
If I set the contents of /etc/apt/sources.list.d/mongodb-org-4.4.list to:
deb http://repo.mongodb.org/apt/debian buster/mongodb-org/4.4 main
as recommended in the document Install MongoDB Community Edition on Debian.
This is the result of running apt-get update :
root#raspberrypi:/home/pi#
root#raspberrypi:/home/pi# apt-get update
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Ign:4 http://repo.mongodb.org/apt/debian buster/mongodb-org/4.4 InRelease
Hit:5 http://repo.mongodb.org/apt/debian buster/mongodb-org/4.4 Release
Hit:6 http://archive.raspberrypi.org/debian buster InRelease
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-armhf/Packages' as repository 'http://repo.mongodb.org/apt/debian buster/mongodb-org/4.4 InRelease' doesn't support architecture 'armhf'
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'http://repo.mongodb.org/apt/debian buster/mongodb-org/4.4 InRelease' doesn't support architecture 'arm64'
root#raspberrypi:/home/pi#
If someone knows how to solve this please let me know.
Follow instructions in https://docs.mongodb.com/manual/tutorial/install-mongodb-on-debian/, specifically the part about adding keys.
There are no prebuilt packages for arm on Debian. https://www.mongodb.com/download-center/community/releases/archive does provide arm64 on Ubuntu 16.04.
Related
Trying to install mongodb for ubuntu and can't solve the issue.
I got lost, need your help please!
Going according the docs:
https://www.mongodb.com/docs/master/tutorial/install-mongodb-on-ubuntu/
wget -qO - https://www.mongodb.org/static/pgp/server-6.0.asc | sudo apt-key add -
Result (CLI output): on mine ubuntu:
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/6.0 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list
Result (CLI output):
deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/6.0 multiverse
sudo apt-get update
Result (CLI output):
et:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Ign:2 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/4.0 InRelease
Hit:3 http://packages.microsoft.com/repos/code stable InRelease
Hit:4 https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu jammy InRelease
Hit:5 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/4.0 Release
Ign:6 https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/6.0 InRelease
Hit:7 http://il.archive.ubuntu.com/ubuntu jammy InRelease
Ign:8 https://ppa.launchpadcontent.net/upubuntu-com/xampp/ubuntu jammy InRelease
Hit:9 http://il.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:11 https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/6.0 Release
Hit:12 http://il.archive.ubuntu.com/ubuntu jammy-backports InRelease
Err:13 https://ppa.launchpadcontent.net/upubuntu-com/xampp/ubuntu jammy Release
404 Not Found [IP: 185.125.190.52 443]
Reading package lists... Done
W: http://repo.mongodb.org/apt/ubuntu/dists/xenial/mongodb-org/4.0/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
E: The repository 'https://ppa.launchpadcontent.net/upubuntu-com/xampp/ubuntu jammy 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.
W: https://repo.mongodb.org/apt/ubuntu/dists/focal/mongodb-org/6.0/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
sudo apt-get install -y mongodb-org
Result (CLI output):
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
mongodb-org-mongos : Depends: libssl1.0.0 (>= 1.0.1) but it is not installable
mongodb-org-server : Depends: libcurl3 (>= 7.16.2) but it is not installable
Depends: libssl1.0.0 (>= 1.0.1) but it is not installable
mongodb-org-shell : Depends: libssl1.0.0 (>= 1.0.1) but it is not installable
mongodb-org-tools : Depends: libssl1.0.0 (>= 1.0.2~beta3) but it is not installable
E: Unable to correct problems, you have held broken packages.
uname -m
Result (CLI output):
x86_64
lsb_release -a
Result (CLI output):
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy
Good evening, I was having the same problem which was basically the lack of libssl1.1
What I did to solve it was to add the repository that contains this lib to download, in this case I used the focal repository.
Use this command in your terminal to add it to your system:
echo "deb http://security.ubuntu.com/ubuntu focal-security main" | sudo tee /etc/apt/sources.list.d/focal-security.list
Then do an update:
sudo apt-get update
And finally install the library:
sudo apt install libssl1.1
After installed try to install mongodb again, if it worked I'm glad to have helped you, if the problem persists I don't know how I can help you :(
whenever I do sudo apt-get update this output appear
$ sudo apt-get update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' doesn't support architecture 'arm64'
N: Skipping acquire of configured file 'contrib/binary-arm64/Packages' as repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' doesn't support architecture 'arm64'
N: Skipping acquire of configured file 'non-free/binary-arm64/Packages' as repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' doesn't support architecture 'arm64'
N: Skipping acquire of configured file 'rpi/binary-arm64/Packages' as repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' doesn't support architecture 'arm64'
and it's so annoying that there are >N: Skipping acquire of configured file line, although these line are not affect the performance, I mean I can still update or upgrade packages or even install packages without problem.
so the question is, how can I remove those >N: Skipping acquire of configures file message
I had the same problem. I fixed it by entering the following command:
sudo dpkg --remove-architecture arm64
I suspect I may have added the arm64 architecture by mistake at some earlier time. The standard 32-bit Raspberry Pi OS (aka Raspbian) does not support 64-bit applications.
Because a repository which defined in your sources.list doesn't support one of your APT::Architectures config options.
Usually, a software developers in their installation's guides writes a common form of repository specification, like a
deb uri suite component1 [component2 component3 ... ]
This is a one-line-style format specification of repository. I assume that your specification looks like:
deb http://raspbian.raspberrypi.org/raspbian buster InRelease,
where http://raspbian.raspberrypi.org/raspbian is a uri, buster is a suite, and InRelease is a component1. The deb uri suite component1 format is the simplest, and it will guarantee that apt-get will work forever with that repository on the most of user's computers. But, there is a little trap: the developers doesn't know in advance which architectures supported on every machine of every user. When a user have architecture, which is not present in repository, he get the Skipping acquire of configured file '.. doesn't support architecture 'arm64' error.
An answer in the man sources.list:
The format for two one-line-style entries using the deb and deb-src types is:
deb [ option1=value1 option2=value2 ] uri suite [component1] [component2] [...]
deb-src [ option1=value1 option2=value2 ] uri suite [component1] [component2] [...]
, and:
Architectures (arch) is an option. If this option isn't set the default is all architectures as defined by the APT::Architectures config option.
It means that architecture arm64 is also set on your machine, and packages with this architecture requested by your package manager when it is calling that repository. All your APT::Architectures you can see in /etc/apt/apt.conf, or executing in the bash:
> apt-config dump | grep -F "APT::Architectures" -
The correct solution of your issue is to use a repository specification with defined Architecture option. If you need the arm, not the arm64, then specification should be:
deb [arch=arm] http://raspbian.raspberrypi.org/raspbian buster InRelease
With this format the apt package manager will request only packages with arm architecture from the repository.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 1 year ago.
Improve this question
I have been getting an error when I execute:
sudo apt-get update
Error:
Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:5 http://apt.postgresql.org/pub/repos/apt bionic-pgdg InRelease
Ign:6 http://apt.postgresql.org/pub/repos/apt utopic-pgdg InRelease
Hit:7 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/bionic pgadmin4 InRelease
Err:8 http://apt.postgresql.org/pub/repos/apt utopic-pgdg Release
404 Not Found [IP: 2604:1380:2000:7501::69 80]
Reading package lists... Done
E: The repository 'http://apt.postgresql.org/pub/repos/apt utopic-pgdg 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.
I have gone through numerous similar questions, but none of the solutions helped me with this issue. I even replaced the source.list and tried to follow all the steps mentioned in these solutions.
As a new user to ubuntu server system, at this point, I am not sure if this is a program installation issue or a system issue.
Server: Ubuntu 18.04 LTS
Can anyone please assist me with this?
The problem is you have :
Ign:6 http://apt.postgresql.org/pub/repos/apt utopic-pgdg InRelease
There is no release for that version. FYI, the Postgres(PGDG) repos only cover LTS releases. You will need to get rid of the Ubuntu Utopic(14.10) repo. It is probably under:
/etc/apt/sources.list.d/pgdg.list
UPDATE. Add further step to find repo.
If that file does not exist try:
/etc/apt/grep -r -i utopic *
to find where the repo is listed.
use the rm function to remove all packages you cannot update, i.e after you check your source list and can confirm packages blocking your updates
or
simply remember that kali cannot update root files that do not follow the HTTPS protocols so if you have packages using only the HTTP protocol you need to simply change these to HTTPS protocols.
Up until this morning, building my container was a smooth process, now I'm running into some issues with apt get -y mongodb.
I have a very simple Dockerfile, relevant code posted since this is all that is needed to make reproduce the issue.
FROM python:2.7
RUN apt-get update && \
apt-get -y install \
gpg \
mongodb \
I've researched some fixes but they seem a little overboard, should I just change my base image? I'm trying to understand the cause behind this error and how to future proof it.
Note, I forgot to put the trace.
Sending build context to Docker daemon 1.354GB
Step 1/7 : FROM python:2.7
2.7: Pulling from library/python
5ae19949497e: Pull complete
ed3d96a2798e: Pull complete
f12136850781: Pull complete
1a9ad5d5550b: Pull complete
6f18049a0455: Pull complete
900d7861659d: Pull complete
536c9e631831: Pull complete
cb522be31b83: Pull complete
d03d3d7b603d: Pull complete
Digest: sha256:ee76dd856d06bdd734e1c3c816b243c984586629708f0a3e32038f94a891a5d8
Status: Downloaded newer image for python:2.7
---> 3edf9092825f
Step 2/7 : RUN apt-get update && apt-get -y install gpg mongodb curl
---> Running in 870a931ec60c
Get:1 http://security.debian.org/debian-security buster/updates InRelease [39.1 kB]
Get:2 http://deb.debian.org/debian buster InRelease [118 kB]
Get:3 http://security.debian.org/debian-security buster/updates/main amd64 Packages [11.9 kB]
Get:4 http://deb.debian.org/debian buster-updates InRelease [46.8 kB]
Get:5 http://deb.debian.org/debian buster/main amd64 Packages [7897 kB]
Fetched 8113 kB in 4s (1805 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Package mongodb is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'mongodb' has no installation candidate
The command '/bin/sh -c apt-get update && apt-get -y install gpg mongodb curl' returned a non-zero code: 100
I guess you delete the old python:2.7 image and rebuild your dockerfile or just change another pc to do the build. If you use a new image, you can see next:
orange#orange:~$ docker images python:2.7
REPOSITORY TAG IMAGE ID CREATED SIZE
python 2.7 3edf9092825f 8 hours ago 884MB
It shows the image was created 8 hours ago, so the image used is quite different compared the one you used days ago.
From this, if you do a search for python:2.7, you may see it now same with 2.7.16-buster, as you know, debian buster released a few days ago, see this:
2019-07-06: Initial release: 10.0 (press release)
So I guess days ago, the python:2.7 is based on debian stretch, so in new debian release, some packages removed which results in your failure.
Best practice:
You can see there are Simple Tags & Shared Tags in python dockerhub repo, please use Simple Tags which will not always change, don't use Shared Tags which may tag to other image id later, for your case, use python:2.7.16-stretch. In fact this base image is the one you used in the past which tagged as python:2.7, the one now which tagged as python:2.7 is not the one you used in the past.
I'm trying to install Visual studio code.
My Raspb. Version is:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.8 (stretch)
Release: 9.8
Codename: stretch
I tried several method (starting to download .deb and using dpkg or install command) but nothing worked.
How can I fix this problem? I really need VSC because my project is growing and Geany messes up.
Downloaded .deb and .tar files from the official site, followed the setup instruction but I got this error
With dpkg (both 32 and 64bit):
"package architecture (amd64) does not match system (armhf)"
"package architecture (i386) does not match system (armhf)"
With sudo install:
sudo apt install ./code_1.33.1-1554971066_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'code:amd64' instead of './code_1.33.1-1554971066_amd64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
code:amd64 : Depends: libnotify4:amd64 but it is not installable
Depends: libnss3:amd64 (>= 2:3.26) but it is not installable
Depends: apt:amd64 but it is not installable
Depends: libxkbfile1:amd64 but it is not installable
Depends: libsecret-1-0:amd64 but it is not installable
Depends: libgtk-3-0:amd64 (>= 3.10.0) but it is not installable
Depends: libxss1:amd64 but it is not installable
E: Unable to correct problems, you have held broken packages.
With repository:
pi#raspberrypi:~/Downloads $ sudo apt-get update
Err:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Temporary failure resolving 'raspbian.raspberrypi.org'
Err:2 http://archive.raspberrypi.org/debian stretch InRelease
Temporary failure resolving 'archive.raspberrypi.org'
Err:3 https://packages.microsoft.com/repos/vscode stable InRelease
Could not resolve host: packages.microsoft.com
Reading package lists... Done
W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/stretch/InRelease Temporary failure resolving 'raspbian.raspberrypi.org'
W: Failed to fetch http://archive.raspberrypi.org/debian/dists/stretch/InRelease Temporary failure resolving 'archive.raspberrypi.org'
W: Failed to fetch https://packages.microsoft.com/repos/vscode/dists/stable/InRelease Could not resolve host: packages.microsoft.com
W: Some index files failed to download. They have been ignored, or old ones used instead.
pi#raspberrypi:~/Downloads $ sudo apt-get install code
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package code
I'm getting mad about this problem, I tried older repository but they don't work.
There are Community builds of Visual Studio Code available (for Raspberry Pi and other ARM and Intel systems).
The packages are currently available in DEB and RPM format. You can use the scripts provided here to install the packages and add their repository to your system or install it manually.
Below I summarized the steps:
Open a new terminal. If you need super-user rights (you probably do), then you can enter sudo -s and press return to enter a super-user session. Run the installer for your current distribution:
APT instructions
(including Debian, Raspbian, Ubuntu and Linux Mint)
. <( wget -O - https://code.headmelted.com/installers/apt.sh )
Press the return key. Once the installer has completed, you should have a "Code - OSS" entry in your desktop program list.
Manual installation
If for any reason the script above will not work on your system, or you do not want to add the package source for updates, you can get the latest version of the package for your system below.
Public GPG key
For either APT or YUM installation, you'll want the public GPG key to verify the package, which you can download here.
APT and YUM packages
The latest packages are available directly from the PackageCloud releases page.
The specific package you need is available here.
EDIT:
At this time (29.04.2019) the current release (v. 1.32) appears not to be working for everybody. See: issue#64. Seems that you'll have to go back to v. 1.29, which is reported to be running fine.
You can choose this package and install it manually, or use APT. If you decide to install it via APT, note that you'll have to mark the package on hold as described below.
To prevent code-oss from upgrading (so that you can keep v. 1.29 until the issue is fixed) follow these instructions:
Install v. 1.29 via APT:
apt-get install code-oss=1.29.0-1539702286
Then mark it on hold by running:
apt-mark hold code-oss
Now running apt-get upgrade won't try to bump it up until you run:
apt-mark unhold code-oss
This will allow it to upgrade again as usual.