Deluge, how to overcome this....?

Hi - I am having a problem with the deluge port.. I am seeing this issue: root@yeaguy:/var/db/ports/net-p2p_deluge # cd /usr/ports/net-p2p/deluge/ root@yeaguy:/usr/ports/net-p2p/deluge # make install ===> deluge-1.3.6_2,1 depends on package: py27-setuptools27>0 - not found pkg-static: No pac

Re: Deluge, how to overcome this....?

Hi, jcv wrote on 30.03.2014 10:14: Hi - I am having a problem with the deluge port.. I am seeing this issue: root@yeaguy:/var/db/ports/net-p2p_deluge # cd /usr/ports/net-p2p/deluge/ root@yeaguy:/usr/ports/net-p2p/deluge # make install ===> deluge-1.3.6_2,1 depends on package: py27-setuptools

Update of freeradius-2.2.3_1 to freeradius-2.2.4 fails

I am running 10.0-RELEASE and when trying to upgrade freeradius-2.2.3_1 to freeradius-2.2.4 after the latest update of the ports tree I obtain the following build error: ... libtool: link: cc -pthread -o .libs/rlm_dbm_parser .libs/rlm_dbm_parser.o -L/usr/local/lib /usr/ports/net/freeradius2/work/

[QAT] 349631: 4x leftovers

Support stage - Build ID: 20140330145200-64024 Job owner: b...@freebsd.org Buildtime: 18 minutes Enddate: Sun, 30 Mar 2014 15:10:29 GMT Revision: 349631 Repository:

Re: unmaintained, expired, but probably working ports

Le sam 29 mar 14 à 19:34:16 +0100, René Ladan écrivait : > > If someone is interested, I have a patch to upgrade tochnog, available > > at: > > > > > > It seems not too bad, but it does not build when the THREADing option is > > enabled. > Se

poudriere skips x11/gnome2 due to ports-mgmt/gnome-packagekit install error (too many docbook2man errors)

Attempting poudriere bulk build of x11/gnome2 fails due to prerequisite failure (ports-mgmt/gnome-packagekit). ports-mgmt/gnome-packagekit fails with "install" error after too many errors from docbook2man. This problem is also being reported by freebsd-pkg-fallout [REL - 10amd64-default][po

Re: Update of freeradius-2.2.3_1 to freeradius-2.2.4 fails

On 30 Mar 2014, at 16:43, Dr. Peter Voigt wrote: > I am running 10.0-RELEASE and when trying to upgrade > freeradius-2.2.3_1 to freeradius-2.2.4 after the latest update of the > ports tree I obtain the following build error: > > ... > libtool: link: cc -pthread > -o .libs/rlm_dbm_parser .libs/rlm

A child Postfix port with TLS enabled by default

Some people have asked for TLS to be enabled by default in mail/postfix. I have been reluctant in order to abide by POLA, and to be consistent with how Wietse distributes Postfix upstream. Recently, bz@ proposed an alternative: http://people.freebsd.org/~bz/20140228-01-postfix-tls.diff I update

Re: A child Postfix port with TLS enabled by default

On 2014-03-30 21:20, Sahil Tandon wrote: > Some people have asked for TLS to be enabled by default in mail/postfix. > I have been reluctant in order to abide by POLA, and to be consistent > with how Wietse distributes Postfix upstream. Recently, bz@ proposed an > alternative: > > http://people.f

Re: A child Postfix port with TLS enabled by default

On 2014-03-30 21:20, Sahil Tandon wrote: > Some people have asked for TLS to be enabled by default in mail/postfix. > I have been reluctant in order to abide by POLA, and to be consistent > with how Wietse distributes Postfix upstream. Recently, bz@ proposed an > alternative: > > http://people.f

Discover stored options different from port defaults/defines

Hello ports@, In the bad old days before poudriere and various improvements to OptionsNG came to town, when I was using portmaster* to handle upgrades, I cobbled together a configuration management practice that involved using rsync and git to store /var/db/ports in a repository. The usual workflo

Re: Update of freeradius-2.2.3_1 to freeradius-2.2.4 fails

On Sun, 30 Mar 2014, 16:43 +0200, Dr. Peter Voigt wrote: > I am running 10.0-RELEASE and when trying to upgrade > freeradius-2.2.3_1 to freeradius-2.2.4 after the latest update of the > ports tree I obtain the following build error: > > ... > libtool: link: cc -pthread > -o .libs/rlm_dbm_parser .l

Re: A child Postfix port with TLS enabled by default

On Sun, 2014-03-30 at 21:40:25 +0200, olli hauer wrote: > long time ago I shaped a patch for postfix-2.10 to support staging, > if required I can create a new patch for 2.11. Could you send a patch vs. mail/postfix? Don't be shy in annotating certain parts of the diff in case the rationale might

[QAT] 349679: 4x fail, 8x success

Update to cups to 1.7.1 - Stage all cups related ports - Cleanup (it still needs more cleanup) Base on [1] PR: ports/186824 [1] Submitted by: bsam - Build ID: 20140330211800-61783 Job owner: b.

Re: A child Postfix port with TLS enabled by default

On Sun, 2014-03-30 at 21:56:08 +0200, olli hauer wrote: > On 2014-03-30 21:20, Sahil Tandon wrote: > > Some people have asked for TLS to be enabled by default in mail/postfix. > > I have been reluctant in order to abide by POLA, and to be consistent > > with how Wietse distributes Postfix upstream

Re: A child Postfix port with TLS enabled by default

On 2014-03-30 23:35, Sahil Tandon wrote: > On Sun, 2014-03-30 at 21:40:25 +0200, olli hauer wrote: > >> long time ago I shaped a patch for postfix-2.10 to support staging, >> if required I can create a new patch for 2.11. > > Could you send a patch vs. mail/postfix? Don't be shy in annotating > c

cups update

Hi! I try to update: ===>>> The following actions will be taken if you choose to proceed: Upgrade cups-base-1.5.4_1 to cups-base-1.7.1 Upgrade cups-client-1.5.4_1 to cups-client-1.7.1 Upgrade cups-image-1.5.4_1 to cups-image-1.7.1 Upgrade py27-Jinja2-2.7.1_1 to py2

Re: Update of freeradius-2.2.3_1 to freeradius-2.2.4 fails

On 31/03/2014 5:38 AM, Dimitry Andric wrote: > On 30 Mar 2014, at 16:43, Dr. Peter Voigt wrote: >> I am running 10.0-RELEASE and when trying to upgrade >> freeradius-2.2.3_1 to freeradius-2.2.4 after the latest update of the >> ports tree I obtain the following build error: >> >> ... >> libtool:

Re: Discover stored options different from port defaults/defines

On Sun, 30 Mar 2014 17:13:15 -0400 "John W. O'Brien" wrote: > Hello ports@, > > In the bad old days before poudriere and various improvements to > OptionsNG came to town, when I was using portmaster* to handle upgrades, > I cobbled together a configuration management practice that involved > usi