Re: Squid 2.6 issues

come! I am sorry that I cannot help you much myself regarding the abovementioned issues. I run 2.6.RC2 in a very lightly loaded environment without issues as of now. Best regards, -- Thomas-Martin Seck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: regression: port www/squid fails to build on ia64 head

* Johan Hendriks : (Squid breakage in the YP/NIS helper) > A long shot > Could it be that you have set the following in your src.conf > WITHOUT_NIS=yes > WITHOUT_RCMDS= yes > WITHOUT_RCS=yes > > If i set those i get a similar error with squid (on i386 and amd64 ) This is possible; the

Re: regression: port www/squid fails to build on ia64 head

* Anton Shterenlikht (me...@bristol.ac.uk): > On Sun, Dec 13, 2009 at 04:27:12PM -0000, Thomas-Martin Seck wrote: > > * Johan Hendriks : > > > > (Squid breakage in the YP/NIS helper) > > > > > A long shot > > > Could it be that you have set the

Re: correct location for third party /var files

* Dmitry Marakasov [gmane.os.freebsd.devel.ports]: > * Eitan Adler (eitanadlerl...@gmail.com) wrote: > >> Are third party tools supposed to use /usr/local/var or /var ? > > /var, absolutely. Everything that uses /usr/local/var or, even worse, > /usr/local/${PORTNAME} should be fixed. I beg to

Re: correct location for third party /var files

* Doug Barton (do...@freebsd.org): > On Wed, 17 Mar 2010, Thomas-Martin Seck wrote: > >When I started maintaining ports in 2004, the (or at least my) goal was > >to avoid absolute paths in pkg-plist like the plague, that is why I do > >not bother to use something /var/ca

Re: Latest squid update

* RW [gmane.os.freebsd.devel.ports]: > And grep found netdb_filename too. > > I don't see the point of this move. I can see a case for relocating the > files properly according to hier, and I can see a case for leaving it > where it is (/usr/local causes fewer hassles with partition > size). /va

Re: FreeBSD Port: squid-3.1.6

* Guido Falsi (m...@madpilot.net): > On Wed, Aug 11, 2010 at 12:54:07PM +0200, Dominique BERTHET wrote: > > Hi, > > I'm a sysadmin in a French School (Ecole des Mines de Saint-Etienne) > > I have 2 squid FreeBSD servers based with ntlm authentification > > I have upgrade squid from 5.1.x to 5.1.6

Re: FreeBSD Port: squid-3.1.6

- Thomas-Martin Seck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: squid-3.1.7

* Paul Gabriel (paul...@me.com): > Hi, I'm trying to run more than one instance of squid on a system. Due > to this, in the rc.conf I'm trying configure each instance to use a > different squid.conf file using > squid_conf="/usr/local/etc/squid/squid_wireless.conf". It appears that > this option i

Re: openoffice package requires libstdc++.so.6

* Garrett Cooper <[EMAIL PROTECTED]> [gmane.os.freebsd.devel.ports]: >> Jason C. Wells wrote: >>> The prebuilt package openoffice-2.3.1 requires libstdc++.so.6. >>> FreeBSD 6.3 has libstdc++.so.5. >>> I have always rolled my own and am unfamiliar with packages. This >>> particular package wo

Re: Squid

* Okalany Daniel <[EMAIL PROTECTED]>: > Trying to compile squid produces: tried to update kernel + ports + > portupgrade and still squid fails to compile.. This should be fixed in squid-2.6.20_2 (committed May 22). Does your ports tree include an older version? If so, please update and try again.

Re: FreeBSD Port: squid-2.6.20_2

* Isnard Jaquet ([EMAIL PROTECTED]): > as I understand you are responsable for the ports of squid in FreeBSD, > right? Well, I'd like to ask you when are you planning on releasing > version 2.7 of it. Any time soon? I have asked the person who originally wanted to maintain the 2.7 port for approv

Quick status update on Squid 3.x ports

names. Should we move www/squid to www/squid27 instead and make all Squid dependend ports that currently depend on www/squid use www/squid27 instead? Best regards -- Thomas-Martin Seck pgpVD4BZTTArF.pgp Description: PGP signature

Re: FreeBSD Port: squid-3.2.3_1, Please, include kerberos_ldap_group helper

* Pavel Bychykhin (pa...@hte.vl.net.ua): > Hi! > > It would be nice to include the kerberos_ldap_group helper in $external_acl > list. Done, see ports/173564 . Note that you need to select LDAP and SASL authentication, too for it to be enabled. Best regards, -- Thomas

Re: FreeBSD Port: squid-3.3

ative to 'transparent' or 'intercept' > connections when using IPV6. I'm working on it and hope to have it ready for commit when the ports tree is unfrozen again. Best regards, -- Thomas-Martin Seck ___ freebsd-ports@freebsd.

Re: FreeBSD Port: squid-3.2.3_1

. > *** [install] Error code 1 > > Stop in /usr/ports/www/squid32. Fixed, thanks for the report. Sorry for the breakage! Best, -- Thomas-Martin Seck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: SQUID Follow X-Forwarded-For headers

* Albert Thiel <[EMAIL PROTECTED]>: > There is a patch to Follow X-Forwarded-For headers to SQUID, but it is > not in the ports. The patch you refer to is probably the outdated patch for Squid <2.6, . You do not need that patch anymore, at leas

Re: Problems with +CONTENTS being messed up by pkg_delete -f

* Alexander Leidinger <[EMAIL PROTECTED]> [gmane.os.freebsd.devel.ports]: > Quoting Robert Noland <[EMAIL PROTECTED]> (Thu, 19 Jul 2007 13:31:42 -0400): > >> Ok, so the issue that I hope to address is not really a "portmanager" >> issue. The original version of package-depends always listed the

Re: Upgrading to squid-2.6.15 is not recommended.

* RW <[EMAIL PROTECTED]> [gmane.os.freebsd.devel.ports]: > The squid site is recommending that people skip 2.6.15 and go straight > to 2.6.16 The Squid maintainer can not resist to recommend that people look at what the FreeBSD port of Squid-2.6.STABLE15 actually delivers. :-) It should be safe

Odd segfault during Squid-2.6.16 compilation on CURRENT

[x-post to freebsd-current@ and freebsd-ports@, replies should probably go to freebsd-current only since I only observe this issue on 7-CURRENT] All, I am currently struggling with an odd issue that keeps me (or rather miwi@) from updating www/squid to 2.6.16: During the compilation process, Squ

Re: Odd segfault during Squid-2.6.16 compilation on CURRENT

I wrote: > [x-post to freebsd-current@ and freebsd-ports@, replies should probably > go to freebsd-current only since I only observe this issue on 7-CURRENT] > > All, > > I am currently struggling with an odd issue that keeps me (or rather > miwi@) from updating www/squid to 2.6.16: This issue

Re: ports/102499: lftp asc file checksum mismatch

* Kris Kennaway <[EMAIL PROTECTED]>: > The other option would be for the squid port to install a fixed > mime.conf. I'd love to, having been bitten by this myself (but only when fetching files from a FreeBSD ftpd IIRC). If there is consensus that the port should be fixed this way, hand me a patch