Bug #5167
closed
"packages are currently being reinstalled in the background" lasts forever
Added by Adam Thompson over 8 years ago.
Updated over 8 years ago.
Affected Architecture:
i386
Description
After upgrading 32-bit 2.2.2 to 2.2.4, I get the "packages are currently being reinstalled in the background" warning that never goes away.
See attached screenshots; hopefully there's something useful in there.
I can't access the package management screens to force an uninstall of the package; nor do I see any errors on the console.
Unsure how I get past this...
Files
- Status changed from New to Rejected
That just means one of the package reinstallation routines stopped. Info should be in logs. Post on the forum for more discussion/info.
Quick way around it is to reset the package lock via Diagnostics > Backup/Restore.
Diagnostics - Backup/Restore - Clear Package Lock button.
(Certainly not going to download "screenshots" in PDF.)
Whoops, let's try that PDF again...
Kill Bill wrote:
Diagnostics - Backup/Restore - Clear Package Lock button.
(Certainly not going to download "screenshots" in PDF.)
1. Thanks! Didn't know about that.
2. Do you have a better way to capture console output from VGA? Would you prefer 15 individual images?
Adam Thompson wrote:
Whoops, let's try that PDF again...
Can't upload it anyway, max file size is 5MB and there's 5.2MB of screenshots.
They're mostly notable for the fact that there are no errors reported during package upgrades, so I can't tell what failed - and thus can't submit a more useful bug report.
Probably not worth diagnosing at this point (and certainly not in a discussion here on redmine) -- the package system is being gutted and rebuilt for 2.3, unlikely to be anything worth looking at now.
I can confirm that only some of the packages got reinstalled, despite the lack of any error message.
For example, this pull request makes some package file download timeouts bigger and improves a bit of error handling. Something like that would be an improvement.
But as Jimp said, unless there is a reasonable way to repeat and diagnose the exact issue you have experienced, then it is probably better to get the new package stuff in 2.3 and then work hard on debugging that (or maybe the squadron of pigs will get off the ground and the new package code will work perfectly).
Also available in: Atom
PDF