gnunet-svn
[Top][All Lists]
Advanced

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

[taler-docs] 03/04: revert "NB:" back to "N:" (turns out it's verbatim o


From: gnunet
Subject: [taler-docs] 03/04: revert "NB:" back to "N:" (turns out it's verbatim output from a program)
Date: Sat, 07 Aug 2021 05:15:55 +0200

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

ttn pushed a commit to branch master
in repository docs.

commit 39ae3f3051bc4ed920231ceb8c4ed171d2b70607
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Fri Aug 6 23:13:41 2021 -0400

    revert "NB:" back to "N:" (turns out it's verbatim output from a program)
---
 taler-exchange-setup-guide.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst
index 7c76328..640fac4 100644
--- a/taler-exchange-setup-guide.rst
+++ b/taler-exchange-setup-guide.rst
@@ -97,7 +97,7 @@ signing key to your list of trusted keys and update the 
package index:
 
 ..
   FIXME: This happens after the update.
-  NB: Skipping acquire of configured file 'main/binary-i386/Packages' as 
repository 'https://deb.taler.net/apt/ubuntu focal-fossa InRelease' doesn't 
support architecture 'i386'.
+  N: Skipping acquire of configured file 'main/binary-i386/Packages' as 
repository 'https://deb.taler.net/apt/ubuntu focal-fossa InRelease' doesn't 
support architecture 'i386'.
 
 Finally, the required packages can be installed:
 
@@ -940,6 +940,6 @@ FIXMEs
 * When multiple TWGs are configured, which one will be used by the 
taler-exchange-transfer? CG: ALL!
 * On Ubuntu focal fossa, I get the following warning on "apt update", are we 
doing something wrong?
 
-  NB: Skipping acquire of configured file 'main/binary-i386/Packages' as
+  N: Skipping acquire of configured file 'main/binary-i386/Packages' as
   repository 'https://deb.taler.net/apt/ubuntu focal-fossa InRelease' doesn't
   support architecture 'i386'.

-- 
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]