Bug 1251916 - [Debian] ioprocess doesn't build in pbuilder
Summary: [Debian] ioprocess doesn't build in pbuilder
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-distribution
Classification: oVirt
Component: ioprocess
Version: ioprocess-0.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-3.6.2
: 3.6.2
Assignee: Simone Tiraboschi
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks: 1163069
TreeView+ depends on / blocked
 
Reported: 2015-08-10 09:57 UTC by Sandro Bonazzola
Modified: 2016-02-02 09:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-02 09:44:26 UTC
oVirt Team: Infra
Embargoed:
oourfali: ovirt-3.6.z?
rule-engine: planning_ack?
oourfali: devel_ack+
rule-engine: testing_ack?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 38074 0 None None None Never
oVirt gerrit 49240 0 None None None Never

Description Sandro Bonazzola 2015-08-10 09:57:59 UTC 
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building ioprocess using existing ./ioprocess_0.15.orig.tar.gz
dpkg-source: info: local changes detected, the modified files are:
 ioprocess-0.15/Makefile.in
 ioprocess-0.15/aclocal.m4
 ioprocess-0.15/bindings/Makefile.in
 ioprocess-0.15/bindings/python/Makefile.in
 ioprocess-0.15/build-aux/compile
 ioprocess-0.15/build-aux/depcomp
 ioprocess-0.15/build-aux/install-sh
 ioprocess-0.15/build-aux/missing
 ioprocess-0.15/configure
 ioprocess-0.15/src/Makefile.in
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/ioprocess_0.15-1.diff.5T85w8
dpkg-buildpackage: error: dpkg-source -b ioprocess-0.15 gave error exit status 2
Comment 1 Sandro Bonazzola 2015-10-01 08:47:41 UTC 
Please review / merge pushed patches.
Comment 2 Red Hat Bugzilla Rules Engine 2015-10-19 10:56:56 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 3 Yeela Kaplan 2015-10-21 11:12:23 UTC 
Sandro, what are the patches you are referring to in comment#1?
Comment 4 Oved Ourfali 2015-10-25 10:59:11 UTC 
Changed the assignee.
Yeela will review the patch.
Comment 5 Yaniv Lavi 2015-10-29 12:27:09 UTC 
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
Comment 6 Yaniv Bronhaim 2015-11-02 12:24:30 UTC 
Putting bug on modified. next ioprocess build please move to ON_QA for verification.
Comment 7 Yeela Kaplan 2015-11-29 09:37:36 UTC 
Moving the bug back to POST.
Patch is not merged yet.
Comment 8 Red Hat Bugzilla Rules Engine 2015-11-29 09:37:41 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 9 Oved Ourfali 2015-12-30 08:35:55 UTC 
Simone - what's the status of this one?
Shall we push it out to 4.0?
Comment 10 Yaniv Bronhaim 2016-01-04 10:27:10 UTC 
The patch was merged 6 weeks ago and part of https://gerrit.ovirt.org/#/projects/releng-tools (https://gerrit.ovirt.org/#/c/49240/). moving bug to ON_QA
Comment 11 Red Hat Bugzilla Rules Engine 2016-01-04 10:27:13 UTC 
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Comment 12 Pavel Stehlik 2016-02-02 09:44:26 UTC 
Closing older BZs, if still happened, please reopen.
Note You need to log in before you can comment on or make changes to this bug.