-
Notifications
You must be signed in to change notification settings - Fork 18
Package failing due to outdated nim version #52
Comments
Doesn't that include https://github.com/rotu/nim-records/blob/f1ae07f13811eda064dd664fbb598f377f66730e/records.nimble#L10 The package specifically asked for this. I think I understand your problem now. The build is executed with a Nim version lower than It's weird, because I always require the, at the time of publishing, most recent stable build in my |
Exactly. This package does not build under Also related is #15 |
I'm against the whole notion of keeping the version as low as possible for "compatibility" reasons or whatever excuse is used to not fix the software. I have lots of experiences with the Java world and one of the worst things is this staying forever on low versions. People stay for so long on too low versions and then complain, that jumping 10 versions at once creates lots of issues... I think, in regards to Nim specifically, it is absolutely reasonable to have every official stable version be a valid version floor. |
I agree with you. Maybe I should have said that "I expect the package to be built against the latest stable release 1.6.6 and I am very surprised the current version is behind the latest feature release 1.6.x" |
I just updated the version of Nim on nimble.directory. Currently it is using 1.6.2 |
Thank you!
|
My package build is failing with "Error: Unsatisfied dependency: nim (>= 1.6.0)". I expect packages to be built against 1.6.6 (which I believe is the current stable version).
https://nimble.directory/ci/badges/records/nimdevel/output.html
The text was updated successfully, but these errors were encountered: