Description of problem: During my post-install tweaking of a new MGA4 machine I tried to install synergy to connect to a mouse and keyboard on my MGA2 machine. I could not find it in the default MIRRORLIST repositories so I manually selected an alternative mirror, having found that the package does exist by googling for it (eg. found at http://pkgs.org/mageia-4/mageia-core-release-x86_64/synergy-1.4.12-3.mga4.x86_64.rpm.html). The synergy packages are still not shown in drakrpm so I downloaded and installed them from a mirror I discovered by googling. Investigation shows that the mirror configured through mcc is not the same URL as the one used to retrieve the packages; no synergy - ftp://ftp.uni-erlangen.de/mirrors/Mageia/distrib/4/x86_64/media/core/release has synergy - ftp://ftp.uni-erlangen.de/mageia/distrib/4/x86_64/media/core/release A small selection of other mirrors configured manually in mcc also fail to show a synergy package. I found none to satisfy my need, so I manually edited the uni-erlangen entry for core release to the URL which has synergy and it now appears in drakrpm display. Version-Release number of selected component (if applicable): How reproducible: See above Steps to Reproduce: 1. see above 2. 3. Reproducible: Steps to Reproduce:
I think that this is a result of bug#12766 and not a problem with the mirrors. There are synergy packages in /core/backports_testing.
No doubt you are right as there are many similarities, though one comment suggested the bug is masked when media are removed and added again. This was not my experience. Also, when the repository URL is modified as shown above the synergy packages reappear in drakrpm display. Could it be that the URL I am using now has no synergy packages in its "Backports" directory to mask the "Core" ones? Dunno, I'll check. R
Got it. I think. Both URLs for (for example) uni-erlangen.de arrive at the same physical directories but I have only manually updated/modified the URLs for the repositories I have enabled. This does not include the various Backports directories. Consequently the Backports are not recorded as being in the same repository as the various Core, Non-Free and Tainted. Perhaps that is enough to escape the masking. This could explain why one commenter suggested removing/replacing repositories was a workaround. If only the repositories actually in use are removed/replaced then the updated list could well use a different mirror from the untouched Backports and thus the effect I am seeing would be achieved. R
This bug was fixed by http://advisories.mageia.org/MGAA-2014-0144.html If not please re-open.
Status: NEW => RESOLVEDResolution: (none) => FIXED