Bug 1278532 - COPR: All builds fail to get srcrpm from dist-git
Summary: COPR: All builds fail to get srcrpm from dist-git
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Copr
Classification: Community
Component: backend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-05 17:21 UTC by Lucas Meneghel Rodrigues
Modified: 2015-11-13 10:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-13 10:22:20 UTC
Embargoed:


Attachments (Terms of Use)

Description Lucas Meneghel Rodrigues 2015-11-05 17:21:09 UTC
Description of problem: All my new builds fail with:

2015-11-05 16:41:39,516][ ERROR][PID:27481] Failed to obtain srpm from dist-git
Traceback (most recent call last):
  File "/usr/share/copr/backend/mockremote/builder.py", line 210, in download_job_pkg_to_builder
    self.remote_pkg_path = list(results["contacted"].values())[0][u"stdout"].split("Wrote: ")[1]
IndexError: list index out of range

See: https://copr-be.cloud.fedoraproject.org/results/lmr/BleedingEdgeStuff/epel-6-i386/00133751-avocado/mockchain.log.gz

Version-Release number of selected component (if applicable): COPR (2015-11-5)

How reproducible: Always

Steps to Reproduce:
1. Send your srcrpm to COPR
2. Wait for the failed messages to get to your e-mail

Actual results: Packages flat out fail to build

Expected results: Packages should at least try to build


Additional info:

Comment 1 Valentin Gologuzov 2015-11-13 10:22:20 UTC
Sorry, but you have bad srpm. 

Look here: http://copr-dist-git.fedorainfracloud.org/cgit/lmr/BleedingEdgeStuff/avocado.git/commit/?h=f22&id=e7eb29cf75ea8eb0f5d533e3fc9186c2324a51b6
In the .spec you specify commit:

%define commit bde85d53a2e1ffde02b2f65ef1f29f912acf5d32

But attached tar.gz has another version:

+7c7056f04f7bec44a8dc27cfee8866e1  avocado-0.30.0-4d1124d.tar.gz


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