Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / agstephens/jaspy-OLD issues and pull requests

#28 - Discuss conda on ingest servers: can we use this Jaspy

Issue - State: closed - Opened by agstephens almost 6 years ago - 1 comment

#27 - Quick sprint

Issue - State: closed - Opened by agstephens almost 6 years ago - 1 comment

#26 - add cdsapi

Issue - State: closed - Opened by alaniwi almost 6 years ago - 1 comment

#25 - include ANTS

Issue - State: closed - Opened by alaniwi almost 6 years ago - 2 comments

#24 - If jaspy was written in python...

Issue - State: closed - Opened by agstephens almost 6 years ago - 1 comment

#23 - Documenting usage on JASMIN - with a virtualenv

Issue - State: closed - Opened by agstephens almost 6 years ago - 1 comment

#21 - Bash refactor 1

Pull Request - State: closed - Opened by agstephens about 6 years ago

#20 - Re-factoring bash

Issue - State: closed - Opened by agstephens about 6 years ago - 1 comment

#19 - Need a one-liner install

Issue - State: closed - Opened by agstephens about 6 years ago - 1 comment

#18 - Managing Aliases

Issue - State: closed - Opened by agstephens about 6 years ago - 1 comment

#17 - Need to use YAML parser

Issue - State: closed - Opened by agstephens about 6 years ago

#16 - Will exactly the same conda be needed in order to use an @EXPLICIT file?

Issue - State: closed - Opened by agstephens about 6 years ago - 1 comment

#15 - Add to jaspy default envs: Support for BigTIFF in GDAL in JAP

Issue - State: closed - Opened by agstephens about 6 years ago - 1 comment

#14 - What is ".about.json" file in channel?

Issue - State: closed - Opened by agstephens about 6 years ago - 1 comment

#13 - Should jaspy-builder be separate repo from jaspy-deploy?

Issue - State: closed - Opened by agstephens about 6 years ago - 1 comment

#12 - Should recipes be in separate repo?

Issue - State: closed - Opened by agstephens about 6 years ago - 2 comments

#11 - How to update an environment when the `environment.yml` file changes

Issue - State: closed - Opened by agstephens about 6 years ago - 1 comment

#10 - Need to put the OS and version into the JASPY env name: ready for RHEL7?

Issue - State: closed - Opened by agstephens about 6 years ago - 2 comments

#9 - Example approach to managing module files

Issue - State: closed - Opened by agstephens about 6 years ago - 1 comment

#8 - Package: Replace psycopg2 with psycopg2-binary

Issue - State: closed - Opened by agstephens over 6 years ago - 1 comment

#7 - Should module files manage "activate" themselves?

Issue - State: closed - Opened by agstephens over 6 years ago - 1 comment

#6 - Look into creating our own Anaconda channel - what about licensing?

Issue - State: closed - Opened by agstephens over 6 years ago - 1 comment

#5 - Proposal for packages not resolved in `create-jaspy-env`

Issue - State: closed - Opened by agstephens over 6 years ago - 3 comments

#4 - Should we override the prompt when you load/activate

Issue - State: closed - Opened by agstephens over 6 years ago - 2 comments

#3 - Module "unload" needs to work

Issue - State: closed - Opened by agstephens over 6 years ago

#2 - Create local channel under cedaproc

Issue - State: closed - Opened by agstephens over 6 years ago

#1 - Fix spec file listing the pip components issue

Issue - State: closed - Opened by agstephens over 6 years ago - 1 comment