Is it something wrong in repositories ? [Solved]

[j2mcgreg]

Guess which one I use that is not working

For kicks just changed to NL-Alblasserdam. Same thing.

Then the glitch must have appeared between 6:30 am EDT and now. Maybe the day shift update pixies went on a wildcat strike for better pay and conditions

[figueroa]

Just deselect the one that is giving the error, the other will upgrade. We'll have to wait till the prob gets sorted, nothing we can do other than wait. Maybe changing the repo source using MX Repo Manager might help, I haven't tried that. Using the same here.

Would you describe how one does this deselect trick?

[abhidesh128]

Just deselect the one that is giving the error, the other will upgrade. We'll have to wait till the prob gets sorted, nothing we can do other than wait. Maybe changing the repo source using MX Repo Manager might help, I haven't tried that. Using the same here.

Would you describe how one does this deselect trick?

You can use synaptic package manager.

[Eadwine Rose]

Right click the updater icon and select Upgrade using Synaptic.

Then on the left hand side click the button that says Status, then click Upgradable. You can select one package at a time if you wish by right-clicking the one you want, and select mark for upgrade.

On top there is a big button Apply and from there on it should pretty much be clear.


And just now I see things were fixed, as the upgrade of the package that didn't want to happen went through

[srq2625]

FWIW - While it doesn't happen often I sometimes run into this sort of "repo problem". My solution has been to change my MX Linux repo (using the MX Repo Manager) to a different server. I usually have success with just one change but sometimes it takes a second attempt at yet a third server to get everything to update.

[abhidesh128]

Yes. Everything is working correctly now. Updates went smoothly.
The issue has been resolved.

[figueroa]

@Eadwine Rose
Once one deselects a package for upgrade in Synaptic, is that permanent for that version, or just temporary until next repository update? In other words, are there possible unintended consequences? Sometimes a package is upgraded because the new specific version is a dependency of another package being upgraded. I see the possibility of cascading "dependency hell" as a result of over-management.

I'm thinking that many (most?) users would benefit from patience and wait for another cycle. Few upgrades are right-now imperative. In general, the importance of timely upgrades are stressed to the point that many users feel a fire lit underneath them when the little box turns green.

[Eadwine Rose]

It does not permanently disable things, the way I described things just selects that package you wanted for upgrade. The rest just stays there, and doesn't get marked.

In fact, if you leave one not upgraded and close Synaptic, you will see when you right-click the updater icon and select Check for Updates that one package is still available for upgrade.

It does not pin anything, or lock anything, or things like that. If you want to stop something from upgrading in the long run, that is a whole different ballgame.

[arjaybe]

This happens once in a while. The solution is to wait a few hours. If the problem persists beyond a day, then it's time to do something.

[MXRobo]

Yesterday, I ran "sudo apt-get update" as suggested, and it updated immediately after that; coincidence, maybe
- but it worked other times also.