Sn Aug 2, 2007, at 05:20, Simon Ruderich wrote:
Ryan Schmidt wrote:
Reading portlivecheck.tcl, I see that if the homepage is not
available,
it already prints "cannot check if $portname was updated ($error)".
It already prints the regex if the regex does not match. I
suggested 2
weeks ago that the regex should always be printed, and since there
have
been no objections since then, I implemented that now (r27379).
This is all in debug mode only.
Thanks for this fix, I hope it makes it into the next release.
So do I.
Yes, I found the revision that broke it (r26041), Kevin Ballard
provided
a fix, and I tested and committed it (r27079).
Also thanks for this fix, but we should remember it means all the
portfiles will need to be updated after this fix when the next version
of macports is released.
Only portfiles whose livecheck regexen have been updated to work with
the "broken" livecheck code will again have to be updated to work
with the "fixed" code. Portfiles which were never initially modified
will work as usual again once 1.5.1 is released.
Trac is our bug tracking system, and the mailing list is our
discussion
system, so it seems to me that bugs are properly reported to Trac.
However, the reporter must remember to Cc the appropriate people,
otherwise nobody is notified of the ticket's existence. Also we don't
have a good system in place for ports that are unmaintained.
I'm not sure if this is mentioned in the documentation but it should
also be displayed on the "New ticket" page. So it's clear for the
reporter of the ticket to add this.
It is quite clearly mentioned in the TracTicketing wiki page.
If you find forgotten patches in Trac, and the ticket is not
assigned to
someone and the port has no maintainer, email the list with the
ticket
URL and someone can have a look at them and commit them. If the
ticket
is assigned to someone, email that person. If the port has a
maintainer,
email that person.
I just did some search in Trac and send the links for the tickes to
macports-dev. I also CCed the maintainers if the ports had one.
Thanks, I'll have a look at those.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
