In file included from /home/pbulk/build/chat/anope/work/anope-2.0.7-source/src/socketengines/socketengine_epoll.cpp:18:0:
/usr/include/sys/epoll.h:1:2: error: #error "This header has been disabled to stop its functionality from being used."
#error "This header has been disabled to stop its functionality from being used."
^~~~~
/home/pbulk/build/chat/anope/work/anope-2.0.7-source/src/socketengines/socketengine_epoll.cpp:23:20: error: 'epoll_event' was not declared in this scope
The notable changes includes:
Fix not sending login data on successful NickServ GROUP
Fix m_httpd to not consider headers to be case sensitive
Add InspIRCd 3 protocol support
Add 'n' email token for use in the email change template
Add logging for NickServ UNGROUP
Fix setting swhois on UnrealIRCd
Add nickserv/recover permission to allow opers to recover other users
Fix superadmin not being removed when deopering
Fix setting nickserv access list in webcpanel
Add support for post-handshake SASL in Unreal 4.2.2+
Add logging for channel memo deletionso
Without gettext-lib and msgfmt being available, package creation fails
because the locale files aren't generated.
Similar reasoning for gnutls as inspircd - anope is based on an old
version of inspircd and is also GPLv2 with no exception for OpenSSL.
gnutls is the recommended TLS library for both.
Performing substitutions during post-patch breaks tools such as mkpatches,
making it very difficult to regenerate correct patches after making changes,
and often leading to substituted string replacements being committed.
Unsorted entries in PLIST files have generated a pkglint warning for at
least 12 years. Somewhat more recently, pkglint has learned to sort
PLIST files automatically. Since pkglint 5.4.23, the sorting is only
done in obvious, simple cases. These have been applied by running:
pkglint -Cnone,PLIST -Wnone,plist-sort -r -F
Problems found with existing distfiles:
distfiles/icb-5.0.9.tar.gz
distfiles/icb.2.1.4.tar.Z
distfiles/zenicb-19981202.tar.gz
No changes made to these /distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Version 1.7.20 (revision 1324)
With all currently known bugs fixed, this new release of Anope contains
loads of bugfixes and should provide a stable experience. This is one of
the last releases in the 1.7 series of Anope. We encourage users who were
not using the 1.7 series for stability reasons to try out this release and
report any bugs found on our bugtracker at http://bugs.anope.org/ .
An important note for MySQL users: various database schema improvements
have been added in Changes.mysql. Be sure to apply these changes to your
database schema for a large increase in performance of the MySQL code.
Take a look at the change log for more information about the changes made
for this release.
Version 1.7.21 (revision 1341)
This new release fixes a XOP-related exploitable crash bug which appeared in
Anope version 1.7.20. Earlier versions are not affected. Networks running
Anope 1.7.20 are strongly advised to upgrade to this release. Even though
networks running earlier versions are not affected by this bug, they are
still advised to upgrade due to numerous other bugfixes.
Next to the fix for the crash bug mentioned above, a number of other things
have been fixed as well, including various InspIRCd-related issues, bugs in
the MySQL code and a shiny new Russian translation.
Take a look at the change log for more information about the changes made
for this release.
Version 1.7.19 (revision 1247)
This new release of Anope contains various bugfixes and adds support for
InspIRCd 1.1. Various minor issues in the new MySQL code have been fixed
and overall stability of the MySQL code has improved.
The behaviour of the UsePrivmsg and NSDefMsg configuration options has
changed and anyone using those options is advised to take a look at the
comments near that options in the updated example.conf.
Take a look at the change log for more information about the various bugs
fixed in this release.
the owner of all installed files is a non-root user. This change
affects most packages that require special users or groups by making
them use the specified unprivileged user and group instead.
(1) Add two new variables PKG_GROUPS_VARS and PKG_USERS_VARS to
unprivileged.mk. These two variables are lists of other bmake
variables that define package-specific users and groups. Packages
that have user-settable variables for users and groups, e.g. apache
and APACHE_{USER,GROUP}, courier-mta and COURIER_{USER,GROUP},
etc., should list these variables in PKG_USERS_VARS and PKG_GROUPS_VARS
so that unprivileged.mk can know to set them to ${UNPRIVILEGED_USER}
and ${UNPRIVILEGED_GROUP}.
(2) Modify packages to use PKG_GROUPS_VARS and PKG_USERS_VARS.
Since the previous release, we have been working on the
MySQL subsytem to improve stability and security of this code. Next to
that, we have added support for encryption modules, finally including
support for encrypting passwords with proper MD5 or SHA1.
Next to these two major improvements there are quite a few bugs fixed,
including bugs related to module code, internal events, various typo's
in the language files, and some IRCd-related issues.
Please note that, due to the big changes, this release might not be
as stable as previous development releases. The new MySQL and encryption
code have been found stable enough to release to the public, but they
might still have undiscovered quirks.
Be sure to check Changes.conf for encryption-related changes to the
configuration file. Users of MySQL should also note that the MySQL
scheme has been changed in this release and needs to be updated. This
can be done using the updates in Changes.mysql.
