On Apr 11, 2006, at 11:09 AM, Clark Williams wrote:
seth vidal wrote:
>> 3. what other patches need to go into mock before we release 0.5?
>> - the one's I know about but wouldn't mind a reference to are:
>> a. /dev/std* patch
>
> 1. the patch submitted to fix this is definitely in mock cvs
> 2. it is not entirely clear if this patch fixes the problem.
>
Well, it fixed it for me, but I wasn't the one that reported the
problem.
Can you verify that you can build that package properly under plague
(not just mock - it seems to work fine under mock, but not under
plague + mock)? Like I reported here,
https://bugzilla.redhat.com/
bugzilla/show_bug.cgi?id=179852#c18 I was still unable to build the
package under plague using the patch provided, although it did bomb
out with a new (and improved?) error message...
-Jeff