Installation on Linux via Apt Repository
Pages 38
Clone this wiki locally
For installation add the ObsPy apt repository to your package manager by adding the following line to the file /etc/apt/sources.list (needs root privileges):
ObsPy is packed for all Debian and Ubuntu releases which are still officially supported.
Replace $CODENAME with the codename of your Debian/Ubuntu release.
deb http://deb.obspy.org $CODENAME main
For example for Debian stretch put this in your /etc/apt/sources.list file:
deb http://deb.obspy.org stretch main
Currently supported releases are (see http://deb.obspy.org/pool/main/p/python-obspy/ for the most up-to-date list of current packages):
- Debian:
-
Ubuntu:
- trusty (i386, amd64)
- xenial (i386, amd64)
- bionic (i386, amd64)
- Raspbian wheezy, jessie, stretch and buster (hard-float, armv6l) * see note below for Raspbian
If you are unsure about the codename of your installation you can use the following command to display it:
lsb_release -csNext you need to import the ObsPy gnupg key so that apt is able to check the integrity of the downloaded packages. The following command needs to be executed only once:
$ wget --quiet -O - https://raw.githubusercontent.com/obspy/obspy/master/misc/debian/public.key | sudo apt-key add -To install ObsPy including all dependencies:
$ sudo apt-get update
$ # python3 package only available for newer Debian/Ubuntu releases
$ sudo apt-get install python-obspy python3-obspyIf you want to uninstall ObsPy and all unneeded dependencies just do:
$ sudo apt-get remove python-obspy python3-obspyFor newer Debian (starting with "jessie") and Ubuntu (starting with "trusty") releases, python3-obspy package will be available. Furthermore data and image files only needed to run ObsPy's test suites are contained in a separate package python-obspy-dbg which can be opted-out when installing with e.g. aptitude install -R python-obspy.
Notes on Raspbian
Raspbian buster (and maybe other versions as well) has some packages specifically recompiled for ARM architecture it seems. This can cause dependency resolution issues, as seen in #2530. Use aptitude and check alternative solutions offered for resolving these conflicts (downgrading custom Raspbian packages to canonical version numbers in this case).
