1 files changed, 11 insertions, 9 deletions
diff --git a/debian/control b/debian/control
index be18eac..d86f01f 100644
--- a/debian/control
+++ b/debian/control
@@ -1,18 +1,15 @@
 Source: lacme
 Section: utils
-Priority: optional
 Maintainer: Guilhem Moulin <guilhem@debian.org>
-Build-Depends: debhelper-compat (= 13), jq, pandoc (>= 2.1~)
-Rules-Requires-Root: no
-Standards-Version: 4.5.1
+Build-Depends: debhelper-compat (= 13), dh-sequence-installsysusers, jq, pandoc (>= 2.1~)
+Standards-Version: 4.7.4
 Homepage: https://git.guilhem.org/lacme/about/
 Vcs-Git: https://salsa.debian.org/debian/lacme.git -b debian/latest
 Vcs-Browser: https://salsa.debian.org/debian/lacme
 
 Package: lacme
 Architecture: all
-Depends: adduser,
-         libconfig-tiny-perl,
+Depends: libconfig-tiny-perl,
          libjson-perl,
          libnet-ssleay-perl,
          libtimedate-perl,
@@ -22,7 +19,9 @@ Depends: adduser,
          ${perl:Depends}
 Recommends: lacme-accountd (>= 0.8.0), liblwp-protocol-https-perl
 Description: ACME client written with process isolation and minimal privileges in mind
- lacme is divided into four components, each with its own executable:
+ lacme is an ACME client which can be used to request X.509 certificates from
+ ACME service providers such as Let's Encrypt or ZeroSSL.  The architecture is
+ divided into four components, each with its own executable:
  .
   * A process to manage the account key and issue SHA-256 signatures needed for
     each ACME command.  (This process binds to a UNIX-domain socket to reply to
@@ -56,9 +55,12 @@ Architecture: all
 Depends: libconfig-tiny-perl, libjson-perl, ${misc:Depends}, ${perl:Depends}
 Recommends: libcrypt-openssl-rsa-perl
 Suggests: gpg, openssl
+Multi-Arch: foreign
 Description: lacme account key manager
- lacme is an ACME client written with process isolation and minimal privileges
- in mind.  It is divided into four components, each with its own executable:
+ lacme is an ACME client which can be used to request X.509 certificates from
+ ACME service providers such as Let's Encrypt or ZeroSSL.  The architecture is
+ designed with process isolation and minimal privileges in mind, and is divided
+ into four components:
  .
   * A process to manage the account key and issue SHA-256 signatures needed for
     each ACME command.  (This process binds to a UNIX-domain socket to reply to