Anope IRC Services
Anope Support => 1.8.x/1.7.x Support (Read Only) => Topic started by: Charles Kingsley on July 26, 2010, 02:54:05 PM
-
Hi folks,
As always, it is important to us that our stable releases are just that, stable.
With that in mind below is a link to a couple of windows builds (MySQL/no MySQL) and a source tar.gz which we would appreciate your help in testing.
You can file all bugs in the normal way via http://bugs.anope.org/ or if you're not sure feel free to use this thread.
MD5: d54c431933d340da0af170a31fa1c4c2 anope-1.8-gittest.tar.gz - - Normal Source Download (http://www.anope.org/downloads/Anope%201.8-Gittest/anope-1.8-gittest.tar.gz)
MD5: 08cff5616ddc6650e90472f8fdcdc263 anope-1.8-gittest.zip - anope-1.8-gittest.zip (Windows MySQL Build) (http://www.anope.org/downloads/Anope%201.8-Gittest/anope-1.8-gittest.zip)
MD5: 1f72dfe5af26d8d9b44f79819c51c812 anope-1.8-gittest-nosql.zip anope-1.8-gittest-nosql.zip (Windows non MySQL Build) (http://www.anope.org/downloads/Anope%201.8-Gittest/anope-1.8-gittest-nosql.zip)
Yes, the filesizes are quite large for Windows; this is because I've not removed the source as per a normal installer release.
Thanks for your help.
-
Well I've been keeping my anope-git updated , and used it back when it was anope-svn and so far no complaints from me, I was told about there being a problem with secureops not revoking +o rights... after a netsplit or something, I didn't try to reproduce it as i wasnt on at the time and have no idea what happened, but I thought i'd say something about it anyways.
-
/me pets Cronus
-
* Cronus purrs :V
-
bump.
-
This is a bump sorta... but... :p
My net i use anope-git on is UnrealIRCd3.2.8.1 My friends net that we kinda use as my nets testnet... is InspIRCd 1.2 and we use anope-git there too.. So im double testing it out ^_^
-
I hope you dont forget about fixes to ignore db.
-
If people test it and it works it will be included. (It was only the installers that didn't include it, those compiling from source would have always had it).
I won't be releasing it unless people take an interest and actually test the software.
-
Upgrade your test versions please, a new fix was introduced yesterday.
-
Upgrade, a bug has been fixed.
(Is anyone actually reading this?)
-
I somehow missed your last two posts, but doesn't matter I stalk the commits from CIA-1 So i update everytime it affects me, and sometimes when it doesn't like the last commit for TS6 ircd's me running unreal ofc
Anope-1.8.4-git (3020)
w00t
-
UPDATE
Please can all testers update as we've just introduced mail forking.
-
Anope-1.8.4-git (3026) global.services UnrealIRCd 3.2.x - M (enc_old) -- build #1, compiled Aug 15 2010 09:48:39
install without any problems on test- and mainnet
no problems with third modules
Greets Han`
-
Top man, cheers Han.
-
Hello!
(Official) InspIRCd 2.0 support has been added in a branch on 1.8, and with enough testing may be included in the 1.8.5 release. If you wish to test this and give some feedback, you can grab a snapshot from the top of http://anope.git.sourceforge.net/git/gitweb.cgi?p=anope/anope;a=shortlog;h=refs/heads/insp20, or clone git and use git checkout -b insp20 origin/insp20
Thanks,
Adam
-
Folks,
We want to release this but if people don't step up and do some proper testing we won't be doing it.
Simple.
-
We are testing it right now, with inspircd 2.0. So far so good. One crash occured, but it was due to a misconfiguration in inspircd (the chghost module of inspircd was not loaded, and when someone used hostserv, it crashed. However, no log error were added in anope).
For the rest, it is good, altho we need more testing.
-
My Unrealircd3.2.8.1 network has been running git forever now, and its still working great, no crashes (cept one that led to a naughty module, ns_totaltime from the modsite) But it runs great, runs smooth, no issues here on my end
-
Excellent, thanks guys, I'm glad a few people are bothering.
Maybe we'll get a release next weekend if a few more people pick up git and give it a kick.
-
I've runned it now for about three weeks and no crashes or bugs found yet.
Latest stable UnrealIRCd.
-
I've been running 1.8 git on my own network with InspIRCd 1.2 for a few weeks now. Aside from a small issue with how 1.8 handles Q:lines on Insp 1.2, I've seen no problems thus far. The ones I did see I already brought up and they have been fixed.
-
For some reason, it does not like inspircd's Y channel mode (when you /OJOIN), there is no bug, but the logs complain a little:
[Sep 05 17:27:18 2010] fjoin: unrecognised prefix: Y
Oh well, nothing really big here. Is it worth filling a bug report?
-
Which version of InspIRCd and what Anope protocol module are you using?
-
I run Inspircd 2.0, the latest git, and I am using prot 1.2 for anope.
-
Try using the latest git's inspircd20 proto mod.
-
Thanks, will do right away.
-
It seems to work now, thank you :)
-
Anope-1.8.4-git (3035) global.services UnrealIRCd 3.2.x - M (enc_old) -- build #1, compiled Sep 11 2010 02:02:07
install without any problems on test- and mainnet
no problems with third modules
Greets Han`
-
Released.
-
Updated to it before you even made this post :P
-
That's great! Installing 1.8.5 on my network now. I am also updating to the latest git on my test server. Once I migrated my ircds, I will change it to start testing 1.9! Can't wait.
-
Good man josh, thanks :)
-
I don't know if it is a bug or not, but it seems that anope does not enforce channel modes correctly if certain modes are MLOCK with the inspircd 20 module. I am not sure what is the problem yet, so I have not reported it yet.
The bug causes an empty channel to not set modes (or not all of them), or will allow mode changes (aka add modes that are locked at "-" or remove modes that are locked at "+").
However if services are restarted and someone is present in the channel, the enforce will trigger. I will dig more into it and come back on this. Thanks for the read :)
EDIT: The cause is not related to the +O or +A channel modes when they are locked (as previously thought) and not related to the unreal to inspircd module switch (I've created new channels and they seem to have the same problem).