Help with getting movement on "anomalous" port
estrabd at gmail.com
Sat Feb 22 22:19:46 UTC 2014
As I've been told this is not a "first come first serve" sort of process,
but this is taking an inordinate amount of time. I am at this point
pleading that someone take this up.
I maintain 2 other ports, lang/qore and www/vee - am the author of the
latter - and have never had such issues as I am having with getting this
port looked at. Please some take a look at it.
On Fri, Feb 14, 2014 at 7:58 AM, Rodrigo Osorio <rodrigo at bebik.net> wrote:
> Thanks for your submition.
> Adding a little comment about what this port does (now I know is a bitcoin
> and why is it needed in the freebsd ports system usually helps a lot.
> - rodrigo
> On 14/02/14 07:41 -0600, B. Estrade wrote:
> > A couple of weeks ago I submitted a new port for net-p2p/feathercoin.
> > Shortly thereafter, it was marked as miscategorized so I resubmitted
> > thinking that this was the proper course of action.
> > (at the bottom of: http://portsmon.freebsd.org/portsanomalies.py)
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=186324
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=186493
> > It now seems that they are stuck in the queue since I have had another
> > maintainer-update (lang/qore) go through without any problems.
> > Please advise on the best way to make progress on this, either through
> > fixing something missing in the new port or getting it pushed through.
> > Thank you!
> > Brett
> > _______________________________________________
> > freebsd-ports at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
More information about the freebsd-ports