Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons

Doug Barton wrote: > >>>... Is it really absolutely necessary > >>>to stop a service before it's files go away? > > IMO the only time the ports infrastructure itself should do this > is if it isn't possible to pkg_delete the port cleanly if it's > running. For example, if there is

Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons

On Wed, Sep 15, 2010 at 12:19:43AM -0700, per...@pluto.rain.com wrote: > Doug Barton wrote: > > > >>>... Is it really absolutely necessary > > >>>to stop a service before it's files go away? > > > > IMO the only time the ports infrastructure itself should do this > > is if it isn'

Re: FreeBSD Port devel/pear

> After a fresh portsnap fetch & extract I get the following error: > > # cd /usr/ports/devel/pear > # make install clean > ===> Vulnerability check disabled, database not found > ===> License check disabled, port has not defined LICENSE > ===> Extracting for pear-1.9.1 > => MD5 Checksum OK for

Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons

On Tue, Sep 14, 2010 at 06:22:24PM -0700, Doug Barton wrote: [...] > I can think of at least one more scenario off the top of my head. You > want to run the new version of the service the next time the box is > restarted for whatever reason, but the update is not so critical that it > justifi

Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons

Quoth Greg Byshenk on Wednesday, 15 September 2010: > On Tue, Sep 14, 2010 at 06:22:24PM -0700, Doug Barton wrote: > > [...] > > > I can think of at least one more scenario off the top of my head. You > > want to run the new version of the service the next time the box is > > restarted for wha

Prova din relation

Hur het är er relation? Kylig som ett isberg eller het som en vulkan? Låt oss hjälpa dig. Vi ger dig svaret vilket kan förändra ditt liv! Skicka ett SMS med sökorden TXT LOVE NAMN+NAMN till nummer 72401 och ta reda på hur kompatibelt du är! Exempel på SMS: TXT LOVE ELIN+SVEN Efter du har skic

Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons

On Wed, 15 Sep 2010 08:15:56 -0700 Chip Camden articulated: > Please don't automatically stop/start anything that might be critical. > I've had enough of Windows' automatic reboots after automatic > upgrades, and I never want to go back. You do realize that, that is extremely easy to deactivate?

Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons

Quoth Jerry on Wednesday, 15 September 2010: > On Wed, 15 Sep 2010 08:15:56 -0700 > Chip Camden articulated: > > > Please don't automatically stop/start anything that might be critical. > > I've had enough of Windows' automatic reboots after automatic > > upgrades, and I never want to go back. >

Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons

On 9/15/2010 1:18 AM, Greg Byshenk wrote: On Tue, Sep 14, 2010 at 06:22:24PM -0700, Doug Barton wrote: [...] I can think of at least one more scenario off the top of my head. You want to run the new version of the service the next time the box is restarted for whatever reason, but the update i

autoconf267

My system: FreeBSD 8.0-RELEASE-p4 #0 I tried to update autoconf and I got: autconf-2.62: Makefile error: you cannot include bsd.port[.pre].mk twice Error 1 Thanks. Mitja http://starikarp.redbubble.com ___ freebsd-ports@freebsd.org mailing lis

RFC: db51 addition to bsd.database.mk

Greetings, any objections against my merging the attached patch to Mk/bsd.database.mk after databases/db51 has been repocopied from /db50 and committed? Thanks for your review & best regards Matthias ? Mk_bsd-database-mk.patch Index: bsd.database.mk ===

Re: autoconf267

ajtiM writes: > My system: FreeBSD 8.0-RELEASE-p4 #0 > > I tried to update autoconf and I got: > > autconf-2.62: Makefile error: > you cannot include bsd.port[.pre].mk twice > Error 1 Make sure your autoconf267/Makefile is at least r1.77. http://docs.freebsd.org/cgi/mid.cgi?201009152019.o8FKJ

autoconf update

Just out of curiosity, why a version bump because of a build dependency? I don't think an autoconf update should have an effect on any /running/ software but build systems. And I don't see how rebuilding all the software improves it. This is not a criticism - I just think there is something I don

Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons

Hi. On Wed, 15 Sep 2010 11:31:51 -0700 Doug Barton wrote: > >> I can think of at least one more scenario off the top of my head. You > >> want to run the new version of the service the next time the box is > >> restarted for whatever reason, but the update is not so critical that it > >> justifie

devel/autotools267 and UPDATING

-Rx autoconf-2.67 Information for autoconf-2.67: $ pkg_info -Rx autoconf-2.62 Information for autoconf-2.62: Required by: automake-1.10.3 automake-1.11.1 automake-1.4.6_6 automake-1.5_6,1 automake-1.6.3_2 automake-1.7.9_3 automake-1.8.5_4 automake-1.9.6_4 autotools-20100915 So it seems that al

Re: build error

On 9/14/2010 11:02 AM, Chip Camden wrote: > I see that the new pcpustat port has a build problem in batch mode: > > http://pointyhat.freebsd.org/errorlogs/amd64-8-latest/pcpustat-1.1.log > > This appears to be due to licensing. What would it take to get the OWL > (http://owl.apotheon.org) added

devel/autotools267 and UPDATING

About my previous mail, shouldn't the upgrade be handled by the entry in MOVED? Is it a portupgrade problem? Is the rebuild of ports like xmms or libX11 really necessary after a new version of autoconf? Thanks Barbara ___ freebsd-ports@freebsd.org ma

Re: devel/autotools267 and UPDATING

Hi, all-- On Sep 15, 2010, at 4:43 PM, Barbara wrote: > About my previous mail, shouldn't the upgrade be handled by the entry in > MOVED? Is it a portupgrade problem? > Is the rebuild of ports like xmms or libX11 really necessary after a new > version of autoconf? It looks like maybe a repocop

Re: build error

Quoth Philip M. Gollucci on Wednesday, 15 September 2010: > On 9/14/2010 11:02 AM, Chip Camden wrote: > > I see that the new pcpustat port has a build problem in batch mode: > > > > http://pointyhat.freebsd.org/errorlogs/amd64-8-latest/pcpustat-1.1.log > > > > This appears to be due to licensing.

devel/autotools267 and UPDATING

First of all, sorry about the error in subject (s/autotools/autoconf/). I've noticed the problem with the first commit on freshports, while running portsnap. So I run portsnap again till a new snapshot containing the new version were fetched. In fact I have: $ cat /usr/ports/devel/autoconf267/

Re: devel/autotools267 and UPDATING

> On Sep 15, 2010, at 4:43 PM, Barbara wrote: >> About my previous mail, shouldn't the upgrade be handled by the entry in >> MOVED? Is it a portupgrade problem? >> Is the rebuild of ports like xmms or libX11 really necessary after a new >> version of autoconf? With "sweeping" ports such as autot

Re: build error

Quoth Philip M. Gollucci on Wednesday, 15 September 2010: > On 9/14/2010 11:02 AM, Chip Camden wrote: > > I see that the new pcpustat port has a build problem in batch mode: > > > > http://pointyhat.freebsd.org/errorlogs/amd64-8-latest/pcpustat-1.1.log > > > > This appears to be due to licensing.

Re: devel/autotools267 and UPDATING

Hi, Ade-- On Sep 15, 2010, at 5:13 PM, Ade Lovett wrote: > On Sep 15, 2010, at 18:48 , Chuck Swiger wrote: >> It looks like maybe a repocopy is going on (or has gone wrong), since it is >> pointing to autoconf-2.62: > > You need to update your ports tree. Makefile is revision 1.77, not 1.75 as

www/openx vuln

This came in last night: http://blog.openx.org/09/security-update/ Port needs to be upgraded to 2.8.8 and a vuln entry created Sorry, bags not me. -- Dan Langille - http://langille.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.free

Re: www/openx vuln

16.09.2010 05:45, Dan Langille пишет: This came in last night: http://blog.openx.org/09/security-update/ Port needs to be upgraded to 2.8.8 and a vuln entry created Sorry, bags not me. Until update is not come up, user can apply this workaround: echo "RemoveType .php" > www/images/.htacc

FreeBSD Port: php5-gd-5.3.3_2

Hello, I am writing to request a change to the php5-gd port. This port requires that the gd extension include xpm support, which relies on a long dependency chain of x11 libraries. Since many PHP users run

new perl / perl-after-upgrade

After upgrading perl to 5.12.2_1 running perl-after-upgrade showed that no files will be moved. And that is a little wierd when there are a lot of files left in /usr/local/lib/perl5/5.12.1. Is that script working as expected? -- chs, ___ freebsd-ports@