Age | Commit message (Collapse) | Author |
|
|
|
already run by it, and it breaks if root isn't in sudoers.
|
|
This was due to the sshd logs being written to the wrong log file.
While there, make save_debug_logs less verbose, write the name of the
tarball to regress.log and use $SUDO to remove the old symlinks (which
shouldn't be needed, but won't hurt). Initial problem spotted by anton@.
|
|
|
|
platforms don't like overwriting existing symlinks.
|
|
ssh.log and sshd.log, but that is insufficient for tests that have more
than one concurent ssh/sshd.
Instead, we'll log to separate datestamped files in a $OBJ/log/ and
leave a symlink at the previous location pointing at the most recent
instance with an entry in regress.log showing which files were created
at each point. This should be sufficient to reconstruct what happened
even for tests that use multiple instances of each program. If the test
fails, tar up all of the logs for later analysis.
This will let us also capture the output from some of the other tools
which was previously sent to /dev/null although most of those will be
in future commits.
|
|
specified hash algorithms; prompted by dtucker@
|
|
|
|
result in the test not cleaning up after itself. Patch from cjwatson
at debian.org vi bz#3536.
|
|
|
|
test. Skip test if neither can work. Patch from anton@, tweaks from me.
|
|
idea markus@
|
|
|
|
wrapping the position in braces (i.e. need ${10}, etc.)
|
|
|
|
|
|
we use it to compute the hash), put the hash at the end and just omit it
if we don't have it. Prompted by bz#3521.
|
|
The previous commit to add scp to the test sshd's path causes the t-envpass
test to fail when the test scp is given using a fully qualified path. Put
this in a helper function and only call it from the scp tests.
|
|
If the scp we're testing is fully qualified (eg it's not in the system
PATH) then add its path to the under-test sshd's PATH so we can find it.
Prompted by bz#3518.
|
|
its lifecycle without risk of race conditions; fixes some of the
Github integration tests for openssh-portable
|
|
xonly by using a new gadget routine written in assembler with the sole
purpose of issuing a syscall. Since it needs to be copied to wx memory,
place it in the rodata section.
|
|
Based on github pr#368 from ren mingshuai.
|
|
|
|
|
|
|
|
|
|
Fixes test failure due to segfault seen on arm64 with xonly snap.
ok djm
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
logname(1) when normalizing the output.
|
|
This will make life easier in -portable where not all diff's understand -N.
|
|
commit but passes now. bz3488; prodded by dtucker@
|
|
Adjust the test for now to -Cr4, which isn't exactly in the spirit of the
test but fixes things for now.
Now that we have agentx I should write a backend with more predictable
output to make regress more stable.
pointed out by anton@
|
|
vertical space after boxed tables).
I'm committing this separately because trying to regenerate the
desired output with groff-current reveals an unrelated, recent
regression in groff. So i fixed the groff output by hand before
committing it, to get rid of the effect of the roff regression.
|
|
and tbl_term.c rev. 1.66 cause quite a bit of churn, unfortunately.
This commit cleans up most of it.
|
|
when comparing section headers. For example, ".Sh SEE ELSEWHERE"
and ".Sh SEE Em ALSO" were considered instances of a SEE ALSO
section. In groff-current, exact matches with no sub-macros are
required. Adjust mandoc behaviour.
While here, also fix a very minor mandoc bug, even though no
detrimental effect of the bug on formatting is known. While using
sub-macros in the .Sh HEAD is bad style, the parsers accept it, so
setting the section attribute on the HEAD needs to act recursively.
|
|
The new version of the output file was generated with groff-current.
|
|
when multiple input or output lines are involved.
|
|
The new version of this file was generated with groff-current.
Heirloom nroff produces exactly the same output for the content
of the DESCRIPTION.
|
|
after vertical spacing was improved in man_term.c rev. 1.192.
|
|
|
|
whatsoever (for example \fR) and escape sequences that produce
invisible zero-width output (for example \&). No, i'm not joking,
groff does make that distinction, and it has consequences in some
situations, for example for vertical spacing in no-fill mode.
Heirloom and Plan 9 behaviour is subtly different, but in case of
doubt, we want to follow groff.
While this fixes the behaviour for the majority of escape sequences,
in particular for those most likely to occur in practice, it is not
perfect yet because some of the more exotic ESCAPE_IGNORE sequences
are actually of the "no output whatsoever" type but treated
as "invisible zero-width" for now. With the new ASCII_NBRZW mechanism
in place, switching them over one by one when the need arises will
no longer be very difficult.
|
|
is forced to the UTC timezone. bz3468 ok dtucker
|
|
* t3 doesn't was fixed anymore
* add a comment describing t19
* add t20 (reversal application of a diff that creates a one-line file)
ok stsp@
|
|
Leaving the body empty is legitimate in this case if the author only
wants to display a mail address or URI without providing a link text.
Output modules already handle this correctly: terminal output shows
just the URI without an accompanying text, HTML output uses the URI
for *both* the href= attribute and as the content of the <a> element.
The documentation was also wrong and claimed that an .MT or .UR block
with an empty body would produce no output. As explained above,
this isn't true.
Bogus warning reported by
Alejandro Colomar <alx dot manpages at gmail dot com>.
|