Bug 511584 - FTBFS 389-ds-base-1.2.1-1.fc12
Summary: FTBFS 389-ds-base-1.2.1-1.fc12
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: 389-ds-base
Version: rawhide
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Fedora Extras Quality Assurance
URL: http://linux.dell.com/files/fedora/Fi...
Whiteboard:
Depends On:
Blocks: F12FTBFS
TreeView+ depends on / blocked
 
Reported: 2009-07-15 03:27 UTC by FTBFS
Modified: 2011-04-25 23:27 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-17 16:16:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
root.log (406.03 KB, text/plain)
2009-07-15 03:27 UTC, FTBFS
no flags Details
build.log (21 bytes, text/plain)
2009-07-15 03:27 UTC, FTBFS
no flags Details
mock.log (325.15 KB, text/plain)
2009-07-15 03:27 UTC, FTBFS
no flags Details

Description FTBFS 2009-07-15 03:27:48 UTC
389-ds-base-1.2.1-1.fc12.src.rpm Failed To Build From Source against the rawhide tree.  See http://fedoraproject.org/wiki/FTBFS for more information.

Comment 1 FTBFS 2009-07-15 03:27:51 UTC
Setting to ASSIGNED per Fedora Bug Triage workflow.  https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow

Comment 2 FTBFS 2009-07-15 03:27:54 UTC
Created attachment 352603 [details]
root.log

root.log for x86_64

Comment 3 FTBFS 2009-07-15 03:27:55 UTC
Created attachment 352604 [details]
build.log

build.log for x86_64

Comment 4 FTBFS 2009-07-15 03:27:56 UTC
Created attachment 352605 [details]
mock.log

mock.log for x86_64

Comment 5 Rich Megginson 2009-07-15 14:33:42 UTC
This looks like some sort of mock/yum failure, not related to the package:

  File "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 1259, in _do_grab
    os.utime(self.filename, (modified_stamp, modified_stamp))
OSError: [Errno 2] No such file or directory: '/var/lib/mock/fedora-development-x86_64-389-ds-base-1.2.1-1.fc12.src.rpm/root/var/cache/yum/fedora/packages/binutils-2.19.51.0.11-23.fc12.x86_64.rpm'

What should I do with this bug?  Mark it as CLOSED/TRYAGAIN later?

Comment 6 Matt Domsch 2009-07-17 16:16:24 UTC
This was a build system failure, not a package bug.  I apologize.


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