gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: packaging updates


From: gnunet
Subject: [taler-docs] branch master updated: packaging updates
Date: Wed, 03 Nov 2021 17:05:47 +0100

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 4437c19  packaging updates
4437c19 is described below

commit 4437c19b20cbabc3776343acdb8ad2ac9814782b
Author: Florian Dold <florian@dold.me>
AuthorDate: Wed Nov 3 17:05:41 2021 +0100

    packaging updates
---
 taler-developer-manual.rst | 35 ++++++++++++++++++++++++++++++-----
 1 file changed, 30 insertions(+), 5 deletions(-)

diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index fdb2a81..2369c0a 100644
--- a/taler-developer-manual.rst
+++ b/taler-developer-manual.rst
@@ -150,6 +150,29 @@ There are separate low-volume mailinglists for 
gnunet-developers (@gnu.org)
 and for libmicrohttpd (@gnu.org).
 
 
+Debian and Ubuntu Repositories
+==============================
+
+We package our software for Debian and Ubuntu.
+
+Nightly Repositories
+--------------------
+
+To try the latest, unstable and untested versions of packages,
+you can add the nightly package sources.
+
+.. code-block:: shell-session
+
+   # For Ubuntu (focal-fossa)
+   $ echo "deb https://deb.taler.net/apt-nightly focal-taler-nightly main" > 
/etc/apt/sources.list.d/taler.list
+
+   # For Debian (bullseye)
+   $ echo "deb https://deb.taler.net/apt-nightly bullseye-taler-nightly main" 
> /etc/apt/sources.list.d/taler.list
+
+   # Both: Install signing key for nightly packages 
+   $ wget -O - https://taler.net/taler-systems-nightly.gpg.key | apt-key add -
+
+
 Language-Specific Guidelines
 ============================
 
@@ -636,20 +659,22 @@ in the respective source directory (GNUnet, exchange, 
merchant) to create the
 ``.deb`` files. Note that they will be created in the parent directory.  This
 can be done on gv.taler.net, or on another (secure) machine.
 
+On ``gv``, we use the ``aptbuilder`` user to manage the reprepro repository.
+
 Next, the ``*.deb`` files should be copied to gv.taler.net, say to
-``/root/incoming``.  Then, run
+``/home/aptbuilder/incoming``.  Then, run
 
 .. code-block:: bash
 
-  # cd /var/www/repos/apt/debian/
-  # reprepro includedeb sid /root/incoming/*.deb
+  # cd /home/aptbuilder/apt
+  # reprepro includedeb bullseye ~/incoming/*.deb
 
-to import all Debian files from ``/root/incoming/`` into the ``sid``
+to import all Debian files from ``~/incoming/`` into the ``bullseye``
 distribution.  If Debian packages were build against other distributions,
 reprepro may need to be first configured for those and the import command
 updated accordingly.
 
-Finally, make sure to clean up ``/root/incoming/`` (by deleting the
+Finally, make sure to clean up ``~/incoming/`` (by deleting the
 now imported ``*.deb`` files).
 
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]