Opened 11 years ago
Closed 5 years ago
#1050 closed defect (worksforme)
chicken-install doesn't check that dependencies installed satisfy the version constraint in the (depends ...) clause
| Reported by: | andyjpb | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 5.2 |
| Component: | core tools | Version: | 4.8.x |
| Keywords: | Cc: | ||
| Estimated difficulty: | medium |
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.
Change History (8)
comment:1 Changed 10 years ago by
| Milestone: | 4.9.0 → 4.10.0 |
|---|
comment:2 Changed 9 years ago by
| Milestone: | 4.10.0 → 4.11.0 |
|---|
Not sure whether we'll get around to fixing this in CHICKEN 4, but let's aim for it anyway
comment:3 Changed 8 years ago by
| Milestone: | 4.11.0 → 5.0 |
|---|
comment:4 Changed 8 years ago by
| Estimated difficulty: | → medium |
|---|
comment:5 Changed 6 years ago by
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)
comment:6 Changed 6 years ago by
| Milestone: | 5.0 → 5.1 |
|---|
comment:7 Changed 5 years ago by
| Milestone: | 5.1 → 5.2 |
|---|
Getting ready for 5.1, moving tickets which won't make it in to 5.2.
comment:8 Changed 5 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
As I said - this is a configuration error (reference to non-existing version). I'm not sure what should be done here.
I think this can be postponed for 4.10.0