Description of problem: When urpmi.update --update is run, the result is : # urpmi.update --update le média « Core Updates (distrib3) » est à jour le média « Nonfree Updates (distrib13) » est à jour le média « Tainted Updates (distrib23) » est à jour le média « Core 32bit Updates (distrib32) » est à jour le média « Nonfree 32bit Updates (distrib37) » est à jour le média « Tainted 32bit Updates (distrib42) » est à jour but when drakrpm-update is run, some packages are displayed. The debugger displays at line 76 : main::refresh_packages_list(./drakrpm-update:76): 76: my @requested = sort grep { $pkgs->{$_}{pkg} } @filtered_pkgs; DB<5> p @requested dumpcap-2.0.12-1.mga5.x86_64gimp-2.8.14-4.2.mga5.x86_64icu53-data-53.1-12.7.mga5.noarchlib64gimp2.0_0-2.8.14-4.2.mga5.x86_64lib64icu-devel-53.1-12.7.mga5.x86_64lib64icu53-53.1-12.7.mga5.x86_64lib64wireshark7-2.0.12-1.mga5.x86_64lib64wiretap5-2.0.12-1.mga5.x86_64lib64wsutil6-2.0.12-1.mga5.x86_64wireshark-2.0.12-1.mga5.x86_64 DB<6> Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. run urpmi.update --update 2. run drakrpm-update 3.
Are you misunderstanding the function of urpmi.update? urpmi.update [options] updates the media drakrpm-update updates the system using the enabled media which it also updates. urpmi.update --update updates only the update media.
CC: (none) => zen25000
Note that the CLI equivalent of drakrpm-update is urpmi --auto-update which first updates the enabled media then updates the system using the enabled media. Hope that helps. Please close this as invalid (unless I have misunderstood your issue). Barry
OK. I wrote this report because it seems that it is the command line used by mgaapplet-update-checker to find if there are new updates not installed and display the red icon (!) in the task bar. So I would rewrite the title of the bug : "The red icon does not display in the task bar when new updates are available". I find the following lines in /var/log/messages : Apr 27 19:49:20 station mgaapplet[4470]: Computing new updates... Apr 27 19:49:20 station mgaapplet[4470]: running: mgaapplet-update-checker Apr 27 19:49:20 station mgaapplet-update-checker[18914]: ### Program is starting ### Apr 27 19:49:21 station mgaapplet-update-checker[18914]: running: urpmi.update --update Apr 27 19:49:27 station mgaapplet-update-checker[18914]: updating inactive backport media Core Backports (distrib7), Nonfree Backports (distrib17), Tainted Backports (distrib27), Core 32bit Backports (distrib34), Nonfree 32bit Backports (distrib39), Tainted 32bit Backports (distrib44) Apr 27 19:49:27 station mgaapplet-update-checker[18914]: running: urpmi.update Core Backports (distrib7) Apr 27 19:49:29 station mgaapplet-update-checker[18914]: running: urpmi.update Nonfree Backports (distrib17) Apr 27 19:49:30 station mgaapplet-update-checker[18914]: running: urpmi.update Tainted Backports (distrib27) Apr 27 19:49:32 station mgaapplet-update-checker[18914]: running: urpmi.update Core 32bit Backports (distrib34) Apr 27 19:49:33 station mgaapplet-update-checker[18914]: running: urpmi.update Nonfree 32bit Backports (distrib39) Apr 27 19:49:34 station mgaapplet-update-checker[18914]: running: urpmi.update Tainted 32bit Backports (distrib44) Apr 27 19:49:37 station mgaapplet[4470]: Packages are up to date
(In reply to Christian CHEVALIER from comment #3) > OK. > I wrote this report because it seems that it is the command line used by > mgaapplet-update-checker to find if there are new updates not installed and > display the red icon (!) in the task bar. > So I would rewrite the title of the bug : > "The red icon does not display in the task bar when new updates are > available". > Some of the updates that you mentioned in comment #0 were pushed a week ago (the packages from wireshark-2.0.12-1.mga5.sprm), it is odd that you didn't get notified. By default, mgaonline (mgaapplet) checks for updates when you boot your system, and then every 3 hours http://doc.mageia.org/mcc/5/en/content/mgaapplet-config.html It is possible that old and new updates hit your mirror in between the last mgaonline check for updates and your running drakrpm-update, if you're using a mirror that has problems syncing or if you're using $Mirrorlist. http://mirrors.mageia.org/status (Note that green only means the mageia_timestamp is up-to-date, it doesn't mean all packages got synced!) IIUC, $Mirrorlist will perform _much_ better when we use Mirrorbrain. The Princeton mirror is up-to-date and fast. Please try whether you still have issues with mgaonline when using that mirror http://mirror.math.princeton.edu/pub/mageia/ and report back. Thanks :-)
Source RPM: urpmi-8.06.1-1.mga5 => mgaonlineCC: (none) => marja11Assignee: bugsquad => mageiatoolsSummary: urpmi.update does not run a complete update => The red icon does not display in the task bar when new updates are availableKeywords: (none) => NEEDINFO
I replaced my previous mirror (ftp.free.fr/mirrors/mageia.org/) by the Princeton mirror and then got the red icon (!) in the task bar ! So, it works now. But I am surprised that checking the updates at the _same_time_ by two different ways (drakrpm-update and mgaapplet-update-checker) could give two different results (new updates available and Packages are up to date).
(In reply to Christian CHEVALIER from comment #5) > I replaced my previous mirror (ftp.free.fr/mirrors/mageia.org/) by the > Princeton mirror and then got the red icon (!) in the task bar ! > So, it works now. > > But I am surprised that checking the updates at the _same_time_ by two > different ways (drakrpm-update and mgaapplet-update-checker) could give two > different results (new updates available and Packages are up to date). It is impossible to successfully run them both at _exactly_ the same time, because the rpm database can only be locked by one of them. The logs of mgaaplet-update-checker will have shown an error, something like "urpmi database is locked (another program is already using it)" They are not very different ways, btw, because they call some same urpmi code ;-) Anyway, switching to a better mirror solved your original problem, so it wasn't a Mageia bug.
Status: NEW => RESOLVEDResolution: (none) => INVALID