Latest update taken for HG, now cannot connect

[Tuicemen]

yes or you'll soon run out of space it will should not affect HG.

[soxfan1966]

Can I do from command line via Putty?

[Tuicemen]

Can I do from command line via Putty?

yes

[soxfan1966]

Do u know what the command is?

[Tuicemen]

same as if your connected locally

Code Select Expand

sudo raspi-config

[soxfan1966]

I see. I thought it would be possible to do just the file unpacking from the command line.

But I will connect, get into the config screen and do it from there.

[soxfan1966]

Ok, sorry.  I get it now.   Been a long day, lots of projects to do today.

Anyway, I connected to the pi via Putty, got the config menu, went to advanced options and chose to expand the file system.  Then when I exited the menu it asked if I wanted to reboot, which I said yes.

So I think I am now finally all set.  Thanks

[Tuicemen]

Yep, you should be good to go now.

[soxfan1966]

Wanted to follow up this afternoon.

With no password still, I am getting the HG info about available updates.

I actually read the info provided (I know, I know) and saw the info about the password and need to remove before installing.

So I wanted to clarify that the problem I ran into is not the fault of HG - rather it was the dreaded user error (failure to read important information).

I was able to take and install the latest update with no issues.

Thanks

[Tuicemen]

The requirement of removing your password prior to updating should have been more noticeable.
This also should be posted for all new updates as so few users update regularly.

[bkenobi]

When updating software, the user should always read the change log.  However, I'd agree that an updated that will most likely break things should have some kind of additional notification (pop-up, bold/red text in the change log, etc).  However, IMO this is not really that big a problem.  For typical HG users, they would simply uninstall HG, run the installer for the old version, and restore the backup.  If you don't have a backup, you are playing with fire and that is the user's fault, not the developer.