Fix error changed its ‘Origin’ value from ‘Google, Inc.’

image

Hi! Whether you must be wondering why this strange error “changed its ‘Origin’ value from ‘Google, Inc.’ to ‘Google LLC’” occurred or you just copied the error, my job is to tell you why this error occurred and how you can fix it!

After running sudo apt-get update, you must have seen this error or similar to this one.

E: Repository 'http://dl.google.com/linux/chrome/deb stable Release' changed its 'Origin' value from 'Google, Inc.' to 'Google LLC'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Why this problem occurred?

I was updating my packages and my terminal showed me this error, so after digging a bit, I found the fix for this problem, but it raised a question, WHY?

So after searching a bit more I found a proper explanation. One of the stack overflow member Wesam explains:-

This error message is meant to ensure that the new entity named Google LLC you are fetching Google Chrome updates from is the same as Google, Inc. that your system trusts and knows its signature. By accepting the change, you are asking your system to trust Google LLC and accept Google Chrome updates from it in the future.

You can read the whole reply in stack overflow’s website. So now it’s clear why this error occurred, so let’s move to the solution.

Solution

So one of the fix is to use, sudo apt update instead of sudo apt-get update

Now, what is the difference between apt and apt-get?

Apt was introduced in 16.04, a new package manager or you can say, an improved version of apt-get. It comes with some new features like progress bar etc., why not find out yourself?

Just type ‘apt’ and it will show you all newly available commands.

 

And if you want to stick with your decision of using apt-get, you have to use –allow-releaseinfo-change, just type the following command on your terminal, and say goodbye to this problem

sudo apt-get –allow-releaseinfo-change update

This was it, just a small tutorial.

Leave a Reply

Your email address will not be published. Required fields are marked *