Re: ports/149686: new port: japanese/py-zinnia

Synopsis: new port: japanese/py-zinnia Responsible-Changed-From-To: freebsd-python-freebsd-ports Responsible-Changed-By: lwhsu Responsible-Changed-When: Sun Aug 22 12:47:24 UTC 2010 Responsible-Changed-Why: New port PR http://www.freebsd.org/cgi/query-pr.cgi?pr=149686

Re: ports/149689: new port: japanese/py-tegaki-gtk

Synopsis: new port: japanese/py-tegaki-gtk Responsible-Changed-From-To: freebsd-python-freebsd-ports Responsible-Changed-By: lwhsu Responsible-Changed-When: Sun Aug 22 12:47:37 UTC 2010 Responsible-Changed-Why: New port PR http://www.freebsd.org/cgi/query-pr.cgi?pr=149689

Re: ports/149688: new port: japanese/py-tegaki

Synopsis: new port: japanese/py-tegaki Responsible-Changed-From-To: freebsd-python-freebsd-ports Responsible-Changed-By: lwhsu Responsible-Changed-When: Sun Aug 22 12:47:31 UTC 2010 Responsible-Changed-Why: New port PR http://www.freebsd.org/cgi/query-pr.cgi?pr=149688

Re: ports/149686: new port: japanese/py-zinnia

Synopsis: new port: japanese/py-zinnia Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs Responsible-Changed-By: lwhsu Responsible-Changed-When: Sun Aug 22 18:38:05 UTC 2010 Responsible-Changed-Why: Should be freebsd-ports-bugs http://www.freebsd.org/cgi/query-pr.cgi?pr=149686

Re: ports/149689: new port: japanese/py-tegaki-gtk

Synopsis: new port: japanese/py-tegaki-gtk Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs Responsible-Changed-By: lwhsu Responsible-Changed-When: Sun Aug 22 18:38:24 UTC 2010 Responsible-Changed-Why: Should be freebsd-ports-bugs http://www.freebsd.org/cgi/query-pr.cgi?pr=149689

Re: ports/149688: new port: japanese/py-tegaki

Synopsis: new port: japanese/py-tegaki Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs Responsible-Changed-By: lwhsu Responsible-Changed-When: Sun Aug 22 18:38:30 UTC 2010 Responsible-Changed-Why: Should be freebsd-ports-bugs http://www.freebsd.org/cgi/query-pr.cgi?pr=149688

Re: net/asterisk16

On Sun, Aug 22, 2010 at 02:22:11AM -0500, Ade Lovett wrote: Given that the port has apparently been broken since early June, and that we have someone willing to take over , I'd say that this is a cast- iron case for a maintainer-timeout commit of the patch along with reassignment of the port.

drop maintainership from games/wesnoth{,-devel} to ports@

I kinda hate having to wait for a timeout instead of approval. If not timeouts then you're just too slow, committing an update just before next release. This makes window for players to report bugs about -devel release to upstream too narrow if not nonexistent. In hopes ports/149899 will be