Re: devel/pylint location fix
On 2007-04-02 at 20:54 -0400, Tom McLaughlin wrote: > On Mon, 2007-04-02 at 15:14 -0700, Phil Pennock wrote: > > Port devel/pylint doesn't seem to be well distributed on the > > ftp.CC.freebsd.org mirrors and can't be retrieved from the currently > > defined master; ftp://ftp.logilab.org/pub/pylint/pylint-0.13.1.tar.gz > > results in an FTP error after anonymous authentication: > > 421 Service not available, remote server has closed connection. > > > > Change the protocol to http: but leave the host and local path alone and > > the file is retrievable, passing checksum tests.. Given that http is > > generally lighter weight, should MASTER_SITES include the http: variant > > before the ftp one? > It's working fine here. Probably just a temporary glitch in the ftp > service on that machine. I should probably have pointed out that this problem persisted across multiple days. I ignored it the first time that portupgrade failed, pursued it when it persisted. I didn't keep notes (personal box) so don't know which day it first failed. Is there any harm to using the http variant too? Perhaps after the ftp schema item? -Phil ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
devel/pylint location fix
[ ports@ listed as current MAINTAINER ] Port devel/pylint doesn't seem to be well distributed on the ftp.CC.freebsd.org mirrors and can't be retrieved from the currently defined master; ftp://ftp.logilab.org/pub/pylint/pylint-0.13.1.tar.gz results in an FTP error after anonymous authentication: 421 Service not available, remote server has closed connection. Change the protocol to http: but leave the host and local path alone and the file is retrievable, passing checksum tests.. Given that http is generally lighter weight, should MASTER_SITES include the http: variant before the ftp one? Regards, -Phil ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
devel/rlwrap PTY problems
Hi,
rlwrap is failing "rlwrap: error: Could not open master pty:
Input/output error" on FreeBSD 6.1.
Upon investigation, I see that the configure script is hardcoding the
list of PTYs to scan based upon those found in /dev/ at time of
compilation. This obviously does not work well with devfs.
Since FreeBSD now has openpty(), the fix is to NOT put
"ptyttylib_cv_ptys=BSD" into CONFIGURE_ENV. I can confirm that an
rlwrap() built in this way appears to work for FreeBSD 6.1/amd64 (I can
"rlwrap tclsh8.4" and get history and the like; no extensive tests have
been performed).
I don't know which release made devfs the standard, but I suspect that
you're looking at another ".if ${OSVERSION}" check. :^(
Thanks,
--
VISTA: Viruses, Infections, Spyware, Trojans & Adware
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
