Hello,
I want to install phpBB on my SRV.
I see the 3.0.6 is just released on 17 november.
Do you know when you upgrade the port ?
Regards,
David KINER
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
Hello,
I am trying to understand how to customize rc.d scripts to get the right
startup sequence for all daemons.
Seems we have (my case havp, but it is also the same problem for example
monit) :
/usr/local/etc/rc.d/havp :
# PROVIDE: havp
# REQUIRE: DAEMON cleanvar
# BEFORE: LOGIN
But in my co
On Fri, 20 Nov 2009 11:38:58 +0100
Xavier Beaudouin replied:
> Hello,
>
> I am trying to understand how to customize rc.d scripts to get the
> right startup sequence for all daemons.
>
> Seems we have (my case havp, but it is also the same problem for
> example monit) :
>
> /usr/local/etc/rc.d
Is it possible some how install this PHP extension (PHP5-OCI8) with
oracle_client on FBSD 7.2 AMD64?
===> oracle8-client-0.2.0_1 is only for i386, while you are running amd64.
*** Error code 1
Stop in /usr/ports/databases/oracle8-client.
*** Error code 1
I undestand that it's not
On Fri, Nov 20, 2009 at 11:38:58AM +0100, Xavier Beaudouin wrote:
> ...
> I am trying to understand how to customize rc.d scripts to get the right
> startup sequence for all daemons.
> ...
> But in my configuration, I need ... clamd to be started before havp.
>
> I have no garantee that clamd is
On Fri, 20 Nov 2009 13:52:39 +0200
"Noisex" wrote:
> Is it possible some how install this PHP extension (PHP5-OCI8) with
> oracle_client on FBSD 7.2 AMD64?
>
>
>
> ===> oracle8-client-0.2.0_1 is only for i386, while you are running amd64.
>
> *** Error code 1
>
>
>
> Stop in /usr/ports
On Fri, 20 Nov 2009 11:38:58 +0100
Xavier Beaudouin wrote:
> Hello,
>
> I am trying to understand how to customize rc.d scripts to get the
> right startup sequence for all daemons.
>
> Seems we have (my case havp, but it is also the same problem for
> example monit) :
>
> /usr/local/etc/rc.d/h
On Fri, Nov 20, 2009 at 04:47:41PM +, Anton Shterenlikht wrote:
> Is there a fbsd port of open64 (http://www.open64.net/),
> or any branched project?
>
> In particular there is a mention of ORC (http://ipf-orc.sourceforge.net/)
> specifically for ia64, but the pages are very out of date.
>
>
Is there a fbsd port of open64 (http://www.open64.net/),
or any branched project?
In particular there is a mention of ORC (http://ipf-orc.sourceforge.net/)
specifically for ia64, but the pages are very out of date.
And then there's something called Aurora, which seems to be the same
as ORC (http:
On Nov 20, 2009, at 8:47 AM, Anton Shterenlikht wrote:
> Is there a fbsd port of open64 (http://www.open64.net/),
> or any branched project?
Not at this time.
> In particular there is a mention of ORC (http://ipf-orc.sourceforge.net/)
> specifically for ia64, but the pages are very out of date.
On Nov 20, 2009, at 9:01 AM, Anton Shterenlikht wrote:
> On Fri, Nov 20, 2009 at 04:47:41PM +, Anton Shterenlikht wrote:
>> Is there a fbsd port of open64 (http://www.open64.net/),
>> or any branched project?
>>
>> In particular there is a mention of ORC (http://ipf-orc.sourceforge.net/)
>>
Claws Mail 3.7.3 was released on 09 October 2009. Usually when
claws-mail is updated, the new version appears in the ports tree within
a week. I was just wondering why there is an extended delay in
releasing this new version?
--
Jerry
ges...@yahoo.com
|===
|===
|===
|
Jerry,
There is PR to update of claws-mail. See:
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/139467
It will be committed soon.
Thanks,
Sylvio Cesar.
2009/11/20 Jerry :
> Claws Mail 3.7.3 was released on 09 October 2009. Usually when
> claws-mail is updated, the new version appears in the
Hi--
On Nov 20, 2009, at 1:07 PM, Sylvio Cesar wrote:
> There is PR to update of claws-mail. See:
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/139467
>
> It will be committed soon.
It's quite useful for people to try the patches for updates that they are
interested in, and report back whe
The Restless Daemon identified a PLIST error while trying to build:
pptpclient-1.7.2_4 maintained by po...@freebsd.org
Makefile ident: $FreeBSD: ports/net/pptpclient/Makefile,v 1.24 2009/11/20
21:49:25 lippe Exp $
Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/pptpclient-1.7.2_4.log :
RW wrote:
> On Fri, 20 Nov 2009 11:38:58 +0100
> Xavier Beaudouin wrote:
>
>> Hello,
>>
>> I am trying to understand how to customize rc.d scripts to get the
>> right startup sequence for all daemons.
>>
>> Seems we have (my case havp, but it is also the same problem for
>> example monit) :
>>
>>
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
22 matches
Mail list logo
