AmiUpdate Update 2.55 (11.10.2024)

Update Amiupdate 2.55

AmiUpdate 2.55 (11.10.2024)

- Fixed an error in the main list helphint where the date of the update was not shown correctly.
Thanks to Niels Bache (#159).

- Made some changes to the routines that handle the Ignore Manager, and saving the list back to disk. An apparent crash appeared to be located there, although it was unreproducible here.

- Fixed a memory leak that occurred each time a scan was started.

- Reworked the "Abort" logic. It is no longer possible to abort the scan, but aborting updatingworks as originally expected.
Whether this fixes the unreproducible crashes or not remains tobe seen.

- Following a successfull login, users were complaining the details were not saved. The call tosave the details was commented out. No idea why, or how long it's been like that, but it shouldwork as expected again!

- Added support for double-clicking items to expand them in the Path Manager.

- Changed the way the notifications are handled when the preferences change.

o Prefs_Updates 53.19 (11.10.2024)
Prefs change notifications are now handled differently to suit the new mechanism.

If the update is not offered or does not work : http://codebench.co.uk/amiupdate_website/files/AmiUpdate.lha

@skynet thanks for your work

@vagappc

Thanks, but it was K-L from the French Amiga-NG forum who saw this update, I'm just relaying K-L's find.

Some of these bugs I reported in 2019 and the guy refused to even acknowledge them at the time

I thinked that he is the author.
I'm sorry.

I don't know who the author is, but an option to postpone the reboot after an update would be nice for those of us with RX cards. I mean, it's not that major of a problem because I just leave the updater running and then reboot the machine myself using a hard reboot, but the option to just say "Later" and quit the updater would be nice.

@MartinW

Simon "Rigo" Archer is the author and maintainer of AmiUpdate.

Thanks to Simon "Rigo" Archer and whoever else is involved.

---
redfox

Thanks for the update

@Rigo

Thanks for the update!

It seems that it have been installed successfully although AmiUpdate crashed at the end, saying: could not open update.library 53.21+

@Primax

Quote:

Here on the “A1222” there were no problems with the update under AmigaOs4.1. “A1222” because I am currently without hardware again

@Primax

Quote:I updated AmiUpdate on a number of partitions (beta test as well as public and others) on a number of machines.

It crashed like you describe only if I didn't use the self-update functionality. When I did, it worked fine.

Best regards,

Niels

Thanks for the update there is still an issue for me, it still does not save the login details


Where are the login details stored? Can I save them manually or copy the eventually encrypted file from my other system?

Edit:
Nevermind, found where it is saved.

However, it keeps asking me about the "Admin Wiki access", is there a way to disable it?

server list (save release info enabled for all):

www.amiupdate.net
update.amigaos.net
sdk.amigaos.net

There seems to be a glitch with the MUI5 shared libraries

MUI5 shared libraries (21.227)
MUI5 3rd party contribution classes (21.11)

AmiUpdate Italian locale files (2.32)

can't be downloaded.

I changed the option to "Store downloaded archives here: RAM Disk:Unpacked" in AmiUpdate preferences but no files are saved in RAM:


I do not have Italian language installed. I checked on my Sam, and there is no Italian.catalog for AmiUpdate, on the Sam no update for Italian locale files is shown. weird.

@Tuvok

Check libs:AmiSSL/ and see if you have amissl_v111m.library. If not, download AmiSSL 4.12 from https://github.com/jens-maus/amissl/releases/tag/4.12

Don't install it (I assume you have the latest AmiSSL v5 installed already). Just copy *only* that 1 file over into libs:AmiSSL/. You might need to reboot. Then try again.

I don't know if this is still required, but it used to be, to get https links working.

@MickJT

Thanks, that did it!!

Now the checksum tab in InfoWB works again too, it refused to calculate checksums for MD5 and SHA1!

Thanks a lot! ) Have a great Weekend!

So I noticed a few discrepancies.

- The latest release is 2.55 but the latest download package is only 2.54.

- The latest download is claimed to be 2.52 on site.

- The latest 2.55 needs to be installed by AmiUpdate updating itself from 2.54 version.

So I grabbed the latest off the website. Installed and it went ok. Reboot. Ran it again and it found a new version. Installed that and reboot again. Now my AmiUpdate is the latest 2.55.

There could be a recurring issue. I didn't see AmiUpdate detect the latest itself. Need to check what I had but it wasn't until I installed the latest available 2.54 manually that AmiUpdate found a newer version.

Also, sometimes I find AmiUpdate checking servers for way too long. Usually finding nothing when there should be some update. I wonder if latest changes cause a slow down in server detection?


Update: (Excusing the pun.)

I updated another volume with the latest AmiUpdate. It had been running 2.49 which is a few releases behind. This confirms my suspicion the issue with AmiUpdate not finding an update to itself is unresolved or has come back. I was stuck on that a few years back.

So I installed 2.54. Reboot and run it. AmiUpdate took a while looking but did not see an update to itself. I then ran a scan and it found an update to itself in the update list. That was strange. Could be a slight bug with latest changes. Well it updated itself fine regardless.