Bug 16968

Summary: Rebuilding the src.rpm from Cauldron stops because of no job control
Product: Mageia Reporter: Kristoffer Grundström <lovaren>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: lovaren
Version: 5   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: python-sphinx_rtd_theme CVE:
Status comment:

Description Kristoffer Grundström 2015-10-15 16:06:13 CEST
Description of problem: I'm trying to build binwalk and its readme file tells me that I need python3-pyqtgraph and that in itself needs python-sphinx_rtd_theme from Cauldron and when I download the src.rpm and then type rpmbuild --rebuild python-sphinx_rtd_theme-0.1.8-2.mga6.src.rpm I end up with an error saying:

/var/tmp/rpm-tmp.GcSwjv: line 31: fg: no job control

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

How reproducible: Everytime.

Steps to Reproduce:
1. Download python-sphinx_rtd_theme-0.1.8-2.mga6.src.rpm from any mirror with Cauldron in it.
2. Make sure rpm-build is installed.
3. Now cd to the dir where you keep the src.rpm and type rpmbuild --rebuild python-sphinx_rtd_theme-0.1.8-2.mga6.src.rpm and see the result.


Reproducible: 

Steps to Reproduce:
Comment 1 Rémi Verschelde 2015-10-15 17:17:03 CEST
Is that on Mageia 5 or on cauldron?
Kristoffer Grundström 2015-10-15 17:28:59 CEST

CC: (none) => kristoffer.grundstrom1983

Comment 2 Kristoffer Grundström 2015-10-15 17:29:24 CEST
Mageia 5, but the src.rpm comes from Cauldron.
Kristoffer Grundström 2015-10-15 17:29:39 CEST

Version: Cauldron => 5

Comment 3 Rémi Verschelde 2015-10-15 17:33:27 CEST
Then it's normal, SRPMs meant for Mageia 6 use new feature of RPM, or in this case probably new python macros, that were not available yet in Mageia 5. "No job control" means that the spec contains a macro that Mageia 5's rpmbuild does not understand.

If you want to rebuild the SRPM, you'll have to edit the spec file yourself to reintroduce the old macros instead of the new ones.

Status: NEW => RESOLVED
Resolution: (none) => INVALID