Date: Sun, 7 Mar 2004 10:08:15 -0800 (PST) From: fenner@freebsd.org (Bill "distfiles" Fenner) To: x11@freebsd.org Subject: FreeBSD ports: 25 unfetchable distfiles: x11-toolkits/libXaw,x11-toolkits/libXmu,x11/compositeext,x11/damageext,x11/fixesext,x11/libX11,x11/libXau,x11/libXcomposite,x11/libXcursor,x11/libXdamage,x11/libXdmcp,x11/libXext,x11/libXfixes,x11/libXfont,x11/libXi,x11/libXpm,x11/libXrandr,x11/libXrender,x11/libXres,x11/libXtrans,x11/libXv,x11/renderext,x11/resourceext,x11/xextensions,x11/xproto Message-ID: <200403071808.i27I8Fsb078516@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
Dear x11@freebsd.org, You are listed as the FreeBSD port maintainer for 25 ports whose distfiles [or main web pages] are not fetchable from their MASTER_SITES. Could you please visit http://people.freebsd.org/~fenner/portsurvey/x11@freebsd.org.html and correct the problems listed there? The individual ports with problems are x11-toolkits/libXaw,x11-toolkits/libXmu,x11/compositeext,x11/damageext,x11/fixesext,x11/libX11,x11/libXau,x11/libXcomposite,x11/libXcursor,x11/libXdamage,x11/libXdmcp,x11/libXext,x11/libXfixes,x11/libXfont,x11/libXi,x11/libXpm,x11/libXrandr,x11/libXrender,x11/libXres,x11/libXtrans,x11/libXv,x11/renderext,x11/resourceext,x11/xextensions,x11/xproto. 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403071808.i27I8Fsb078516>