Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#23489 - [namcap] inconsistent dependency resolution
Attached to Project:
Arch Linux
Opened by Eric Belanger (Snowman) - Tuesday, 29 March 2011, 00:37 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Tuesday, 29 March 2011, 23:27 GMT
Opened by Eric Belanger (Snowman) - Tuesday, 29 March 2011, 00:37 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Tuesday, 29 March 2011, 23:27 GMT
|
DetailsDescription:
I ran namcap on a lm_sensors package I'm currently working on. Namcap return that incorrect warning: lm_sensors W: Dependency included but already satisfied ('rrdtool') The rrdtool package is not in the dependency tree of the other lm_sensors dependency. So namcap shouldn't have returned that warning. I also notice that, if I install a lm_sensors package without the rrdtool dependency (although is linked by one of lm_sensors binary), then the incorrect warning is not displayed. It looks like namcap is using the installed lm_sensors package in its dependency resolution. Please ask if you need more or better explanation. |
This task depends upon
Closed by Rémy Oudompheng (remyoudompheng)
Tuesday, 29 March 2011, 23:27 GMT
Reason for closing: Fixed
Additional comments about closing: in version 3.0.5
Tuesday, 29 March 2011, 23:27 GMT
Reason for closing: Fixed
Additional comments about closing: in version 3.0.5
Comment by Eric Belanger (Snowman) -
Tuesday, 29 March 2011, 00:38 GMT
BTW, I'm using namcap 3.0.3-1
Comment by Rémy Oudompheng (remyoudompheng) -
Tuesday, 29 March 2011, 23:27 GMT
The rule checking for these was nonsensical since namcap 3.0. It should be fixed with namcap 3.0.5.