- This topic has 4 replies, 3 voices, and was last updated Apr 12-5:45 pm by BobC.
-
Posts
-
seaken64
I have several antiX machines in my lab and I have them all set to my default repo at mirror.rit.edu. I stumbled across a couple of threads both here on the antiX forum and at the MX forum where it was stated that the rit.edu mirror was not being updated properly and it was suggested to change to another repo.
Today I updated my “testing” 32-bit antiX and I noticed about three messages at the end of the process that said some packages were not upgraded and pointed to the rit.edu site repo. I changed the repo to la.mxrepo and ran the update and upgrade again and this time it finished with no errors.
My question is how does a user know when to change their repo? Especially given the propensity to use GUI tools to run the updates and upgrades. If I don’t see the error messages on the console how do I know I have a repo problem? And should a user just assume that if something is not working right that their last upgrade failed and change to another repo and try again? And when can I change back to my default repo that is closer to my location? How will I know when it is no longer a “bad repo”?
seaken64
- This topic was modified 2 years ago by seaken64.
BobC
If you are getting errors when connecting to one repo, try a different one. If not sure which to try, let the repo manager choose one. If it chooses the one you were having problems with, guess at a different one that seems reasonably close by.
I had that problem last night, BTW.
anticapitalista
Simply put, user doesn’t know.
Another good reason for people not to fear using the command line.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Simply put, user doesn’t know.
Another good reason for people not to fear using the command line.That’s what I thought. I agree whole-heartedly – I think the command line is the best way to do updates/upgrades.
seaken64
I let the Updater program run so I know when updates are available, but I run the update/upgrade process itself from a terminal so I can see what’s happening and have more control with what’s going on. I just tried it from the updater without changing the defaults, and like how it worked, actually, but I’m the type that wants to know what’s going on.
I don’t change repos by hand, though. I use the repo manager to change things if I ever need to. Not that I couldn’t, just that I have much lower chance of making a mistake that way.
The computer works for ME! Not the other way around 🙂
- You must be logged in to reply to this topic.
