| Summary: | Update urpmi to say There are no updates available when running urpmi --auto-select --auto if all packages have been updated | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | ftg, mageiatools, marja11 |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | urpmi | CVE: | |
| Status comment: | |||
|
Description
Kristoffer Grundström
2017-02-15 13:59:29 CET
Kristoffer Grundström
2017-02-15 14:00:12 CET
Summary:
Update urpmi to say All packages are up to date when running urpmi.update -a =>
Update urpmi to say All packages are up to date when running urpmi --auto-select --auto
Kristoffer Grundström
2017-02-15 14:01:23 CET
Summary:
Update urpmi to say All packages are up to date when running urpmi --auto-select --auto =>
Update urpmi to say There are no updates available when running urpmi --auto-select --auto if all packages have been updated (In reply to Kristoffer Grundström from comment #0) > 5. If there are no updates, then you'll see Packages are up to date when it > in fact should say "There are no updates available". Why? Because, especially in stable, there'll often be a newer version upstream? Then you could still argue that "There are no updates available" is wrong, too, because a user can fetch the update from upstream and compile it locally. Or because, if a user didn't configure the needed update media, or uses an outdated mirror, he won't get (all) the updates? In that case, "There are no updates available" isn't correct, either, because they are available after correctly adding the update media from a good mirror. CC:
(none) =>
mageiatools, marja11
Marja Van Waes
2017-02-18 20:54:42 CET
Keywords:
(none) =>
NEEDINFO As Marja says, when you factor in the fallibility of the mirror, both phrases mean virtually the same thing. However, "Packages are up to date" is more technically accurate for those who maintain a local mirror of MGA. Updating in this case has two phases: first, sync with your reference mirror and second, do urpmi --auto-update. Unless you have every package in the repository instaled on your system (which is impossible since some conflict with others), the sync may download lots of updated packages that you just don't have installed, but if there just don't happen to be any updates to your install set, "Packages are up-to-date" is more accurate than "there are no updates", since you just saw the sync download a bunch of updates. CC:
(none) =>
ftg Thanks, Frank. @ Kristoffer I'm closing this report as wontfix, because the suggestion isn't an improvement. Even if it were an improvement: Changing existing strings breaks all translations, some of them will take a very long time to be fixed. Please only ask for changes when the original string is really wrong. Status:
NEW =>
RESOLVED |