Mageia forum

anyone know if there is a template or something that can be fixed to stop writing rsync or ftp into the repo stansas of this file.

ive tried using mcc software repos to set this, but it does not seem to make any difference.
so i edit the mirrors.cache file and replace all ftp with http and all rsync with http, and it fixes the
problem im trying to resolve.

at work our local wan prohibits the use of ftp or rsync, so the only way i can update my laptop is
using http.

the above fixes the problem, but id rather it did not get overwritten again by some unknown update.

regards peter

My usual solution when I encounter that problem is to tunnel via an allowed protocol to my workstation at home, then use it as a proxy to obtain what I need.

I have, in the past, gone to the company I was doing work for, described my problem, and told them that it was going to raise their cost of having me working for them (I'm a consultant) if I was forced to spend extra time and effort working around the problem, given the restraints their IT department was placing on me. Sometimes that works.

That file does not even exist here. If you don't use MIRRORLIST, then that file should not be used at all.
Would be helpful if you provide the output of either urpmq --dump or urpmq --list-media active --list-url
or possibly the complete /etc/urpmi/urpmi.cfg from the affected box.

Best do the following: Remove all your repositories, and add a complete set of new ones, but don't use mirrorlist automatism. Check https://wiki.mageia.org/en/Software_man ... dia_source
You can also do it using commandline, as an example I'm using ftp.snt.utwente.nl as mirror. Feel free to use another one that's near you and up-to-date according to http://mirrors.mageia.org/status

Code: Select all

urpmi.removemedia -a urpmi.addmedia --distrib --wget 'ftp://ftp.snt.utwente.nl/pub/os/linux/mageia/distrib/$RELEASE/$ARCH'

to also enable nonfree and tainted repositories, do afterwards

Code: Select all

urpmi.update --no-ignore "Tainted Release" && urpmi.update --no-ignore "Tainted Updates" && urpmi.update --no-ignore "Nonfree Release" && urpmi.update --no-ignore "Nonfree Updates" && urpmi.update -av

IIRC when you switch to using a specific mirror, /var/cache/urpmi/mirrors.cache will not be automatically deleted. However, it will not be used and you can if you wish delete it.

Jim