[trinidad]

Well the two upgrades I finished both required running updates twice. The first update attempt failed in both cases (one in qemu on Debian, one on a quad core CPU bare metal) but after waiting a few minutes both second attempts at updates were successful. The upgrade routine then ran smoothly and quickly for both. Curious about the cause, maybe linked to kernel fwupd? I did not reboot between the two attempts at updates and both machines had ample RAM and disk space. I was using the default US repo.

TC 

[Şerban S.]

I watched the 6.2 RC1 review [...] he was having a hard time running it in a virtual box.

I'm nothing like an expert in computers, let alone programmer expert. Yet, I posted a video showing me run Linux Lite 6.2 RC 1 in Virtual Box:

https://dfgkh547-jsdfv8.iyhkj.tk/forums/relea.../#msg59322

May I question the good will of the reviewer?

Best regards!

[Şerban S.]

Well the two upgrades I finished both required running updates twice. The first update attempt failed in both cases (one in qemu on Debian, one on a quad core CPU bare metal) but after waiting a few minutes both second attempts at updates were successful. The upgrade routine then ran smoothly and quickly for both. Curious about the cause, maybe linked to kernel fwupd? I did not reboot between the two attempts at updates and both machines had ample RAM and disk space. I was using the default US repo.

TC

It seems the error happened to many. It happened to me too, but I forgot if I rebooted. I guess that being in the CLI, I just reissued "sudo apt upgrade" and it worked.
The error came from "lite-patch" and I guess it was an internal dpkg - System signalling error.
Thinking and reading about "kernel fwupd", makes me belive that fwupd is vulnerable to CPU tick delays, which often occure when storage media is involved. I got this kind of errors when working on some programs written in RapidQ and Gambas.

The Repo:
I switched to a Romanian mirror, so it's debatable if there was a wget error.

Best regards!

[valtam]

Well the two upgrades I finished both required running updates twice. The first update attempt failed in both cases (one in qemu on Debian, one on a quad core CPU bare metal) but after waiting a few minutes both second attempts at updates were successful. The upgrade routine then ran smoothly and quickly for both. Curious about the cause, maybe linked to kernel fwupd? I did not reboot between the two attempts at updates and both machines had ample RAM and disk space. I was using the default US repo.

TC 

The upgrade logs in each instance would provide clues.

[valtam]

Some interesting info. The lite-themes packages contains 142,000 files, by contrast, the linux image directory for the 6.0 kernel is 7,000 files.
Extracting the lite-themes package in a VM or low end hardware is going to take quite a while, and may give the impression that nothing is happening. Lite Themes is generally only released during Linux Lite releases, and deliberately at least 3 days prior to the official release so as to not impact on people's upgrade experience. That might be why some people say that the upgrade is stalling or they kill it before it has a chance to end, or have to reboot more than once.

At the end of the day, if you are patient and follow the Upgrade instructions to the letter, there should be no issues. In 10 years I think I've released Lite Upgrade twice where it has had an unforseen bug, in which case each time, it is very quickly patched and released straight away. I'm quite paranoid and very careful when it comes to testing over and over, the Lite Upgrade package.

Recent 6.2 Facebook release comment...

[WytWun]

I've now upgraded 2 laptops: both experienced the lite-patch gpg failure (logs from first here).  Once past that, the process - including the actual Lite 6.0 to 6.2 upgrade - completed normally (or at least in straightfoward fashion for 1 of them).

Both machines are relatively low end: one a dual-core Celeron with a 2.5" SATA SSD and the other a quad core Atom with an eMMC SSD module (which are known to be slow).  The machine with the eMMC drive was unpacking the lite-themes package for a good few minutes, while the time to unpack that package on the machine with the SATA SSD wasn't really noticeable.

The Atom machine also hung during the post-update and post Lite-upgrade reboots, but booted ok from a power-down in both cases (and restarts ok from the logout dialog).  I've not seen that behaviour with this machine with previous in-series upgrades...

Despite the problems encountered both upgrades are working fine.

[valtam]

I fresh installed 6.0 in a VM > Rebooted > ran Install Updates (354 packages) >

Got the following error:



Ran Install Updates a second time, no problem (not ideal and I'll see if I can correct the error, in the meantime I've updated the Release Announcement for 6.2)

Rebooted > ran Lite Upgrade to 6.2

Upgrade worked.

Thanks for reporting the error folks

[trinidad]

upgrade logs in each instance would provide clues

Sorry Jerry. I'm so used to LL being stable, and fairly confident in my own abaility to fix things anyway, that I never thought to post the log after the first machine failed and then updated and sucessfully upgraded. I just wanted to report it and see if anybody else had the same little problem with the US repo. The log you posted is from the same error I got. I really thought it might be caused by a CPU delay on my end ( I've had that happen intermittantly on Debian with offline updates) even though my hardware is pretty good.

TC   

[Şerban S.]

[...]
Got the following error:


[...]

Now, seeing the lines, I remembered I saw the same sequence of messages, related to GPG.
Since I'm used to take care of my own, I just pressed "Up Arrow", "Enter" and here we are, update completed.
The rest, was trivial. Took me 3 minutes flat to move from 6.0 to 6.2.
Nothing required any "fine tuning", nothing even close to any kind of regression.
Just this message related to the deprecated key management.
I forgot when I encountered the same sequence. Somewhere in the 5.x series and I remember I did exactly the same thing and it also worked.

Thanks for posting the dpkg messages sequence!

[valtam]

Yeah, that's why I'm not rushing into a 'fix'.