1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
*****************************
Keeping AstroConda "Like New"
*****************************
Anaconda's package manager, Conda, will not automatically update unless a newer version of a package is detected during
a routine package installation. Suffice to say, unless you keep your packages up to date with ``conda update``, the
packages installed in your Anaconda distribution will remain relatively static.
Updating AstroConda
===================
There are few simple ways to update packages obtained from AstroConda:
Method One - Updating the Metapackage
-------------------------------------
.. code-block:: sh
$ conda update -n astroconda astroconda
Updating the ``astroconda`` metapackage only effects packages that are part of the **official public release** of our software.
Using this method, packages that are in the AstroConda repository, but not controlled by the ``astroconda`` metapackage,
**will not receive updates**. Please use method two below.
Method Two - Updating All Packages
----------------------------------
.. code-block:: sh
$ conda update -n astroconda --all
This method will update the ``astroconda`` metapackage, as well all other packages installed in your enviroment.
Please keep in mind, this updates **all packages** regardless if they were installed from AstroConda, Continuum, Inc.,
or other third party repositories defined in ``$HOME/.condarc``.
(`ref <http://conda.pydata.org/docs/using/pkgs.html#package-update>`__)
Method Three - Updating Packages Individually
---------------------------------------------
.. code-block:: sh
$ conda update -n astroconda stsci.tools
If you are interested in receiving updates for a particular package, then this method is for you. Be aware that packages
may depend on other packages, so the total list returned by this command will be variable.
Downgrading Packages
====================
Did a recent update break your code? Don't wait around for a bugfix... Keep working. For example, if a bug is introduced
into ``stsci.tools``, you can easily downgrade it to a known-good version:
.. code-block:: sh
$ conda search stsci.tools
. 3.4.0 py35_6 astroconda
* 3.4.1 py35_0 astroconda
The ``*`` denotes the current version installed locally.
Now the only thing left to do, is to tell Conda to install the previous release of the package:
.. code-block:: sh
$ conda install stsci.tools=3.4.0
At this point you should be back in business.
(`ref <http://conda.pydata.org/docs/faq.html#managing-packages>`__)
Pinning Packages
================
.. caution:: Pinning packages has the potential to break Conda. Only pin packages as a last resort.
Let's take the previous example one step further... Imagine ``stsci.tools`` is broken, and the hotfix release of ``3.4.2``
only partially solved the original issue. Now what? You still need to receive updates to other packages, but
``stsci.tools`` keeps trying to update back to ``3.4.2`` every time you touch ``conda update``.
.. code-block:: sh
$ echo "stsci.tools <=3.4.0" > ${CONDA_ENV_PATH}/conda-meta/pinned
From now on, future calls to ``conda update`` will omit ``stsci.tools`` while performing dependency resolution. However,
a clear side-effect of this will also be losing the ability to update packages that depend strictly on version ``3.4.2``.
Although this is not a permanent solution it can prove useful in a bad situation.
(`ref <http://conda.pydata.org/docs/faq.html?highlight=pinning#pinning-packages>`__)
|
