>Number: 171347
>Category: misc
>Synopsis: Filename conflict in subversion
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-requ
Synopsis: Updating www/rubygem-passenger gives error
State-Changed-From-To: open->closed
State-Changed-By: bdrewery
State-Changed-When: Wed Sep 5 16:00:13 UTC 2012
State-Changed-Why:
This has been fixed, update your ports tree and try again
http://www.freebsd.org/cgi/query-pr.cgi?pr=171335
_
>Number: 171354
>Category: misc
>Synopsis: Medium not present error on flash drive
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-
The following reply was made to PR bin/166293; it has been noted by GNATS.
From: Shane Ambler
To: bug-follo...@freebsd.org, free...@shaneware.biz
Cc:
Subject: Re: bin/166293: clang(1) regression from 9.0 to 9-STABLE
Date: Thu, 06 Sep 2012 05:53:24 +0930
This would appear to be fixed.
9.1-R
The following reply was made to PR kern/166262; it has been noted by GNATS.
From: Bill McGonigle
To: bug-follo...@freebsd.org, frankrep...@googlemail.com
Cc:
Subject: Re: kern/166262: [syscons] syscons issue on DN2800MT
Date: Wed, 05 Sep 2012 17:20:31 -0400
Seeing the same symptom - anybody h
Synopsis: clang(1) regression from 9.0 to 9-STABLE
State-Changed-From-To: open->closed
State-Changed-By: eadler
State-Changed-When: Wed Sep 5 21:32:27 UTC 2012
State-Changed-Why:
Per submitter request
http://www.freebsd.org/cgi/query-pr.cgi?pr=166293
_
>Number: 171360
>Category: kern
>Synopsis: [patch][dtrace] the fasttrap fork handler recurses on the
>child proc mutex
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
The following reply was made to PR bin/169642; it has been noted by GNATS.
From: Mark Johnston
To: bug-follo...@freebsd.org, sh...@fmepnet.org
Cc:
Subject: Re: bin/169642: rarpd(8) doesn't drop a PID file
Date: Wed, 5 Sep 2012 21:41:52 -0400
This has been fixed in r238282. I can provide a pat