Hi,
I did a make deinstall/reinstall of horde4-base and to my surprise the
installation placed the web accessible files in
/usr/local/lib/php/pear/www/horde/
and they used to be in
/usr/local/www/horde
Is this intentional or did I mess anything up somewhere? I have no
special options set any
On Tue, 2011-11-15 at 17:55:57 +0100, Pav Lucistnik wrote:
> Jase Thew píše v út 15. 11. 2011 v 16:31 +:
>
> > What networking/DNS configuration is Pointyhat lacking (or have
> > sufficiently different to break the socket code inside of postconf)?
>
> It is a purposefully no-networking sand
Currently, 12. Plus 3 committed, 1 unsubmitted, 3~4 planning to port. The
total existing addons are listed here:
http://code.google.com/p/pure-lang/wiki/Addons
I probably not going to port all of them, but this list is growing.
On Tue, Nov 15, 2011 at 3:36 PM, Ion-Mihai Tetcu wrote:
> On Thu,
On Thu, 10 Nov 2011 13:02:38 -0600
Zhihao Yuan wrote:
> Hi,
>
> The PR which updates all pure-* ports was passed to portmgr for a long
> time, since it seem that to put a
>
> .if defined(USE_PURE)
> .include "${PORTSDIR}/Mk/bsd.pure.mk"
> .endif
>
> In bsd.port.mk may a be better choice. Thoug
15.11.2011 01:29, Raphael Kubo da Costa пишет:
> Thanks, I've just fixed this upstream and added my fix to area51
> (r7826). I'll commit it to ports as soon as I get an OK from avilla or
> makc.
Great, the port compiles now. Thanks!
> BTW, you were supposed to get a warning instead of an error to
On 15/11/2011 19:25, Chris Rees wrote:
> On 15 November 2011 19:19, Matthew Seaman
> wrote:
>> On 15/11/2011 19:01, Matthew Seaman wrote:
>>> On 11/11/2011 22:23, Doug Barton wrote:
> By its
>> nature, deprecated ports tends not to be updated for long time, port
>> tools like portmaste
On 15 November 2011 19:19, Matthew Seaman
wrote:
> On 15/11/2011 19:01, Matthew Seaman wrote:
>> On 11/11/2011 22:23, Doug Barton wrote:
By its
> nature, deprecated ports tends not to be updated for long time, port
> tools like portmaster, portupgrade will not even see it because no
>
On 15/11/2011 19:01, Matthew Seaman wrote:
> On 11/11/2011 22:23, Doug Barton wrote:
>>> By its
nature, deprecated ports tends not to be updated for long time, port
tools like portmaster, portupgrade will not even see it because no
PORTREVISION bump happen.
>
>> portmaster -L will w
On 11/11/2011 22:23, Doug Barton wrote:
>> By its
>> > nature, deprecated ports tends not to be updated for long time, port
>> > tools like portmaster, portupgrade will not even see it because no
>> > PORTREVISION bump happen.
> portmaster -L will warn you about ports marked
> DEPRECATED/FORBIDDEN
On Nov 15, 2011, at 11:55 AM, Pav Lucistnik wrote:
> Jase Thew píše v út 15. 11. 2011 v 16:31 +:
>
>> What networking/DNS configuration is Pointyhat lacking (or have
>> sufficiently different to break the socket code inside of postconf)?
>
> It is a purposefully no-networking sandbox jail.
on 15/11/2011 18:04 Chris Rees said the following:
> On 15 November 2011 14:34, Andriy Gapon wrote:
>>
>> Does anyone know good any alternative(s) for cpuburn?
>> If not, then I would like to request that this port be restored.
>> I am prepared to be designated as its maintainer and to host its di
on 15/11/2011 17:07 Baptiste Daroussin said the following:
> On Tue, Nov 15, 2011 at 04:34:22PM +0200, Andriy Gapon wrote:
>>
>> Does anyone know good any alternative(s) for cpuburn?
>> If not, then I would like to request that this port be restored.
>> I am prepared to be designated as its maintai
Quoth Daniel Nebdal on Tuesday, 15 November 2011:
> On Tue, Nov 15, 2011 at 12:00 PM, Matthew Seaman
> wrote:
> > On 15/11/2011 09:48, Matthias Apitz wrote:
> >> Since many years I'm fetching or updating /usr/ports with
> >>
> >> # cd /usr
> >> # setenv CVSROOT :pserver:anon...@anoncvs.fr.freebsd.
Jase Thew píše v út 15. 11. 2011 v 16:31 +:
> What networking/DNS configuration is Pointyhat lacking (or have
> sufficiently different to break the socket code inside of postconf)?
It is a purposefully no-networking sandbox jail. What networking
activity postconf wants to run?
--
--
Pav L
Synopsis: New port: www/cronolog
State-Changed-From-To: open->closed
State-Changed-By: miwi
State-Changed-When: Tue Nov 15 16:51:48 UTC 2011
State-Changed-Why:
close again was a mistake
http://www.freebsd.org/cgi/query-pr.cgi?pr=16254
___
freebsd-ports
On 15/11/2011 14:31, Sahil Tandon wrote:
It was marked broken on a particular architecture, hence the genesis of this
thread. I appreciate that diagnosis is difficult; perhaps Olli's suggestion is
helpful in isolating the issue. I do not know how else to troubleshoot since
these pointyhat er
Synopsis: New port: www/cronolog
State-Changed-From-To: closed->open
State-Changed-By: miwi
State-Changed-When: Tue Nov 15 16:26:29 UTC 2011
State-Changed-Why:
Maintainer has approved.
http://www.freebsd.org/cgi/query-pr.cgi?pr=16254
___
freebsd-ports@
On 15 November 2011 14:34, Andriy Gapon wrote:
>
> Does anyone know good any alternative(s) for cpuburn?
> If not, then I would like to request that this port be restored.
> I am prepared to be designated as its maintainer and to host its distfile
> (via my
> FreeBSD account).
>
> Maintaining the
On 15.11.2011 16:07, Baptiste Daroussin wrote:
On Tue, Nov 15, 2011 at 04:34:22PM +0200, Andriy Gapon wrote:
Does anyone know good any alternative(s) for cpuburn?
If not, then I would like to request that this port be restored.
I am prepared to be designated as its maintainer and to host its
d
On Tue, 15 Nov 2011 09:31:49 -0500
Sahil Tandon articulated:
> It was marked broken on a particular architecture, hence the genesis
> of this thread. I appreciate that diagnosis is difficult; perhaps
> Olli's suggestion is helpful in isolating the issue. I do not know
> how else to troubleshoot
On Tue, Nov 15, 2011 at 04:34:22PM +0200, Andriy Gapon wrote:
>
> Does anyone know good any alternative(s) for cpuburn?
> If not, then I would like to request that this port be restored.
> I am prepared to be designated as its maintainer and to host its distfile
> (via my
> FreeBSD account).
>
>
Does anyone know good any alternative(s) for cpuburn?
If not, then I would like to request that this port be restored.
I am prepared to be designated as its maintainer and to host its distfile (via
my
FreeBSD account).
Maintaining the port should be rather easy as it can not have any security
i
It was marked broken on a particular architecture, hence the genesis of this
thread. I appreciate that diagnosis is difficult; perhaps Olli's suggestion is
helpful in isolating the issue. I do not know how else to troubleshoot since
these pointyhat errors are not - AFAIK - reproducible by othe
On Tue, Nov 15, 2011 at 12:00 PM, Matthew Seaman
wrote:
> On 15/11/2011 09:48, Matthias Apitz wrote:
>> Since many years I'm fetching or updating /usr/ports with
>>
>> # cd /usr
>> # setenv CVSROOT :pserver:anon...@anoncvs.fr.freebsd.org:/home/ncvs
>> # cvs checkout ports
>>
>> and later do the up
On 2011-11-15 10:45, Pav Lucistnik wrote:
> 1) The problem is not amd64 specific
>
> 2) No point unmarking BROKEN, it currently fails on i386 pointyhat nodes
> too
>
> 3) Diagnosis is hard because the postfix-install shell script prints no
> useful progress messages
>
> Example failure log:
> ht
On 15/11/2011 09:48, Matthias Apitz wrote:
> Since many years I'm fetching or updating /usr/ports with
>
> # cd /usr
> # setenv CVSROOT :pserver:anon...@anoncvs.fr.freebsd.org:/home/ncvs
> # cvs checkout ports
>
> and later do the updating just with:
>
> # cd /usr/ports
> # cvs update
> # portup
1) The problem is not amd64 specific
2) No point unmarking BROKEN, it currently fails on i386 pointyhat nodes
too
3) Diagnosis is hard because the postfix-install shell script prints no
useful progress messages
Example failure log:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20
Hello,
Since many years I'm fetching or updating /usr/ports with
# cd /usr
# setenv CVSROOT :pserver:anon...@anoncvs.fr.freebsd.org:/home/ncvs
# cvs checkout ports
and later do the updating just with:
# cd /usr/ports
# cvs update
# portupgrade -ai
The FreeBSD handbook describes (or recommend
28 matches
Mail list logo
