taler-docs

commit 51c9e686d114ba1c786e08eb3365c6f5686a02ec
parent 2648ef6f9cacd20ad532e8f351054354685b2705
Author: Florian Dold <florian@dold.me>
Date:   Wed, 20 Aug 2025 14:51:53 +0200

update reprepro docs

Diffstat:
M
system-administration/reprepro.rst
 | 
48
+++++++++++++++++++++++++++++++++---------------

1 file changed, 33 insertions(+), 15 deletions(-)
diff --git a/system-administration/reprepro.rst b/system-administration/reprepro.rst
@@ -14,6 +14,7 @@
   TALER; see the file COPYING.  If not, see <http://www.gnu.org/licenses/>
 
   @author Christian Grothoff
+  @author Florian Dold
 
 Reprepro setup
 ==============
@@ -72,7 +73,7 @@ simply move everything at once (after testing it!):
   Components: main
   Architectures: amd64
   UDebComponents:
-  FilterFormula: Package (% package-name-pattern )
+  FilterFormula: Package (% * )
 
 If we in the future wanted to only pull packages that have been in
 testing for at least 10 days, we could use:
@@ -92,23 +93,40 @@ The ``conf/options`` file used is mainly giving the path:
   ask-passphrase
 
 
-Shell scripts
--------------
+taler-pkg
+---------
 
-We install various simple shell scripts in the ``taler-packaging`` HOME
-directory to call reprepro.  They are maintained in the
-``taler-deployment.git`` under ``packaging/ng/server-side``.
+The ``taler-pkg`` tool from ``taler-deployment.git/packaging/ng``
+is used to both build packages (via podman containers) and upload them
+to ``deb.taler.net``.
 
-The following shell scripts are used to manage the system:
+Building packages:
 
-* ``include-$DISTRO-$RELEASE.sh`` imports new packages from the
-  respective origin directory into *testing*
+.. code::
 
-* ``promote-$DISTRO-$RELEASE.sh`` promotes packages from *testing*
-  to *stable* for the respective distribution
+   $ ./taler-pkg build $TARGET
 
-* ``show-$DISTRO-$RELEASE.sh`` shows all packages from the
-  respective distribution
+where target is of the form ``$VENDOR-$CODENAME``. For example, ``debian-trixie`` or ``ubuntu-noble``.
 
-* ``export-$DISTRO-$RELEASE.sh`` scripts export the respective distributions
-  (this is mostly useful after errors)
+Publishing packages:
+
+.. code::
+
+   $ ./taler-pkg publish $TARGET
+
+Publishing packages only publishes them to the ``-testing`` distro.
+
+Promoting packages:
+
+.. code::
+
+   $ ./taler-pkg promote $TARGET --dry
+   $ ./taler-pkg promote $TARGET
+
+To show which packages are currently available, use:
+
+
+.. code::
+
+   $ ./taler-pkg show-published debian-trixie-testing
+   $ ./taler-pkg show-published debian-trixie