Re: kern/181132: [iwn] stream calculation is wrong for the Intel 4965

2013-08-07 Thread adrian
Synopsis: [iwn] stream calculation is wrong for the Intel 4965 Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: adrian Responsible-Changed-When: Thu Aug 8 05:51:05 UTC 2013 Responsible-Changed-Why: Changing to owner http://www.freebsd.org/cgi/query-pr.cgi?pr=1

kern/181132: [iwn] stream calculation is wrong for the Intel 4965

2013-08-07 Thread Adrian Chadd
>Number: 181132 >Category: kern >Synopsis: [iwn] stream calculation is wrong for the Intel 4965 >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class:

misc/181131: sys/dev/netmap memory allocation improvement

2013-08-07 Thread Alexander
>Number: 181131 >Category: misc >Synopsis: sys/dev/netmap memory allocation improvement >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class:

bin/181129: fnmatch doesn't translate "\\"

2013-08-07 Thread Garrett Cooper
>Number: 181129 >Category: bin >Synopsis: fnmatch doesn't translate "\\" >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submi

bin/181130: HN_DECIMAL failures with humanize_number

2013-08-07 Thread Garrett Cooper
>Number: 181130 >Category: bin >Synopsis: HN_DECIMAL failures with humanize_number >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-

kern/181127: [PATCH] set{domain, host}name doesn't permit NUL terminated strings that are MAXHOSTNAMELEN long

2013-08-07 Thread Garrett Cooper
>Number: 181127 >Category: kern >Synopsis: [PATCH] set{domain,host}name doesn't permit NUL terminated >strings that are MAXHOSTNAMELEN long >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter:

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Garrett Cooper
The following reply was made to PR conf/181116; it has been noted by GNATS. From: Garrett Cooper To: "Simon J. Gerraty" Cc: "freebsd-gnats-sub...@freebsd.org" , "freebsd-bugs@FreeBSD.org" Subject: Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Garrett Cooper
On Wed, Aug 7, 2013 at 1:32 PM, Simon J. Gerraty wrote: > > On Wed, 7 Aug 2013 11:24:15 -0700, Garrett Cooper writes: >>Ah, but src.conf controls WITH* (and the option is documented in the manage,= >> along with all the others). You accidentally broke POLA :(. > > The real issue is that the option

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
The following reply was made to PR conf/181116; it has been noted by GNATS. From: "Simon J. Gerraty" To: Garrett Cooper Cc: "freebsd-gnats-sub...@freebsd.org" , "freebsd-bugs@FreeBSD.org" Subject: Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
On Wed, 7 Aug 2013 11:24:15 -0700, Garrett Cooper writes: >Ah, but src.conf controls WITH* (and the option is documented in the manage,= > along with all the others). You accidentally broke POLA :(. The real issue is that the option handling needs an overhaul. The processing of options should be

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Garrett Cooper
The following reply was made to PR conf/181116; it has been noted by GNATS. From: Garrett Cooper To: "Simon J. Gerraty" Cc: "freebsd-gnats-sub...@freebsd.org" , "freebsd-bugs@FreeBSD.org" Subject: Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified Date: W

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
The following reply was made to PR conf/181116; it has been noted by GNATS. From: "Simon J. Gerraty" To: Garrett Cooper Cc: "freebsd-gnats-sub...@freebsd.org" , "freebsd-bugs@FreeBSD.org" Subject: Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
Also the synopsis is somewhat missleading. It only doesn't work when WITHOUT_BMAKE is specified in src.conf which src/Makefile does not honor - so would apply to any WITH[OUT]_ knob. But the larger question is why you are wanting to use fmake Thanks --sjg _

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Garrett Cooper
On Aug 7, 2013, at 10:51 AM, "Simon J. Gerraty" wrote: > > src/Makefile does not read bsd.own.mk so does not see src.conf > it does however see make.conf Ah, but src.conf controls WITH* (and the option is documented in the manage, along with all the others). You accidentally broke POLA :(. >

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
The following reply was made to PR conf/181116; it has been noted by GNATS. From: "Simon J. Gerraty" To: Garrett Cooper Cc: "freebsd-gnats-sub...@freebsd.org" , "freebsd-bugs@FreeBSD.org" Subject: Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
src/Makefile does not read bsd.own.mk so does not see src.conf it does however see make.conf More importantly, is this a "test" or is there a percieved need to continue building with fmake? If so why? I was aiming to get rid of WITH[OUT]_BMAKE soon - in time for 10.0 _

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Garrett Cooper
The following reply was made to PR conf/181116; it has been noted by GNATS. From: Garrett Cooper To: "freebsd-gnats-sub...@freebsd.org" , "freebsd-bugs@FreeBSD.org" Cc: "Simon J. Gerraty" Subject: Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified Date: W

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Garrett Cooper
FYI On Aug 7, 2013, at 4:50 PM, freebsd-gnats-sub...@freebsd.org wrote: > Thank you very much for your problem report. > It has the internal identification `conf/181116'. > The individual assigned to look at your > report is: freebsd-bugs. > > You can access the state of your problem report at

conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Garrett Cooper
>Number: 181116 >Category: conf >Synopsis: CURRENT build always uses bmake, even though WITHOUT_BMAKE is >specified >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >D

Re: bin/181090: zfs(1): "zfs list -r" and "zfs list -t all" doesn't show snapshots

2013-08-07 Thread Andriy Gapon
The following reply was made to PR bin/181090; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, littlesandr...@gmail.com Cc: Subject: Re: bin/181090: zfs(1): "zfs list -r" and "zfs list -t all" doesn't show snapshots Date: Wed, 07 Aug 2013 11:58:36 +0300 > Accordi

Re: bin/181090: zfs(1): "zfs list -r" and "zfs list -t all" doesn't show snapshots

2013-08-07 Thread avg
Synopsis: zfs(1): "zfs list -r" and "zfs list -t all" doesn't show snapshots State-Changed-From-To: open->closed State-Changed-By: avg State-Changed-When: Wed Aug 7 08:59:27 UTC 2013 State-Changed-Why: Pilot error. http://www.freebsd.org/cgi/query-pr.cgi?pr=181090 ___

Re: misc/181104: audio/mumble: dubious patch to allow OSS device selection

2013-08-07 Thread Natacha Porté
The following reply was made to PR misc/181104; it has been noted by GNATS. From: Natacha =?iso-8859-1?Q?Port=E9?= To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Cc: Subject: Re: misc/181104: audio/mumble: dubious patch to allow OSS device selection Date: Wed, 7 Aug 2013 10:43:

Re: misc/181104: audio/mumble: dubious patch to allow OSS device selection

2013-08-07 Thread Natacha Porté
Hello, on Wednesday 07 August 2013 at 08:10, freebsd-gnats-sub...@freebsd.org wrote: > >Category: misc The category is actually ports, I must have misclicked on the combobox. Sorry for the inconvenience /o\ ___ freebsd-bugs@freebsd.org mailing lis

misc/181106: logrotate bus error (core dumped)

2013-08-07 Thread Alexey
>Number: 181106 >Category: misc >Synopsis: logrotate bus error (core dumped) >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >S

misc/181104: audio/mumble: dubious patch to allow OSS device selection

2013-08-07 Thread Natacha Port�
>Number: 181104 >Category: misc >Synopsis: audio/mumble: dubious patch to allow OSS device selection >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >C