| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
save the output from any failing tests. If a test fails the debug output
from ssh and sshd for the failing tests (and only the failing tests) should
be available in failed-ssh{,d}.log.
|
|
log from sshd and the output from the client command (ssh, scp or sftp).
Somewhat functional now, will become more useful when ssh/sshd -E is added.
|
|
to a pkgconfig file (currently fails).
the fix for pkg-config will be committed shortly
|
|
|
|
since they were. Reduces test runtime by 5-30% depending on machine
speed.
|
|
- libj -> libmj (my error)
- fix some incorrect warnings about `new sentence, new line' (1.25)
stuff we don;t have:
- the -A and -O options (not fully implemented on netbsd anyway)
- $order (not currently used on netbsd)
also we have a couple of fixes not yet in netbsd:
- -l added correctly to usage
- correct line number reporting for dup rcs ids
|
|
- pull in 1.24: do not warn about () in literal strings or when used
as macro argument
|
|
off by default on openbsd, and the libraries checked are netbsd ones (we
can tweak this later if we ever want to start using Lb)
also rolls in 1.2{3,6,7,8}, which simply added some libraries to the list.
|
|
for netbsd;
|
|
- zap trailing whitespace
- report duplicate rcs id
(including a fix from wiz to correctly report the line number of the dup,
which isn't yet committed in netbsd)
|
|
one change (coming next), syncs mdoclint to netbsd -r1.17;
|
|
|
|
|
|
reached in it's stream and turn it on for t-integrity. This should catch
cases where the session is not fuzzed for being too short (cf. my last
"oops" commit)
|
|
we actually reach $offset
|
|
portable test hosts at 2800
|
|
least offset+tries bytes in the stream.
|
|
types. diffie-hellman-group-exchange-sha256 requires an offset around
2700. Noticed via test failures in portable OpenSSH on platforms that
lack ECC and this the more byte-frugal ECDH KEX algorithms.
|
|
|
|
|
|
|
|
on the same output line, even if it is longer than the output width.
This commit fixes a bug allowing an overly long last line of an
indented block (.RS) to be broken even in literal mode.
The bug was found using the sudo_plugin(4) manual provided by millert@.
I introduced the bug in rev. 1.84 during the g2k12 Budapest hackathon.
|
|
to fix multiple issues reported by Todd Miller; thanks!
Specifically,
- avoid double indentation after .Bd inside .Bl
- set up correct indentation after .Bl inside .Bl
- set up correct indentation after .Dl and .D1 inside .Bl
While here, also
- set up correct indentation *inside* .Dl and .D1 inside .Bl.
|
|
|
|
OK millert@
|
|
|
|
|
|
|
|
|
|
has a fix under review.
OK otto@ blambert@
|
|
|
|
- use string comparison rather than numeric comparison
- check for existing KEY_COMMAND file and don't clobber if it exists
- clean up KEY_COMMAND file if we do create it.
- check that KEY_COMMAND is executable (which it won't be if eg /var/run
is mounted noexec).
ok djm.
|
|
|
|
|
|
Problem reported by jmc@, thanks.
|
|
just like in -Tascii mode; requested by millert@.
While here, do not escape the blank characters terminating man(7)
macros; this is becoming more important as we use more keeps now.
Note that -Tman still does not support .nr nS.
|
|
to .Bl -tag and .TP the same way as groff, even via -Tman.
Some time ago, millert@ reported issues with these;
apparently, those issues were fixed since then.
|
|
Inspired by a diff from millert@, but implemented rather
differently and with slightly better functionality.
In particular, this one respects -offset and -width
arguments found in the input file.
|
|
related to man_term.c rev. 1.88, man_validate.c rev. 1.56.
|
|
reported by Nicolas Joly <njoly at pasteur dot fr>:
- add EOS spacing after trailing punctuation after .Cd, .Fc, and .Lb
- suppress spacing before trailing punctuation after .Fd
|
|
This fixes the end of sentence spacing in open(2)
and in about 150 pages in the NetBSD base system.
Reported by Nicolas Joly <njoly a pasteur point fr>, merci!
|
|
The basic idea is to already pop the font at the end marker
instead of allowing it to linger until the final end of the block.
This requires a few preliminaries:
* For each block, save a pointer to the previous font
to be used in case the block breaks another and gets extended.
* That requires making node information writable during rendering.
* Now fonts may get popped in the wrong order; hence, after the stack
has already been rewound further by some block that began earlier,
ignore popping a font that was put on the stack later.
* To be able to exploit all this for font blocks, tie processing
to their body, not their block, which is more logical anyway.
Triggered by florian@ reporting vaguely similar issues with list blocks.
|
|
|
|
* When allocating a body end marker, copy the pointer to the normalized
block information from the body block, avoiding the risk of subsequent
null pointer derefence.
* When inserting the body end marker into the syntax tree, do not try to
copy that pointer from the parent block, because not being a direkt child
of the block it belongs to is the whole point of a body end marker.
* Even non-callable blocks (like Bd and Bl) can break other blocks;
when this happens, postpone closing them out in the usual way.
|
|
|
|
Add missing RCS Ids.
ok sthen@
|
|
newsyslog test failing atm on NFS..
ok sthen@
|
