Skip to content
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

the repository cannot be signed #9735

Closed
outbreak-sen opened this issue Sep 7, 2021 · 14 comments
Closed

the repository cannot be signed #9735

outbreak-sen opened this issue Sep 7, 2021 · 14 comments

Comments

@outbreak-sen
Copy link

outbreak-sen commented Sep 7, 2021

I got a problem about install . I use ubuntu 18.04 in pc and I follow the instruction. I use the vckg to build the sdk successfully but this can not be used. so then I try to add key and got the repository as instruction for linux and the result is

gpg: key C8B3A55A6F3EFCDE: ""CN = Intel(R) Intel(R) Realsense", O=Intel Corporation" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

And then i add the repository . the result is

E: Failed to fetch http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo/dists/bionic/InRelease 403 Forbidden [IP: 52.218.97.234 80]
E: The repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic 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.

it seems something wrong , then I also can not "sudo apt update"

how to solve?

@MartyG-RealSense
Copy link
Collaborator

Hi @outbreak-sen Intel changed their URL addresses from http to the more secure https in March 2021. Intel updated their official installation documentation pages, but non-official instructions or installation scripts that still use the old http addresses may fail.

#9349 (comment)

@outbreak-sen
Copy link
Author

Hi @outbreak-sen Intel changed their URL addresses from http to the more secure https in March 2021. Intel updated their official installation documentation pages, but non-official instructions or installation scripts that still use the old http addresses may fail.

#9349 (comment)

sorry ,I havn‘t got your point. I just follow the github 's instruction. And I wonder if you could give me some detail instruction about my problem . thanks

@outbreak-sen
Copy link
Author

And when i run "sudo add-apt-repository "deb https://librealsense.intel.com/Debian/apt-repo $(lsb_release -cs) main" -u
" ,the process showed that
"Err:10 http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic InRelease
403 Forbidden [IP: 52.218.1.154 80]
"
i think that this is the main reason ,and i have no idea what to do

@MartyG-RealSense
Copy link
Collaborator

vcpkg is maintained by Microsoft and not Intel.

https://github.com/IntelRealSense/librealsense#building-librealsense---using-vcpkg

Whilst some RealSense users prefer vcpkg to installing librealsense from packages or source code using Intel's official instruction pages, it is not an installation method that I would personally recommend if you have the option of installing librealsense by another method.

I note though that you said after you had built the SDK successfully using vcpkg that "this can not be used". Do you mean that your vcpkg installation did not work and that you then tried building librealsense from packages with the official Intel instructions for doing so on the distribution_linux.md page?

https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md

If you are using Intel's official package instructions then I will next refer you to the discussion in #9105 about the errors that you experienced.

@ttencate
Copy link

ttencate commented Sep 8, 2021

@outbreak-sen

Err:10 http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo bionic InRelease
403 Forbidden [IP: 52.218.1.154 80]

The realsense-hw-public.s3.amazonaws.com is the old repository, and you shouldn't be using it anymore. Probably this was left over from a previous installation, even if you added the new librealsense.intel.com repository today.

You should look at the file /etc/apt/sources.list and all files in /etc/apt/sources.list.d, and remove any mentions of the old repository there (or comment them out by prefixing with #). Then run sudo apt-get update again and the error should be gone.

@outbreak-sen
Copy link
Author

@ttencate
my problem had been solved with your method. It's pretty strange to fix my trouble like this
thank you

@sub400
Copy link

sub400 commented Nov 30, 2021

Hello,

I'm running into a similar problem when trying to install librealsense on Debian (tested Bullseye and Buster). I followed the instructions and successfully registered the servers public key.

But the next step fails:

sudo add-apt-repository "deb https://librealsense.intel.com/Debian/apt-repo $(lsb_release -cs) main" -u

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 570, in update
    res = self._cache.update(fetch_progress, slist,
apt_pkg.Error: E:Failed to fetch https://librealsense.intel.com/Debian/apt-repo/dists/bullseye/InRelease  403  Forbidden [IP: 99.86.241.53 443], E:The repository 'https://librealsense.intel.com/Debian/apt-repo bullseye InRelease' is not signed.

Any suggestions would be very helpful! Thanks in advance.

@ttencate
Copy link

ttencate commented Dec 1, 2021

@sub400 That's a different issue. I don't think Debian is supported at all, only Ubuntu. You may need to switch distros or build from source.

@sub400
Copy link

sub400 commented Dec 1, 2021

@ttencate Thanks for your reply, but I'm pretty sure it worked some time ago on Debian.

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Dec 1, 2021

Hi @sub400 You mention that you tested the package installation on 'Buster and Bullseye'. Those are versions of Raspbian OS, suggesting that you are using a Raspberry Pi. Can you confirm whether that is the case, please? If you are using a Pi and Raspbian then the packages on the distribution_linux_md instruction page would not work as they are designed for x86/AMD64 processors (such as those in desktop and laptop computers), whilst Raspberry Pi has an Arm chip architecture. The Acrobotic guide in the link below would be an appropriate method for Raspian OS on a Pi 4.

https://github.com/acrobotic/Ai_Demos_RPi/wiki/Raspberry-Pi-4-and-Intel-RealSense-D435

Intel has a similar guide for Pi 3.

https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_raspbian.md

@sub400
Copy link

sub400 commented Dec 1, 2021

Hi @MartyG-RealSense, no I'm not talking abauot Raspberry OS, we are using regular Debian on x86/AMD64 architecture.

@MartyG-RealSense
Copy link
Collaborator

@sub400 I see, Raspian OS is based on Debian and has a Bullseye version, but there is also Debian 11 Bullseye, and you are attempting to install librealsense using the Debian packages on the distribution_linux.md page. Thanks very much for the clarification.

I have seen Debian package builds based on the Xenial (16.04), Bionic (18.04) and Focal (20.04) branches of Ubuntu, but not Debian Buster or Bullseye.

@sub400
Copy link

sub400 commented Dec 1, 2021

So I have built the libraries form source on Debian abd everithing is working now. The manual for building from source is not 100% accurate when doing this on Debian as some prerequisites are missing on a fresh Debian installation that might be present on Ubuntu.

Thanks a lot for your assistance.

@MartyG-RealSense
Copy link
Collaborator

It's great to hear that you succeeded, @sub400 - thanks very much for the update and sharing your experience of a Debian build with the RealSense community!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants