SCIENTIFIC-LINUX-USERS Archives

December 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Fri, 16 Dec 2011 01:27:26 +0900
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
On 12/16/2011 01:12 AM, Akemi Yagi wrote:
> On Thu, Dec 15, 2011 at 6:50 AM, zxq9<[log in to unmask]>  wrote:
>> I've never had any problem with Mock before, and haven't seen a problem like
>> this for the last several years with it -- so I'm assuming this isn't
>> affecting others.
>>
>> Any insights would be greatly appreciated -- this has put passable test
>> builds for EPEL and some side projects like LibreCAD on hold for me, which
>> really chafes.
>
> Which version of mock is this?
>
> Akemi

Mock 1.1.18

But I got it working. The problem was dangling locks and a stale 
buildroot that needed to be scrubbed. Manually deleting the locks by 
itself didn't work 100%, but the fact that they were there to be found 
didn't make me happy. I have no idea how that ever got that way, but 
"mock --clean" and "mock --scrub=all" got me working again.

I sort of hate blanket commands like that; its too much like 
"reinstall/reboot" advice in Windows land and hides whatever the problem 
that got things screwy in the first place was. :-/

ATOM RSS1 RSS2