Motsognir is a robust, reliable and easy to install open-source gopher server
for Unix-like systems (Linux, BSD, and anything else POSIX-compliant).
The Motsognir gopher server is meant to be used for small projects (like home
servers), but should scale well on bigger architectures as well. All the
configuration is done via a single configuration file, which has very
reasonable defaults. That makes Motsognir easily maintainable, and allows the
administrator to have a full knowledge of what features are allowed/enabled on
the server. Motsognir supports server-side CGI applications and PHP scripts, is
plainly compatible with UTF-8 filesystems, and is entirely written in ANSI C
without external dependencies.
WWW: http://sourceforge.net/projects/motsognir
PR: 184203
Submitted by: Mateusz Viste <mateusz@viste.fr>
Approved by: mentors (implicit)
A portion of this patch to upgrade makepatch was committed almost 2
months ago; this is the rest of it. It changes the directory separator
to "_" and it will transform "_" in the filename to "__" to avoid
ambiguous file names (e.g. A/B/C.c and A_B/C.c won't have the same patch
name).
The new logic will not rename an existing patch that used previously
standard separators of "-", "+", or "__" in its name. It is desireable
to avoid commits that only change the filename of the patch, so that's
why existing filenames are re-used if previously legal.
The diff command is also pass the -p argument for additional useful
context.
Differential Revision: https://reviews.freebsd.org/D582
Approved by: portmgr (bapt)
- update to 0.10.1
- convert to USES=python
- remove unneeded patch
This version also works with python3.
PR: 194339
Submitted by: rm (myself)
Approved by: maintainer timeout (two weeks)
Released on October 23rd, 2014.
* Added support to print the details of all test cases (metadata and
their output) to 'report'. This is via a new '--verbose' flag which
replaces the previous '--show-context'.
* Added support to specify the amount of physical disk space required
by a test case. This is in the form of a new "required_disk_space"
metadata property, which can also be provided by ATF test cases as
"require.diskspace".
* Assimilated the contents of all the kyua-*-tester(1) and
kyua-*-interface(7) manual pages into more relevant places. In
particular, added more details on test program registration and their
metadata to kyuafile(5), and added kyua-test-isolation(7) describing
the isolation features of the test execution.
* Assimilated the contents of all auxiliary manual pages, including
kyua-build-root(7), kyua-results-files(7), kyua-test-filters(7) and
kyua-test-isolation(7), into the relevant command-specific manual
pages. This is for easier discoverability of relevant information
when reading how specific Kyua commands work.
* Issue 30: Plumbed through support to query configuration variables
from ATF's test case heads. This resolves the confusing situation
where test cases could only do this from their body and cleanup
routines.
* Issue 49: Extended 'report' to support test case filters as
command-line arguments. Combined with '--verbose', this allows
inspecting the details of a test case failure after execution.
* Issue 55: Deprecated support for specifying test_suite overrides on
a test program basis. This idiom should not be used but support for
it remains in place.
* Issue 72: Added caching support to the getcwd(3) test in configure so
that the result can be overriden for cross-compilation purposes.
* Issue 83: Changed manual page headings to include a "kyua" prefix in
their name. This prevents some possible confusion when displaying,
for example, the "kyua-test" manual page with a plain name of "test".
* Issue 84: Started passing test-suite configuration variables to plain
and TAP test programs via the environment. The name of the
environment variables set this way is prefixed by TEST_ENV_, so a
configuration variable of the form
'test_suites.some_name.allow_unsafe_ops=yes' in kyua.conf becomes
'TEST_ENV_allow_unsafe_ops=YES' in the environment.
* Issue 97 and 116: Fixed the build on Illumos.
* Issue 102: Set TMPDIR to the test case's work directory when running
the test case. If the test case happens to use the mktemp(3) family
of functions (due to misunderstandings on how Kyua works or due to
the reuse of legacy test code), we don't want it to easily escape the
automanaged work directory.
* Issue 103: Started being more liberal in the parsing of TAP test
results by treating the number in 'ok' and 'not ok' lines as optional.
* Issue 105: Started using tmpfs instead of md as a temporary file
system for tests in FreeBSD so that we do not leak md(4) devices.
* Issue 109: Changed the privilege dropping code to start properly
dropping group privileges when unprivileged_user is set. Also fixes
testers/run_test:fork_wait__unprivileged_group.
* Issue 110: Changed 'help' to display version information and clarified
the purpose of the 'about' command in its documentation.
* Issue 111: Fixed crash when defining a test program in a Kyuafile that
has not yet specified the test suite name.
* Issue 114: Improved the kyuafile(5) manual page by clarifying the
restrictions of the include() directive and by adding abundant
examples.
Differential Revision: https://reviews.freebsd.org/D1002
Approved by: bapt
Released on October 23rd, 2014.
* Restored the atf(7) manual page to serve as a reference to all the other
manual pages shipped by ATF.
* Added the -s flag to atf-sh to support specifying the shell interpreter
to be used.
* Removed ATF_WORKDIR. The only remaining consumers have been converted to
use the standard TMPDIR environment variable. As a benefit, and because
Kyua forces the TMPDIR to live within the test case's work directory,
any stale files left behind by ATF will be automatically cleaned up.
* Documented the environment variables recognized by each component in the
relevant manual pages. This information was lost with the atf-config(1)
removal.
* Added a new "require.diskspace" metadata property to test cases so that
they can specify the minimum amount of disk space required for the test
to run.
* Renamed the atf-{c,c++,sh}-api(3) manual pages to atf-{c,c++,sh}(3) for
discoverability purposes. Symbolic links are provided for the time
being to still make the old names visible.
* Issue #5: Recommend the (expected, actual) idiom for calls to the test
macros in the manual pages.
* Issue #7: Stopped catching unhandled exceptions in atf-c++ tests. This
propagates the crash to the caller, which in turn allows it to obtain
proper debugging information. In particular, Kyua should now be able to
extract a stacktrace pinpointing the problem.
* Issue #8: Fixed atf-c/macros_test:use test failures spotted by the clang
that ships with FreeBSD 11.0-CURRENT.
* Issue #12: Improved documentation of atf-sh(3) and atf-check(1) by better
explaining how they relate to each other.
* Issue #14: Stopped setting 'set -e' in atf-sh. This setting was
initially added as a way to enable a "strict" mode in the library and to
make test cases fail fast when they run unprotected commands. However,
doing so in the library is surprising as the responsibility of enabling
'set -e' should be on the user's code. Also, 'set -e' introduces
inconsistent behavior on subshells and users do not expect that.
* Issue #15: Fixed atf_utils_{fork,wait} to support nested calls.
* Issue #16: Fixed test failures (by removing a long-standing hack) on
systems that lack \e support in printf(1).
* Issue #19: Removed stale references to atf-config and atf-run.
Differential Revision: https://reviews.freebsd.org/D1001
Approved by: bapt
Changes:
- Reinstall packages if one of its dependency have change
While hackish this allows seamless upgrade of perl5 and ruby2
- Fix pkg audit as used from ports
- Reject chroot for unknown ABIs
- Fix generating repos from 1.3 created packages
- Allow to build out of the source tree
- Fix ABI detection on armeb
- Fix some left overs from Unique id migration
- Fix pkg delete regression (it is again recursive by default)
- Locked packages prevent deleting anything that depends on them
- Fix pkg upgrade on multi repo
- Fix pkg upgrade ignoring the lock flag
Thank you very much for all the testers and reports! Please keep testing!
