kubeflow / kubeflow/mpi-operator
Intel OneAPI PGP key does not support new APT requirements
- Dominant language
- Go
- Stars
- 535
- Forks
- 238
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 10
Description
# What happens
The `apt update` with the intel OneAPI sourcelist does not succeed since the current Intel OneAPI PGP key format does not satisfy new apt PGP management requirements.
# Background
Since Debian trixie, the apt was switched PGP management tools to `Sequoia` which require more restricted PGP format and does not have backward compatibility compared with older debian apt.
However, the intel OneAPI PGP does not satisfy the new requirement.
# Workaround
We need to unconditionally trust the Intel OneAPI PGP key by the `trusted=yes`option when we register it to the apt sourcelist.
# Appendix
- https://community.intel.com/t5/oneAPI-Registration-Download/intel-oneapi-installation-failes-on-debian-trixie-currently/td-p/1655431
- https://github.com/go-gitea/gitea/issues/33400
- https://wiki.debian.org/OpenPGP/Sequoia
- https://github.com/orgs/community/discussions/27607
- https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg2023150.html#:~:text=After%20apt%20switched%20to%20sqv,fails%20to%20update%2C%20failing%20with
Contributor guide
Research direction
No file or test is named in the issue. Start by locating where the Intel OneAPI apt sourcelist is registered, then verify the change with apt update on Debian trixie; done means the sourcelist uses the stated trusted=yes workaround and apt update succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100