Description of problem: mgaonline rpm will not reinstall all files on Cauldron and Mageia 2 Once you remove/install it, you no longer get update notifications. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Clean install of Mageia-3-beta1-x86_64-DVD.iso. Default runlevel: 3 Package Group Selection has all package groups selected except LSB and Other Graphical Desktops + updates followed with urpme --auto-orphans and reboot. 1. click up a terminal 2. su - root 3. ls -al â/etc/cron.daily/mgaupdate 4. Note file exists on clean install 5. mcc ->Software Management->Install & Remove Software 6. enter mgaonline in search box 7. click Files: and note it has â/etc/cron.daily/mgaupdate as part of rpm. 8. remove the package 9. ls -al â/etc/cron.daily/mgaupdate 10. Note file does not exist 11. Back to mcc and install mgaonline rpm 12. ls -al â/etc/cron.daily/mgaupdate 13. Note file does not exist
Cannot reproduce this on a fully updated M2 and Cauldron. Both on step 3 I get a file not found error message. And when I do find / - iname mgaupdate on Cauldron I see this output : [root@localhost /]# find / -iname mgaupdate /usr/sbin/mgaupdate Roelof
CC: (none) => r.wobben
CC: (none) => thierry.vignaud
@thierry : Can you shine a light at this matter ? Roelof
(In reply to comment #1) > Cannot reproduce this on a fully updated M2 and Cauldron. > Both on step 3 I get a file not found error message. Sorry, bad assumption on my part. I was assuming that the file was supposed to be there according to the FILES given for the rpm in mcc. The problem is, automatic update notification quit working after remove/install of the rpm. My workaround solution was to create a /etc/cron.daily script to run urpmi --downloader wget --auto --auto-update --test since I assumed it was because /etc/cron.daily/mgaupdate did not exist after reinstall. Reason I remove the rpm is, I have a bunch of clean install scripts, one of which removes mgaonline because during it's execution it would lock the rpm database and cause package install failures from the rest of my install scripts.
It's a ghost file. It's normal it doesn't exist until filled in.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX