Re: sshguard dumping core on 9-STABLE

On Wed, 2 Jan 2013 20:27:46 +0200 Konstantin Belousov wrote: > On Wed, Jan 02, 2013 at 02:38:34PM +0200, Ion-Mihai Tetcu wrote: > > Hi, > > > > > > I'm seeing shhguard-ipfw sig 10 on start on my machines updated to > > 9-STABLE (eg. FreeBSD 9.1-STABLE #5 r244924: Tue Jan 1 19:45:55 > > EET 201

Re: FreeBSD Port: www/mod_security (ap22-mod_security-2.6.6)

On Tue, 18 Dec 2012, Marcelo Araujo wrote: ...and the 'portmaster' command finishes. Do you have any idea as to what is going on? I have never experienced anything simillar. Hello Martin, First of all, thank you so much by the report. I didn't see it before, looks pretty strange, I need to che

Updating "fetchmail"

"Fetchmail" was recently updated to version: "6.3.24". The port version is "6.3.22". The new version fixs some regressions and plug the OpenSSL memory leak. There is also a development version of 7.0.0 alpha available at . I was won

Re: What is policy about auto-editing config files on port install / deinstall?

Scot Hetzel wrote: > On Wed, Jan 2, 2013 at 2:37 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > > Is somewhere written policy or portmgr recommendation about ports behavior > > on install / deinstall? My impression is that every maintainer has her own undocumented policy although the approache

Re: update for DESKTOP_ENTRIES framework

On Wed, Jan 02, 2013 at 01:45:52PM +, Max Brazhnikov wrote: > Hi folks, > > I propose an update for DESKTOP_ENTRIES: > http://people.freebsd.org/~makc/patches/desktop_entry_20130102.diff > > Changes: > - update list of categories to the version 1.1 of Desktop Menu Specification > - require Ic

Updating "Bash"

Bash is currently at Bash-Release: 4.2, patch level 42. The port's version is only at patch level 37, which was released on 16-Jul-2012. This is an important port and since the freeze is over with, I was wondering if this port will be updated? -- Jerry ♔ Disclaimer: off-list followups get on-lis

Re: www/geneweb-5.02 Outdated, Won't Compile.

On Wed, Jan 02, 2013 at 08:32:14PM -0800, Jason Helfman wrote: > Thanks very much for filing the report, but it is possible that it hasn't > been worked on > at this point due to the patch not being attached properly. I would suggest > a follow-up > to the problem report you original had posted wit

Re: sshguard dumping core on 9-STABLE

On Thu, Jan 03, 2013 at 01:15:49PM +0200, Ion-Mihai Tetcu wrote: > On Wed, 2 Jan 2013 20:27:46 +0200 > Konstantin Belousov wrote: > > > On Wed, Jan 02, 2013 at 02:38:34PM +0200, Ion-Mihai Tetcu wrote: > > > Hi, > > > > > > > > > I'm seeing shhguard-ipfw sig 10 on start on my machines updated to

New version of PyGreSQL

Version 4.1 of PyGreSQL has just been released. I think the following will update your Makefile: Index: Makefile === --- Makefile(revision 309880) +++ Makefile(working copy) @@ -6,11 +6,10 @@ # PORTNAME= PyGreSQL -PO

Re: What is policy about auto-editing config files on port install / deinstall?

On 3 January 2013 12:12, Fabian Keil wrote: > Scot Hetzel wrote: > >> On Wed, Jan 2, 2013 at 2:37 PM, Miroslav Lachman <000.f...@quip.cz> wrote: >> > Is somewhere written policy or portmgr recommendation about ports behavior >> > on install / deinstall? > > My impression is that every maintainer

Re: FreeBSD Port: rubygem-chef-0.10.8_1

Le Wed, 2 Jan 2013 09:00:13 -0800, Jason Helfman a écrit : > > After updating all of the aforementioned ports, I was able to build > the update to chef to 0.10.2 successfully, and everything in the > dependency chain required without error. The only other item I may > recommend, is that we test c

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

Re: Updating "fetchmail"

On 2013-01-03, Jerry wrote: > "Fetchmail" was recently updated to version: "6.3.24". The port version > is "6.3.22". The new version fixs some regressions and plug the OpenSSL > memory leak. A patch was submitted to update to 6.3.24 on 01 Jan, which I've not yet had a chance to test and review

Re: Updating "fetchmail"

On Thu, 3 Jan 2013 09:04:30 -0600 Corey Halpin articulated: > On 2013-01-03, Jerry wrote: > > "Fetchmail" was recently updated to version: "6.3.24". The port > > version is "6.3.22". The new version fixs some regressions and plug > > the OpenSSL memory leak. > > A patch was submitted to update

Re: Updating "fetchmail"

Am 03.01.2013 16:37, schrieb Jerry: > Thanks for the feedback. When the 6.x branch is abandoned in favor of > the 7.x branch, which I tend to believe is not that far off, will you > then be creating a 7.x port? Whens, ifs and buts... 7.x is not ready for public consumption or production, there is

Re: Updating "fetchmail"

On 2013-01-03, Jerry wrote: > Thanks for the feedback. When the 6.x branch is abandoned in favor of > the 7.x branch, which I tend to believe is not that far off, will you > then be creating a 7.x port? When 7.x becomes the supported release, rather than a pre-release alpha, then mail/fetchmai

Re: Updating "fetchmail"

Am 03.01.2013 16:46, schrieb Corey Halpin: > On 2013-01-03, Jerry wrote: >> Thanks for the feedback. When the 6.x branch is abandoned in favor of >> the 7.x branch, which I tend to believe is not that far off, will you >> then be creating a 7.x port? > > When 7.x becomes the supported release,

Re: FreeBSD Port: rubygem-chef-0.10.8_1

On Thu, Jan 3, 2013 at 6:52 AM, Renaud Chaput wrote: > Le Wed, 2 Jan 2013 09:00:13 -0800, > Jason Helfman a écrit : > > > > After updating all of the aforementioned ports, I was able to build > > the update to chef to 0.10.2 successfully, and everything in the > > dependency chain required witho

Re: What is policy about auto-editing config files on port install / deinstall?

--On January 3, 2013 1:12:43 PM +0100 Fabian Keil wrote: Scot Hetzel wrote: On Wed, Jan 2, 2013 at 2:37 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > Is somewhere written policy or portmgr recommendation about ports > behavior on install / deinstall? My impression is that every maintai

Re: New version of PyGreSQL

Hello, D'Arcy J.M. Cain wrote on 03.01.2013 18:14: Version 4.1 of PyGreSQL has just been released. I think the following will update your Makefile: [...] The port was just updated, thank you for heads up. You may point your users here: http://www.freshports.org/databases/py-PyGreSQL for

Re: www/geneweb-5.02 Outdated, Won't Compile.

On Thu, Jan 03, 2013 at 08:00:34AM -0600, Alex Stangl wrote: > BTW, I notice now the download patch link from the PR seems to deliver a > corrupted file. It's not clear why that is, since I was able to > copy/paste the uuencoded text and uudecode it, and got the correct file. Further investigation

Re: New version of PyGreSQL

On Thu, 03 Jan 2013 21:50:01 +0400 Ruslan Makhmatkhanov wrote: > D'Arcy J.M. Cain wrote on 03.01.2013 18:14: > > Version 4.1 of PyGreSQL has just been released. I think the > > following will update your Makefile: > > The port was just updated, thank you for heads up. You may point your > users

Re: New version of PyGreSQL

D'Arcy J.M. Cain wrote on 03.01.2013 22:18: On Thu, 03 Jan 2013 21:50:01 +0400 Ruslan Makhmatkhanov wrote: D'Arcy J.M. Cain wrote on 03.01.2013 18:14: Version 4.1 of PyGreSQL has just been released. I think the following will update your Makefile: The port was just updated, thank you for he

Re: What is policy about auto-editing config files on port install / deinstall?

Scot Hetzel wrote: On Wed, Jan 2, 2013 at 2:37 PM, Miroslav Lachman<000.f...@quip.cz> wrote: Is somewhere written policy or portmgr recommendation about ports behavior on install / deinstall? I am talking about some ports doing "nasty" things. Some ports are stopping services on deinstall, som

Re: What is policy about auto-editing config files on port install / deinstall?

On 2013-01-03 22:49, Miroslav Lachman wrote: > Scot Hetzel wrote: >> On Wed, Jan 2, 2013 at 2:37 PM, Miroslav Lachman<000.f...@quip.cz> wrote: >>> Is somewhere written policy or portmgr recommendation about ports behavior >>> on install / deinstall? >>> I am talking about some ports doing "nasty"

RE: What is policy about auto-editing config files on port install / deinstall?

So, what is the general recommended policy on the network services ports in regard to /etc/rc.conf file ? If I install a port that creates a service "foodbank", then which choice is better: 1) "Automatically" edit /etc/rc.conf in the port installation script to include the line: foodban

Re: What is policy about auto-editing config files on port install / deinstall?

On 2013-01-03 23:14, Oleg Moskalenko wrote: > So, what is the general recommended policy on the network services ports in > regard to /etc/rc.conf file ? If I install a port that creates a service > "foodbank", then which choice is better: > > 1) "Automatically" edit /etc/rc.conf in the port ins

Re: What is policy about auto-editing config files on port install / deinstall?

On 03/01/2013 22:14, Oleg Moskalenko wrote: > So, what is the general recommended policy on the network services > ports in regard to /etc/rc.conf file ? If I install a port that > creates a service "foodbank", then which choice is better: > > 1) "Automatically" edit /etc/rc.conf in the port insta

Re: What is policy about auto-editing config files on port install / deinstall?

olli hauer wrote: The point is at the moment the port is uninstalled the port has no knowledge about the reason (uninstall permanent / reinstall / upgrade ) so the assumption is permanent. What I really don't get is users complaining about critical machines, special workflow and then thy do b

RE: 3. Updating "Bash" (Jerry)

>Message: 3 >Date: Thu, 3 Jan 2013 08:32:49 -0500 >From: Jerry >To: freebsd-ports@freebsd.org, obr...@freebsd.org >Subject: Updating "Bash" >Message-ID: <20130103083249.5708bb78@scorpio> >Content-Type: text/plain; charset=UTF-8 > >Bash is currently at Bash-Release: 4.2, patch level 42. The port's

Re: 3. Updating "Bash" (Jerry)

On Thu, Jan 3, 2013 at 4:16 PM, Michael Zoon wrote: > >Message: 3 > >Date: Thu, 3 Jan 2013 08:32:49 -0500 > >From: Jerry > >To: freebsd-ports@freebsd.org, obr...@freebsd.org > >Subject: Updating "Bash" > >Message-ID: <20130103083249.5708bb78@scorpio> > >Content-Type: text/plain; charset=UTF-8 >