Bug 1304957 - SRPM build fails for unknown reason
Summary: SRPM build fails for unknown reason
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Copr
Classification: Community
Component: frontend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: clime
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-05 04:35 UTC by Matt Spaulding
Modified: 2016-02-29 13:50 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-29 13:50:51 UTC
Embargoed:


Attachments (Terms of Use)
This is the SRPM package I am attempting to use for the build. (41.87 KB, application/x-rpm)
2016-02-05 04:37 UTC, Matt Spaulding
no flags Details

Description Matt Spaulding 2016-02-05 04:35:56 UTC
Description of problem: Package build is failing for an unknown reason.


Version-Release number of selected component (if applicable):


How reproducible: Every time


Steps to Reproduce:
1. Select to create a new build
2. Upload SRPM package
3. Run build

Actual results:

Build fails stating "Could not download the SRPM. Probably bad URL."


Expected results:

Build completes successfully


Additional info:
Other builds I have run work fine.  Only this particular SRPM is failing.  I am able to use it to build packages locally so I'm not sure why it would be failing in Copr.

Comment 1 Matt Spaulding 2016-02-05 04:37:02 UTC
Created attachment 1121280 [details]
This is the SRPM package I am attempting to use for the build.

Comment 2 clime 2016-02-05 13:49:47 UTC
Import into dist-git failed. I'll have a closer look at logs if I can find out what happened. I think it is not an always-reproducible kind of an error, so you can probly try again.

Comment 3 clime 2016-02-29 13:50:51 UTC
I can see you were successful the day after with build 158108. I had a brief look at the logs on 02-05 but I could only see that it was very likely a communication error when downloading the package. Let us know, if that happens again.


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