Repository 'https://install.husarnet.com/deb all InRelease' changed its 'Origin' value from '. all' to 'Husarnet'. This must be accepted explicitly before updates for this repository can be applied

Hi @ympek and @dominik,

I’m Ruben, and I work with Ricardo on The Construct.

We provide a script for The Construct users to setup their robots so that they can move robots from the rosjects.

We use the following command to install Husarnet:

curl https://install.husarnet.com/install.sh | sudo bash 

I’ve just tried to setup a robot (my PC, actually) and I was unable, and I had the following error message:

 ‘husarnet’: No such file or directory

With a little more investigation, I found these logs when installing Husarnet:

Hit:1 http://br.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://br.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://br.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 https://linux.teamviewer.com/deb stable InRelease
Get:6 https://deb.nodesource.com/node_14.x focal InRelease [4,583 B]
Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease
Hit:8 http://packages.ros.org/ros/ubuntu focal InRelease
Hit:9 http://packages.ros.org/ros2/ubuntu focal InRelease
Ign:5 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
Err:10 https://packages.cloud.google.com/apt kubernetes-xenial Release
  404  Not Found [IP: 142.251.135.110 443]
Get:11 https://install.husarnet.com/deb all InRelease [7,217 B]
Hit:12 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal InRelease
Reading package lists...
E: The repository 'http://apt.kubernetes.io kubernetes-xenial Release' does not have a Release file.
E: Repository 'https://install.husarnet.com/deb all InRelease' changed its 'Origin' value from '. all' to 'Husarnet'
E: Repository 'https://install.husarnet.com/deb all InRelease' changed its 'Label' value from '. all' to 'Husarnet'
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  husarnet
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 7,162 kB of archives.
After this operation, 13.7 MB of additional disk space will be used.
Err:1 https://install.husarnet.com/deb all/husarnet amd64 husarnet amd64 1:2.0.180
  404  Not Found [IP: 57.129.24.10 443]
E: Failed to fetch https://install.husarnet.com/deb/pool/husarnet/h/husarnet/husarnet-2.0.180-amd64.deb  404  Not Found [IP: 57.129.24.10 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

If I try sudo apt-get update or sudo apt-get update --fix-missing I had:

Hit:1 http://br.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://br.archive.ubuntu.com/ubuntu focal-updates InRelease                                                                                                                                                 
Hit:4 http://br.archive.ubuntu.com/ubuntu focal-backports InRelease                                                                                                                                               
Get:5 https://deb.nodesource.com/node_14.x focal InRelease [4,583 B]                                                                                                                                              
Hit:6 https://linux.teamviewer.com/deb stable InRelease                                                                                                                          
Hit:7 http://packages.ros.org/ros/ubuntu focal InRelease                                                                                                                           
Hit:8 http://security.ubuntu.com/ubuntu focal-security InRelease                                                                                                                   
Ign:3 https://packages.cloud.google.com/apt kubernetes-xenial InRelease                                                                                     
Hit:9 http://packages.ros.org/ros2/ubuntu focal InRelease                                                              
Err:10 https://packages.cloud.google.com/apt kubernetes-xenial Release
  404  Not Found [IP: 142.251.135.110 443]
Hit:11 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal InRelease
Get:12 https://install.husarnet.com/deb all InRelease [7,217 B]
Reading package lists... Done         
E: The repository 'http://apt.kubernetes.io kubernetes-xenial Release' does not have a Release file.
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.
E: Repository 'https://install.husarnet.com/deb all InRelease' changed its 'Origin' value from '. all' to 'Husarnet'
E: Repository 'https://install.husarnet.com/deb all InRelease' changed its 'Label' value from '. all' to 'Husarnet'
N: Repository 'https://install.husarnet.com/deb all InRelease' changed its 'Suite' value from 'all' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

I found a possible solution on the link below:

But since we rely on https://install.husarnet.com/install.sh, I think it would be better if this error is attacked in that https://install.husarnet.com/install.sh script directly, because I’m sure I’m not the only one facing this error.

Please let us know your thoughts/actions on this.

Hi @ralves,
thank you for the report. My rationale for not including this was two fold: as this is an install script I thought that new users will use this for a new install (thus that prompt will never be shown as there will be no metadata change for a freshly added repo), and existing users will simply use apt-get update and hit y when prompted. I’ve never considered using the install script for updating… but it indeed seems like a valid workflow too.
I’ve updated the install script to use the flag you’ve found. Please let me know if it fixes your workflow and sorry for the interruption.


Have a wonderful day
Paweł

Hi @pidpawel,

Thank you for updating the script.

I couldn’t wait for you to update the script, and I had to manually run that --allow-releaseinfo-change option because I had some tests to do.

I suppose your changes will work fine for other users.

I’ll let you know if someone complains.

Cheers.