Summary

chicken-install doesn't check that dependencies installed satisfy the version constraint in the (depends ...) clause

Metadata

Description

The coops branch of the ssql egg depends on coops 1.93. However, the (currently) tagged coops is only 1.92.

When chicken-installing the coops branch of ssql, the user is invited to upgrade coops and, if accepted, coops is upgraded. The installation of ssql then proceeds but issuing chicken-status reveals that coops is only at 1.92.

Changes and comments

[2014-02-01 17:20:00 UTC] sjamaan changed milestone from 4.9.0 to 4.10.0

[2014-02-01 17:20:00 UTC] sjamaan wrote:

I think this can be postponed for 4.10.0

[2015-08-27 08:44:04 UTC] sjamaan changed milestone from 4.10.0 to 4.11.0

[2015-08-27 08:44:04 UTC] sjamaan wrote:

Not sure whether we'll get around to fixing this in CHICKEN 4, but let's aim for it anyway

[2016-02-02 09:44:24 UTC] sjamaan changed milestone from 4.11.0 to 5.0

[2016-08-25 21:11:49 UTC] sjamaan set difficulty to medium

[2017-10-26 23:36:20 UTC] felix wrote:

What would be the desired behaviour here? This particular case means basically a misconfiguration combined with trust in whatever henrietta delivers for the requested version. Shouldn't henrietta fail if the tag doesn't exist?

Or is the version shown by chicken-status wrong? In the C4 repo, the tag and the version in coops.setup seem to be correct (1.93)

[2017-11-23 10:57:37 UTC] felix changed milestone from 5.0 to 5.1

[2019-04-07 12:23:24 UTC] sjamaan changed milestone from 5.1 to 5.2

[2019-04-07 12:23:24 UTC] sjamaan wrote:

Getting ready for 5.1, moving tickets which won't make it in to 5.2.

[2019-08-25 10:26:37 UTC] felix changed status from new to closed

[2019-08-25 10:26:37 UTC] felix set resolution to worksforme

[2019-08-25 10:26:37 UTC] felix wrote:

As I said - this is a configuration error (reference to non-existing version). I'm not sure what should be done here.