Closed bsipocz closed 7 years ago
I'll check when github comes back to life....
On Mon, Jul 31, 2017 at 1:11 PM, Brigitta Sipocz notifications@github.com wrote:
@mwcraig https://github.com/mwcraig - Have you seen these issues before? I've tried to add back the version pinning of conda-build, but obviously it didn't solve them.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/astropy/conda-channel-astropy/pull/161#issuecomment-319133285, or mute the thread https://github.com/notifications/unsubscribe-auth/ABGBHywjYuzGq5ZlZDyBZJCAKTz9gC5_ks5sTgrSgaJpZM4OnK07 .
Yeah, this has been happening on all builds recently. I'm working on getting more recipes moved over to conda-forge.
In the short run I think we could skip building astropy-helpers. None of the packages we are currently building omit it as a submodule.
I'll take a look at conda-build-all later today.
OK, I'll try to comment out the helpers in one of the other PRs to see whether that solves the issue.
I don't think helpers will fix it...it would just mean we don't have to build it. How about if I move the other PRs over to conda-forge today?
Sure, that sounds good too.
Can we close this, @bsipocz? Think we can stop building astropy-helpers. I know @astrofrog doesn't want it moved over to conda-forge. The original reason for building it was that some affiliated packages didn't submodule helpers, but I do not believe that is still the case .
OK, let's close it and stop building them altogether. I cannot remember I saw any package use this recently, and even if they do they can always speak up.
@mwcraig - Have you seen these issues before? I've tried to add back the version pinning of conda-build, but obviously it didn't solve them.