I think the name is not very important (2015.rpm , omvlx3.rpm etc)
a good name for the repository is more important
I think the name is not very important (2015.rpm , omvlx3.rpm etc)
a good name for the repository is more important
Hope to be in the right topic.
Have just (fresh) installed OpenMandrivaLx-2014.0.x86_64.iso via DVD. Then tried to update it. The point is that only very old packages were available! Firefox 29, etc.
Tried,
urpmi.removemedia -a
and reconfiguring repositories. No help. Only old packages available!
Donât understand.
Can someone tell me what to do?
Not to be misunderstood: Internet was available and repository information was downloaded time after time. Always pointing to very old packages.
Must be wrong repository. Youâre not using âhttp://abf-downloads.abf.io/â or âhttp://abf-downloads.rosalinux.ru/â? If so those are no longer in play. Try:
urpmi.addmedia --distrib http://ftp-stud.hs-esslingen.de/pub/Mirrors/openmandriva/openmandriva2014.0/repository/x86_64/
If youâre using x86_64 try this:
urpmi.addmedia --distrib http://ftp-stud.hs-esslingen.de/pub/Mirrors/openmandriva/openmandriva2014.0/repository/x86_64/
For i586:
urpmi.addmedia --distrib http://ftp-stud.hs-esslingen.de/pub/Mirrors/openmandriva/openmandriva2014.0/repository/i586/
Instead of âhttp://ftp-stud.hs-esslingen.deâ substitute the mirror of your choice.
Edit: Changed to show use of mirrors for repositories as I should have done in the first place. Sorry about that. Using a mirror in stead of âabf-downloadsâ lessens the load on our busy servers and frees them up for development tasks. My mistake.
In fact i have tried updating repos but did not use abf.
urpmi.addmedia --distrib http://downloads.openmanâŚ
I will try again with abf.
Thanks
It is really weird. This time I tried,
$ urpmi.removemedia -a
$ urpmi.addmedia --distrib http://abf-downloads.openmandriva.org /openmandriva2014.0 /repository/x86_64/
as suggested but did not work.
After a lot of downloads of synthesis files, including files marked as 2016XXXX, the command
$ urpmi --auto --auto-select --replacefiles 2>&1 | tee /root/upgrade.log
returns that the system is updated!
And Yes, all updates are selected.
What makes me wonder is that my own old system has been updated since OMV 2013 and my repositories has newer packages without any change whatsoever ever since its installation. So why would a fresh installation of 2014.0 do not see the new available packages?
A look at
http://abf-downloads.openmandriva.org /openmandriva2014.0 /repository/x86_64/
reveals that, in spite of following the recipe of urpmi.removemedia and urpmi.addmedia, the fresh installed OMV 2014.0 do not have this repository as a reference! Which repository is this looking at?
Maybe this is clue:
It seems that the fresh install of 2014.0 do not have symbolic links like,
/etc/release, /etc/redhat-release or /etc/rosa-release
pointing to the (also absent) file,
/etc/distro-release
which contains in my own working system,
OpenMandriva Lx release 2014.1 (Phosphorus) for x86_64
Hum, the command line given by ben79 contains wrong spaces. Here they are replaced by #:
http://abf-downloads.openmandriva.org#/openmandriva2014.0#/repository/x86_64/
Did you simply copy/paste it? In this case, they should be suppressed, of course.
Try this:
urpmi.removemedia -a
#
urpmi.addmedia --update main http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/x86_64/main/release/
urpmi.addmedia --update main_Up http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/x86_64/main/updates/
urpmi.addmedia --update non-free http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/x86_64/non-free/release/
urpmi.addmedia --update non-free_Up http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/x86_64/non-free/updates/
urpmi.addmedia --update contrib http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/x86_64/contrib/release/
urpmi.addmedia --update contrib_Up http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/x86_64/contrib/updates/
urpmi.addmedia --update restricted http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/x86_64/restricted/release/
urpmi.addmedia --update restricted_Up http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/x86_64/restricted/updates/
urpmi.addmedia --update main32 http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/i586/main/release/
urpmi.addmedia --update main32_Up http://mirror.yandex.ru/openmandriva/openmandriva2014.0/repository/i586/main/updates/
#
You can replace Yandex by your preferred mirror.
Iâve typed correctly. Hope the problem iss that i should update urpmi first and then try updating the system.
Live mode, with above repository set, updates around (IIRC) 600 MB of packages, among them FF 47.0 for example.
Btw I didnât run update, just launched for test but enough to see it could work.
First thanks for help. Trying to answer everybodyâs:
These commands were issued after fresh installing OMV 2014.0 and OMV 2013.0. Using 2013.0 there was the option to update, for instance, firefox 25 to firefox 29 but no chance to firefox 47 and other updated 2014.2 packages. I have checked for repository updates marked on.
Donât understand why I had not seen /etc/release files in first attempts but they appeared in last attempts. Also no /var/cache/urpmi/mirrors.cache âŚ
I will try my last chances with OMV 2014.2 (maybe i should have done this in the first place!) and OMV 2016 (even for no testing installation).
As root run âurpmi.update -aâ and post all of the output here.
adelson.oliveira based on your last post FF 29 is in main repo FF 47 is in main-updates repo. All package updates go in the âupdatesâ repositories after original release of 2014.0. So looks like for some reason main-testing repo is not enabled?
Hereâs what I have in my 2014:
# urpmi.update -a
medium "main" is up-to-date
medium "main updates" is up-to-date
medium "Main32" is up-to-date
medium "Main32 Updates" is up-to-date
medium "contrib" is up-to-date
medium "contrib updates" is up-to-date
medium "non-free" is up-to-date
medium "non-free updates" is up-to-date
medium "restricted" is up-to-date
medium "restricted updates" is up-to-date
and I think what most people would consider a âfull setâ of repos.
Ben79,
First let me tell you that the OMV LX 3 was installed and it worked fine.
But letâs go to your questions because the situation is really weird (hope LX 3 final comes asap):
urpmi.removemedia -a
returns the expected list of repos: main, contrib, main32, non-free, restricted and their _updates version. I donât see a problem here but no reference is made on what specific repo was being used.
urpmi.update -a
I had not used in fact and, since OMV LX 3 is already installed, I will not be able to give you a return on this; But all repos you list on your post was said to be properly configured with the option to update set but the whole options in a apparently dimming gray as if it could not be unset.
Before trying OMV LX 3 (RC1), I tried OMV 2014.2 iso. Then updates do FF 47 was available and it seemed that everything could go with that. However, since HP printer did not worked (although recognized and configured by the system), OMV LX 3 turn out to be the last chance.
OMV LX 3 worked relatively fine.
Thanks a lot.