Package: libcrypt-urandom-perl
Version: 0.55-1
Severity: minor
Tags: patch, upstream
Dear Maintainer,
>From "/usr/share/doc/debian/bug-reporting.txt.gz":
Don't file bugs upstream
If you file a bug in Debian, don't send a copy to the upstream software
maintainers yourself, as it is possible that the bug exists only in
Debian. If necessary, the maintainer of the package will forward the
bug upstream.
-.-
I do not send reports upstream if I have to get an account there.
The Debian maintainers have one already.
If I get a negative (or no) response from upstream, I send henceforth
bugs to Debian.
-.-
* What led up to the situation?
Checking for defects with a new version
test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z < "man page"
[Use
grep -n -e ' $' -e '\\~$' -e ' \\f.$' -e ' \\"' <file>
to find (most) trailing spaces.]
["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).
[The fate of "test-nroff" was decided in groff bug #55941.]
* What was the outcome of this action?
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":
troff:<stdin>:86: warning: trailing space in the line
troff:<stdin>:130: warning: trailing space in the line
troff:<stdin>:140: warning: trailing space in the line
troff:<stdin>:145: warning: trailing space in the line
* What outcome did you expect instead?
No output (no warnings).
-.-
General remarks and further material, if a diff-file exist, are in the
attachments.
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.18.9+deb14-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages libcrypt-urandom-perl depends on:
ii libc6 2.42-11+b1
ii perl 5.40.1-7
ii perl-base [perlapi-5.40.1] 5.40.1-7
libcrypt-urandom-perl recommends no packages.
libcrypt-urandom-perl suggests no packages.
-- no debconf information
Input file is Crypt::URandom.3pm
Output from "mandoc -T lint Crypt::URandom.3pm": (shortened list)
11 STYLE: input text line longer than 80 bytes:
4 STYLE: whitespace at end of input line
Find most trailing spaces with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
-.-.
Output from
test-nroff -mandoc -t -Kutf8 -ww -z Crypt::URandom.3pm: (shortened list)
4 line(s) with a trailing space
Find most trailing spaces with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
-.-.
Input file is Crypt::URandom.3pm
Show if Pod::Man generated this.
2:.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45)
Latest version in Debian testing:
This is perl 5, version 40, subversion 1 (v5.40.1) built for
x86_64-linux-gnu-thread-multi
(with 48 registered patches, see perl -V for more detail)
-.-.
Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".
Number of lines affected is
4
-.-.
Wrong distance (not two spaces) between sentences in the input file.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
Mark a final abbreviation point as such by suffixing it with "\&".
Some sentences (etc.) do not begin on a new line.
Split (sometimes) lines after a punctuation mark; before a conjunction.
Lines with only one (or two) space(s) between sentences could be split,
so latter sentences begin on a new line.
Use
#!/usr/bin/sh
sed -e '/^\./n' \
-e 's/\([[:alpha:]]\)\. */\1.\n/g' $1
to split lines after a sentence period.
Check result with the difference between the formatted outputs.
See also the attachment "general.bugs"
[List of affected lines removed.]
96:filled with random data. It will throw an exception if the requested amount
of
97:random data is not returned. The first call will initialize the native
203:Copyright (c) 2025, David Dick \f(CW\*(C`<[email protected]>\*(C'\fR. All
rights reserved.
210:FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
214:WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
216:YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
-.-.
Split lines longer than 80 characters (fill completely
an A4 sized page line on a terminal)
into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
Add "\:" to split the string for the output, "\<newline>" in the source.
[List of affected lines removed.]
Longest line is number 199 with 138 characters
The Win32::API code for interacting with Microsoft's CryptoAPI
<https://en.wikipedia.org/wiki/Microsoft_CryptoAPI> was copied with extreme
-.-.
Add a zero (0) in front of a decimal fraction that begins with a period
(.)
7:.if t .sp .5v
-.-.
Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".
Crypt::URandom.3pm:79:\& use Crypt::URandom qw( urandom );
Crypt::URandom.3pm:98:cryptographic libraries (if necessary) and load all the
required Perl libraries.
Crypt::URandom.3pm:107:cryptographic libraries (if necessary) and load all the
required Perl libraries.
-.-.
Only one space character is after a possible end of sentence
(after a punctuation, that can end a sentence).
Crypt::URandom.3pm:96:filled with random data. It will throw an exception if
the requested amount of
Crypt::URandom.3pm:97:random data is not returned. The first call will
initialize the native
Crypt::URandom.3pm:203:Copyright (c) 2025, David Dick
\f(CW\*(C`<[email protected]>\*(C'\fR. All rights reserved.
Crypt::URandom.3pm:210:FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE
LAW. EXCEPT WHEN
Crypt::URandom.3pm:214:WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. THE
Crypt::URandom.3pm:216:YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE
COST OF ALL
-.-.
Add lines to use the CR font for groff instead of CW.
.if \n(.g \{\
. ie t .ftr CW CR
. el .ftr CW R
.\}
11:.ft CW
-.-.
Test nr. 94:
.\" Define a fallback for the CW font
.
.if \n(.g \{\
. ie t .ftr CW CR
. el .ftr CW R
.\}
[List of affected lines removed.]
-.-.
Put a (long) web address on a new output line to reduce the posibility of
splitting the address between two output lines.
Or inhibit hyphenation with "\%" in front of the name.
193:To report a bug, or view the current list of bugs, please visit
<https://github.com/david\-dick/crypt\-urandom/issues>
199:The Win32::API code for interacting with Microsoft's CryptoAPI
<https://en.wikipedia.org/wiki/Microsoft_CryptoAPI> was copied with extreme
200:gratitude from Crypt::Random::Source::Strong::Win32 by Max Kanat-Alexander
<https://metacpan.org/author/MKANAT>
-.-.
Change comment lines of type '.\" ====' (and an empty '.\"' line) to
a single period, as they contain no information and waste work each time
they are processed.
3:.\"
5:.\" ========================================================================
28:.\"
32:.\"
37:.\"
55:.\" ========================================================================
56:.\"
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":
troff:<stdin>:86: warning: trailing space in the line
troff:<stdin>:130: warning: trailing space in the line
troff:<stdin>:140: warning: trailing space in the line
troff:<stdin>:145: warning: trailing space in the line
-.-
Generally:
Split (sometimes) lines after a punctuation mark; before a conjunction.
-.-
Tables:
Use the preprocessor 'tbl' to make tables.
Put data, that are wider than the header in the (centered) last column,
in a "T{...\nT}" block(, when the table gets wider than the output line).
Table headers, that are wider than any data in the corresponding column,
do not need to be centered, so left adjustment (l, L) is sufficient.
--- Crypt::URandom.3pm 2026-02-19 23:07:26.870056407 +0000
+++ Crypt::URandom.3pm.new 2026-02-19 23:37:53.019788407 +0000
@@ -1,14 +1,18 @@
.\" -*- mode: troff; coding: utf-8 -*-
.\" Automatically generated by Pod::Man 5.0102 (Pod::Simple 3.45)
-.\"
+.
.\" Standard preamble:
-.\" ========================================================================
+.
.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
+.if t .sp 0.5v
.if n .sp
..
.de Vb \" Begin verbatim text
-.ft CW
+.ie \n(.g \{\
+. ie t .ftr CW CR
+. el .ftr CW R
+.\}
+.el .ft CW
.nf
.ne \\$1
..
@@ -16,6 +20,14 @@
.ft R
.fi
..
+.
+.\" Define a fallback for the CW font
+.
+.if \n(.g \{\
+. ie t .ftr CW CR
+. el .ftr CW R
+.\}
+.
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
.ie n \{\
. ds C` ""
@@ -25,11 +37,11 @@
. ds C`
. ds C'
'br\}
-.\"
+.
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el .ds Aq '
-.\"
+.
.\" If the F register is >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
@@ -52,8 +64,8 @@
. \}
.\}
.rr rF
-.\" ========================================================================
-.\"
+.
+.
.IX Title "Crypt::URandom 3pm"
.TH Crypt::URandom 3pm 2026-02-16 "perl v5.40.1" "User Contributed Perl
Documentation"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
@@ -83,7 +95,7 @@ OR
.SH DESCRIPTION
.IX Header "DESCRIPTION"
This Module is intended to provide
-an interface to the strongest available source of non-blocking
+an interface to the strongest available source of non-blocking
randomness on the current platform. Platforms currently supported are
anything supporting \fBgetrandom\fR\|(2), /dev/urandom and versions of Windows
greater
than or equal to Windows 2000.
@@ -127,7 +139,7 @@ cryptographic functions provided by the
.ie n .IP """Could not import CryptAcquireContext""" 4
.el .IP "\f(CWCould not import CryptAcquireContext\fR" 4
.IX Item "Could not import CryptAcquireContext"
-The module was unable to load the CryptAcquireContextA function from the
+The module was unable to load the CryptAcquireContextA function from the
advapi32 dynamic library. The advapi32 library cannot probably be loaded.
.ie n .IP """CryptAcquireContext failed""" 4
.el .IP "\f(CWCryptAcquireContext failed\fR" 4
@@ -137,12 +149,12 @@ advapi32 dynamic library.
.ie n .IP """Could not import CryptGenRandom""" 4
.el .IP "\f(CWCould not import CryptGenRandom\fR" 4
.IX Item "Could not import CryptGenRandom"
-The module was unable to load the CryptGenRandom function from the
+The module was unable to load the CryptGenRandom function from the
advapi32 dynamic library.
.ie n .IP """Could not import SystemFunction036""" 4
.el .IP "\f(CWCould not import SystemFunction036\fR" 4
.IX Item "Could not import SystemFunction036"
-The module was unable to load the SystemFunction036 function from the
+The module was unable to load the SystemFunction036 function from the
advapi32 dynamic library.
.ie n .IP """The length argument must be supplied and must be an integer""" 4
.el .IP "\f(CWThe length argument must be supplied and must be an integer\fR" 4
@@ -190,14 +202,21 @@ no other modules other than those provid
None reported.
.SH "BUGS AND LIMITATIONS"
.IX Header "BUGS AND LIMITATIONS"
-To report a bug, or view the current list of bugs, please visit
<https://github.com/david\-dick/crypt\-urandom/issues>
+To report a bug, or view the current list of bugs, please visit
+.br
+<https://github.com/david\-dick/crypt\-urandom/issues>
.SH AUTHOR
.IX Header "AUTHOR"
David Dick \f(CW\*(C`<[email protected]>\*(C'\fR
.SH ACKNOWLEDGEMENTS
.IX Header "ACKNOWLEDGEMENTS"
-The Win32::API code for interacting with Microsoft's CryptoAPI
<https://en.wikipedia.org/wiki/Microsoft_CryptoAPI> was copied with extreme
-gratitude from Crypt::Random::Source::Strong::Win32 by Max Kanat-Alexander
<https://metacpan.org/author/MKANAT>
+The Win32::API code for interacting with Microsoft's CryptoAPI
+.br
+<https://en.wikipedia.org/wiki/Microsoft_CryptoAPI>
+was copied with extreme
+gratitude from Crypt::Random::Source::Strong::Win32 by Max Kanat-Alexander
+.br
+<https://metacpan.org/author/MKANAT>
.SH "LICENSE AND COPYRIGHT"
.IX Header "LICENSE AND COPYRIGHT"
Copyright (c) 2025, David Dick \f(CW\*(C`<[email protected]>\*(C'\fR. All rights
reserved.
Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)
[gn]roff -mandoc -t -ww -b -z -K utf8 <man page>
To find trailing space use
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
The same goes for man pages that are used as an input.
-.-
For a style guide use
mandoc -T lint
-.-
For general input conventions consult the man page "nroff(7)" (item
"Input conventions") or the Texinfo manual about the same item.
-.-
Any "autogenerator" should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.
It should also check its input files for too long (> 80) lines.
This is just a simple quality control measure.
The "autogenerator" may have to be corrected to get a better man page,
the source file may, and any additional file may.
-.-
Common defects:
Not removing trailing spaces (in in- and output).
The reason for these trailing spaces should be found and eliminated.
"git" has a "tool" to point out whitespace,
see for example "git-apply(1)" and git-config(1)")
-.-
Not beginning each input sentence on a new line.
Line length and patch size should thus be reduced when that has been fixed.
The script "reportbug" uses 'quoted-printable' encoding when a line is
longer than 1024 characters in an 'ascii' file.
See man-pages(7), item "semantic newline".
-.-
The difference between the formatted output of the original
and patched file can be seen with:
nroff -mandoc <file1> > <out1>
nroff -mandoc <file2> > <out2>
diff -d -u <out1> <out2>
and for groff, using
\"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - \"
instead of 'nroff -mandoc'
Add the option '-t', if the file contains a table.
Read the output from 'diff -d -u ...' with 'less -R' or similar.
-.-.
If 'man' (man-db) is used to check the manual for warnings,
the following must be set:
The option "-warnings=w"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT="-ww -b -z"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-
