[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=5
bugtracker_url=http://dev.nethserver.org/projects/nethserver
distroverpkg=centos-release
# This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
# It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
I uncommented the baseurls in the nethserver.repo file for centos-base and centos-updates and it appears to be working now… weird.
Comparing the nethserver.repo file to a few other installs, the baseurl options should be commented out. So does anyone have any thoughts about what happened and why?
yum update
Loaded plugins: changelog, fastestmirror, nethserver_events, presto
Setting up Update Process
Loading mirror speeds from cached hostfile
YumRepo Error: All mirror URLs are not using ftp, http[s] or file.
Eg. Invalid release/
YumRepo Error: All mirror URLs are not using ftp, http[s] or file.
Eg. Invalid release/
* nethserver-base: mirror1.nethserver.org
* nethserver-updates: mirror1.nethserver.org
No Packages marked for Update
You should have a forum title of “Forum Nazi” or something. You seem to always be the one setting people straight, whether people are veering from the preferred NS roadmap or posting incorrectly.
since we are not in fron of the “problematic” server and everybody here is trying to help in his spare time, I think that we all should help the others to help…
in other words, if you (generally speaking) think I (generally speaking) will re-type all the error messages and commands (to try to reproduce the issue or just to search with google), well, you (generally speaking) are wrong…
moreover, using a CLI makes cut and paste the text so easy that you (generally speaking) have no reason to create a screenshot and upload here… and, remember, trying to read and understand what is wrote into a minipicture (using my smartphone) is quite difficult…
this is no a nazi approach, this is almost 15 years in helpdesk (starting from usenet and going trought may, many forums)
Maybe you took what I was saying the wrong way. I’m almost always in agreement with what you have to say, I was just joking around referring to other posts I’ve seen by you in the past. Rather than having to go digging through the forum quoting all of your prior comments that I’m referring to which will even further derail this thread… nevermind.
