-
-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds pinnings for ffmpeg, libblitz, libmatio, libsvm, sox, vlfeat. #194
Conversation
These are the dependencies that I care about and I don't want them to break my packages in future. |
Why does |
I read their change log and guessed. |
Also: http://semver.org/#spec-item-4 |
True, but that assumes 1) That they are following semver 2) That they would some day move to 1.x It doesn't quite work if you stay 0.x forever! Still, I admit that they do appear to be making breaking changes on patch versions, so fair enough. Though it hasn't updated in a long time! |
Yes but also their changelog suggests that they add new features in patch version:
|
Sure, but new features aren't breaking changes. Only changing previously provided public API behaviour/existence is. Anyway, I agreed with you in that their version system is merely one of their own and so pinning it seems the safest option! |
New features will break our packages: conda-forge/staged-recipes#475 |
As I said, I think pinning this is safe since vlfeat seems to be following no real versioning scheme whatsoever (the first version was |
@@ -31,19 +31,25 @@ | |||
pinned = { | |||
'boost': 'boost 1.61.*', | |||
'bzip2': 'bzip2 1.0.*', | |||
'ffmpeg': 'ffmpeg 2.8.*', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Happy with the |
LGTM? |
@conda-forge/core, any comments by anyone to these pinnings? It seems we are in agreement. Would it be too extreme to say we should merge this within 24hrs if there are no objections? |
All good from my end. |
LGTM |
Could you please merge this then? |
Although this has been merged, I have not seen the pull requests suggesting these pins on my feedstocks. Am I missing something here? Is our automatic pin process broken still? |
Hello, Missed libraries have been added to the tracker: http://abi-laboratory.pro/tracker/timeline/vlfeat/ |
@183amir, could you please open a new issue on this repo with a list of the feedstocks that have not received pinning PRs? |
Thanks @lvc. That's very nice of you. |
@jakirkham I thought the whole purpose of adding the pinnings here was that they would be fixed automatically. Why do you need a list of repos for these pull requests? |
Because the pinning service is working on repos. So if you are having issues, these are special case failures. In any event, the real point is that we should no longer be discussing this in a merged PR. This is going to get lost. Please open it in a new issue with this info, @183amir. |
@lvc could you add |
Done: http://abi-laboratory.pro/tracker/timeline/giflib/ Feel free to add more libraries to the tracker (add an issue to https://github.com/lvc/upstream-tracker/issues). I'm interested to add all "live" and popular libraries. Thank you. |
Thank you @lvc |
'fontconfig': 'fontconfig 2.11.*', | ||
'freetype': 'freetype 2.6.*', | ||
'hdf5': 'hdf5 1.8.17|1.8.17.*', | ||
'icu': 'icu 56.*', | ||
'jpeg': 'jpeg 9*', | ||
'libblitz': 'libblitz 0.10|0.10.*', | ||
'libmatio': 'libmatio 1.5.*', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like libmatio
might need to be pinned tighter than 1.5.*.
For
libblitz
: http://upstream.rosalinux.ru/versions/blitz.htmlFor
ffmpeg
: http://abi-laboratory.pro/tracker/timeline/ffmpeg/For
vlfeat
: They keep adding new features in patch version: http://www.vlfeat.org/ and major version is0
. If they are following the semantic versioning schemes:Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.
. New features will break our packages: conda-forge/staged-recipes#475 but however maybe pinning like>0.9.20
be a better option but since this is version0
and they don't follow good practices, the safest bet is to pin it on a patch version. They don't release often.For
sox
: There is no guarantee that they will not break API: http://upstream.rosalinux.ru/versions/libsox.htmlI am guessing API compatibility for
libmatio
,libsvm
.