Date: Tue, 06 Mar 2007 18:02:03 +0900 From: gnn@FreeBSD.org To: ports@FreeBSD.org Cc: Tom McLaughlin <tmclaugh@FreeBSD.org>, Li-Wen Hsu <lwhsu@lwhsu.org> Subject: Re: FreeBSD ports: 1 unfetchable distfile: net/py-pypcap Message-ID: <m2mz2qrbhw.wl%gnn@neville-neil.com> In-Reply-To: <200702211000.l1LA0qVZ039693@freefall.freebsd.org> References: <200702211000.l1LA0qVZ039693@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At Wed, 21 Feb 2007 10:00:52 GMT, Bill "distfiles" Fenner wrote: > > Dear gnn@freebsd.org, > > 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/gnn@freebsd.org.html > > and correct the problems listed there? The individual port with > a problem is net/py-pypcap. > > 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. Hi, Sorry to respond to this automagic message, but hopefully someone is out there listening. The port should now point to my modified code. I believe both Li-Wen Hsu <lwhsu@lwhsu.org>, and Tom McLaughlin <tmclaugh@FreeBSD.org> have looked into this. I was away on a work trip for a couple of weeks so I have to update my ports and see what's what. At any rate the port should get the file from: http://downloads.sourceforge.net/pcs/py-pypcap-1.1.2.tar.gz?modtime=1169813864&big_mirror=0 or the appropriate Source Forge location. Best, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2mz2qrbhw.wl%gnn>