Hi,
I'm trying to solve two errors associated with running KDE over
TightVNC. When I look at the log, I consistently see these errors. I've
tried to find answers on how to solve each of them and have not had
anything work at this point.
Thanks,
-Troy
QPainter::setCompositionMode: PorterDu
On Thu, 30 Apr 2009, matt donovan wrote:
On Thu, Apr 30, 2009 at 8:55 PM, Josh Rickmar wrote:
I just noticed that www/firefox-devel was still in the ports tree.
Looking at the Makefile, this port will install 3.0 alpha 2. Shouldn't
this port be deleted?
--
To send me a personal email, please
On Thu, Apr 30, 2009 at 8:55 PM, Josh Rickmar wrote:
> I just noticed that www/firefox-devel was still in the ports tree.
> Looking at the Makefile, this port will install 3.0 alpha 2. Shouldn't
> this port be deleted?
>
> --
> To send me a personal email, please place [personal] in the Subject l
I just noticed that www/firefox-devel was still in the ports tree.
Looking at the Makefile, this port will install 3.0 alpha 2. Shouldn't
this port be deleted?
--
To send me a personal email, please place [personal] in the Subject line.
___
freebsd-por
Zabbix_Server port maintainer,
Been having problems with zabbix_server startup after reboot. It was trying
to latch onto mysql too early before mysql was completely initialized. I've
found a workaround using the REQUIRE: and making mysql start first, and
putting many other services in the req
Ok, I`ll have a look at this through weekend...
Wesley Shields napsal(a):
On Thu, Apr 30, 2009 at 07:49:07PM +0200, Jan Sebosik wrote:
Hi all
why is in ports collection MaraDNS 1.2, if we have 1.3 out there for
some time?
This port is not maintained. If you would like to see it updated the
I have been unable to update e2fsprogs-libuuid on two systems. It has
updated fine on all of my other systems.
These systems stand out in that they are running FreeBSD V6. Is this
known to be a problem?
The build runs fine but 'make check' yields:
cd /usr/ports/misc/e2fsprogs-libuuid/work/e2fspr
On Thu, Apr 30, 2009 at 07:49:07PM +0200, Jan Sebosik wrote:
> Hi all
>
> why is in ports collection MaraDNS 1.2, if we have 1.3 out there for
> some time?
This port is not maintained. If you would like to see it updated the
best way is to update it yourself and submit it as a PR. It is also a
g
Hi all
why is in ports collection MaraDNS 1.2, if we have 1.3 out there for
some time?
Best regards, Jan
--
Jan Sebosik, Slovakia
sebo...@demax.sk
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To u
Hello,
The PR referenced in the subject is in maintainer timeout.
I don't mean to abuse this mechanism, but, as stated in teh PR
itself, the port at present is effectively broken.
A few people have contacted me via email telling me this update is
the only way to make it work and asked me to try
On Apr 29, 2009, at 22:43 , Ralf Wildenhues wrote:
So, where is autom4te-2.62, and why was it not installed alongside
autoconf-2.62?
Looks like a ports packaging issue to me.
No, it's a localized issue:
[...@foo:/usr/local/bin] 7% pkg_info -W autom4te-2.62
/usr/local/bin/autom4te-2.62 was in
11 matches
Mail list logo
