[taler-docs] branch master updated: explain how to create Debian packages in dev guide

[gnunet]

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

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new cb2a8e9  explain how to create Debian packages in dev guide
cb2a8e9 is described below

commit cb2a8e96ce4467da6ff21f607922ceb2618a9823
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Thu Dec 31 20:15:10 2020 +0100

    explain how to create Debian packages in dev guide
---
 developers-manual.rst | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/developers-manual.rst b/developers-manual.rst
index 22e933e..df12bd4 100644
--- a/developers-manual.rst
+++ b/developers-manual.rst
@@ -613,6 +613,33 @@ Directive file:
 Upload the files in **binary mode** to the ftp servers.
 
 
+Creating Debian packages
+------------------------
+
+Our general setup is based on
+https://wiki.debian.org/DebianRepository/SetupWithReprepro
+
+First, update at least the version of the Debian package in
+debian/changelog, and then run:
+
+$ dpkg-buildpackage -rfakeroot -b -uc -us
+
+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.
+
+Next, the "*.deb" files should be copied to gv.taler.net, say to
+``/root/incoming``.  Then, go to ``/var/www/repos/apt/debian/`` and run
+``reprepro includedeb sid /root/incoming/*.deb`` to import all Debian files
+from ``/root/incoming/`` into the ``sid`` 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
+now imported "*.deb" files).
+
+
+
 Continuous integration
 ======================
 

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