ports/58500 submission got mangled
kosmos
abowhill at blarg.net
Tue Oct 28 14:06:11 PST 2003
I recently tried submitting a new port (ports/58500) using
send-pr on my home unix machine. However, since I didn't have
the correct MTA setup, Gnats would not accept the e-mail from
send-pr.
So, I forwarded the port .shar file in the body of a message
to freebsd-bugs at freebsd.org using MS outlook express. Someone
from the list (linimon) kindly created a PR for it.
Unfortunately, the forwarded message had extraneous characters
inserted by outlook express, and is probably corrupted.
So, after talking with a couple of people, I decided to configure
my unix machine's MTA to use it as my mail client (bastion host)
so it could talk to freebsd's mail servers properly.
Then I submitted a followup to the PR in an e-mail with a
clean copy of the .shar file attached, to bug-followup at freebsd.org.
However, the attachment got mangled evenn worse than the first
time.
What would be the correct thing to do at this point?
Should I send a simple e-mail to bug-followup at freebsd.org
for ports/58500 with the text: "This PR can be closed", then
resubmit the port with send-pr? I am pretty sure my MTA
is configured correctly to send a PR now (knock on wood).
Or, should I just submit another followup to ports/58500 but
uuencode the .shar file before attaching it?
I am not too sure what bug-followup at freebsd.org requires
in terms of e-mail format. Does it need the send-pr template?
Thanks for any help in advance.
--
Allan Bowhill
abowhill at blarg.net
Go placidly amid the noise and waste, and remember what value there may
be in owning a piece thereof.
-- National Lampoon, "Deteriorata"
More information about the freebsd-ports
mailing list