Currently showing all newsitems posted in 2014. Newsitems are available for these years:
Anope 1.8.9 Release
Today we are announcing the release of Anope 1.8.9, which includes minor bug fixes and support for Hybrid 8.1.
With the release of Anope 2 later this month, Anope 1 will be officially moved to "Legacy" status and we will no longer be recommending users use it.
As such, this will be the last release of the Anope 1 branch.
However we will continue to support users running Anope 1.8.x until at least March 23, 2015, at which point we will reevaluate the situation.
The downloads will also remain on anope.org until at least this time.
06/05 F Fixed modules being loaded regardless of the load abort signal. [#1527]
08/16 F Fixed hs_request to show requested ident in memos [#1545]
08/16 F Fix kick reason in cs_suspend/cs_forbid if no reason is given [#1544]
12/09 F Fix undefined symbol error on Solaris11 [ #00]
Provided by Michael Wobst - 2013
05/25 U Update Hybrid protocol module to support Hybrid 8.1
06/21 U Update Hybrid protocol module to support vhosts
MD5: c482d37301dc7c67ee98bf796b329be0 Anope-1.8.9.tar.gz
MD5: 9a4108570d600cf57d19d6ddf92deb06 Anope-1.8.9.exe
MD5: c088db8885b9731e446d89a759218135 Anope-1.8.9-MySQL.exe
Posted on Tue, Mar 4 by Adam (Read More...)
Anope 2.0.0-rc4 - Release (updated)
We are proud to announce the release of Anope 2.0.0-rc4, which is the final release candidate for the final Anope 2.0.0 release.
Once fully released, Anope 2 will replace the current stable branch, 1.8, which will be considered legacy and will no longer be maintained. We will no longer recommend it for use by new networks. However, we intend to continue supporting users currently using 1.8 after the final release for some time, including keeping the download on http://anope.org. Unseating a branch that has been in existance for a decade this March is not an easy task, and we understand it will take some time for users to move over.
While we still classify this release as not production ready, is has a great degree of stability and may very well be the same as the final release. We highly recommend networks wanting to use Anope 2 once it has been officially marked as stable test this release candidate. Bugs can be reported on our bug tracker at https://bugs.anope.org.
Overview of changes from 1.8 to 2.0:
Use an account style system instead of the old NSNickTracking option, which allows you to stay logged in no matter what nick you are on.
Fantasy support for all commands.
Can assign core pseudo clients (such as ChanServ) to channels.
A built in web panel.
Persistent channels, which allows services bots to stay in empty channels.
Channel passwords replaced with founder level access (QOP, or the FOUNDER access level).
OWNER access levels added, defaults to access level 9999.
The option to use a flags based channel access system.
Ability to authenticate via SSL certificates
Autojoin channels on authentication (ns_ajoin)
Significantly more advanced logging system, choose what is logged and where it is logged.
Support for other optional database backends, such as SQL and Redis.
Granular command configuration. Configure which command is on what service, what it's called, and who can use it.
Configurable opertypes, which allows defining new services operator levels (Root, Admin, Oper, etc.) and what permissions each has.
Ability to authenticate users against external databases, such as by SQL or LDAP.
Capability to switch between different encryption methods.
Installation instructions for Linux/UNIX:
Anope 2 requires CMake to be built. On most systems you can simply install the package from your package manager, eg. sudo apt-get install cmake or sudo yum install cmake.
First, enable any extra modules you want by executing the 'extras' script. Extra modules generally depend on other libraries, such as MySQL, and are not enabled by default due to their dependencies. Then run:
1) Install Anope 2 to a separate directory from your old install (such as ~/services2)
2) Copy 1.8's databases to the 'data' directory of your new install.
3) Configure services, the configuration files are located in the 'conf' directory.
Anope 2 uses a different configuration file format from 1.8, you will have to reconfigure them completely.
Use your old configuration as a reference.
4) While configuring, be sure to load db_old, which loads the old 1.8.x databases, and db_flatfile, which writes out the new Anope 2 database.
Ensure that the hash method in db_old's configuration block is the same encryption method that you are currently using on 1.8.
Load the correct encryption module, which is the same one configured in db_old.
5) Start services. Once you confirm your database has been successfully imported, comment or remove db_old from the configuration file, so that the next time services restart, they will load the newer database.
Third party modules, such as most of the ones found on on the Modsite, that are written for 1.7.x or 1.8.x
will not work with Anope 2. However, many of the features of the most popular 1.8 modules have been included in the Anope 2 release, so you may find you no longer need your extra modules. If it is unclear to you whether or not a given feature is in Anope 2, come ask us
Foreign language support:
If foreign languages are not working on your install, see docs/LANGUAGE in the source distribution. Additionally, we only have translators for the Spanish, German, French, Dutch, and Italian languages. The translations for the other languages are out of date, and are built from the old 1.8 language files. However as many of the language strings have changed in the development of 1.9, most of the language strings for the other languages are not translated. If you would like to contribute by translating Anope, we will accept translation updates prior to the final release. Contact us on IRC for more information.
Join our IRC channel at irc://irc.anope.org/anope for questions or comments.
MD5 Sum: 6bebab85c3bc975da965b61c507ffb5b anope-2.0.0-rc4-source.tar.gz
MD5 Sum: b9429e6d0777fe6e9d014d9d9ae06abe anope-2.0.0-rc4.exe