On Tue, January 8, 2008 8:27 am, Aryeh M. Friedman wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Remko Lodder wrote:
>> [snip irrelevant info]
>>
>>> Where do I find acroread8?
>>
>> [snip irrelevant info]
>>
>> Sigh, you never -ever- learn do you?
>>
>> checkout www.freshports.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remko Lodder wrote:
> [snip irrelevant info]
>
>> Where do I find acroread8?
>
> [snip irrelevant info]
>
> Sigh, you never -ever- learn do you?
>
> checkout www.freshports.org for a real easy search option, or what
> I just
Never heard of freshports
slunky wrote:
> Will you please update this port to the latest version (I believe it is 0.32
> from the Warsow website) The version in ports is only 0.12, and it will not
> allow me to play online or over LAN without the latest version.
Giving it a go yourself would get the update done that much
"Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote
in <[EMAIL PROTECTED]>:
ar> Where do I find acroread8?
See http://www.freshports.org/print/acroread8/.
--
| Hiroki SATO
pgphR4ln4i3sY.pgp
Description: PGP signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hiroki Sato wrote:
> Hi all,
>
> If you are using Adobe Reader 8.1.1 with SCIM or UIM, please try
> the following and then run acroread8:
>
> # cd /usr/ports # fetch
> http://people.allbsd.org/~hrs/FreeBSD/imm-ports.tar.gz # tar xzvf
> imm-ports.tar.gz
Hi all,
If you are using Adobe Reader 8.1.1 with SCIM or UIM, please try the
following and then run acroread8:
# cd /usr/ports
# fetch http://people.allbsd.org/~hrs/FreeBSD/imm-ports.tar.gz
# tar xzvf imm-ports.tar.gz
# cd /usr/ports/textproc/linux-scim-libs && make install
# cd /usr/ports
Hey,
Just letting you know that nmap 4.52 is out, along with a new frontend.
I was wondering when you'll add it to the ports tree.
Thanks.
--
Regards,
Ghirai.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scot Hetzel wrote:
> I have noticed that sysutils/cfengine is using USE_BDB incorrectly.
>
> USE_BDB?= 46
>
> The USE_BDB variable is not a user setable variable. If someone were
> to read this Makefile, they would get the wrong impression that they
Nikola Lečić <[EMAIL PROTECTED]> wrote
in <[EMAIL PROTECTED]>:
ni> 1. Is the purpose of
ni>
ni> case ${ADOBE_LANG} in
ni> .
ni> JPN) : ${GTK_IM_MODULE:=xim}; export GTK_IM_MODULE ;;
ni>
ni>to override any other existing value?
This line does not override the existing v
On Sat, Jan 05, 2008 at 12:57:27PM -0800, Stephen Hurd wrote:
> Mark Linimon wrote:
> >On Wed, Jan 02, 2008 at 05:10:56PM -0600, Mark Linimon wrote:
> >
> >>Please see http://wiki.freebsd.org/Sparc64Packages for a writeup on where
> >>we are with respect to sparc64 packages, from portmgr's perspe
Will you please update this port to the latest version (I believe it is 0.32
from the Warsow website) The version in ports is only 0.12, and it will not
allow me to play online or over LAN without the latest version.
--
-Tony Chidester
___
freebsd-po
On Sat, 05 Jan 2008 15:00:27 +0900 (JST)
Hiroki Sato <[EMAIL PROTECTED]> wrote:
[...]
> - XIM does not work at least in japanese/acroread8 even if
> GTK_IM_MODULE=xim is defined. Since several Linux users around me
> pointed out this, this seems not FreeBSD-specific. I have heard
>
Vic,
On Mon, 7 Jan 2008, Vic Abell wrote:
VA> I'll let you know when I have something to test. As I said
VA> earlier, this will be a substantial modification. I will
VA> provide a pre-release distribution in the 4.79 series,
VA> probably an 'F' edition, that you can download and build.
Thank y
Dmitry,
You write:
>
> I'll more than happy to test on my machines with ZFS root -
> my home FreeBSD workstation has been configured with ZFS-on-root, and so
my
> notebook FreeBSD boot (it's triple-booted).
>
> Which info should I provide?
The important thing will be to make sure that lsof rep
On Mon, 7 Jan 2008, Vic Abell wrote:
VA> Larry,
VA>
VA> You write:
VA> >
VA> > On Sat, 5 Jan 2008, Dmitry Morozovsky wrote:
VA> > >
VA> > > The only additional thing I would like to bring attention
VA> > > at is the fact that
VA> > > ZFS can be used as root, requiring to additionally patch
VA>
Hi,
I intend to upgrade graphics/hugin from 0.6.1 to 0.7.b4.
The beta4 has been available for quite sometime.
It would be nice if you can test the attached patch - that's what I am
going to commit in the next few days, provided there are not any
problems reported. There may be some pkg-plist issu
On Mon, Jan 07, 2008 at 11:14:49AM -0800, Brian wrote:
> Pav Lucistnik wrote:
>> Cy Schubert pí?e v po 07. 01. 2008 v 09:15 -0800:
>>
>>
>>> Is there a documented or preferred approach to migrate ports from i386 to
>>> AMD64? Portupgrade has issues. Deleting and reinstalling 1954 ports by
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian wrote:
> Pav Lucistnik wrote:
>> Cy Schubert píše v po 07. 01. 2008 v 09:15 -0800:
>>
>>
>>> Is there a documented or preferred approach to migrate ports from
>>> i386 to AMD64? Portupgrade has issues. Deleting and reinstalling 1954
>>> ports b
Pav Lucistnik wrote:
Cy Schubert píše v po 07. 01. 2008 v 09:15 -0800:
Is there a documented or preferred approach to migrate ports from i386 to
AMD64? Portupgrade has issues. Deleting and reinstalling 1954 ports by hand
would be a monumental project. Any suggestions?
Reinstall from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pav Lucistnik wrote:
> Cy Schubert píše v po 07. 01. 2008 v 09:15 -0800:
>
>> Is there a documented or preferred approach to migrate ports from i386 to
>> AMD64? Portupgrade has issues. Deleting and reinstalling 1954 ports by hand
>> would be a monu
Cy Schubert píše v po 07. 01. 2008 v 09:15 -0800:
> Is there a documented or preferred approach to migrate ports from i386 to
> AMD64? Portupgrade has issues. Deleting and reinstalling 1954 ports by hand
> would be a monumental project. Any suggestions?
Reinstall from scratch.
--
Pav Lucistni
Is there a documented or preferred approach to migrate ports from i386 to
AMD64? Portupgrade has issues. Deleting and reinstalling 1954 ports by hand
would be a monumental project. Any suggestions?
--
Cheers,
Cy Schubert
<[EMAIL PROTECTED]>
___
fre
On Sat, Jan 05, 2008 at 12:57:27PM -0800, Stephen Hurd wrote:
> In debugging it though, it seems that gdb doesn't support thread debugging
> on sparc64 which is causing some problems... is this due to the lack of
> TLS?
Nope.
___
freebsd-ports@freebsd.
On Sat, Jan 05, 2008 at 07:08:57PM -0500, Derek Tattersall wrote:
> Patch 7.1.186 to vim-7.1 is dependent on changes made in patch 7.1.126.
> However, 7.1.126 will not apply cleanly to the tree in vim-7.1.tar.bz2,
> as the file gui_w48.c is not in that archive. Conversation on the
> vim-use list a
Larry,
You write:
>
> On Sat, 5 Jan 2008, Dmitry Morozovsky wrote:
> >
> > The only additional thing I would like to bring attention
> > at is the fact that
> > ZFS can be used as root, requiring to additionally patch
> > lsof like FreeSBIE people did for cd9660 root.
I'm not sure about that.
On Sat, 5 Jan 2008, Dmitry Morozovsky wrote:
On Sat, 5 Jan 2008, Wesley Shields wrote:
WS> > > can anyone sched me a light when lsof start supporting ZFS under
FreeBSD? I
WS> > > tried to quick hack configure, but did not have much success...
WS> > >
WS> > I actually talked to the author the o
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
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 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
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including experimental
development code and obsolete releases.
Bugs can be in one of several states:
o - open
A problem report has bee
32 matches
Mail list logo
