Bug 1401157

Summary: lua-posix-33.3.1-2.fc24 FTBFS
Product: [Fedora] Fedora Reporter: Petr Šabata <psabata>
Component: lua-posixAssignee: Tim Niemueller <tim>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: michel, orion, sgallagh, tim
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-12 19:54:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1400162    

Description Petr Šabata 2016-12-03 02:41:09 UTC
lua-posix-33.3.1-2.fc24 fails to build from source.
This affects Base Runtime, Rawhide, F25 and possibly older releases as well.

There are two reasons:

1) It expects lua to be available in the SRPM buildroot, which is (no longer)
   the case.  You could work around that by providing a fallback value for
   %luaver like this:

%{!?luaver: %global luaver %(lua -e "print(string.sub(_VERSION, 5))" || echo 0)}

   This will work just fine as SRPMs get actually built twice and %luaver
   will be properly defined during the second pass while not failing the first.

   Note: This should be fixed in the Lua packaging guidelines as well as this
   probably affects all Lua packages in the distribution.

2) Another issue is an undeclared build dependency on perl which is executed
   during the build phase.  Neither perl is included in the default buildroot
   anymore.

   This can be easily fixed by buildrequiring perl.

Comment 1 Stephen Gallagher 2016-12-12 19:54:00 UTC
Sorry, I accidentally opened a new BZ while writing a patch. I'll close this one as a dupe of the other, since it has more detail and a fix.

*** This bug has been marked as a duplicate of bug 1403991 ***