Apt repository check failure (1. sudo -S apt-get update && sudo -S apt-get check; 2. dpkg --audit).
E: Failed to fetch http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo/dists/focal/InRelease 403 Forbidden [IP: 3.5.70.81 80]
E: The repository ‘http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo focal InRelease’ is not signe
I have an Ubuntu 20.04 , Host machine.
I initially got this error while flashing my Jetson to deprecate from Jetpack 6 to Jetpack 5.1.3 . It failed the check , I clicked on skip check and then after the necessary packages were downloaded , while preparing the os , i got error again , I have attached the logs for reference. Could the problem be because i am using an AMD based host machine
SDKM_logs_JetPack_5.1.4_Linux_for_Jetson_Orin_Nano_[8GB_developer_kit_version]_2024-12-09_12-29-08.zip (92.5 KB)
Hi
Please refer to related link to fix the issue.
opened 08:42AM - 08 Jun 21 UTC
closed 06:31AM - 03 Jul 21 UTC
installation
sudo apt-get update
받기:1 file:/var/cuda-repo-10-2-local-10.2.89-440.33.01 InRe… lease
무시:1 file:/var/cuda-repo-10-2-local-10.2.89-440.33.01 InRelease
받기:2 file:/var/cuda-repo-10-2-local-10.2.89-440.33.01 Release [574 B]
받기:2 file:/var/cuda-repo-10-2-local-10.2.89-440.33.01 Release [574 B]
기존:3 http://mirror.kakao.com/ubuntu bionic InRelease
기존:5 http://mirror.kakao.com/ubuntu bionic-updates InRelease
기존:6 http://mirror.kakao.com/ubuntu bionic-backports InRelease
기존:7 http://mirror.kakao.com/ubuntu bionic-security InRelease
기존:8 https://linux.teamviewer.com/deb stable InRelease
기존:9 https://packages.microsoft.com/repos/vscode stable InRelease
무시:10 http://dl.google.com/linux/chrome-remote-desktop/deb stable InRelease
기존:11 http://dl.google.com/linux/chrome/deb stable InRelease
기존:12 http://dl.google.com/linux/chrome-remote-desktop/deb stable Release
기존:13 http://packages.ros.org/ros/ubuntu bionic InRelease
오류:14 http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial InRelease
403 Forbidden [IP: 52.218.104.41 80]
기존:15 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease
기존:17 http://ppa.launchpad.net/jonathonf/ffmpeg-4/ubuntu bionic InRelease
패키지 목록을 읽는 중입니다... 완료
E: http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo/dists/xenial/InRelease 파일을 받는데 실패했습니다 403 Forbidden [IP: 52.218.104.41 80]
E: The repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial InRelease' is no longer 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 think your server is broken, can you fix it??
# Linux Distribution
#### Using pre-build packages
**Intel® RealSense™ SDK 2.0** provides installation packages for Intel X86/AMD64-based Debian distributions in [`dpkg`](https://en.wikipedia.org/wiki/Dpkg) format for Ubuntu 16/18/20/22 [LTS](https://wiki.ubuntu.com/LTS).
The Realsense [DKMS](https://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support) kernel drivers package (`librealsense2-dkms`) supports Ubuntu LTS kernels 4.4, 4.8, 4.10, 4.13, 4.15, 4.18*, 5.0*, 5.3*, 5.4, 5.13, 5.15, 5.19, 6.2 and 6.5. Please refer to [Ubuntu Kernel Release Schedule](https://wiki.ubuntu.com/Kernel/Support) for further details.
#### Configuring and building from the source code
While we strongly recommend to use DKMS package whenever possible, there are certain cases where installing and patching the system manually is necessary:
- Using SDK with non-LTS Ubuntu kernel versions: **4.16 **
- Integration of user-specific patches/modules with `librealsense` SDK.
- Adjusting the patches for alternative kernels/distributions.
The steps are described in [Linux manual installation guide](./installation.md)
## Installing the packages:
- Register the server's public key:
```
sudo mkdir -p /etc/apt/keyrings
curl -sSf https://librealsense.intel.com/Debian/librealsense.pgp | sudo tee /etc/apt/keyrings/librealsense.pgp > /dev/null
This file has been truncated. show original
Thanks
system
Closed
December 31, 2024, 7:16am
5
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.