The tarball should be put on the macports mirrors to avoid these
issues in the future. This is the third time I've seen this happen.
I contacted the dev the last time (March-ish), but they seem to have
not understood the problem...
On Jun 1, 2009, at 22:28, Jeremy Huddleston wrote:
The problem is that the old checksums are actually *correct* for the
version of the tarball that was there originally... upstream has the
bad habbit of "fixing" things without version bumping...
On Jun 1, 2009, at 22:17, Kristofer Henriksson wrote:
I attached a patch to ticket 19365 over a week ago to fix the bug it
indicates, but the ticket is still open. If someone with commit
privileges could apply it and close the ticket, I would be much
obliged.
Thanks,
Kris Henriksson
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
