Bug 26448 - urpmq should not warn about 5+ years old behaviour changes
Summary: urpmq should not warn about 5+ years old behaviour changes
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Low minor
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-07 12:37 CEST by Olav Vitters
Modified: 2022-07-28 08:02 CEST (History)
0 users

See Also:
Source RPM: urpmi-8.120-2.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Olav Vitters 2020-04-07 12:37:14 CEST
Description of problem:

urpmq can print the following warnings:
> --requires behaviour changed, use --requires-recursive to get the old behaviour
and
> --suggests now displays the suggested packages, see --allow-suggests for previous behaviour
> You should now use --recommends.

It seems the --requires warning was added on 2008-02-25 14:10:34 +0000 by Pascal Rigaux. I think everyone knows there's a --requires-recursive option by now. I think it's nicer if urpmq is a bit more silent. This behaviour changed 12+ years ago.

For the --suggests change, it was initially added on 2008-07-08 07:58:05 by Pascal Rigaux, then the second sentence was added by Thierry Vignaud on 2014-09-05 16:46:54. Way more recent, though easily 5 years. I don't care too much about the --suggests though, I don't use it that much.

Version-Release number of selected component (if applicable):
8.120-2.mga8.src.rpm

How reproducible:
See steps to reproduce.

Steps to Reproduce:
1. urpmq --suggests something
2. or: urpmq --requires something
3.
Olav Vitters 2020-04-07 12:37:58 CEST

Priority: Normal => Low

Comment 1 Olav Vitters 2020-04-07 12:40:13 CEST
Forgot to add, (obviously) please WONTFIX if you disagree.
Comment 2 Thierry Vignaud 2022-07-28 07:54:24 CEST
No it makes sense
Comment 3 Thierry Vignaud 2022-07-28 08:02:17 CEST
Fixed in git

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.