On 3/14/07, Nate Eldredge [EMAIL PROTECTED] wrote:
Hi all,
portsnap is a very nice way to keep your ports tree in sync, but it has
the disadvantage that it keeps your ports tree in sync :) If you make
local changes (e.g. adding a patch) they get clobbered. Does anyone know
of a convenient way
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we are attempting to notify maintainers 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
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we are attempting to notify maintainers of
ports that are marked as forbidden in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
Stefan Lambrev wrote:
After upgrade from openssh from 4.5 to 4.6 I'm unable to login using
password authentication.
Neither with RSA keys.
After putting PasswordAuthentication yes in sshd_conf I'm able to
login using username/password,
Idem.
but this is built-in password authentication
Dear porters,
This is just a reminder to please periodically check the list of
unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ .
A list by MAINTAINER is
http://people.freebsd.org/~fenner/errorlogs/
so you can easily check the status of ports that you maintain. In
addition, the
Dear maintainers (who uses/have used FORTRAN in your ports)
According to http://people.freebsd.org/~maho/gfortran/gfortran.html ,
gfortran migration is almost done. Except for ports/science/hdf,
and still there are some build issues. I'd like to move the status to
stabilize and wait for ~one
Stephen Montgomery-Smith wrote / napísal(a):
Are the different versions of tcl and tk really not backwards
compatible with earlier versions? I can guess that there have been
heated conversations about this, but a my look at the mailing list
archives didn't give me anything. But it sure
Hi,
I have installed vpopmail port where you are maintainer. I check
spamassassin patch, It works well but some e-mails aren't checked.
It looks that only physical mailboxess are checked but aliases not.
Is it possible? What may I change to test all e-mails?
Thank you
Radek
--
On Wednesday 14 March 2007 02:12, Scot Hetzel wrote:
On 3/14/07, Nate Eldredge [EMAIL PROTECTED] wrote:
Hi all,
portsnap is a very nice way to keep your ports tree in sync, but
it has the disadvantage that it keeps your ports tree in sync :)
If you make local changes (e.g. adding a
On Mar 13, 2007, at 10:47 PM, Kris Kennaway wrote:
On Tue, Mar 13, 2007 at 06:46:48PM -0700, Garrett Cooper wrote:
Begin forwarded message:
From: Stephen Montgomery-Smith [EMAIL PROTECTED]
Date: March 13, 2007 3:48:56 PM PDT
To: freebsd-ports@freebsd.org
Subject: Re: Why so many tcl's and
Bc. Radek Krejca ha scritto:
I have installed vpopmail port where you are maintainer. I check
spamassassin patch, It works well but some e-mails aren't checked.
It looks that only physical mailboxess are checked but aliases not.
Is it possible?
Yes and no. Only local Maildirs are
--On Tuesday, March 13, 2007 23:26:26 -0700 Nate Eldredge [EMAIL PROTECTED]
wrote:
Hi all,
portsnap is a very nice way to keep your ports tree in sync, but it has
the disadvantage that it keeps your ports tree in sync :) If you make
local changes (e.g. adding a patch) they get clobbered.
Hi,
AD Yes and no. Only local Maildirs are checked. Aliases normally point to
AD local Maildirs, so they are checked in any case at a later stage. If you
AD have a forward to a remote address, then no checking is done.
I don't think so or I have a problem. I have physical maildir darius
created
Bc. Radek Krejca ha scritto:
In .qmail-radek:krejca I have this
/usr/local/vpopmail/domains/2/starnet.cz/darius/Maildir/
You should modify your aliases to be forwards (as qmailadmin does).
So .qmail-radek:krejca should become:
[EMAIL PROTECTED]
--
Alex Dupre
First let me say I'm not a programmer, just a humble designer who happens to
know enough to make himself dangerous. Anyway, three things started
happening with my ports tree that make me unhappy. They may be unrelated,
but since I don't know i'll list all three.
this is all on freebsd 4.11
1) a
On Wednesday 14 March 2007 10:56, timmartin said:
First let me say I'm not a programmer, just a humble designer who
happens to know enough to make himself dangerous. Anyway, three
things started happening with my ports tree that make me unhappy.
They may be unrelated, but since I don't know
On Mar 14, 2007, at 11:56 AM, timmartin wrote:
this is all on freebsd 4.11
Please be aware that FreeBSD 4.11 is no longer supported-- the ports
framework has been updated in a fashion which is no longer backwards
compatible with that version of the OS, so you're going to be rolling
your
On Wed, Mar 14, 2007 at 07:26:25AM -0700, Garrett Cooper wrote:
Are the different versions of tcl and tk really not backwards
compatible with earlier versions?
No, they are not.
What a pity. So how come the various linux distributions seem to
get away with only one version of tcl and tk?
On Wed 14 Mar 2007 01:03, Kris Kennaway wrote:
On Tue, Mar 13, 2007 at 05:48:56PM -0500, Stephen Montgomery-Smith wrote:
Kris Kennaway wrote:
On Tue, Mar 13, 2007 at 04:09:26PM -0500, Stephen Montgomery-Smith wrote:
Are the different versions of tcl and tk really not backwards compatible
19 matches
Mail list logo
