On Sat, 2 Jun 2007 18:11:46 -0400
"Indigo 23" <[EMAIL PROTECTED]> wrote:
> After upgrading ports and subsequently upgrading to Gnome 2.18.2 from
> 2.18.1, gnome-terminal seems to have a problem where it just litters
> the window with various artifacts, I'm not sure if this is a
> gnome-terminal pr
On Sun, 03 Jun 2007 19:31:33 +0200
martinko <[EMAIL PROTECTED]> wrote:
> after reinstallation of my freebsd system (6.2-stable) i noticed the
> latest azureus (3.0.1.3_cvs) behaving erratically. also looking at its
> website it seems to me azureus is going to grow to accommodate new
> function
On 6/3/07, Ion-Mihai Tetcu <[EMAIL PROTECTED]> wrote:
The only thing I can think of for improving this part is to set the
default MySQL version in the port's OPTIONs to the one installed on the
system, if any and default to 50 if no MySQL is installed. Which will
further complicate an already lon
(Updated the otherwise highly misleading subject of only "sed
errors".)
in message <[EMAIL PROTECTED]>,
wrote Ivan Voras thusly...
>
> I've recently started getting these errors while running portupgrade:
>
> sed: 1: "s|^\(@comment[": unbalanced brackets ([])
> sed: 1: "s|^\(@comment[": unbalance
On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote:
> I was taking a look at why math/lapack fails to build on -CURRENT and
> discovered that the port uses ${FC} to find the FORTRAN compiler. I
> then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
> fort77). I don't this is
Hi!
I've recently started getting these errors while running portupgrade:
sed: 1: "s|^\(@comment[": unbalanced brackets ([])
sed: 1: "s|^\(@comment[": unbalanced brackets ([])
sed: 1: "s|^\(@comment[": unbalanced brackets ([])
sed: 1: "s|^\(@comment[": unbalanced brackets ([])
The above lines ar
On Fri, Jun 01, 2007 at 10:43:06AM -0400, Adam McDougall wrote:
> On Fri, Jun 01, 2007 at 02:15:48AM -0700, Ade Lovett wrote:
>
>
>On Jun 01, 2007, at 01:33 , Kris Kennaway wrote:
> > Download the packages from the FTP site and either reinstall them or
> > extract the +CONTENTS. This w
I was taking a look at why math/lapack fails to build on -CURRENT and
discovered that the port uses ${FC} to find the FORTRAN compiler. I
then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or
fort77). I don't this is appropriate since f77 has been removed from
-CURRENT.
I don't know
Marek Holly wrote:
> Hi,
>
> I am trying to build psi but I get following error:
There is a 0.11-RC1 available (http://forum.psi-im.org/thread/4447),
but it requires Qt4 and QCA2. We seem to have the former, but don't
seem to have the latter. Shaun, any interest in working this up?
Doug
--
On Jun 3, 2007, at 1:37 PM, Daniel Dvořák wrote:
Hi ler,
today I have decided to upgrade my ports and have checked /usr/
ports/UPDATING. There were nothing about lsof concretely in recently.
[snip]
See PR ports/113310 for an update.
The reason for the message was that Vic Abell (The lso
http://www.freebsd.org/cgi/ports.cgi?query=metamail
shows all the bells and whistles the mail processing utility metamail
now requires. Is there any way to avoid all those X stuff on a headless
mail server? Setting "USE_XLIB=no" didn't help.
Thanks!
Matt Grimes
__
On Sun, 3 Jun 2007, Sven Schellack wrote:
> just some observations that might help: I installed a new -CURRENT test
> system about 1.5 weeks ago and then built 7.2. drmOpenOnce and
> drmCloseOnce do belong to libdrm - see
> http://lists.freedesktop.org/archives/xorg-announce/2006-November/000175
+-Le 03/06/07 20:37 +0200, Daniel Dvořák a dit :
| Does it mean lsof is not suitable for FreeBSD 6.2 at all and is suitable
| only with FreeBSD 6.0-RELEASE.
No, it just means that lsof tries to use the best thing it knows about the
FreeBSD version you're running. In that case, 6.0 and all 6.X vers
i'll check my 6.2 system when I get back to Austin later tonight, and fix the
port.
Configing as 6.0 is probably ok for now as it compiles against the system
headers.
--
Larry Rosenman
(via mobile)
--- Original Message ---
From: Daniel Dvořák <[EMAIL PROTECTED]>
To: [EMAIL PROTECT
Hi ler,
today I have decided to upgrade my ports and have checked /usr/ports/UPDATING.
There were nothing about lsof concretely in recently.
When the process has begun, these messages appeared shortly:
=> Attempting to fetch from ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/NEW/.
lsof_4.79A.
On Sun, Jun 03, 2007 at 09:46:22PM +0400, Ruslan Ermilov wrote:
> Hi Kris,
>
> On Sun, Jun 03, 2007 at 01:03:53PM -0400, Kris Kennaway wrote:
> > On Sun, Jun 03, 2007 at 06:01:05PM +0400, Ruslan Ermilov wrote:
> > > Hi there,
> > >
> > > Anyone knows why the latest packages for 7-current/i386
> >
Hi Kris,
On Sun, Jun 03, 2007 at 01:03:53PM -0400, Kris Kennaway wrote:
> On Sun, Jun 03, 2007 at 06:01:05PM +0400, Ruslan Ermilov wrote:
> > Hi there,
> >
> > Anyone knows why the latest packages for 7-current/i386
> >
> > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-current/All/
> >
Hallo,
I've installed new X.org 7.2 on clean 6.2-STABLE system and everything
went fine except for the following package:
pkg_version: font-adobe-utopia-type1-1.0.1 does not appear to be a valid
package!
I tried to reinstall it but that didn't help (see below). also i could
not install so
hallo,
after reinstallation of my freebsd system (6.2-stable) i noticed the
latest azureus (3.0.1.3_cvs) behaving erratically. also looking at its
website it seems to me azureus is going to grow to accommodate new
functionalities which many users might not need.
therefore i wonder whether y
On Sun, Jun 03, 2007 at 06:01:05PM +0400, Ruslan Ermilov wrote:
> Hi there,
>
> Anyone knows why the latest packages for 7-current/i386
>
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-current/All/
>
> miss the xorg-7.2 package and some others, while according
> to pointyhat logs ther
Hi,
just some observations that might help: I installed a new -CURRENT test system
about 1.5 weeks ago and then built 7.2.
drmOpenOnce and drmCloseOnce do belong to libdrm - see
http://lists.freedesktop.org/archives/xorg-announce/2006-November/000175.html
I got the same error and recompiled lib
Hi there,
Anyone knows why the latest packages for 7-current/i386
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-current/All/
miss the xorg-7.2 package and some others, while according
to pointyhat logs there were no errors.
Cheers,
--
Ruslan Ermilov
[EMAIL PROTECTED]
FreeBSD committ
thank you all for your detailed help! I don't know how I ended up with
mysql-5.1, but it's all working now and I have a lot better understanding of
ports.
Cheers,
Klaus
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listi
I'm afraid I did not get a response to this problem, which is strictly
related to the X.org update and now I'm really stuck.
Could any of the experts look into my analysis below and advise how to
proceed?
Thanks,
Gerald
On Sun, 27 May 2007, Gerald Pfeifer wrote:
> After updating my test system
On Sun, 3 Jun 2007 12:33:52 +0200
Klaus Koch <[EMAIL PROTECTED]> wrote:
> > The error you're getting is not from the port or portinstall but
> > from the bsd.*.mk framework. You can't have multiple mysql versions
> > on your system.
> >
> > If you're sure you want mysql51 then upgrade the client,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Klaus Koch wrote:
> sorry for not making myself clear, but I _have_ mysql-client-5.1 installed.
> It's what freebsd installs by default if you're doing portinstall
> mysql-server/mysql-client.
Ummm... no it doesn't. The default version is mysql
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Klaus Koch wrote:
> sorry for not making myself clear, but I _have_ mysql-client-5.1 installed.
> It's what freebsd installs by default if you're doing portinstall
> mysql-server/mysql-client.
Ummm... no it doesn't. The default version is mysql
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Klaus Koch wrote:
> sorry for not making myself clear, but I _have_ mysql-client-5.1 installed.
> It's what freebsd installs by default if you're doing portinstall
> mysql-server/mysql-client.
Ummm... no it doesn't. The default version is mysql
> The error you're getting is not from the port or portinstall but from
> the bsd.*.mk framework. You can't have multiple mysql versions on your
> system.
>
> If you're sure you want mysql51 then upgrade the client, upgrade
> dependent ports then config and install dspam:
>
> portupgrade -f -o data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Make update is broken on my system. Due to the removal of PORTSNAP_UPDATE it
now complains about a missing PORTSSUPFILE (SUP_UPDATE is defined for updating
/usr/src) instead of using portsnap.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebs
On Sun, 3 Jun 2007 06:33:47 GMT
Erwin Lansing <[EMAIL PROTECTED]> wrote:
> INDEX build failed with errors:
> Generating INDEX-5 - please wait..routers2-extras-2.17_1:
> "/local0/tmp/erwin/tindex/ports/net/mrtg-ping-probe" non-existent --
> dependency list incomplete ===> net-mgmt/routers2-extras f
32 matches
Mail list logo
