Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
218 Views

The repository 'https://apt.repos.intel.com/intelpython/binary Release' is no longer signed.

After following instructions from https://software.intel.com/content/www/us/en/develop/articles/installing-intel-free-libs-and-python-... and running 'apt-get update', I get this error message: # apt-get update [...] Ign:34 https://apt.repos.intel.com/intelpython/binary InRelease Get:35 https://apt.repos.intel.com/intelpython/binary Release [874 B] Err:36 https://apt.repos.intel.com/intelpython/binary Release.gpg 403 Forbidden Reading package lists... Done E: The repository 'https://apt.repos.intel.com/intelpython/binary Release' 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.
0 Kudos
3 Replies
Highlighted
Moderator
218 Views

Hi, 

Thanks for reaching out to us. We couldn't reproduce the issue and we were able to run instructions in the given link without any issues and able to install intelpython successfully So, we are forwarding this case with SME to check. They will get back to you on this.

0 Kudos
Highlighted
Employee
218 Views

Hello,

 

I also could not reproduce this issue, so the problem may be related to some permission issues somewhere. That is a "may" here akin to the 403 error code here. 

Could you please try an apt-key update or even try to remove and re-add the key again, and then proceed with apt-get update?

Thanks,

Shailen 

0 Kudos
Highlighted
Beginner
218 Views

Shailen Sobhee (Intel) wrote:

Hello,

 

I also could not reproduce this issue, so the problem may be related to some permission issues somewhere. That is a "may" here akin to the 403 error code here. 

Could you please try an apt-key update or even try to remove and re-add the key again, and then proceed with apt-get update?

Thanks,

Shailen 

A couple of days after the first comment above, the issue "magically" went away. Given that the issue has been there for weeks, I can only deduce that someone has fixed it after my report has been passed on. I obviously had done what you suggested on two different machines before I reported the issue here :^) Someone, somewhere is not taking the credit^W^W^Wadmitting to have fixed it ;^) Cheers, Raf
0 Kudos