Bug 511496
| Summary: | FTBFS 389-dsgw-1.1.3-1.fc12 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | FTBFS <ftbfs> | ||||||||
| Component: | 389-dsgw | Assignee: | Rich Megginson <rmeggins> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | rawhide | CC: | matt_domsch, nhosoi, nkinder, rmeggins, xjakub | ||||||||
| Target Milestone: | --- | Keywords: | screened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| URL: | http://linux.dell.com/files/fedora/FixBuildRequires/mock-results/ | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2009-07-17 16:16:50 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 511348 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
FTBFS
2009-07-15 03:07:03 UTC
Setting to ASSIGNED per Fedora Bug Triage workflow. https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow Created attachment 352139 [details]
root.log
root.log for x86_64
Created attachment 352140 [details]
build.log
build.log for x86_64
Created attachment 352141 [details]
mock.log
mock.log for x86_64
This looks like some sort of transient failure, not related to the package: Error Downloading Packages: gcc-4.4.0-12.x86_64: failure: Packages/gcc-4.4.0-12.x86_64.rpm from fedora: (256, 'No more mirrors to try.') What should I do with this bug? Mark it as CLOSED/TRYAGAIN later? I'm rebuilding all the failed packages; transient build failures will get flagged as no longer failing, and I'll close those bugs later today. This was a build system failure, not a package bug. I apologize. (In reply to comment #7) > This was a build system failure, not a package bug. I apologize. Matt, I just rebuilt this one -- we probably shouldn't close FTBFS bugreports until there is the build indeed present, otherwise we loose the ability to track them (IMO it's not important whether it is a package bug or a build system failure, we need to know and rebuild) :( I have actually some more thoughts about FTBFS bugs in relation with the mass rebuilds, I'll send them to you (and others) later. |