FS#43970 - [namcap] warns incorrectly about dependency already satisfied

Attached to Project: Arch Linux
Opened by Christian Krause (wookietreiber) - Friday, 27 February 2015, 08:58 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 26 June 2015, 23:43 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I have PKGBUILD that has a single dependency on readline, however, namcap reports this dependency as included but already satisfied.


Additional info:
* package version(s): namcap 3.2.5-2



Steps to reproduce:

* This is the PKGBUILD: https://raw.githubusercontent.com/wookietreiber/PKGBUILDs/8ac6989426cf781ec606a666b05995bc2b5296b2/mrbayes/PKGBUILD
* makepkg -fs
* namcap mrbayes-3.2.4-1-x86_64.pkg.tar.xz
mrbayes W: Dependency readline included but already satisfied
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 26 June 2015, 23:43 GMT
Reason for closing:  Fixed
Comment by Kyle Keen (keenerd) - Thursday, 25 June 2015, 20:51 GMT
Awesome, this is a great test case. Usually this problem crops up in much larger and more complicated packages.

The superficial cause is from readline somehow getting sucked into the implicitdepend and indirectdependlist list. Removing explicitdepends (readline) from either of those would fix the problem, but it really shouldn't be there at all. It smells like a side effect of a dependency loop.
Comment by Kyle Keen (keenerd) - Friday, 26 June 2015, 23:33 GMT
Fixed in commit f75df6960

Loading...