Bug 1372310 - "Failed to obtain srpm from dist-git" error
Summary: "Failed to obtain srpm from dist-git" error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Copr
Classification: Community
Component: backend
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-09-01 11:43 UTC by Tomas Smetana
Modified: 2016-09-01 12:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-01 12:07:52 UTC

Attachments (Terms of Use)
Sample log output (5.25 KB, text/plain)
2016-09-01 11:43 UTC, Tomas Smetana 		no flags Details
The "broken" spec file (12.13 KB, text/plain)
2016-09-01 12:01 UTC, Tomas Smetana 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Tomas Smetana 2016-09-01 11:43:33 UTC 
Created attachment 1196769 [details]
Sample log output

Firing up a build through API (using Jenkins COPR plugin) results in error like this one:
https://copr-be.cloud.fedoraproject.org/results/tsmetana/storaged/epel-7-x86_64/00448264-storaged/mockchain.log.gz:

Actually the error looks to be the same for all the branches. I have no idea what have I done wrong. I suspect this is a bug in COPR.
Comment 1 clime 2016-09-01 11:52:53 UTC 
There is also this error message:

"can't parse\n\nCould not execute srpm: Could not get n-v-r-e from '\\n\\n'"

Usually this suggest something might wrong with the spec file definition. Please, try to make sure the spec file is correct.
Comment 2 Tomas Smetana 2016-09-01 12:00:22 UTC 
Hm. That would be it. I have overlooked that part. And you're right, my SPEC file will not work the way I intended. However it's odd COPR can't parse it (there is just %if ... %else ... %endif construction around the Release tag).
Comment 3 Tomas Smetana 2016-09-01 12:01:34 UTC 
Created attachment 1196779 [details]
The "broken" spec file

Just for the record...
Comment 4 clime 2016-09-01 12:07:52 UTC 
Glad you solve it.
Comment 5 Tomas Smetana 2016-09-01 12:28:30 UTC 
(In reply to clime from comment #4)
> Glad you solve it.

I did. You did not. :) COPR still can't parse a valid SPEC file...
Note You need to log in before you can comment on or make changes to this bug.