Skip to content
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

Update mica to 4.18 #166

Merged
merged 3 commits into from
Jul 25, 2019
Merged

Update mica to 4.18 #166

merged 3 commits into from
Jul 25, 2019

Conversation

jeanconn
Copy link
Contributor

@jeanconn jeanconn commented Jul 17, 2019

Update mica to 4.18

Closes #150

@jeanconn
Copy link
Contributor Author

jeanconn commented Jul 23, 2019

I added numpy 1.12.1 here because now that I'm trying to remove the "defaults" from the aca build .condarc, this wasn't building. For some reason it was trying to build using numpy 1.11 which is not in our repo, even though a perfectly useful numpy 1.12.1 is in our repo. I think a bunch of these problems will go away with newer conda; and I'll need to come back and fix recipes at that point.

@jeanconn jeanconn requested a review from taldcroft July 23, 2019 13:51
@jeanconn
Copy link
Contributor Author

It looks like I'm not getting the task_schedule this way though

WARNING:conda_build.noarch_python:Don't know how to handle file: share/mica/task_schedule.cfg. Omitting it from package.

The acis_taco package that appeared to be the model for this is an arch package (not a no-arch python conda package) so that's handled differently. If I can't figure out a work around we can just convert mica to an arch package (though that will be annoying for basically pure Python packages).

@jeanconn
Copy link
Contributor Author

It looks like converting from noarch: python to noarch: generic seems to work?

The mica package made noarch generic looks to install like a Python package but also keeps the task schedule and scripts. The internals of the conda package look a little different, but I don't think we care? I've installed in my devska and the mica tests pass; do we need to do other testing for that change? I can't find useful documentation describing what "magic" we're not getting if we don't use noarch: python on a python package.

@jeanconn
Copy link
Contributor Author

Otherwise I could just remove the noarch altogether and have this install like acis_taco.

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

Successfully merging this pull request may close these issues.

Add mica with starcheck cron task (vers 4.18) to ska3-flight
1 participant