mod_log_mysql ->
https://github.com/freebsd/freebsd-ports/blob/master/www/mod_log_sql
On Wed, Apr 11, 2018 at 12:52 PM, Łukasz Wąsikowski
wrote:
> W dniu 2018-04-11 o 20:29, Bernard Spil pisze:
>
> > You are all maintainer of a port that depends on www/apache22. The
> > Apache 2.2 port has been
W dniu 2018-04-11 o 20:29, Bernard Spil pisze:
> You are all maintainer of a port that depends on www/apache22. The
> Apache 2.2 port has been marked EXPIRED for almost a year. I was about
> to delete it but didn't want to go ahead without informing you. My
> analysis of the dependent ports can be
#winning!
On Sun, Apr 8, 2018 at 3:52 AM, Spil Oss wrote:
> There's been no-one wanting to keep Apache 2.2 that has come forward.
>
> Expect www/apache22 to be removed later in the week. Cleanup of
> Mk/Uses/apache.mk after that.
>
> 2018-03-30 17:37 GMT+02:00 Spil Oss :
> > Thanks Vincent! I wa
Hi All,
You are all maintainer of a port that depends on www/apache22. The
Apache 2.2 port has been marked EXPIRED for almost a year. I was about
to delete it but didn't want to go ahead without informing you. My
analysis of the dependent ports can be found in the FreeBSD wiki
https://wiki.freebsd
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
Am 10.04.18 um 21:59 schrieb Udit agarwal:
> Hi,
> I am trying to make uboot for beaglebone black using
> sysutils/u-boot-beaglebone port package, but getting the following error.
> How to resolve this? I tried with FORCE_PKG_REGISTER also, but no success.
>
> root@rtemsbuild1:/usr/ports/sysutils/
On Tue, Apr 10, 2018 at 07:59:10PM +, Udit agarwal wrote:
> Hi,
> I am trying to make uboot for beaglebone black using
> sysutils/u-boot-beaglebone port package, but getting the following error.
> How to resolve this? I tried with FORCE_PKG_REGISTER also, but no success.
>
> root@rtemsbuild1:/
