Page 1 of 1

AmiUpdate - how I fall behind?

Posted: Wed Oct 15, 2025 2:24 pm
by Yoji
Hi all, quick question please..

I have an install of AmigaOS4.1FE fully patched on my AmigaForever environment.. I have had it in place for at least 3 years and I dont really use it much, but just log in about every month to patch it.. via AmiUpdate.

it was working for ages.. but over last at least 6 months, there were no updates, and then recently (last 3 months or so) it started asking me to log in to the "AmigaOSUpdateServer".. I suspect I logged in AGES ago, but it cached it.. so didnt prompt me, but started to again.
Anyway, I saw a post elsewhere that said I needed updated AmiUpdate (I was on 2.49 IIRC) and latest is 2.58 so I tried update manually, but needed update the update_lib to 53.21 first.. so did that first, updated to latest AmiUpdate and then it started to update OK, with no request to log in.
So my first question.... how/why did I have to go through this manual process, should not AmiUpdate have kept my system up to date if i doing it each month? Should I not have been able get so behind?

These are core parts of OS4.1FE? so should have been covered/updated?

Re: AmiUpdate - how I fall behind?

Posted: Wed Oct 15, 2025 5:05 pm
by nbache
Actually, AmiUpdate is - as far as I know - a contribution.

But never mind.

There were some problems with recent versions of AmiUpdate and its servers (or something), which made it necessary for many users to install 2.58 manually and start from there.

Once you have that in place, you should be able to get all pending updates again.

Best regards,

Niels

Re: AmiUpdate - how I fall behind?

Posted: Wed Oct 15, 2025 6:05 pm
by Yoji
OK, thanks for the reply..
Yes, I am sure AmiUpdate is not exactly part of the OS, but it is distributed in the core OS, advertised as a core feature.
So while your explanation sort of makes sense... but is not really OK..
Sure, we can expect blips where something does not work, but it should be fixed robustly, not just left that everyone has to execute a manual workaround.
There does not seem to be robust communication processes in place to let people know... they are just left with "HHmmmm... not seen any updates for a while".... and nothing to explain that there is a required update to get them back on track.

Not really very good..
Lets see if anyone else chips in with more details/explanation.
I will then do a separate post adding extra reasons why it is a PITA and should be better.