Bug 485146 - Mock build fails, koji builds succeeds
Summary: Mock build fails, koji builds succeeds
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mock
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F11Target
TreeView+ depends on / blocked
 
Reported: 2009-02-11 20:54 UTC by Nicolas Mailhot
Modified: 2013-01-10 05:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-12 18:37:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Mock logs (4.97 KB, application/x-bzip)
2009-02-11 20:55 UTC, Nicolas Mailhot
no flags Details

Description Nicolas Mailhot 2009-02-11 20:54:17 UTC
Description of problem:

Trying to build
http://www.auroralinux.org/people/spot/review/new/bpg-fonts-20090203-1.fc11.src.rpm

in mock fails (see attached logs)

Trying to scratch-build the same srpm in koji succeeds
http://koji.fedoraproject.org/koji/taskinfo?taskID=1120306

Clearly we are hitting some mock bug (probably because the font autoprovides include the names the font files declare, and those name have a & in them)

Version-Release number of selected component (if applicable):
mock-0.9.14-1.fc11.noarch

Comment 1 Nicolas Mailhot 2009-02-11 20:55:23 UTC
Created attachment 331619 [details]
Mock logs

Comment 2 Jesse Keating 2009-02-11 22:27:25 UTC
Don't suppose you have this in english?  Would be weird that it would be a mock bug, given that your mock is likely newer than what's on the builders.

Comment 3 Nicolas Mailhot 2009-02-12 18:37:15 UTC
Today everything builds so someone fixed his bug.

Good job :p

Comment 4 Jesse Keating 2009-02-12 18:56:07 UTC
That sounds more like the repodata you are using was different from what the buildsystem was using.  The static repos only update the symlink on the server once per hour, so there could have been a window in there.


Note You need to log in before you can comment on or make changes to this bug.