Problems updating on Ubuntu

I am having the same problem when updating to 1.2 from 1.17. Namely, when installing the chia-blockchain-gui, here it is what I have on output:

error: Your local changes to the following files would be overwritten by checkout: package-lock.json package.json Please commit your changes or stash them before you switch branches.

Can anyone help? I have followed the instructions from the official chia git-hub page for updating:

Thanks in advance

You local repo of Chia has some changes. You have to stash them as it’s blocking you from updating.

Do below to check what has changed in your local Chia repo.
git status

Then, do below to save the changes if any. I know you’ll say I haven’t made any changes to the cloned repo. Just do this anyway if you want to be able to update Chia.
git stash

Check if all good, it should display nothing to commit.
git status

Your good to go to update Chia local repo.
cd chia-blockchain
. ./activate
chia stop -d all
deactivate
git fetch
git checkout latest
git reset --hard FETCH_HEAD
sh install.sh
. ./activate
chia init

WOW, so quick. Thanks. I will try it now. Thanks again, will report back.

Her is what I have when git status:

On branch latest
Your branch is up to date with ‘origin/latest’.

Changes not staged for commit:
(use “git add …” to update what will be committed)
(use “git restore …” to discard changes in working directory)
(commit or discard the untracked or modified content in submodules)
modified: chia-blockchain-gui (new commits, modified content)

no changes added to commit (use “git add” and/or “git commit -a”)

Should I make git stash?

Looks like nothing to commit anymore (meaning no changes tracked). Just try to stash or continue install.

I am trying but:

Installing on Ubuntu 20.04 LTS or newer: Using installed node.js version.
Running git submodule update --init --recursive.

error: Your local changes to the following files would be overwritten by checkout:
package-lock.json
package.json
Please commit your changes or stash them before you switch branches.
Aborting
Unable to checkout ‘55752b2707de612f6b0c94808b7d5ef9b6dd3617’ in submodule path ‘chia-blockchain-gui’

Have you stopped Chia?

chia stop -d all

Or close the GUI first.

Also try, cd chia-blockchain-gui then git status, git stash.

Of course. I have also restarted several times, made sure chia is not running. There is no gui started, checked “chia stop -d all” plus “ps -Af | grep chia”. Everything is fine. I have also updated everything first via:
sudo apt-get update , sudo apt-get upgrade -y
and tried again, no change.

Is there a chance to delete everything and start the install from scratch? Meaning delete/uninstall chia, not the whole Ubuntu OS. :slight_smile:

Yes, just you may start over. But backup first your keys… the mnenomic if you have plots and some xch already.

I have already done that.
So you are saying to simply remove da chia-blockchain folder and proceed with the installation tutorial as new install, not as upgrade?

Yes, so long as you have the keys that’s safe.

Also you may retain the .chia folder in home… when you do chia init after install it will read that folder.

init checks for old versions of chia installed in your ~/.chia directory.

If so, init migrates these old files to the new version:

  • config (including old SSL files)
  • db
  • wallet
  • Using config.yaml, updates wallet keys and ensures coinbase rewards go to the right wallet puzzlehash.

Worked smooth eve without your last recommendations. Just deleted the folder and installed all again. It even remembered my keys. Thanks for everything. Wish you all the best.

1 Like

I also have a problem updating from 1.1.7 to 1.2.0. I’ve had the full node running on RasPi 4 / Ubuntu 21.04 for a little over a month. Today I followed the official git-hub instructions for updating and ran into some errors that I couldn’t resolve and didn’t find support answers for. So I decided to remove the chia-blockchain folder and do a fresh install (keeping the .chia folder). I followed the standard install instructions, first running apt-get update/upgrade. When I ran install.sh there were a few errors which I wasn’t sure about but even if I tried to continue the activate link was not there. Can someone help me troubleshoot the issue? I am a noob when it comes to this kind of thing.

This was the end of the output when running install.sh that looks to list all the errors.

Ign:139 http://archive.ubuntu.com/ubuntu hirsute-security/universe arm64 Packages                                                                                          
Ign:125 http://archive.ubuntu.com/ubuntu hirsute-security/restricted arm64 Packages                                                                                        
Ign:138 http://archive.ubuntu.com/ubuntu hirsute-security/main arm64 Packages                                                                                              
Ign:139 http://archive.ubuntu.com/ubuntu hirsute-security/universe arm64 Packages                                                                                          
Err:125 http://archive.ubuntu.com/ubuntu hirsute-security/restricted arm64 Packages                                                                                        
  404  Not Found [IP: 91.189.88.142 80]
Ign:138 http://archive.ubuntu.com/ubuntu hirsute-security/main arm64 Packages                                                                                              
Ign:139 http://archive.ubuntu.com/ubuntu hirsute-security/universe arm64 Packages                                                                                          
Fetched 1,058 kB in 11s (94.1 kB/s)                                                                                                                                        
Reading package lists... Done
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/hirsute/main/binary-arm64/Packages  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/hirsute-updates/main/binary-arm64/Packages  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/hirsute-backports/universe/binary-arm64/Packages  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/hirsute/multiverse/binary-arm64/Packages  404  Not Found [IP: 91.189.88.142 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/hirsute-updates/multiverse/binary-arm64/Packages  404  Not Found [IP: 91.189.88.142 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/hirsute-backports/universe/binary-arm64/Packages  404  Not Found [IP: 91.189.88.142 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/hirsute-security/restricted/binary-arm64/Packages  404  Not Found [IP: 91.189.88.142 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

@joelrb You were very helpful with Alex’s issue any thoughts on this one?

Im seeing a lot of ‘404 Not Found’. Check the network connection on the pi. Or the server might be unavailable.

Before I started the Chia update there were some Ubuntu updates that I did. It looks like there were some errors there that I had not noticed or resolved. There were some repositories that weren’t updating correctly which looks to have contributed to the issue. After fixing those I re-ran the install process without those errors.