- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I added intel-oneapi to /etc/apt/sources.list.d/intel-oneapi.list after installing Debian 13 (Trixie)
echo "deb https://apt.repos.intel.com/oneapi all main" | sudo tee /etc/apt/sources.list.d/intel-oneapi.list
I installed new keys:
wget -qO /etc/apt/trusted.gpg.d/intel-oneapi.asc https://apt.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS.PUB
(The new keys are the same as the ones I already had, dated 2 Oct 2023.)
I got this when I tried to update :
root@Blue:~# apt update
Hit:1 http://security.debian.org/debian-security trixie-security InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease
Get:3 http://deb.debian.org/debian trixie-updates InRelease [47.1 kB]
Get:4 https://apt.repos.intel.com/oneapi all InRelease [5,680 B]
Err:4 https://apt.repos.intel.com/oneapi all InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010100 (54)
Warning: OpenPGP signature verification failed: https://apt.repos.intel.com/oneapi all InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Malformed MPI: leading bit is not set: expected bit 8 to be set in 1010100 (54)
Error: The repository 'https://apt.repos.intel.com/oneapi all InRelease' is not signed.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
(1) Why has signature verification failed? Is it because Debian switched to sqv and Intel didn't?
(2) Is there a work-around?
Link Copied
0 Replies

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page