[SOLVED] Differences between rpmdrake and urpmi

[wobo]

Installation of MGA2 from free DVD. After installation I configured package media, including non-free and tainted.

During installation I also installed packages like mplayer and vlc which have extended version in tainted. So when I configured the media and started the graphical update function from MCC I expected those packages to be updated to their "tainted" versions (including additional libs and plugins f.ex. gstreamer-ugly and such things. They were not. The GUI said: "No packages available for updates."

I closed rpmdrake and right after I did 'urpmi --auto-update'. urpmi told me that all media were up-to-date, but it listed 39 packages available for updates, including all the expected packages from tainted.

To re-check I closed without updating and opened the update GUI again. And again the GUI did not offer any packages for updates. Then I did the update of the 39 packages via urpmi, no problems.

Is there any explanation why the commandline tool offers packages while the GUI does not although both are using the same information?

[Ken-Bergen]

I thought we'd been over this before.

The GUI updater only looks at repositories flagged as updates.
'urpmi --auto-u' looks at all enabled repositories.

[wobo]

I thought we'd been over this before.

The GUI updater only looks at repositories flagged as updates.
'urpmi --auto-u' looks at all enabled repositories.

Arf!
I know that and still I did not think of it! May be because I use the GUI only once or twice a year...

Sorry for the dumb question!

[Ken-Bergen]

Sorry for the dumb question!

As someone once said "The only dumb question is the one not asked."

[wobo]

As someone posted:

"sorry for the dumb question" is just a rethorical "sorry".

[S_W]

The GUI updater only looks at repositories flagged as updates.
'urpmi --auto-u' looks at all enabled repositories.

Emmmm - is there a special reason for this behaviour? ^^^
For me as a Mageia beginner it would be more logical if GUI updater and Terminal command would have the same result.

Could anybody please enlight me?

[djennings]

The GUI uses only update media to avoid you accidentally installing packages from the backports repository. Packages in backports are not subject to as rigorous QA and so should only be installed by choice.

The command line has many options to control its behaviour. With the --update switch it behaves just like the GUI and will use only update media. (The GUI is after all only a front end to the command line)

BTW: There are two ways to update using GUIs. The update GUI will only use update media as discussed, but if you use the Install/Remove GUI and list 'All Updates' it will show the most recent packages from all enabled repositories.

[S_W]

Code: Select all

(The GUI is after all only a front end to the command line)

^^^ Sure

Thanks a lot for answering!

[Ken-Bergen]

The GUI uses only update media to avoid you accidentally installing packages from the backports repository. Packages in backports are not subject to as rigorous QA and so should only be installed by choice.

Are you serious?
Anyone who enables backports and leaves it enabled has already shot them self in the foot.

It's more likely to be big brother telling you what you can and can't do, sort of like "Install and Remove Software" only showing packages with GUI.

[doktor5000]

BTW: There are two ways to update using GUIs. The update GUI will only use update media as discussed, but if you use the Install/Remove GUI and list 'All Updates' it will show the most recent packages from all enabled repositories.

Exactly, IIRC there was also another view to only show Backports (which is currently useless/empty as there are none of those) which can be used to selectively install such packages. This is better for novices, everybody else will probably use urpmi --auto-update for the core/tainted switch or similar tasks.