Description: fix warning cannot select font 'C'
 Replace with Bold the 'C' font that is not recognized as a valid
 font name in the groff system
Author: Roberto Lumbreras <rover@debian.org>
Forwarded: no
Index: iperf3-3.20/src/iperf3.1
===================================================================
--- iperf3-3.20.orig/src/iperf3.1	2025-11-15 09:23:00.296066704 +0100
+++ iperf3-3.20/src/iperf3.1	2025-11-15 09:29:06.134275964 +0100
@@ -22,9 +22,9 @@
 An iperf3 server can be started using either of the -s or
 --server command-line parameters, for example:
 .IP
-\fCiperf3 -s\fR
+\fBiperf3 -s\fR
 .IP
-\fCiperf3 --server \fR
+\fBiperf3 --server \fR
 .PP
 Note that many iperf3 parameters have both short (-s) and long
 (--server) forms.
@@ -36,7 +36,7 @@
 A custom port can be specified by using the -p flag, for
 example:
 .IP
-\fCiperf3 -s -p 5002\fR
+\fBiperf3 -s -p 5002\fR
 .PP
 After the server is started, it will listen for connections from
 iperf3 clients (in other words, the iperf3 program run in client
@@ -45,16 +45,16 @@
 which also requires a host to which iperf3 should connect.
 The host can be specified by hostname, IPv4 literal, or IPv6 literal:
 .IP
-\fCiperf3 -c iperf3.example.com\fR
+\fBiperf3 -c iperf3.example.com\fR
 .IP
-\fCiperf3 -c 192.0.2.1\fR
+\fBiperf3 -c 192.0.2.1\fR
 .IP
-\fCiperf3 -c 2001:db8::1\fR
+\fBiperf3 -c 2001:db8::1\fR
 .PP
 If the iperf3 server is running on a non-default TCP port, that port
 number needs to be specified on the client as well:
 .IP
-\fCiperf3 -c iperf3.example.com -p 5002\fR
+\fBiperf3 -c iperf3.example.com -p 5002\fR
 .PP
 The initial TCP connection is used to exchange test parameters,
 control the start and end of the test, and to exchange test results.
@@ -69,7 +69,7 @@
 the -R flag on the client.
 This causes data to be sent from the server to the client.
 .IP
-\fCiperf3 -c iperf3.example.com -p 5202 -R
+\fBiperf3 -c iperf3.example.com -p 5202 -R\fR
 .PP
 Results are displayed on both the client and server.
 There will be at least one line of output per measurement interval (by
@@ -87,7 +87,7 @@
 least as much as possible) a summary of the test as seen by both the
 sender and the receiver, with lines tagged accordingly.
 Recall that by default the client is the sender and the server is the
-receiver, although as indicated above, use of the \fC-R\fR flag will
+receiver, although as indicated above, use of the \fB-R\fR flag will
 reverse these roles.
 .PP
 The client can be made to retrieve the server-side output for a given
@@ -189,11 +189,11 @@
 Prepend a timestamp at the start of each output line.
 By default, timestamps have the format emitted by
 .BR ctime ( 1 ).
-Optionally, \fC=\fR followed by
+Optionally, \fB=\fR followed by
 a format specification can be passed to customize the
 timestamps, see
 .BR strftime ( 3 ).
-If this optional format is given, the \fC=\fR must immediately
+If this optional format is given, the \fB=\fR must immediately
 follow the \fB--timestamps\fR option with no whitespace intervening.
 .TP
 .BR --rcv-timeout " \fI#\fR"
@@ -255,7 +255,7 @@
 When the sum of the client's time and omit values exceeds the max duration set by the server
 or the client's time value is 0, the measurement is rejected.
 .TP
-.BR --server-bitrate-limit " \fIn\fR[KMGT][/\fCn\fR]"
+.BR --server-bitrate-limit " \fIn\fR[KMGT][/\fBn\fR]"
 Set a limit on the server side, which will cause a test to abort if
 the client specifies a test of more than \fIn\fR bits per second, or
 if the average data sent or received by the client (including all data
@@ -349,7 +349,7 @@
 iperf3's internal throughput pacing (\-b/\--bitrate flag), and both can be
 specified for the same test.
 Only available on platforms supporting the
-\fCSO_MAX_PACING_RATE\fR socket option (currently only Linux).
+\fBSO_MAX_PACING_RATE\fR socket option (currently only Linux).
 The default is no fair-queueing based pacing.
 .TP
 .BR --no-fq-socket-pacing
@@ -549,13 +549,13 @@
 An example of a set of UNIX/Linux commands using OpenSSL
 to generate a correctly-formed keypair follows:
 .IP
-\fC> openssl genrsa -des3 -out private.pem 2048\fR
+\fB> openssl genrsa -des3 -out private.pem 2048\fR
 .sp 0
-\fC> openssl rsa -in private.pem -outform PEM -pubout -out public.pem\fR
+\fB> openssl rsa -in private.pem -outform PEM -pubout -out public.pem\fR
 .sp 0
-\fC> openssl rsa -in private.pem -out private_not_protected.pem \\ \fR
+\fB> openssl rsa -in private.pem -out private_not_protected.pem \\ \fR
 .sp 0
-\fC  -outform PEM\fR
+\fB  -outform PEM\fR
 .PP
 After these commands, the public key will be contained in the file
 public.pem and the private key will be contained in the file
@@ -566,29 +566,29 @@
 The file is a simple list of comma-separated pairs of a username and a
 corresponding password hash.
 The password hash is a SHA256 hash of the string "{$user}$password".
-The file can also contain commented lines (starting with the \fC#\fR
+The file can also contain commented lines (starting with the \fB#\fR
 character).
 An example of commands to generate the password hash on a UNIX/Linux system
 is given below:
 .IP
-\fC> S_USER=mario S_PASSWD=rossi\fR
+\fB> S_USER=mario S_PASSWD=rossi\fR
 .sp 0
-\fC> echo -n "{$S_USER}$S_PASSWD" | sha256sum | awk '{ print $1 }'\fR
+\fB> echo -n "{$S_USER}$S_PASSWD" | sha256sum | awk '{ print $1 }'\fR
 .PP
 An example of a password file (with an entry corresponding to the
 above username and password) is given below:
 .IP
-\fC> cat credentials.csv\fR
+\fB> cat credentials.csv\fR
 .in -.5i
 .sp 0
-\fC# file format: username,sha256\fR
+\fB# file format: username,sha256\fR
 .sp 0
-\fCmario,bf7a49a846d44b454a5d11e7acfaf13d138bbe0b7483aa3e050879700572709b\fR
+\fBmario,bf7a49a846d44b454a5d11e7acfaf13d138bbe0b7483aa3e050879700572709b\fR
 .in +.5i
 .SH AUTHORS
 A list of the contributors to iperf3 can be found within the
 documentation located at
-\fChttps://software.es.net/iperf/dev.html#authors\fR.
+\fBhttps://software.es.net/iperf/dev.html#authors\fR.
 
 .SH "SEE ALSO"
 libiperf(3),
Index: iperf3-3.20/src/libiperf.3
===================================================================
--- iperf3-3.20.orig/src/libiperf.3	2025-11-15 09:23:00.296066704 +0100
+++ iperf3-3.20/src/libiperf.3	2025-11-15 09:23:00.292066725 +0100
@@ -108,7 +108,7 @@
 .SH AUTHORS
 A list of the contributors to iperf3 can be found within the
 documentation located at
-\fChttps://software.es.net/iperf/dev.html#authors\fR.
+\fBhttps://software.es.net/iperf/dev.html#authors\fR.
 
 .SH "SEE ALSO"
 iperf3(1),