Quoting Andrew Pantyukhin [EMAIL PROTECTED] (from Sun, 28 Jan
2007 21:58:28 +0300):
On 1/28/07, Alexander Leidinger [EMAIL PROTECTED] wrote:
Quoting Andrew Pantyukhin [EMAIL PROTECTED] (Sun, 28 Jan
2007 18:35:30 +0300):
I'm porting a simple util requiring aio(4). My plan is
to install a
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
On 1/29/07, Alexander Leidinger [EMAIL PROTECTED] wrote:
Quoting Andrew Pantyukhin [EMAIL PROTECTED] (from Sun, 28 Jan
2007 21:58:28 +0300):
On 1/28/07, Alexander Leidinger [EMAIL PROTECTED] wrote:
Quoting Andrew Pantyukhin [EMAIL PROTECTED] (Sun, 28 Jan
2007 18:35:30 +0300):
I'm porting a
Quoting Andrew Pantyukhin [EMAIL PROTECTED] (from Mon, 29 Jan
2007 14:53:41 +0300):
On 1/29/07, Alexander Leidinger [EMAIL PROTECTED] wrote:
I agree, but if you are interested in a general solution, how do you
want to apply it to the linux stuff?
See my original message.
grep /etc/rc.d
In response to George Hartzell [EMAIL PROTECTED]:
I'm curious how other freebsd postgresql users handle databases with
passwords and running the 502.pgsql periodic script.
I've solved the problem by creating a ~pgsql/.pgpass file with the
pgsql users password.
Is there a better way?
Filippo,
none of the source links can be accessed from a Unix server for this
port. I have downloaded directly plone 2.5.2.1 from plone.org, but it
isn't working. There are some changes necessary. Can you help me ?
This is what my event log says:
2007-01-29T20:22:09 WARNING Init Class
Hi,
I've just upgraded my squirrelmail port to 1.4.9a, and I believe there's a
problem with the upgrade. Perhaps it was caused by me not upgrading for
several months I missed a release.
In any event, it's no longer possible to log in to my Squirrelmail; the
login page gives the error
PHP Fatal
That's probably it. I did portupgrade the compatibility plugin, but
obviously that wasn't sufficient.
Thanks for your help,
Yours,
Mark
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Alexander Wittig
Sent: 29 January 2007 22:05
To: Mark
Cc:
Hello
I'm not sure if this is the source of your problem, but do you also have
mail/squirrelmail-compatibility-plugin installed?
If so, you have to reinstall it after you upgrade squirrelmail because
the compatibility plugin patches strings.php of the original
squirrelmail installation. If
In message [EMAIL PROTECTED], Jeremie Le
Hen wr
ites:
Hi Cy,
On Mon, Jan 29, 2007 at 08:04:09AM -0800, Cy Schubert wrote:
A couple of comments. Something like this should be integrated into the
base screen software. [EMAIL PROTECTED] or screen-users@gnu.org might be
a good place to
On Mon, Jan 29, 2007 at 09:23:52AM -0500, Bill Moran wrote:
In response to George Hartzell [EMAIL PROTECTED]:
I've solved the problem by creating a ~pgsql/.pgpass file with the
pgsql users password.
Is there a better way?
Depends. Do you allow untrusted users to log in to that
Hi I would like to be the maintainer of the following port:
fluxconf 0.9.9_1*
*Is there anything else I should do for that?
Thanks
Alfredo*
*
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On Mon, Jan 29, 2007 at 08:45:38PM -0500, Alfredo Perez wrote:
Hi I would like to be the maintainer of the following port:
You are now!
Please read the Porters Handbook at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
for all the nasty details on the ports system,
Edwin
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
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
16 matches
Mail list logo
