Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 07 Nov 2020 21:44:28 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 250931] net/asteriskXX + blacklistd
Message-ID:  <bug-250931-7788-O6LCIDyFSG@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-250931-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-250931-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250931

Guido Falsi <madpilot@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |madpilot@FreeBSD.org
             Status|New                         |Open
           Assignee|ports-bugs@FreeBSD.org      |madpilot@FreeBSD.org

--- Comment #1 from Guido Falsi <madpilot@FreeBSD.org> ---
Hi,

I'm the maintainer of the asterisk port.

I noticed this bug report by change. Please put the origin of the port at t=
he
start of the object like "net/asterisk16", so the system can automatically
assign them. This gives them higher chance to be noticed.

Regarding your request, as far as I know there is no support for blacklistd=
 in
asterisk code. SO this would be a feature request for the upstream.

I'm unable to develop such a feature myself, but if it was available in
upstream code I'd have no problem adding to the port what is needed to make=
 it
work.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250931-7788-O6LCIDyFSG>