Please confirm (conf#201ab215b2d995ca1cde406a4496467f)

Joerg Wunsch joerg at freebsd.org
Sun Jan 7 10:33:58 UTC 2007


<< IMPORTANT INFORMATION! >>

This is an automated message. 

The message you sent (attached below) requires confirmation
before it can be delivered. To confirm that you sent the
message below, just hit the "R"eply button and send this
message back (you don't need to edit anything). Once this is
done, no more confirmations will be necessary.

<< WICHTIGE INFORMATION >>

Dies ist eine automatisch generierte Antwort.

Ihre Mail (unten angehaengt) muss vor der Zustellung an mich
explizit bestaetigt werden.  Um dies zu tun, beantworten Sie
einfach diese Mail mit der "Antworten" oder "Reply"-Funktion
Ihres Mailprogramms. Es sind keine Aenderungen am Text
noetig. Dies ist die einzige Bestaetigung die Sie je an mich
senden muessen; Ihre weiteren Nachrichten werden automatisch
akzeptiert. Diese Massnahme dient der Bekaempfung von Spam.

This email account is protected by:
Active Spam Killer (ASK) V2.4.1 - (C) 2001-2002 by Marco Paganini
For more information visit http://www.paganini.net/ask

--- Original Message Follows ---

Date: Sun, 7 Jan 2007 10:03:48 GMT
From: fenner at freebsd.org (Bill "distfiles" Fenner)
To: joerg at freebsd.org
Subject: FreeBSD ports: 1 unfetchable distfile: devel/avr-gdb

Dear joerg at 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/joerg@freebsd.org.html

and correct the problems listed there?  The individual port with
a problem is devel/avr-gdb.

	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.

(Original message truncated)




More information about the freebsd-ports mailing list