Bug 23754 - update port: net/p5-Net-Jabber
Summary: update port: net/p5-Net-Jabber
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-12-22 14:30 UTC by Yen-Ming Lee
Modified: 2000-12-25 02:20 UTC (History)
0 users

See Also:


Attachments
file.diff (478 bytes, patch)
2000-12-22 14:30 UTC, Yen-Ming Lee
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Yen-Ming Lee 2000-12-22 14:30:01 UTC
fix another problem of p5-Net-Jabber, remove extra directories:
lib/perl5/site_perl/%%PERL_VER%%/mach/auto/Net
lib/perl5/site_perl/%%PERL_VER%%/Net

How-To-Repeat: 
http://bento.freebsd.org/errorlogs/5-latest/p5-Net-Jabber-1.0020.log
Comment 1 Kevin Lo freebsd_committer freebsd_triage 2000-12-22 14:39:54 UTC
State Changed
From-To: open->closed

Committed, thanks.
Comment 2 andrea 2000-12-24 18:24:52 UTC
> 
> fix another problem of p5-Net-Jabber, remove extra directories:
> lib/perl5/site_perl/%%PERL_VER%%/mach/auto/Net
> lib/perl5/site_perl/%%PERL_VER%%/Net
> 

Did anybody get Net::Jabber to work with Jabber 1.2 as currently in ports?

I had to cvs the latest Jabber in order to make it work! If this is a case,
why don't we roll a better distfile (or have somebody from jabber.org do it
for us)?
The impression I got from hours of experimentation is that we are being
bitten by some strange interaction between our threads implementation and
libpth. At least under -CURRENT, that is.

Bye,
	Andrea

-- 
                           Reboot America.
Comment 3 Yen-Ming Lee 2000-12-25 02:17:04 UTC
On Sun, 24 Dec 2000, Andrea Campi wrote:
> > fix another problem of p5-Net-Jabber, remove extra directories:
> > lib/perl5/site_perl/%%PERL_VER%%/mach/auto/Net
> > lib/perl5/site_perl/%%PERL_VER%%/Net
> Did anybody get Net::Jabber to work with Jabber 1.2 as currently in ports?
> I had to cvs the latest Jabber in order to make it work! If this is a case,
> why don't we roll a better distfile (or have somebody from jabber.org do it
> for us)?
> The impression I got from hours of experimentation is that we are being
> bitten by some strange interaction between our threads implementation and
> libpth. At least under -CURRENT, that is.

I tried to install jabber related libraries and daemon v1.2, but I found
that jabberd-1.2 can't response <presence/> request. Not only Net::Jabber
but also JabberIM can't communicate with jabberd-1.2 (FreeBSD) correctly.

Erich Zigler <needo@superhero.org> and Keith Minkler <keith@digix.dyndns.org>
found several problem in jabber-1.2/1.3+ , about select(), io_select(1.2) 
and MIO(1.3), I think it's the subject.

http://mailman.jabber.org/pipermail/jdev/2000-November/003780.html
http://mailman.jabber.org/pipermail/jdev/2000-December/004019.html
http://mailman.jabber.org/pipermail/jdev/2000-December/004055.html

Maybe we can ask Kostya Lukin <lukin@okbmei.msk.su>, the MAINTAINER of
jabber related libraries and daemon, how to deal with it ?

Luckily Net::Jabber can communicate with jabber-transport-1.0 prefectly.
I suggest not to upgrade to jabber-1.2 before this problem solved.

Regards,
--
 Yen-Ming Lee [§õ«Û©ú]          | http://cae.ce.ntu.edu.tw/~leeym/
 CAE Group, Civil Engineering, NTU, Taipei, Taiwan