Jabberd2 is the new implementation of the jabber protocol ( http://jabberd.jabberstudio.org/2/ ) but many problems arrive when trying to have jabberd2 and old transports. This bug is a place for discussion of those issues to take place.
Created attachment 24500 [details] jabberd-2.0_rc1.ebuild This is my first test on this one. Lots of commented stuff (tests i was making) Right now i dont like the way the configure/install process changes the xml files that it will latter install.
Created attachment 25533 [details] jabberd-2.0_rc1.ebuild With this version now I use berkdb (4.1.25 is now stable) right i have no idea if this works (it builds and installs). Next step is to read the rest of the docs and give jabberd2 a test run.
You can find my stuff of jabberd2 in my dev.gentoo.org dir http://dev.gentoo.org/~cybersystem/ebuild/net-im/jabberd/.. I did in a few minutes so some parts may be a bit weird but some parts are better i guess :) also its for stable2..
Is it stable with OpenLDAP?
I do not know if this is stable with OpenLDAP. On the server admin mailing list i see many people that use it like that.
Created attachment 25809 [details] jabberd-2.0_rc2.ebuild This is a mixed version of my version and cybersystem (more his version than mine :) ). I still have to give a good look to the init script. Any ideas on that? A separate script for jabberd2, or a new version that uses some external information to know what services to start and with what jabberd?
i'd suggest adding an option for the pipe authreg module, as it is very useful. and as for the pid and logging directories.. the ebuild i created (which was sadly lost after a HD crash), used /var/run/jabberd/$pids and /var/log/jabberd/$logs... but maybe that's just an aesthetic point. enewuser already checks if the user exists, so you don't need those if statements same with enewgroup.. And a few other questions.. do you want it to be installed alongside jabberd 1.4.. it's kinda necessary for some components... unless they work with the JCR so at that point.. we'd need to make jcr a useflag of the mu-conference package or move everything towards jabberd2.. which may or may not be possible right away. What do you guys think?
>>> Unpacking jabberd-2.0s2.tar.gz to /var/tmp/portage/jabberd-2.0_rc2/work >>> Source unpacked. /usr/sbin/ebuild.sh: line 62: ./configure: No such file or directory !!! ERROR: net-im/jabberd-2.0_rc2 failed.
the fix: S="${WORKDIR}/jabberd-2.0s2
Created attachment 27373 [details] jabberd-2.0_rc2.ebuild Solved axxackall's problem. As always all comments are more than welcome.
where is /etc/init.d/jabberd ? Looks like it missed...
/etc/init.d/jabberd found in cybersystem files.
Still not running: # jabberd -D JBRD: debug on JBRD: version(2.0s2) JBRD: config_dir(/etc/jabberd) JBRD: LaunchJob: router -> /usr/bin/router -c /etc/jabberd/router.xml -D JBRD: LaunchJob: resolver -> /usr/bin/resolver -c /etc/jabberd/resolver.xml -D JBRD: LaunchJob: sm -> /usr/bin/sm -c /etc/jabberd/sm.xml -D JBRD: LaunchJob: s2s -> /usr/bin/s2s -c /etc/jabberd/s2s.xml -D JBRD: LaunchJob: c2s -> /usr/bin/c2s -c /etc/jabberd/c2s.xml -D Broken pipe
When trying out Sascha's jabberd 2.0s2 ebuild, I get the following error: http://segfault.slackware.co.nz/jabberd-2.0s2_error.txt I'm sure I didn't get this last week when compiling with this ebuild (using the MySQL USE flag), but I have reinstalled gentoo on this server and now get the above error (with the PostreSQL USE flag). I've also tried compiling with just the "db" USE flag but still get the same error. How do I fix this? Thanks
First of all i will use bug 43851 for a new init.d system. There will be a init for the main jabber server (with option to use jabberd14, jabberd2 or another jabber daemon) and then all external transports/modules will have their own init script that will depend on the main one. Second: James i could not see your error message, I get a (110) Connection timed out
I adjusted cyber's init script a little and this works, for the most part. Its not perfect, but I thought I'd at least show you something that works. (Sometimes, it doesn't stop all the processes right.) Gustavo mentioned that we should have separate init scripts for each module/transport to make this more scalable. I'm going to try and work on that. Axxackall: I had the same error you had. Make sure your configuration is all correct, and also, I think there was a permissions error somewhere. Try running the modules/transports individually with -D and see what errors you get. I'm also wondering if the permissions on the binaries aren't right, so I'm looking into that as well. Below is a diff of the init script that was based on cybers. Remember, I'm going to try a different approach to this. :) --- jabberd.orig 2004-02-14 05:55:35.000000000 -0600 +++ /etc/init.d/jabberd 2004-03-16 07:02:03.310162080 -0600 @@ -9,12 +9,16 @@ start() { ebegin "Starting jabberd" - start-stop-daemon --start --quiet --exec /usr/bin/jabberd + start-stop-daemon --start --quiet -b --exec /usr/bin/jabberd eend $? } stop() { ebegin "Stopping jabberd" - start-stop-daemon --stop --quiet --exec /usr/bin/jabberd + start-stop-daemon --stop --quiet --exec /usr/bin/router + start-stop-daemon --stop --quiet --exec /usr/bin/resolver + start-stop-daemon --stop --quiet --exec /usr/bin/sm + start-stop-daemon --stop --quiet --exec /usr/bin/s2s + start-stop-daemon --stop --quiet --exec /usr/bin/c2s eend $? }
Created attachment 27496 [details] jabberd Ok, here's a much better init script for jabberd2. It starts each component from the script instead of using the perl wrapper that comes with jabber. Evenutally, we could have it read the jabberd.cfg file in /etc/jabber and have it run other modules from there. I don't have time today to mess with that, but its a start. At least I know this works! I've started/stopped the service many times w/o any problems. Let me know how it works.
what are correct permissions for binaries? should it be 750 or 775?
Also, there should a way for the init script to print error output (instead of "green" [OK]) when the service doesn't really start.
looks like the DB setup script did not fix permissions peroperly: # /usr/bin/c2s -D Wed Mar 17 00:05:30 2004 [notice] starting up Wed Mar 17 00:05:30 2004 [info] process id is 10472, written to /var/jabberd/pid/c2s.pid Wed Mar 17 00:05:30 2004 authreg_mysql.c:456 SQL to create account: INSERT INTO `authreg` ( `username`, `realm` ) VALUES ( '%s', '%s' ) Wed Mar 17 00:05:30 2004 authreg_mysql.c:457 SQL to query user information: SELECT `password`,`hash`,`token`,`sequence` FROM `authreg` WHERE `username` = '%s' AND `realm` = '%s' Wed Mar 17 00:05:30 2004 authreg_mysql.c:458 SQL to set password: UPDATE `authreg` SET `password` = '%s' WHERE `username` = '%s' AND `realm` = '%s' Wed Mar 17 00:05:30 2004 authreg_mysql.c:459 SQL to set zero K: UPDATE `authreg` SET `hash` = '%s', `token` = '%s', `sequence` = '%d' WHERE `username` = '%s' AND `realm` = '%s' Wed Mar 17 00:05:30 2004 authreg_mysql.c:460 SQL to delete account: DELETE FROM `authreg` WHERE `username` = '%s' AND `realm` = '%s' Wed Mar 17 00:05:30 2004 authreg_mysql.c:479 mysql connecting as 'jabberd2' to database 'jabberd2' on localhost:3306 Wed Mar 17 00:05:30 2004 [error] mysql: connection to database failed: Access denied for user: 'jabberd2@localhost' (Using password: YES) Wed Mar 17 00:05:30 2004 [error] failed to initialise auth module 'mysql'
Oops, sorry. This link should work: http://www.archnetnz.com/text/jabberd-2.0s2_error.txt I don't know if it matters, but I'm running the latest gs-sources kernel (2.4.25_pre7). Thanks
Axxackall: 1) That's something else I need to include is the permissions. I'll work on that tomorrow for the ebuild. Basically, if you look at the comments the bottom of this [1] page, You'll see what you need to do. All the components need to be owned by jabber:jabber, and the they needs to be chmod u+s. I'll add that to the build and test it tomorrow. This will enable the components to be run as the jabber user and *not* root. Running as root is generally bad. 2) On your init script error, I'll add that too.. not hard at all. 3) The database errors you have looks like you don't have proper permissions setup for the jabber sql user. The script that comes with jabber only creates the database/tables/etc. It doesn't do anything about setting up proper permissions. Check out this [2] link and follow their instructions. [1] http://www.jabberdoc.org/app_rc.html [2] http://www.jabberdoc.org/section05.html James: Were you running anything else at the same time of that installation? It looks like passwd or some other program had a lock on the passwd/shadow file and it couldn't create the jabber user/group. I'd look into that and see what's going on.
manula fix (but I guess it must fixed autmaitally in 'ebuild config'): # mysql -u root -P 'rootpasswd' GRANT ALL PRIVILEGES ON *.* TO 'jabberd2'@'localhost' IDENTIFIED BY 'secret' WITH GRANT OPTION; \q mysql -u jabberd2 -P 'secret' \. db-setup.mysql now c2s starts
now it starts, I can register a new accoubt. But when I try to connect I've got an error that a login is incorrect. Although in mysql records I see a correct username and paasword of just added jabber user. So, now what? How make the user to login to the server? What permissions shoould I check in /etc/jabberd/*xml files?
problem to login. on the client-side: <iq xmlns='jabber:client' id='auth_2' type='error'><error type='wait' code='500'><internal-server-error xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq> on the server log: /var/log/jabberd/c2s: Wed Mar 17 01:35:01 2004 [notice] [7] [myip, port=43994] connect Wed Mar 17 01:35:01 2004 [notice] [7] auth succeeded: username=axxackall, resource=Psi Wed Mar 17 01:35:01 2004 [notice] [7] requesting session: jid=axxackall@myhost/home Wed Mar 17 01:35:01 2004 [notice] [7] [myip, port=43994] disconnect /var/jabberd/log/sm: Wed Mar 17 01:35:01 2004 [notice] user not found, can't start session: jid=axxackall@myhost/Psi However, the user is in mysql db already - I've just created a new account using Psi.
Lance: I'm fairly sure that no process is using the group file. To try to prove this to myself, I put my machine into "init 2" and tried compiling again. It still wouldn't compile. So I created the group and username manually according to the commands in the ebuild, recompiled the ebuild and voila - it worked! :)
In my case the login is failed as the registration did create the record in the authreg table, but did not create a record in the active table. I don't know why, but the advise in the troubleshooting guide is to create such record manually (!), but they did not give any advise what should be in such a record. If anyone here has got jabber2 running, can you give me an example of active table records?
I found the fix. I switched from mysql to pgsql and found something new in logs: that it cannot start pgsql module refering further to pg_hba.conf which told me immidiately that the problem in host permissions. I've changed FQDN to localhost in jabberd XMLs and - ta-da! - now it works and I login! I haven't checked yet with mysql, but I am sure it's the same. Mysql is just much weaker than pgsql as it gives much better diagnostics. Also mysql is much stranger about host permissions. Anyway, I've already advised jabberd2 developers to reflect my case in FAQ - other people may have the same problem.
Created attachment 27690 [details, diff] Fix for the invalid xml stream bug I attached a patch that fixes the bug described in http://www.jabberstudio.org/projects/jabberd2/bugs/view.php?id=3061 .. I'm using that patch on im.gentoo.org and it seems to work well.. also you might want to change some permissions in the ebuild so that jabberd is run by the user jabber (http://www.jabberdoc.org/app_rc.html at the bottom) Humpback: if you add that patch to the ebuild please give credit to the guy who made it (cfs@nova.es)
I added jabberd-2.0 (s2) to portage with a modified init script that starts either jabberd2 or jabberd1.4 . It is hardmasked so please test and report here.
Okay couple of notes on the ebuild process (nothing yet on stability/usage still setting it up). 1) --enable-debug is used in the ./configure call but shouldn't that be only used if we are enabling the "debug" use flag? 2) This error occured after creating the user and group jabber but before gzipping the man pages chmod: invalid mode string: `jabber' Looks like only directories/files not jabber:jabber /etc/jabberd/templates/ roster.xml roster.xml.dist /var/spool/jabber/ 3) FS is specifically not recommended as a storage driver. While I haven't seen anything that gives a better reason then poor performance (mailing lists) and for use only with development. Still doing research on this I'm not satisfied with the lack of information about why this is not recommended. 4) self-cert.sh needs to be modified The script references /etc/jabber/ instead of /etc/jabberd/ so the self cert doesn't get placed into the /etc/jabberd/ directory. Still working on configuring this monster so may have more to add later this weekend.
bfriday: Thanks for your notes, please keep them coming. 1- --enable-debug normally is only activated with debug in use flags, but this is a beta release in Gentoo so he have it there at least untill it gets out of packages.mask. 2- I have to check this carefully. 3- Well fs is just there, I have only seen notes about performance. 4- I will update that to use conf.d entry and place the certificate in the correct place.
2nd Update: Ah okay didn't realize that was why debug was enabled. Here are two other debug lines that might be good for future use potentially. --enable-debug Enable debug messages --enable-nad-debug Enable NAD debugging --enable-pool-debug Enable pool debugging Anyways found one additional problem in /etc/init.d/jabber has an error in the kill command after stop should be removed. I believe the if else section should take care of stopping the jabber 1.4 server. stop() { ebegin "Stopping main Jabber Component" # kill `/var/log/jabber/jabberd14.pid` if [ "${JABBERD}" = "jabberd14" ] then Here is my notes/comments based on what I've done so far: - Initial Configuration Comments - Everything connects via 0.0.0.0 the only one which needs to connect to an outside IP is c2s.xml all the rest can connect via localhost without a problem (tested). Changing this to 127.0.0.1 would make gentoo's installation more secure by default. Though I'll leave that decision to you Gustavo - Usage Tests Box: x86, 128 MB Ram, CFLAGS = -march=i686 -O3 -pipe, - MySQL storage and authentication with registration - storage works - authentication works - MySQL storage and LDAP authentication without registration - storage works - authentication to our existing ldap server works great - autocreate sessions are needed with ldap, and it works great I'm in the process of installing this on a Sun Blade 100 so hopefully I can give a report on that later this weekend. If you have any specific request on usage testing let me know and I'll run them. MySQL and LDAP pretty well cover my needs for implementation...
can you add the authreg module pipe please? i had this in my original ebuild to humpback not sure if it should be a use flag... it should prolly just be in by default.. and it is quite useful. I use it to authenticate against my cms with a custom php script, and the perl example script is pretty nice too :)
<snip> if [ `use db` ]; then storage="${storage} db" authreg="${authreg} db" fi </snip> I think it should be "if [ `use berkdb` ]; then" ... The keepdir statements on the /var/*/* dirs are missing. Emerging jabberd twice results in missing /var/*/* directories.
*** Bug 49863 has been marked as a duplicate of this bug. ***
Created attachment 30750 [details] added authreg pipe support adding authreg pipe as it is very valuable for integration with external authentication methods
JIT is nice because it almost drops right into jabberd2 with no modifications. But. Since Jabberd2 doesn't include xdb, JIT must use its own. The current ebuild for jit doesn't build the xdb driver, xdb_file.so, even though it's sitting right there in the source directory. I would suggest that the JIT ebuild include a step to compile and install xdb_file.so next to jit.so.
I'm running jabberd2 (2.0s3) on my Gentoo box now (without plugins though). I do use the wrapper-script though, sinve I use multiple c2s-Services and I don't like the idea of changing "the way things work" in distributions.. The wrapper script works fine and works the same on Fedora, Debian or Gentoo -> So I keep it. I had lots of problems with the storage first. It seems that --enable-storage and --enable-authreg don't work as expected, especially with more than one option ("db mysql"). I used ./configure --enable-db instead (mysql is enabled anyway -> default) and it works flawlessy now. One last point: The selfcert-script tries to create a certificate in /etc/jabber/, the ebuild (and the source/distribution) installs to /etc/jabberd/ . I guess that's a typo or just obsolete.
hi, i noticed that libidn should be added to the requirements as otherwise configure will fail. the useflags and there effect on the configure line need work, as in stable3 which is the current package, the configure switches changed
Created attachment 34523 [details] LDAP Full (Backend) made by Nikita Smirnov With this patch it should be possible to use your LDAP server with the same VCARD functionality as the default database stuff in Jabberd2. I'm going to test it so I hope this is a real usefull upstream something.
*** Bug 55795 has been marked as a duplicate of this bug. ***
ok, since my bug was marked as a dup (?), here goes to people who are maintaining this ebuild: All the paths in /etc/jabberd/self-cert.sh need to be changed from /etc/jabber to /etc/jabberd
Alastair: maybe another way is to change the jabberd-2.0 ebuild from: exeinto /etc/jabberd to: exeinto /etc/jabber the .xml for the configuration files have diferent names so i dont expect overlap. That would save us have two scripts and would ease upgrades because the .pem file would be the same.
if you move that, what happens with people who have jabberd-2 installed already? i guess they have to move all the configuration files over? possibly its not too bad given that its hard-masked atm.
Created attachment 34777 [details] jabberd-2.0.3.ebuild This ebuild is for 2.0s3 (darn naming scheme in jabberd2). It is a quick hack due to the new configure options. I have only built this but have not even tried the install part (altought i changed the place were config files are placed to be consistent with 1.4). Next wednesday i have a very hard exam but after that i will continue to work on this. Sorry for the delay this bug has been having but right now I have a server to test stuff and that will help developing (I was making tests on the same server where i had my jabber.felisberto.net ).
Tried to install and got the same authentication errors. Would insert a new user into the database, but user then could not login. Noticed on the development site, that maybe Berkeley DB is used for some authentication stuff, so emerged the most recent DB ebuild. Then I took the suggestion to put the --enable-db in the ebuild, and heck just for the fun i emerged open LDAP. So I am not sure which one did the trick but I am up and operating with a cacert key no problem on SSL, so far so good. I like the way it is being done now for files. If here was a change I would suggest that the etc directory be jabber2 versus jabberd. More in line with the current jabber install, and since jabber is a pre-req for mu-conference might be more compatible, but I think they should be seprate tree's instead of mixing the version directories. Maybe an unmerge of jabber would for some reason delete jabber2, visa versa.
Can anyone suggest how the init script can launch the processes as user jabber? The install doc specifically say not to run as root.
Created attachment 37929 [details] Fixed jabberd init script Fixed Lance Albertson's init script to run as jabber user/group instead of root. Recommended in the jabberd documentation.
Created attachment 39538 [details] ebuild - fixing somethings This would not compile w/o mysql support, I added a bunch of elses to the if statements to disactivate things that I did not want. After that it built 100% ok w/ just Pg support.
Created attachment 39541 [details] Ebuild - Normalize the formatting. I noticed that some tabs snuck in, and i wanted to get rid of them. Also I didn't do a very neat job of keeping the options if..else..fi's uniform.
please include the init script changes suggested in #49 in cvs - as running the jabber as root user is not too wise indeed (current cvs situation).
I am getting a lot of crashes with my jabberd2 install. So I began looking to upgrade - unfortunatley jabberstudio got hacked, so there are no downloads till at least Feb 11th. I located a Source RPM for Jabber-2.0s5, so I ripped it apart, and I took in patches from http://www.marquard.net/jabber/. I am posting all of the above here. Here is my key fingerprint: 329C 5D8B D091 2936 818F 290D 7307 8CEA DEF5 547B You can download the package from: http://dev.imr-net.com/distfiles/jabberd-2.0s5.tar.gz Ebuild to follow here.
Created attachment 49718 [details] jabberd-2.0.5.ebuild
* Updated to jabberd-2.0s5 * recommend name chages to jabberd-2.0.5.ebuild * merged jabber.rc6-r7 with script from #49 to produce jabber.rc6-r8 * added patches: * patch-c2s-pipe2.patch * patch-mysql-indexes.patch * patch-s2s-ssl-startup.patch * patch-sm-object-fix.patch * patch-zzzz-s2s-v3e.patch I added most of those patches because the RPM recommended them. RPM Location: http://php.cujae.edu.cu/downloads/jabberd2/srpms/rhel/as3/ Recommended by: http://www.marquard.net/jabber I am taking this to production because one of my sessions managers keeps dumping.
Oops! Forgot this: (no browsing, must have URLs) http://dev.imr-net.com/distfiles/jabberd-2.0.5-ebuild.tar.bz2 http://dev.imr-net.com/distfiles/jabberd-2.0.5-ebuild.tar.bz2.asc
net-im/jabberd-2.0_p20050119 has just been committed and should hit the mirrors in some hours (see http://www.gentoo.org/cgi-bin/viewcvs.cgi/net-im/jabberd/jabberd-2.0_p20050119.ebuild this is the latest available CVS snapshot of the jabberd2 sourcecode and *HIGHLY* recommended by the jabberd2 developers, as it contains several important patches/fixes which which aren't even contained in 2.0s6. the developers even verified the sourcecode contained in that file didn't suffer any manipulation related to the jabberstudio.org breakage. the md5sum in portage is the one I got from the developers, so you should be in a safe harbor :) thanks.
i'm trying to upgrade from 2.0-r2 to jabberd-2.0_p20050119 and all else seems fine but this: * Adding group 'jabber' to your system ... * - Groupid: next available groupadd: group jabber exists !!! ERROR: net-im/jabberd-2.0_p20050119 failed. !!! Function enewgroup, Line 882, Exitcode 9 !!! enewgroup failed ... i don't know, but it seems that enewgroup/enewuser don't do checks the way they are supposed to? or they should be used somehow differently? my emerge info output: Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.4.3-20050110, glibc-2.3.4.20040808-r1,glibc-2.3.4.20041102-r0, 2.6.7-gentoo-r14 i686) ================================================================= System uname: 2.6.7-gentoo-r14 i686 AMD Duron(tm) Processor Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Jul 12 2004, 12:34:16)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.14.90.0.8-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.7-r4 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -O2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks prelink sandbox sfperms" GENTOO_MIRRORS="ftp://mirror.switch.ch/mirror/gentoo/ http://trumpetti.atm.tut.fi/gentoo/ http://ftp.ntua.gr/pub/linux/gentoo/ ftp://ftp.wh2.tu-dresden.de/pub/mirrors/gentoo" LANG="sl_SI.UTF-8" MAKEOPTS="-j2" PKGDIR="/usr/src/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 3dnow X aac aalib acl acpi alsa apache2 apm arts artswrappersuid audiofile avi berkdb bitmap-fonts blas blender-game bonobo bzip2 cdr chroot crypt cups curl dga doc dvb emboss encode f77 faac faad fam flac fmod foomaticdb fortran gd gdbm gif gimpprint gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile hbci imagemagick imap imlib imlib2 ithreads java jpeg jpeg2k junit kde kerberos krb4 lcms ldap libg++ libwww mad maildir mailwrapper memlimit mikmod mmx mng monkey motif mozilla mp3 mpeg mpi mule mysql ncurses nls nptl nptlonly nvidia oav odbc ofx oggvorbis ooo-kde opengl oss pam pda pdflib perl php pic png postgres ppds pwdb python qt quicktime quotas quotes readline real ruby samba sasl scanner sdl slang slp snmp socks5 speex spell ssl svg svga tcltk tcpd tetex theora threads tiff truetype truetype-fonts type1-fonts unicode usb vda vhosts vidix vim-with-x wmf xine xml xml2 xosd xprint xv xvmc zeroconf zlib" Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL, LDFLAGS thx for your work and cheers
in /usr/bin/jabberd (2.0.8-r2): my $Bin = "@bindir@"; hmm .... baad :(
can you please add pipe support by default?
A brief question - did you have in mind that jabberd and jabberd2 are distinct projects? AFAIK putting them both into portage as different versions of the same package is an error.
in portage for a very long time.
