Skip to content
This repository has been archived by the owner on Mar 21, 2018. It is now read-only.

build number 0 needs to be fixed. #4

Closed
183amir opened this issue Jun 20, 2016 · 11 comments
Closed

build number 0 needs to be fixed. #4

183amir opened this issue Jun 20, 2016 · 11 comments

Comments

@183amir
Copy link
Contributor

183amir commented Jun 20, 2016

@conda-forge/core build number 0 was not pinned on a boost version. I am trying to fix this build: conda-forge/staged-recipes#751 by downgrading conda-build but that version of conda-build pulls the build number 0 of bob.ip.base. Could you please either delete bob.ip.base-2.0.9-py*_0 from conda-forge channel or hotfix its dependency on boost -> boost 1.60.*?
I did write a hotfix script here: conda-forge/conda-forge.github.io#170 a while ago but it is not complete.

@183amir
Copy link
Contributor Author

183amir commented Jun 20, 2016

The same for bob.io.base build numbers 0, 1, and 2.

@jakirkham
Copy link
Member

I'm confused bob.ip.base build number 0 doesn't seem to be dependent on boost at all.

@183amir
Copy link
Contributor Author

183amir commented Jun 21, 2016

Because it was not listed as dependency but was being pulled during build because of their dependencies.

@jakirkham
Copy link
Member

I see. Thanks for the clarification. So, they are linking to boost, but they just didn't list it explicitly. Correct?

@183amir
Copy link
Contributor Author

183amir commented Jun 21, 2016

I mean boost was a dependency but I did not know at that time.

@183amir
Copy link
Contributor Author

183amir commented Jun 21, 2016

Correct

@jakirkham
Copy link
Member

jakirkham commented Jun 21, 2016

Ok, so those are now removed.

FYI there didn't seem to be a build for bob.ip.base version 2.0.9 build number 0 on Mac. I don't remember if this was intentional (e.g. BLAS related) or unintentional (e.g. failed build).

@183amir
Copy link
Contributor Author

183amir commented Jun 21, 2016

It's because I introduced the mac builds later.

@jakirkham
Copy link
Member

Ok, that's fine.

Do things seem to be working for you now? Should we close this?

@183amir
Copy link
Contributor Author

183amir commented Jun 21, 2016

Thank you but not yet. I need to test this later.

On Tue, Jun 21, 2016, 5:25 PM jakirkham notifications@github.com wrote:

Ok, that's fine.

Do things seem to be working for you now? Should we close this?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#4 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AFeQx7eJfoDw8xxTjbSfJqMqUjhAB_pGks5qOAJYgaJpZM4I5xkQ
.

@183amir 183amir closed this as completed Jul 8, 2016
@183amir
Copy link
Contributor Author

183amir commented Jul 8, 2016

This is fixed. Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants