From owner-freebsd-ports@FreeBSD.ORG Mon Mar 8 08:31:19 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ADCA16A4CE for ; Mon, 8 Mar 2004 08:31:19 -0800 (PST) Received: from mail.vineyard.net (k1.vineyard.net [204.17.195.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5650C43D31 for ; Mon, 8 Mar 2004 08:31:18 -0800 (PST) (envelope-from ericx@vineyard.net) Received: from localhost (loopback [127.0.0.1]) by mail.vineyard.net (Postfix) with ESMTP id 917A4933D1 for ; Mon, 8 Mar 2004 11:30:20 -0500 (EST) Received: from mail.vineyard.net ([127.0.0.1]) by localhost (king1.vineyard.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19233-10 for ; Mon, 8 Mar 2004 11:30:20 -0500 (EST) Received: from vineyard.net (loopback [127.0.0.1]) by mail.vineyard.net (Postfix) with ESMTP id C1C1F91DA6 for ; Mon, 8 Mar 2004 11:30:19 -0500 (EST) Message-ID: <404C9F35.9060805@vineyard.net> Date: Mon, 08 Mar 2004 11:28:37 -0500 From: "Eric W. Bates" User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ports@FreeBSD.Org References: <200403071802.i27I2owm072738@freefall.freebsd.org> In-Reply-To: <200403071802.i27I2owm072738@freefall.freebsd.org> X-Enigmail-Version: 0.83.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS at Vineyard.NET Subject: Re: FreeBSD ports: 1 unfetchable distfiles: mail/pop-before-smtp X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2004 16:31:19 -0000 I'm sorry to bother you. I'm trying to test/confirm the problem. The log you referred me to seems to indicate that all 4 URL were skipped (rather than failed); but there is no indication why they were skipped or whether that is something I can address. Of the 4 URL, 3 work fine (the fourth seems to timeout at the moment); but I suspect that is more a problem at sourceforge than something I can address? Thank you for your time. pop-before-smtp cvs tree / pkg-descr File: pop-before-smtp-1.33.tar.gz has 4 possible URLs: 0 OK, 0 bad, 4 skipped Port maintainer: ericx@vineyard.net http://heanet.dl.sourceforge.net/sourceforge/popbsmtp/pop-before-smtp-1.33.tar.gz: Not checked (Last actual result NEVER [checked 0 times since Wed Dec 31 16:00:00 1969 , last time was Wed Dec 31 16:00:00 1969 ]) http://aleron.dl.sourceforge.net/sourceforge/popbsmtp/pop-before-smtp-1.33.tar.gz: Not checked (Last actual result NEVER [checked 0 times since Wed Dec 31 16:00:00 1969 , last time was Wed Dec 31 16:00:00 1969 ]) http://unc.dl.sourceforge.net/sourceforge/popbsmtp/pop-before-smtp-1.33.tar.gz: Not checked (Last actual result NEVER [checked 0 times since Wed Dec 31 16:00:00 1969 , last time was Wed Dec 31 16:00:00 1969 ]) http://umn.dl.sourceforge.net/sourceforge/popbsmtp/pop-before-smtp-1.33.tar.gz: Not checked (Last actual result NEVER [checked 0 times since Wed Dec 31 16:00:00 1969 , last time was Wed Dec 31 16:00:00 1969 ]) Summary 0 files fetchable out of 1 Bill distfiles Fenner wrote: > Dear ericx@vineyard.net, > > You are listed as the FreeBSD port maintainer for 1 port > whose distfiles [or main web pages] are not fetchable from their > MASTER_SITES. Could you please visit > > http://people.freebsd.org/~fenner/portsurvey/ericx@vineyard.net.html > > and correct the problems listed there? The individual port with > a problem is mail/pop-before-smtp. > > Note that the main port web page, as listed in the WWW: line > of the pkg-descr, is checked just as though it was a port distfile. > This is an unfortunate side effect of the architecture of the distfile > survey reporting tool, but if you see a distfile being reported as > not fetchable that's not actually a distfile, see if it's from the > pkg-descr. > > 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 always 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 ftpsearch (http://ftpsearch.ntnu.no/ftpsearch) or other > search engines 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.