0.7.9: This time a lot of little bugs has been fixed and some major crashbugs
as well. Namely, I found problem in the hash table routine that could
have caused some really weird problems, and I've encountered such
problem at least in one core file earlier. Some additional desync
problems has been fixed as well, so if you are running a normal server
then upgrading is strongly recommended.
check full changelog at:
http://silcnet.org/txt/changes-server.txt
Patch submitted by Lubomir Sedlacik <salo@silcnet.org> in PR 15453
this release includes many patches which fix various problems ending in
crashing the server. upgrade is strongly recommended.
0.7.7: This server attempts to fix various crash bugs, for example one crash
relating to BAN command is fixed.
0.7.8: Another quick bugfix to fix the descync problems of normal SILC server
when it connects to SILC router. The descyning could happen if there
were a lot of channels, like we had on Sunday and Monday after being
slashdotted. Upgrading is strongly recommended if you are running
a server that is connected to a router. Took me only 6 hours to find
the problem...
Patch submitted by Lubomir Sedlacik <salo@silcnet.org> in PR 15416
"IMP 3.0 is now available! This major release delivers a brand-new, cleaner
user interface, improved internationalization, mail filtering, identities,
and much more, the result of over two years of feedback and experience
based on the successful IMP 2.2.x releases."
Note that the database format has changed, use
${PREFIX}share/horde/imp/scripts/imp2horde.pl
to convert to the new format.
"has been released. The 2.0 release is a massive upgrade of the Horde Application Framework. Many components have been added or streamlined. Inter-application support is much more robust, a generic MIME_Viewer framework is included, a new preferences system supports global or application scope for preferences, and more!"
*) Upgraded to Apache 1.3.23
*) Fixed a subtle indexing bug in SHMCB. Each sub-cache used an
indexing structure that (correctly) used index values (and ranges)
as "unsigned int", but the meta-structure in the header had these
ranged as "unsigned char".
*) Perform the SHMCB remove operation under mutual exclusion
to prevent a inter-process synchronization problem.
*) Made sure that mod_ssl does not segfault in case of
SCOREBOARD_SIZE < 1024.
*) Merged in the SDBM patch from Uwe Ohse which fixes a problem with
sdbms .dir file, which arrises when a second .dir block is needed
for the first time. read() returns 0 in that case, and the library
forgot to initialize that new block. A related problem is that the
calculation of db->maxbno is wrong. It just appends 4096*BYTESIZ
bits, which is not enough except for small databases (.dir
basically doubles everytime it's too small).
The main new features in 1.3.23 (compared to 1.3.22) are:
* HTTP/1.1 support for mod_proxy.
* Other mod_proxy improvements.
* The new 'FileETag' directive to allow one to build the
format of the ETag via runtime directives.
* Addition of a 'filter callback' function to enable modules to
intercept the output byte stream for dynamic page caching.
The following bugs were found in Apache 1.3.22 and have been fixed in
Apache 1.3.23:
* Fix incorrect "Content-Length" header in the 416 response.
* Revert mod_negotation's handling of path_info and query_args
to the 1.3.20 behavior (PRs: 8628, 8582, 8538).
* Prevent an Apache module from being loaded or added twice due
to duplicate LoadModule or AddModule directives.
pwcheck only checks against the /etc/passwd database. Users that need
CRAM-MD5 or SCRAM-MD5 authentication can initialize the sasldb and add
themselves in the process by running saslpasswd.
aware applications look for authentication mechanisms by default.
* Warn package admin if ${PREFIX}/lib/sasl is non-empty after
deinstallation, as it may contain service config files.
* Purge use of PKGDIR.
Lots of bug fixes in SQL parsing and supports more weildy SQL code like
using the right of an AS in athe column list of a SELECT as part of an
expression in the WHERE, ORDER BY, GROUP BY and/of HAVING clauses.
For a full report see the changelog on
http://www.hwaci.com/sw/sqlite/changes.html
post-install target, just add install-config to the list of
INSTALL_TARGETS. This is much simpler, duh! Thanks to Thomas Klausner
<wiz@netbsd.org> for pointing this out.
CUPS 1.1.13 adds support for the KOI8-R and KOI8-U encodings, message
catalogs for several Russian locales and for Simplified Chinese,
improvements for MacOS X (Darwin) and IRIX, improvements to the PDF,
PostScript, and text filters, status reporting for IPP-based printers
(paper out, etc.), and improvements to the SAMBA driver export facility.
The new release also fixes bugs in the scheduler, the lpstat command, the
CUPS API, and the pstoraster filter.
the right way to call the target is:
${SETENV} ${MAKE_ENV} ${MAKE_PROGRAM} target
The environment should be set explicitly, and one should _always_ call
"${MAKE_PROGRAM}", and not "${MAKE}" since the former always refers to
the name of the actual make program used, regardless of whether USE_GMAKE
is defined or not.
* Applied patch from Juergen Kreileder that provides the net.slp.multicastIF
slp.conf setting. net.slp.multicastIF is useful in setting up OpenSLP on
multi-homed machines where it is desireable to configure which interface
should send multicast traffic.
* Applied patch from Garth Bushell that fixes a problem where not enough
memory was being allocated to hold an escaped string in SLPEscape().
* Changed slpd "daemonize" code to chdir() to "/" so that the PWD is not
left unmountable.
> Fix problem where
> % echo $20000000000
> Segmentation fault (core dumped)
I believe the problem is already known to the maintainer of tcsh
(=christos).
bsd.pkg.mk. buildlink.mk files never need to add rpaths to LDFLAGS unless
a package installs libraries in some place other than ${PREFIX}/lib, e.g.
mysql-client, qt2-libs.
