UpdateManager repeatedly fails to get 28 updates

[Scott Cowles Jacobs]

I am preparing an old computer to give away, and have installed Peppermint 10.

The other day, I invoked Update Manager, to make sure all packages were as up-to-date as possible prior to calling my work finished, and giving away the computer.

There were 230 or so packages to update, and after it ran for awhile, it reported that it had finished all there was for one media, and asked if I wished to continue for another media.

I had no idea what it was talking about, but assumed it knew what it was supposed to do and said "OK".

It shortly put up a window that said (approximately):
"Some packages could not be installed ... would you like to proceed anyway?"
Sure! might as well do what you can. I can try again in a couple days...

There were 28 (?) packages that it could not find ("W: ... 404 Not Found")
under the heading:
"E: Internal Error, ordering was unable to handle the media swap".

I still don't know what "Media Swap" is, but the same thing happened when I tried to get
these final 28 packages a couple of days later.

I will attach a text file showing the output.

I then did apt-get update and apt-get upgrade, and it then successfully installed 35 packages.

tl;dr but the few packages I compared appeared to have a later version in the successfully installed apt-get packages.

I will attach a text file showing the apt-get terminal output, as well.

[I attempted to report this with ubuntu-bug, but it was not installed.
Is there a Peppermint bug-reporting package here somewhere, or ... ?]

[Scott Cowles Jacobs (scott092707)]

In case it is of interest, I will attach also the output of "inxi -Fpm"

[Mark-pcnetspec (mark-pcnetspec)]

I doubt this was a bug as much as you'd just not clicked the "Refresh" button in the update manager .. so it was working with old information.

You might want to check in the update managers

Edit > Preferences

it's set to automatically refresh every 30 minutes.

And remember this auto refresh still leaves scope for packages in the repos to be out of sync with your system cache should they have changed in the last 30 mins (or longer if update manager was not minimised to the system tray).

[Mark-pcnetspec (mark-pcnetspec)]

When you ran 'sudo apt-get update' from the commandline, that had the same effect as clicking the "Refresh" button in update manager would have .. it synced your package cache with the repos prior to you running the 'sudo apt-get upgrade'.

[Scott Cowles Jacobs (scott092707)]

>I doubt this was a bug as much as you'd just not clicked the "Refresh" button in the update
>manager .. so it was working with old information.

So... either Update Manager did not immediately call for an update before informing the user of what updates were available, or the update list became outdated during the downloading/installation of the large list of original packages, such that when it tried to get some of them, it couldn't find them....

Should it not have performed "Update" immediately?

When it couldn't find some of the packages, perhaps it should have suspected some had been replaced, and done an update then, and reported that some of the original packages had been replaced - should it go ahead and get them?...