Bug 159414
Summary: | something went wrong rebuilding the .src.rpm | ||
---|---|---|---|
Product: | [Retired] Fedora Infrastructure | Reporter: | Michael Schwendt <bugs.michael> |
Component: | extras buildsys | Assignee: | Seth Vidal <skvidal> |
Status: | CLOSED WONTFIX | QA Contact: | Jeremy Katz <katzj> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | paul, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-07-08 05:14:26 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: |
Description
Michael Schwendt
2005-06-02 14:55:44 UTC
1.2.5-4 failed to build the src.rpm again for ppc. :( I'm fed up with the buildsys for today. If you know why it failed again, please tell. Surprise, surprise! After ppc src.rpm build failure of 1.2.4-5, current 1.2.4-6 build request did succeed for ppc. Agreed, better error reporting is important. The build failures from today and yesterday for FC4 are related to the rawhide changes. I posted to -maintainers and -extras explaining what went on and how we resolved it. For the future I'll try to figure out better error reports. I've had two failed builds like this for bittorrent in devel today: See: http://extras64.linux.duke.edu/failed/development/bittorrent/ Same issue? Or is it different this time? Tried building bittorrent again today after seeing lots of successful builds in the extras build report. Same problem. That's the one thing I dislike about this error message. It is completely unclear whether the packager can do something to fix it. It hits you like a hammer on the head, and you sit there and feel helpless as you don't know the cause of it. well then it is fortunate we'll be getting rid of this error and the conditions that make it happen. There's not much point to leaving this bug open - that code is going away as the new code comes in this weekend. So I'm closing this as wontfix. |