cyrus-sasl alternative?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello group, what alternative can I use insted of the port scheduled for deletion: portname: security/cyrus-sasl description:RFC SASL (Simple Authentication and Security Layer) maintainer: [EMAIL PROTECTED] deprecated because: patches are unfetchable and this software is unsupported expiration date:2007-01-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=cyrus-sasl I'm integrating it with postfix. Any tips and ideas please. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGEhe3zpU6eaWiiWgRAqprAJ4hUq4iBwgbY2iLMVkvX+TDXj6LKgCeJY6R vO5eTTeL54lIt2r/s4qbUj4= =CSah -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cyrus-sasl alternative?
On 4/3/07, Anton Blajev <[EMAIL PROTECTED]> wrote: Hello group, what alternative can I use insted of the port scheduled for deletion: portname: security/cyrus-sasl description:RFC SASL (Simple Authentication and Security Layer) maintainer: [EMAIL PROTECTED] deprecated because: patches are unfetchable and this software is unsupported expiration date:2007-01-02 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=cyrus-sasl I'm integrating it with postfix. Any tips and ideas please. Use cyrus-sasl2 instead. Regards, Rong-En Fan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: otrs-2.1.3_1 update to 2.1.6?
I've submitted a PR with an update: http://www.freebsd.org/cgi/query- pr.cgi?pr=79 Thanks Nick On Mar 31, 2007, at 11:42 PM, Thomas Schürmann wrote: Hello, From otrs.org 2007-03-05 OTRS 2.1.6 (Playa Esmeralda) is released! Can you make an update? greetings ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ports tree infrastructure
I am having trouble finding documentation that goes in more detail then that of the handbook. I am sending this message in hopes that you may be able to point me in the right direction, or know of a better way to accomplish this. I am setting up a single server as a 'build box' for our freebsd servers. We want to build our own packages because 1. we may need to compile certain ports with different flags then freebsd chooses. 2. We want to update ports only when needed. Ie: Unless we need something in a new version of a port, or unless there is a security hole, we want to keep the old version. What I'm setting up is a regular ports tree (/usr/ports) which is Not updated. Then a second tree /usr/local/current-ports which is updated daily with portsnap. When I want to upgrade a port, I would copy it over from the current ports tree. I'm not sure what to do about the INDEX files, which is what i had trouble finding documentation on. This looks like it is going to be a pain to maintain this. Are there any ports or scripts that pointy hat uses that could be helpful in my type of environment. Are there any better solutions? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: OPTIONS improvement
* Rong-En Fan ([EMAIL PROTECTED]) wrote: > After pav@'s commit to bsd.port.mk, now you can test WITH/WITHOUT > freely with OPTIONS. Also, when the set of OPTIONS is changed, users > will be prompted to the dialog again (thank you pav!). So good, thanks a lot pav! -- Best regards, Dmitry Marakasov mailto:[EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports tree infrastructure
Dan Casey píše v út 03. 04. 2007 v 11:42 -0400: > I am setting up a single server as a 'build box' for our freebsd > servers. We want to build our own packages because > 1. we may need to compile certain ports with different flags then > freebsd chooses. > 2. We want to update ports only when needed. Ie: Unless we need > something in a new version of a port, or unless there is a security > hole, we want to keep the old version. http://tinderbox.marcuscom.com/ ? > When I want to upgrade a port, I would copy it over from the current > ports tree. This will not work. You need to have a consistent ports tree. Just pulling a single new port and inserting it into old tree will not work. -- Pav Lucistnik <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Pilot to Co-Pilot: Boo. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Ports tree infrastructure
Quoting Pav Lucistnik <[EMAIL PROTECTED]> (Tue, 03 Apr 2007 19:04:25 +0200): > Dan Casey píše v út 03. 04. 2007 v 11:42 -0400: > > > I am setting up a single server as a 'build box' for our freebsd > > servers. We want to build our own packages because > > 1. we may need to compile certain ports with different flags then > > freebsd chooses. > > 2. We want to update ports only when needed. Ie: Unless we need > > something in a new version of a port, or unless there is a security > > hole, we want to keep the old version. > > http://tinderbox.marcuscom.com/ ? > > > When I want to upgrade a port, I would copy it over from the current > > ports tree. > > This will not work. You need to have a consistent ports tree. Just > pulling a single new port and inserting it into old tree will not work. Sounds a little bit harsh... I would say "It may or may not work. If it doesn't work don't complain here." as this will work if it is done right. But doing it right (handling the dependencies and the ports infrastructure bits) requires time/man power/following the commits. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports tree infrastructure
On Tue, 03 Apr 2007 11:42:20 -0400 Dan Casey <[EMAIL PROTECTED]> wrote: > I am having trouble finding documentation that goes in more detail > then that of the handbook. I am sending this message in hopes that > you may be able to point me in the right direction, or know of a > better way to accomplish this. > > I am setting up a single server as a 'build box' for our freebsd > servers. We want to build our own packages because > 1. we may need to compile certain ports with different flags then > freebsd chooses. > 2. We want to update ports only when needed. Ie: Unless we need > something in a new version of a port, or unless there is a security > hole, we want to keep the old version. > > What I'm setting up is a regular ports tree (/usr/ports) which is Not > updated. Then a second tree /usr/local/current-ports which is updated > daily with portsnap. > > When I want to upgrade a port, I would copy it over from the current > ports tree. I'm not sure what to do about the INDEX files, which is > what i had trouble finding documentation on. You can build your own with make index; or just ignore it, it's only used by a few minor targets and the tools in the portupgrade package. A more serious problem is that eventually a new port may not work in the old ports infrastructure. As far as security is concerned it's probably easier just to incorporate a patch into the old port - see the porters' handbook. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports tree infrastructure
Dan Casey wrote: > ... > > What I'm setting up is a regular ports tree (/usr/ports) which is Not > updated. Then a second tree /usr/local/current-ports which is updated > daily with portsnap. Packages make this kind of messing unnecessary. Having an up to date ports tree doesn't force you to update your ports. > ... > > This looks like it is going to be a pain to maintain this. Are there > any ports or scripts that pointy hat uses that could be helpful in my > type of environment. Are there any better solutions? The best solution would most likely be to build packages with tinderbox. This way you can keep your package repository up to date and only actually update the running software when this is wanted. Portaudit looks to me like a must have for your needs. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
link exchange
The Directory of Clubrural.com Tourism invites to you to interchange a connection if these interested beam click but down http://www.clubrural.com/links/ El Directorio de Turismo Clubrural.com te invita a intercambiar un enlace si estas interesado haz click mas abajo http://www.clubrural.com/links/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: postfix-2.3.8,1
postfix 2.4 is out, if you don't take a stab it, we might look at what it needs for freebsd ports next week sometime. if you have experimental patches in the mean time, feel free to send them to us to test. _ This email has been scanned and certified safe by SpammerTrap(tm). For Information please see http://www.spammertrap.com _ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: postfix-2.3.8,1
Michael Scheidell wrote: > postfix 2.4 is out, if you don't take a stab it, we might look at what > it needs for freebsd ports next week sometime. I'm working on that. Possible patch: http://people.freebsd.org/~mnag/postfix.patch Regards > > if you have experimental patches in the mean time, feel free to send > them to us to test. > > > _ > This email has been scanned and certified safe by SpammerTrap(tm). For > Information please see http://www.spammertrap.com > _ > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Marcus Alves Grando marcus(at)sbh.eng.br | Personal mnag(at)FreeBSD.org | FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: OPTIONS improvement
On 2007/04/03 14:12, Rong-En Fan wrote: > After pav@'s commit to bsd.port.mk, now you can test WITH/WITHOUT > freely with OPTIONS. I filed a PR ports/78343 with similar patch, but the PR was rejected. Why the policy has been changed? -- NIIMI Satoshi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: OPTIONS improvement
On Wed, Apr 04, 2007 at 07:52:57AM +0900, NIIMI Satoshi wrote: > On 2007/04/03 14:12, Rong-En Fan wrote: > > After pav@'s commit to bsd.port.mk, now you can test WITH/WITHOUT > > freely with OPTIONS. > > I filed a PR ports/78343 with similar patch, but the PR was rejected. > Why the policy has been changed? Different committer, different opinion I guess. Opinions change over time, too :) Kris pgpXcjFaxl8OR.pgp Description: PGP signature
Re: [EMAIL PROTECTED]: gnono-1.9.1_1 failed on amd64 7]
On 4/4/07, Kris Kennaway <[EMAIL PROTECTED]> wrote: === cc1: warnings being treated as errors In file included from /usr/local/include/libgnome-2.0/libgnome/gnome-program.h:41, from /usr/local/include/libgnome-2.0/libgnome/gnome-init.h:30, from /usr/local/include/libgnome-2.0/libgnome/gnome-config.h:34, from game.c:31: /usr/local/include/popt.h:444: warning: type qualifiers ignored on function return type gmake[3]: *** [game.o] Error 1 gmake[3]: Leaving directory `/work/a/ports/games/gnono/work/gnono-1.9.1/src' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/work/a/ports/games/gnono/work/gnono-1.9.1/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/work/a/ports/games/gnono/work/gnono-1.9.1' gmake: *** [all] Error 2 *** Error code 2 === popt has a few places like this: const char *const poptStrerror(const int error)... I see the samba project patched this: http://lists.samba.org/archive/samba-cvs/2006-May/067499.html Should we do the same? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: OPTIONS improvement
On 4/4/07, Kris Kennaway <[EMAIL PROTECTED]> wrote: On Wed, Apr 04, 2007 at 07:52:57AM +0900, NIIMI Satoshi wrote: > On 2007/04/03 14:12, Rong-En Fan wrote: > > After pav@'s commit to bsd.port.mk, now you can test WITH/WITHOUT > > freely with OPTIONS. > > I filed a PR ports/78343 with similar patch, but the PR was rejected. > Why the policy has been changed? Different committer, different opinion I guess. Opinions change over time, too :) Well, current implementation still has one flaw. If users specify WITH/WITHOUT in make.conf which conflicts with OPTIONS (/var/db/ports/somewhere), the result depends on how port's Makefile written. However, I think it's not how OPTIONS works. Regards, Rong-En Fan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
