jekillen wrote:
Hello;
I have a few questions about the port cyrus-imap23:
pkg_info produces a long list of software including a
lot of GUI related stuff. Does this mean that there
would be a GUI tool for administration of Cyrus Imap?
I did not see pam as one of the items in this list, but
I did
Hello;
I have a few questions about the port cyrus-imap23:
pkg_info produces a long list of software including a
lot of GUI related stuff. Does this mean that there
would be a GUI tool for administration of Cyrus Imap?
I did not see pam as one of the items in this list, but
I did see pam-mysql (af
On Nov 27, 2007, at 5:41 PM, Wes Morgan wrote:
On Tue, 27 Nov 2007, Clint Olsen wrote:
I've tried redirecting standard output/error, both /bin/sh and /
bin/csh,
and I can't run this in batch. I'm trying to build gnome which takes
hours, and I want it backgrounded so that if this SSH shell
On Tue, Nov 27, 2007 at 05:36:23PM -0800 I heard the voice of
Clint Olsen, and lo! it spake thus:
>
> I'm trying to build gnome which takes hours, and I want it
> backgrounded so that if this SSH shell disconnects it doesn't crater
> the build.
I've generally found screen(1) the better solution to
On Tue, 27 Nov 2007, Clint Olsen wrote:
I've tried redirecting standard output/error, both /bin/sh and /bin/csh,
and I can't run this in batch. I'm trying to build gnome which takes
hours, and I want it backgrounded so that if this SSH shell disconnects it
doesn't crater the build. You would t
I've tried redirecting standard output/error, both /bin/sh and /bin/csh,
and I can't run this in batch. I'm trying to build gnome which takes
hours, and I want it backgrounded so that if this SSH shell disconnects it
doesn't crater the build. You would think that --batch would make this
happen, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[EMAIL PROTECTED] wrote:
> I'm not 100% sure (and can't check right now), but there might be an
> option that you can (reasonably) safely set globally in /etc/make.conf to
> prefer apache 2.2, but I don't know what it is.
APACHE_PORT=www/apach
I believe there is an updater available to deal with this problem.
Will this port be updated or do we have to wait for the end of the portfreeze
in December??
Here is the output from my daily security report:
**
Checking for packages with security vulnerabilities:
Affected pac
Quoting Martin Wilke <[EMAIL PROTECTED]> (from Mon, 26 Nov 2007
23:40:58 +0100):
On Mon, Nov 26, 2007 at 08:15:59PM +0100, Pawe? P?kala wrote:
1) There are port options for OpenSSL and GnuTLS, those libraries
implement same thing - TLS & SSL protocols and claws-mail can be linked
only with
On Nov 27, 2007, at 4:18 AM, [EMAIL PROTECTED] wrote:
Thinking in retrospective - /etc/make.conf was perhaps not the best
place to put USE_APACHE=2.2 when I needed it only for php.
Sure it is a great place to set options...
Try something like this:
.if ${.CURDIR:M*/lang/erlang}
WITHOUT_ODB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
>
> Then, I execute this command:
> mount -t ntfs-3g -o ro /dev/ad6s10 /media/g
> but is also says:
> mount: /dev/ad6s10 : Operation not supported by device
>
> Is this a bug of mount?
I get exactly the same thing on -current AMD64.
>
> uname -a:
>
Hello!
I've already upgraded ntfs-3g to the latest version via ports.
ls /var/db/pkg | grep ntfs
fusefs-ntfs-1.1004
when I mount the partition using this command:
mount_ntfs-3g -o ro /mnt/ad6s10 /media/g
everything is OK.
but when I add these to fstab and mount by
mount /media/g
. It tells me:
> David Taylor wrote:
>> Do you have anything odd in your /etc/make.conf (e.g. USE_APACHE)
>
> This did it!
>
> I had USE_APACHE=2.2 in /etc/make.conf,
> because I think php was building with Apache
> 1.3 by default.
>
> Did not think this would confuse perl.
>
The problem is that you should never
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johan van Selst wrote:
> Aryeh M. Friedman wrote:
What is the current ETA on when the ports freeze will end?
>>> See the freebsd.org release pages
>> I know you will kill me for this but the URL?
>
> http://www.freebsd.org/releases/6.3R/schedule.h
Aryeh M. Friedman wrote:
> >> What is the current ETA on when the ports freeze will end?
> > See the freebsd.org release pages
> I know you will kill me for this but the URL?
http://www.freebsd.org/releases/6.3R/schedule.html
http://www.freebsd.org/releases/7.0R/schedule.html
"Ports tree unfrozen
So, I'm trying to get vncserver running, and it's dying on the 'fixed'
font. I should have all the pre-requisite ports installed. I've tried
fiddling with the -fp arguments in vncserver without success. Since this
is a port, I have higher expectations about having to modify files after
installin
Anton Berezin wrote:
> Right, so as I said - apxs could not be
invoked because there was no perl
> installed at that particular instant.
Right. Though this did not occur to me right
away.
>> Thinking in retrospective -
/etc/make.conf was perhaps not the best place
>> to put USE_APACHE=2.2 w
On Tue, Nov 27, 2007 at 10:18:07AM +0100, [EMAIL PROTECTED] wrote:
> Anton Berezin wrote:
>> Without knowing at what stage of the portupgrade process you got this
>> problem - just guessing - it might have confused bsd.port.mk when it
>> invoked
>> stuff in bsd.apache.mk (because of USE_APACHE sta
Anton Berezin wrote:
Without knowing at what stage of the portupgrade process you got this
problem - just guessing - it might have confused bsd.port.mk when it invoked
stuff in bsd.apache.mk (because of USE_APACHE statement) while the old perl
was deinstalled.
It happened when portupgrade tried
On Tue, Nov 27, 2007 at 09:52:23AM +0100, [EMAIL PROTECTED] wrote:
> David Taylor wrote:
>> Do you have anything odd in your /etc/make.conf (e.g. USE_APACHE)
>
> This did it!
>
> I had USE_APACHE=2.2 in /etc/make.conf, because I think php was building
> with Apache 1.3 by default.
>
> Did not t
Anton Berezin wrote:
The output of the following might help in debugging the problem.
uname -a
cat /etc/make.conf
perl -V
pkg_info
Yes, indeed, it was USE_APACHE=2.2 in
/etc/make.conf as David suggested.
Sorry, for not providing these outputs in the
beginning.
And thanks for your att
David Taylor wrote:
Do you have anything odd in your /etc/make.conf (e.g. USE_APACHE)
This did it!
I had USE_APACHE=2.2 in /etc/make.conf,
because I think php was building with Apache
1.3 by default.
Did not think this would confuse perl.
Thank you so much!
Iv
22 matches
Mail list logo
