Hi,
I found that an ipv6 client's ipv6 address would show up wrong in the
logs and that the address could not be resolved. Access control also
did not work. On FreeBSD struct sockaddr is too small to hold an ipv6
address. With this patch everything seems to work... for me. :-)
--- socket.c.orig
Andrew Pantyukhin wrote:
On 1/30/07, Alagarsamy [EMAIL PROTECTED] wrote:
I want to know whether we are having REPLACES variable just
like CONFLICTS variable in the Makefile ?
I have two packages A and B. Package A is already installed.
I want to install package B which should automatically
On Jan 30, 2007, at 23:27 , Ade Lovett wrote:
In the true spirit of oh crap, let's fix this thing properly, I now
present to you:
http://www.lovett.com/ade/freebsd/gettext-2.diff
MD5 (gettext-2.diff) = 97d80b61281f6bc5aa88362a970b50a3
This significantly reworks the original 0.16.1
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the following error message:
%portupgrade -ai
--- Session started at: Wed, 31 Jan 2007 15:44:44 +
[missing key:
Hello,
this is to announce a first cut at an upgrading system more centered on
packages than portupgrade or portmaster, so i have called it pkgupgrade.
This is a python program, so not convenient for pytho-phobic people.
You can find it at:
http://www.lpthe.jussieu.fr/~talon/pkgupgrade
as well
Michael Fuhr writes:
[...]
The ident sameuser method causes the backend to ask the OS what
user is at the other end of the Unix socket. If the OS username
matches the database username then the connection is authenticated;
otherwise it's rejected. You can use pg_ident.conf to define
On 01/31/2007 09:48, Bartosz Fabianowski wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the following error message:
%portupgrade -ai
--- Session started
Ons 2007-01-31 klockan 11:29 -0600 skrev Eric Schuele:
On 01/31/2007 09:48, Bartosz Fabianowski wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the
On Wed, Jan 31, 2007 at 05:19:33PM +0100, Michel Talon wrote:
In my experience the Debian system is far more reliable than the
FreeBSD one, but such reliability will never be accessible to FreeBSD
as long as *all* ports are not available as packages.
I have also been working on the 'packages
Joel Dahl a écrit :
Ons 2007-01-31 klockan 11:29 -0600 skrev Eric Schuele:
On 01/31/2007 09:48, Bartosz Fabianowski wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running
Joel Dahl a écrit :
Ons 2007-01-31 klockan 11:29 -0600 skrev Eric Schuele:
On 01/31/2007 09:48, Bartosz Fabianowski wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running
I upgraded yesterday and today get the same sequence on 2 stable v6 boxen.
Building new INDEX files... done.
[Updating the portsdb format:bdb_btree in /usr/ports ... - 16411 port
entries found
So ... on the topic of large-scale FreeBSD deployment ...
How are people handling package version consistency in large groups of
servers? If you have a web farm with 10 hosts, plus 3 hosts in a QA
farm, and you want to make sure you're using the same version everywhere
and upgrading production
* Bartosz Fabianowski ([EMAIL PROTECTED]) wrote:
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the following error message:
%portupgrade -ai
--- Session started at:
Does anyone have a configuration trick or anything else to make
ZendOptimizer not sigfault. I have been using eaccelerator-0.9.5 and
it works fine but I have some compiled php5 code that I need to run
(opensrs).
Any suggestions greatly appreciated.
ed
I'm using:
6.2-STABLE FreeBSD
Hi
Portupgrade problems here as well.
Rico
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
On 1/31/07, Paul Chvostek [EMAIL PROTECTED] wrote:
So ... on the topic of large-scale FreeBSD deployment ...
How are people handling package version consistency in large groups of
servers? If you have a web farm with 10 hosts, plus 3 hosts in a QA
farm, and you want to make sure you're using
On 1/31/07, Bartosz Fabianowski [EMAIL PROTECTED] wrote:
Hi all
As part of the daily portupgrade run on my 6-STABLE box, I upgraded
sysutils/portupgrade to version 2.2.2_1,2 yesterday. Today, when I tried
running this version, I got the following error message:
%portupgrade -ai
--- Session
David Stanford wrote:
missing key: categories: Cannot read the portsdb!
Something broken in INDEX :(
--
Dixi.
Sem.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Eric Schuele wrote:
I'm seeing this as well. Though I had thought it was because my
`/usr/ports/make fetchindex` had failed.
Anyone else?
Me too, on two 6-Stable machines.
___
freebsd-ports@freebsd.org mailing list
On Wed, 31 Jan 2007 15:48:49 -0500 Paul Chvostek wrote:
How are people handling package version consistency in large groups of
servers? If you have a web farm with 10 hosts, plus 3 hosts in a QA
farm, and you want to make sure you're using the same version everywhere
and upgrading production
Thanks for the input. I have cleaned up the Makefile to make it as
portlint-happy as it's going to get, addressing the INSTALLS_SHLIB -
USE_LDCONFIG change, and also removed the removal of share/locale/eo,
since that is now present in the /etc/mtree/BSD.local.dist (it wasn't
at the
Same here... Out of the blue...
Removing old files and directories... done.
Extracting new files:
/usr/ports/audio/prokyon3/
/usr/ports/devel/cogito/
/usr/ports/net/ipw-firmware-kmod/
/usr/ports/net/iwi-firmware-kmod/
/usr/ports/textproc/xmlto/
The Prayer Webmail system has an unnecessary 8-character
limit on the length of user names. The limit appears
to only occur in the prayer login form, and changing
the limit there solves the problem. No problems appear
to be created by this change. I have included
a context diff appropriate as a
Since this is not particular to the FreeBSD port of the software, you
should submit this to the author of the software. The web page seems to be
http://www-uxsup.csx.cam.ac.uk/~dpc22/prayer/ .
mcl
___
freebsd-ports@freebsd.org mailing list
Something broken in INDEX :(
For the record: I am using p5-FreeBSD-Portindex-1.8 to build INDEX-6 and
have received a reply off list from somebody who has the same problems
with an INDEX-6 retrieved via make fetchindex. So, it's not just a
single broken INDEX-6 file on the server that needs
Hallo,
I get the same error on two machines too. Have someone a practical idea
http://dict.leo.org/ende?lp=endep=/gQPU.search=idea how to fix it.
Joachim
___
freebsd-ports@freebsd.org mailing list
As previously announced, FreeBSD 4.x has now reached its end of life
and is no longer supported in the ports collection (or by the security
officer for security fixes).
I have tagged the ports collection with the RELEASE_4_EOL tag to
provide a last known good tree as a convenience to those
Thanks for the quick response. I will forward my request.
-- Mikel
Mark Linimon wrote:
Since this is not particular to the FreeBSD port of the software, you
should submit this to the author of the software. The web page seems to be
http://www-uxsup.csx.cam.ac.uk/~dpc22/prayer/ .
mcl
2007. February 1. 00.34 dátummal Joachim Bethke ezt írta:
Hallo,
I get the same error on two machines too. Have someone a practical idea
http://dict.leo.org/ende?lp=endep=/gQPU.search=idea how to fix it.
Joachim
I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I think, and
Csaba Molnar wrote:
I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I think, and
that seems to have worked.
While I was updating ports before this error showed up, the options screen
for
portupgrade showed up - and option WITH_BDB4 was unchecked. I changed that
(so
I've just tried to reinstall the linphone port and see that it's
marked broken and deprecated. Does anybody know of an alternative
which supplies a command-line SIP client?
Greg
--
See complete headers for address and phone numbers.
pgpODw5K3adWJ.pgp
Description: PGP signature
On Wed, 31 Jan 2007 18:51:49 -0600, Kris Kennaway [EMAIL PROTECTED]
wrote:
As previously announced, FreeBSD 4.x has now reached its end of life
and is no longer supported in the ports collection (or by the security
officer for security fixes).
I have tagged the ports collection with the
Hello,
I am aware that the following port nwclient602 6.0.2_2 is forbidden, but I
was wondering do you have a back port available that one could obtain? I am
trying to maintain some systems on the network and keep one backup solution.
Thank you
---
Anthony
Hello,
I updated the port to current version 254
Patch attached.
Cheers,
Tyoma.
diff -ruN nss_ldap.port.251/Makefile nss_ldap.port.254/Makefile
--- nss_ldap.port.251/Makefile Thu Feb 1 10:46:59 2007
+++ nss_ldap.port.254/Makefile Thu Feb 1 11:00:24 2007
@@ -17,7 +17,7 @@
MAINTAINER= [EMAIL
On Wed, Jan 31, 2007 at 03:48:49PM -0500, Paul Chvostek wrote:
So ... on the topic of large-scale FreeBSD deployment ...
How are people handling package version consistency in large groups of
servers? If you have a web farm with 10 hosts, plus 3 hosts in a QA
farm, and you want to make sure
On 2007, Jan 31, at 18:45, Csaba Molnar wrote:
I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I
think, and
that seems to have worked.
While I was updating ports before this error showed up, the options
screen for
portupgrade showed up - and option WITH_BDB4 was unchecked. I
37 matches
Mail list logo