David DEMELIER writes:
> Hi,
>
> I can't change the language in Wesnoth. They are shown but you can't
> click on (they are not-clickable).
>
> The messages files are installed : pkg_info -L wesnoth\*
>
> [...]
> /usr/local/share/locale/zh_TW/LC_MESSAGES/wesnoth-l.mo
> /usr/local/share/locale/zh_T
Can anyone confirm that subversion fails to build with www/neon28 and
requires www/neon29? This is not mentioned in UPDATING.
Running FreeBSD 7.3-REL.
Thanks,
Regards
Andrew
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
On Tue, Jul 6, 2010 at 9:06 AM, andrew clarke wrote:
> Can anyone confirm that subversion fails to build with www/neon28 and
> requires www/neon29? This is not mentioned in UPDATING.
I'm using neon28 and subversion without issues here, but I'm running CURRENT.
Thanks,
-Garrett
__
I recently upgraded to the new port version of virtualbox - 3.2.6. After
completing the upgrade, I'm seeing a massive amount of wcpu consumption (145%)
with virtualbox when I use the vm to rdp to a different windows box. As long
as I'm not using rdp, it works fine. When I first start the rdp,
On Tue, Jul 6, 2010 at 9:06 AM, andrew clarke wrote:
> Can anyone confirm that subversion fails to build with www/neon28 and
> requires www/neon29? This is not mentioned in UPDATING.
>
> Running FreeBSD 7.3-REL.
FreeBSD 7.3-RELEASE amd64, subversion-freebsd 1.6.9 installed with
neon28 0.28.6.
Fr
(CC'ing freebsd-ports@)
Christopher Key writes:
> Is there any equivalent to IA32_BINARY_PORT for linux binary
> distributions? I assume that at the moment, linux binary
> compatibility only exists on i386 and amd64, but I don't see any
> reason why this should always be the true, in which case
On Thu, Jun 3, 2010 at 9:00 PM, Torfinn Ingolfsen wrote:
> Hello,
>
> gscan2pdf 0.9.30 hangs when I am trying to save a document. Scanning works.
> When started from a shell, here is the output:
> gscan2pdf 0.9.30
> Startup LC_NUMERIC C
> [snapscan] Scanner warming up - waiting 15 seconds.
>
> (g
Does anyone else see this?
I have 2 (of 2) amd64 8.x systems which don't start MIMEDefang on reboot
properly, I get this..
Jul 7 06:34:58 cain mimedefang-multiplexor[1747]: Starting slave 3 (pid 41198)
(1 running): Bringing slaves up to minSlaves (2)
Jul 7 06:34:58 cain mimedefang-multiplexor[
On Wed, Jul 07, 2010 at 08:35:28AM +0930, Daniel O'Connor wrote:
> Does anyone else see this?
> I have 2 (of 2) amd64 8.x systems which don't start MIMEDefang on reboot
> properly, I get this..
>
> Jul 7 06:34:58 cain mimedefang-multiplexor[1747]: Starting slave 3 (pid
> 41198) (1 running): Bri
On 07/07/2010, at 12:12, Jeremy Chadwick wrote:
>> --- /usr/local/etc/rc.d/mimedefang.sh-dist 2010-04-07
>> 10:30:46.586067014 +0930
>> +++ /usr/local/etc/rc.d/mimedefang.sh 2010-05-01 13:47:47.340517685 +0930
>> @@ -316,7 +319,7 @@
>> rm -f $MX_SOCKET > /dev/null 2>&1
>> rm -f $SOCKET
A recent revision of lang/itcl has apparently broken
security/gorilla, which now pops up a window which says:
The Password Gorilla requires the
[incr Tcl] add-on to Tcl. Please install
the [incr Tcl] package.
I've tried reinstalling itcl and everything else tcl- and
tk-related, to no avail.
On Sat, Jul 03, 2010 at 12:45:49PM -0700, George Hartzell wrote:
> Emanuel Haupt writes:
> > George Hartzell wrote:
> > > Emanuel Haupt writes:
> > > > Hi
> > > >
> > > > The current audio/squeezeboxserver port is still broken for me. I
> > > > just built a package set with an up to dat
On Wed 2010-07-07 02:06:39 UTC+1000, andrew clarke (m...@ozzmosis.com) wrote:
> Can anyone confirm that subversion fails to build with www/neon28 and
> requires www/neon29? This is not mentioned in UPDATING.
Building subversion 1.6.11_3 with neon28-0.28.6_1 installed:
===> Configuring for subv
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
19 matches
Mail list logo
