Date: Thu, 9 Dec 1999 18:50:11 -0500 From: Randall Hopper <aa8vb@ipass.net> To: ports@freebsd.org Subject: Getting commit priviledge to fix a port (was: FreeBSD ports: 1 unfetchable distfiles: graphics/py-opengl) Message-ID: <19991209185011.A4389@ipass.net>
next in thread | raw e-mail | index | archive | help
What's the procedure here?
On 11/7, I received an auto-mail about a broken port, requesting I fix it.
Roger Hardiman suggested I touch base with Satoshi.
I mailed Satoshi Asami <asami@FreeBSD.ORG> the same day asking how to become
a ports committer.
No response.
On 11/21, I received another auto-mail from fenner@freebsd.org
I mailed fenner and asked how to become a ports committer.
No response.
On 12/7, I get another auto-mail about this.
I checked the FAQ, and unless I missed something, "how to become a
committer" isn't there.
So, who knows who has the authority to grant commit priviledges (and
responds to e-mail ;-)
Or heck, if someone just wants to fix it, be my guest. The new distfile
path is:
http://starship.python.net/crew/da/PyOpenGL-1.5.5.tar.gz
Thanks,
Randall
----- Forwarded message from fenner@FreeBSD.org -----
From: fenner@FreeBSD.org
Date: Tue, 7 Dec 1999 10:00:04 -0800 (PST)
Subject: FreeBSD ports: 1 unfetchable distfiles: graphics/py-opengl
Dear aa8vb@ipass.net,
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://www.freebsd.org/~fenner/portsurvey/aa8vb@ipass.net.html
and correct the problems listed there? The individual port with
a problem is graphics/py-opengl.
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.
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 new port on your own system,
test it (and maybe even run "portlint" on it), and then use "send-pr"
to submit a "diff -uNr old-port new-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.
----- End forwarded message -----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991209185011.A4389>