.. -*- mode: rst; fill-column: 78 -*-
.. ex: set sts=4 ts=4 sw=4 et tw=79:
- ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
- #
- # See COPYING file distributed along with the PyMVPA package for the
- # copyright and license terms.
- #
- ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ### ###
.. _faq:
--------------------------------------------
NeuroDebian offers backported binary packages for recent Ubuntu releases
- whenever possible. However, since Ubuntu is a rather thin shell around Debian
- it is more efficient to spend time packaging for Debian. After the appearance
- of new packages in Debian, Ubuntu typically synchronizes them quickly and
- they become available in the *Ubuntu universe* -- a repository of Debian
- packages rebuilt for a particular Ubuntu release. We are not constantly
- rebuilding of all available NeuroDebian packages for new Ubuntu
- releases. Therefore, you might find some packages only being available
- for older Ubuntu releases -- until the point when a new package version is
- made and gets built for all currently supported releases.
+ whenever possible. However, since Ubuntu (like many other derivatives) uses
+ Debian as its foundation, it is more efficient to spend time maintaining
+ packages in Debian, instead of having to directly contribute to countless
+ child-distributions. After the appearance of new packages in Debian, Ubuntu
+ typically synchronizes them quickly and they become available in the *Ubuntu
+ universe* -- a repository of Debian packages rebuilt for a particular Ubuntu
+ release. We are not constantly rebuilding of all available NeuroDebian
+ packages for new Ubuntu releases. Therefore, you might find some packages
+ temporarily being available for older Ubuntu releases only -- until the point
+ when a new package version is made and gets built for all currently supported
+ releases.
How to create a mirror of the repository?
How do I get a new neuroscience-related FOSS into (Neuro)Debian?
----------------------------------------------------------------
- * You can approach packaging it yourself (file an ITP_ (Intent to package)
- bugreport) and `ask us <team@neuro.debian.net>`_ to mentor your upload to
- Debian_ if you are not a Debian developer.
+The goal of NeuroDebian is to package neuroscience software for Debian. Hence
+getting software into NeuroDebian means trying to get it into Debian. There are
+at least two possibilities to achieve that:
- * `Contact us <team@neuro.debian.net>`_, but then it might take longer
- depending on our workload and interest to the particular software.
+* You can approach packaging it yourself. Start by filing an ITP_ (Intent to
+ package) bugreport) and `ask us <team@neuro.debian.net>`_ to mentor your
+ upload to Debian_, if you are not a Debian developer.
+
+* `Contact us <team@neuro.debian.net>`_ -- but then it might take a little
+ longer, depending on our current workload and interest in a particular
+ software.
+
+
+I have heard that some packages are non-free. Will you charge me for them?
+--------------------------------------------------------------------------
+
+ No. The term :term:`non-free` refers to an archive section. NeuroDebian uses
+ exactly the same :ref:`archive sections as Debian proper
+ <http://www.debian.org/doc/debian-policy/ch-archive.html>`. The *non-free*
+ section contains packages that have certain restrictions regarding **your
+ freedom** to employ them for a particular purpose. In contrast, for packages
+ in the *main* section your are completely free to do whatever and in whatever
+ context you like. Regardless of the actual license or archive section, all
+ packages in NeuroDebian are provided free of charge and under the licensing
+ terms of the original developers.
+
+.. _sec_pkg_authentication:
+
+What means "The following signatures couldn't be verified..."?
+--------------------------------------------------------------
+
+When you start using this repository, you probably get warning messages
+like this::
+
+ The following signatures couldn't be verified because
+ the public key is not available.
+
+Or you will be asked questions like this over and over::
+
+ WARNING: The following packages cannot be authenticated!
+ ...
+ Install these packages without verification [y/N]?
+
+This is because your APT installation initially does not know the GPG
+key that is used to sign the release files of this repository. It is easy to
+make APT happy again. The simplest way is to install the ``neurodebian-keyring``
+package that is available from the NeuroDebian repository. Alternatively:
+
+1. Get the key. Either download the `repository key from here
+ <_static/neuro.debian.net.asc>`_
+ or fetch it from http://wwwkeys.pgp.net (2649A5A9).
+
+2. Now feed the key into APT by invoking::
+
+ apt-key add #file#
+
+ Where `#file#` has to be replaced with the location of the key file you just
+ downloaded. You need to have superuser-privileges to do this (either do it
+ as root or use sudo).
.. include:: links_names.rst