oneAPI Registration, Download, Licensing and Installation
Support for Getting Started questions related to download, Installation and licensing for Intel oneAPI Toolkits and software development tools.

Intel oneAPI stil not working in Fedora 38

gronki
Beginner
622 Views

Half a year has passed, and Intel oneAPI still fails to install in Fedora 38. https://community.intel.com/t5/oneAPI-Registration-Download/Expired-signing-key-for-Intel-oneAPI/m-p/1481424

 

It is caused by using a change in the pgp package used by Rpm, which occured between Fedora 37 and 38 (not an expert on this stuff, just a result of a bit of googling).

https://fedoraproject.org/wiki/Changes/RpmSequoia

 

Fedora 37 is nearing end of life and should not be used anymore as it is unmaintained. Therefore currently it is impossible to use oneAPI with any supported version of Fedora. This change will likely be soon rolling to other rpm-based distros.

 

Please fix this, Intel.

Labels (2)
0 Kudos
1 Solution
gronki
Beginner
612 Views

Turns out I was impatient and did not search for the solution. Apparently Intel fixed this already, but it takes a little action if the 2023 version is still installed on the system. Here is what I did:

 

```

LC_ALL=en_US rpm -qa 2>&1 | grep 'rpmdbNextIterator: skipping h#' | cut -d\# -f 2 | while read pkid; do rpm -ev --nodeps --nosignature $(rpm -q --nosignature --querybynumber $pkid); done

```

 

(basically following advice from https://discussion.fedoraproject.org/t/third-party-rpms-with-an-invalid-signing-key-might-cause-errors-during-package-operations/80077)

 

After that, I was able to install oneapi using ``dnf``.

 

Can be closed!

 

 

View solution in original post

0 Kudos
2 Replies
gronki
Beginner
613 Views

Turns out I was impatient and did not search for the solution. Apparently Intel fixed this already, but it takes a little action if the 2023 version is still installed on the system. Here is what I did:

 

```

LC_ALL=en_US rpm -qa 2>&1 | grep 'rpmdbNextIterator: skipping h#' | cut -d\# -f 2 | while read pkid; do rpm -ev --nodeps --nosignature $(rpm -q --nosignature --querybynumber $pkid); done

```

 

(basically following advice from https://discussion.fedoraproject.org/t/third-party-rpms-with-an-invalid-signing-key-might-cause-errors-during-package-operations/80077)

 

After that, I was able to install oneapi using ``dnf``.

 

Can be closed!

 

 

0 Kudos
Vipin_Singh1
Moderator
596 Views

Hi Dominik, thank you for sharing an update. We are glad that the issue has been resolved.  


If you have any further queries, please post a new question as this thread will no longer be monitored by Intel®. 


0 Kudos
Reply