Date: Wed, 7 Feb 2007 07:54:04 -0500 From: dewey hylton <freenx@deweyonline.com> To: ports@FreeBSD.org Subject: Re: FreeBSD ports: 1 unfetchable distfile: net/freenx Message-ID: <1170852844.45c9cbeca40a9@webmail.hyltown.com> In-Reply-To: <200702071001.l17A1J7f050947@freefall.freebsd.org> References: <200702071001.l17A1J7f050947@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Bill distfiles Fenner <fenner@FreeBSD.org>: > Dear freenx@deweyonline.com, > > You are listed as the FreeBSD port maintainer for 1 port > whose distfiles are not fetchable from their MASTER_SITES. Could > you please visit > > http://people.freebsd.org/~fenner/portsurvey/freenx@deweyonline.com.html > > and correct the problems listed there? The individual port with > a problem is net/freenx. > > If you have already corrected the problems and submitted a > PR, please accept my thanks and apologies for the delay in getting > the fixes into the tree. This reminder is created automatically > and does not (yet) have a way to know if a PR fixing the problem > has been submitted. Please do *NOT* send your response to me > directly; I do not necessarily have time to commit your fix; please > instead submit a PR via 'send-pr' so it doesn't get lost. > > Problems are usually of two types: > 1. The software package has been upgraded and the version in the > port has been removed. The best solution to this problem is to > upgrade the port to the most current version of the software package. > If you are a FreeBSD committer, then you can just upgrade the port > directly. If not, you should create the updated port on your own machine, > test it (and maybe even run "portlint" on it), and then use "send-pr" > to submit a "diff -uNr old-port updated-port". If you added or deleted > any files, please make an explicit note of it. > > 2. The mirror site being used no longer contains the software package > in question, or no longer exists. Solutions include: > a) If there are other mirror sites, just remove the bad site > from the list. (Make sure that what appears to be a bad site > isn't actually a problem of type 1, upgrade) > b) If the README or other support files in the software > documentation mention where to get the software package, > use one of those sites. > c) Use a search engine to find another place to get the original > DISTFILES. Make sure that you don't pick a FreeBSD distfiles > mirror -- if you can't find any other places where the file > exists, it can be a LOCAL_PORT or you can simply comment out > the MASTER_SITES= line, with a comment explaining why. > Once you have a solution, use "send-pr" to submit a "diff -u" of the > Makefile. > > Note that this isn't an urgent issue, as people who try to > build the port now will just fall back to the FreeBSD distfiles mirror. > Please just put it on your list to do and get to it when you have time. > These messages will continue to arrive twice a month until the fix is > committed, as a reminder. > > Thanks, > Bill "distfiles" Fenner. > the distfiles aren't available at any (stable) site as far as i can tell. in an effort to make this right, i looked into the "LOCAL_PORT" idea. i couldn't find it mentioned in the porter's handbook, and this is all i found in the current ports tree: lamp62# find . -type f -name Makefile -exec grep -iH local_port {} \; ./japanese/makejvf/Makefile:MASTER_SITE_SUBDIR= asami/LOCAL_PORTS ./japanese/tgif/Makefile:MASTER_SITES= http://home.jp.FreeBSD.org/~mita/LOCAL_PORTS/ ./sysutils/extipl/Makefile:MASTER_SITES= ftp://ports.jp.FreeBSD.org/pub/FreeBSD-jp/ports-jp/LOCAL_PORTS/ \ can you point me to documentation that describes "LOCAL_PORT" please? and if you're a committer, feel free to comment out the MASTER_SITES line as suggested above. otherwise, i'll eventually figure something out.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1170852844.45c9cbeca40a9>