FreeBSD ports: 2 unfetchable distfiles: devel/freebase, irc/ircg

[alecn2002]

Hi Bill,

devel/freebase is a repocopy of devel/freeride and doesn't describe any own distfiles or distfile sources. So how it's possible that 

----------

freebase
cvs tree / pkg-descr 
URL from pkg-descr: http://freeride.rubyforge.org/wiki/wiki.pl ok 
File: freeride-0.9.6.tar.gz has 4 possible URLs: 0 OK, 4 bad, 0 skipped 
Port maintainer: alecn2002 at yandex.ru 
http://rubyforge.rubyuser.de/freebase/freeride-0.9.6.tar.gz: 404 Not Found (Last OK result NEVER [checked 10 times since Sat Aug 12 09:47:40 2006 UTC, last time was Sat Sep 2 18:48:55 2006 UTC]) 
http://rubyforge.iasi.roedu.net/files/freebase/freeride-0.9.6.tar.gz: 404 Not Found (Last OK result NEVER [checked 10 times since Fri Aug 11 10:28:39 2006 UTC, last time was Sat Sep 2 02:12:37 2006 UTC]) 
http://rubyforge.halostatue.info/freebase/freeride-0.9.6.tar.gz: 404 Not Found (Last OK result NEVER [checked 10 times since Sat Aug 12 17:13:27 2006 UTC, last time was Sun Sep 3 05:27:02 2006 UTC]) 
http://files.rubyforge.vm.bytemark.co.uk/freebase/freeride-0.9.6.tar.gz: 404 Not Found (Last OK result NEVER [checked 10 times since Fri Aug 11 23:15:59 2006 UTC, last time was Sat Sep 2 11:40:23 2006 UTC]) 
Summary 0 files fetchable out of 1 

-----------

freeride
cvs tree / pkg-descr 
URL from pkg-descr: http://freeride.rubyforge.org/wiki/wiki.pl ok 
File: freeride-0.9.6.tar.gz has 4 possible URLs: All OK! 
Summary 1 files fetchable out of 1

--------

?

Probably you've got some local network problems when tried to fetch from freebase, and they gone to the freeride time?


WBR,
Alexander Novitsky
freebase/freeride port maintainer

>Dear alecn2002 at yandex.ru,
>
>	You are listed as the FreeBSD port maintainer for 2 ports
>whose distfiles are not fetchable from their MASTER_SITES.  Could
>you please visit
>
>http://people.freebsd.org/~fenner/portsurvey/alecn2002@yandex.ru.html
>
>and correct the problems listed there?  The individual ports with
>problems are devel/freebase,irc/ircg.
>
>	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.