AmiUpdate - how I fall behind?

[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?

[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

[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.

[Yoji]

LOL, May be Hyperion heard me, just seen that update 3 was released yesterday!!!
May be that will resolve.. by going to update 3, it may in effect jump start everything to "catch up" and all OK.

[MichaelMerkel]

update 3 also shipped the latest amiupdate contribution archive.
that one fixes the (so far known) connection problems of older amiupdate versions.

regards...
michael

[nbache]

But if you have an older AmiUpdate installed now, I'd recommend getting the newest (2.58) from amiupdate.net and install it first, then you will be able to use it to get Update 3 installed. It's the good old chicken and egg issue .

Alternatively, get the Update 3 archive yourself from Hyperion's website, unpack it and install it directly with the installation program inside it (i.e. not using AmiUpdate), so it also installs AmiUpdate for you.

Best regards,

Niels

[Yoji]

Thanks guys...
You missed the point of the post..
I should never have been able to get into the catch 22 situation..
SO while its great that Patch 3 does indeed perform all the catch up needed... they need make sure we dont get in this situation again.

[nbache]

It should also never rain when I want the sun to shine.

But sh*t happens.

Please remember you're not dealing with a multi-trillion dollar company (such as Apple e.g.), but with small, partly volunteer-driven outfits (yes, outfits in plural).

And it's not Update 3 itself which solved the issue, but AmiUpdate 2.58. Because it was known that this version had solved the previous Catch-22-like issues, it was decided to include it (still as a contribution) in the Update 3 archive.

So there you have it. Glad you've solved it, and yes, everybody is - as ever - trying to avoid things like this happening.

You're welcome .

Best regards,

Niels