FS#22215 - tucan has wrong dependency

Attached to Project: Community Packages
Opened by Heiko Baums (cyberpatrol) - Saturday, 25 December 2010, 23:56 GMT
Last edited by Thomas Dziedzic (tomd123) - Sunday, 26 December 2010, 04:18 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Thomas Dziedzic (tomd123)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
tucan 0.3.10RC has 'pil' as dependency. This should be 'python-imaging' instead.
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Sunday, 26 December 2010, 04:18 GMT
Reason for closing:  Fixed
Additional comments about closing:  pkgrel 3
Comment by Heiko Baums (cyberpatrol) - Sunday, 26 December 2010, 00:17 GMT
Could be, that there is a different bug in tucan. I just saw that python-imaging has a provides=("pil=$pkgver").
But tucan asked me for entering some captchas manually after the last update. So I don't know if this is a down- or an upstream bug.
Comment by Thomas Dziedzic (tomd123) - Sunday, 26 December 2010, 04:14 GMT
Ok, I can change the depends from pil to python-imaging because I think the provides=('pil') was just there for compatibility reasons, to not break older packages that relied on pil. (python-imaging used to be called pil)

Please open another bug report if there is another issue besides the dependency issue.

Loading...