Bug 1367681

Summary:	LuaRocks: Failed loading manifest
Product:	[Fedora] Fedora EPEL	Reporter:	Roman Tsisyk <roman>
Component:	luarocks	Assignee:	Michel Lind <michel>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	michel
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-30 15:04:27 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:

Description Roman Tsisyk 2016-08-17 08:42:38 UTC

Description of problem:
LuaRocks is outdated and fails to parse metadata from LuaRocks servers.

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

luarocks 2.1.2-1.el6

How reproducible:
Install luarocks from EPEL6 and then try to install some rock using luarocks install.

Steps to Reproduce:
1. docker run -t -i centos:6
2. yum install -y http://mirror.logol.ru/epel/6/x86_64/epel-release-6-8.noarch.rpm
3. yum install luarocks
4. luarocks install luafilesystem

Actual results:

# luarocks install luafilesystem
Warning: Failed searching manifest: Failed loading manifest: Failed extracting manifest file
^C^C^CWarning: Failed searching manifest: Failed loading manifest: Failed fetching manifest for http://luarocks.giga.puc-rio.br/ - Failed downloading http://luarocks.giga.puc-rio.br/manifest
Warning: Failed searching manifest: Failed loading manifest: Failed extracting manifest file
Warning: Failed searching manifest: Failed loading manifest: Failed extracting manifest file
^C^C^CWarning: Failed searching manifest: Failed loading manifest: Failed fetching manifest for http://luarocks.logiceditor.com/rocks - Failed downloading http://luarocks.logiceditor.com/rocks/manifest
^CWarning: Failed searching manifest: Failed loading manifest: Failed loading manifest for http://luafr.org/luarocks/rocks: Error loading file: /root/.cache/luarocks/http___luafr.org_luarocks_rocks/manifest-5.1:1: unexpected symbol near '<'


Expected results:

$ luarocks install luafilesystem --local
Installing https://rocks.moonscript.org/luafilesystem-1.6.3-2.src.rock...
Using https://rocks.moonscript.org/luafilesystem-1.6.3-2.src.rock... switching to 'build' mode
gcc -O2 -fPIC -I/usr/include/lua5.1 -c src/lfs.c -o src/lfs.o
gcc -shared -o lfs.so -L/usr/local/lib src/lfs.o
Updating manifest for /home/roman/.luarocks/lib/luarocks/rocks
luafilesystem 1.6.3-2 is now built and installed in /home/roman/.luarocks (license: MIT/X11)

Additional info:

Please update LuaRocks package in EPEL6 to the latest version.

Comment 1 Roman Tsisyk 2016-08-17 08:45:35 UTC

I found that `yum instal unzip` sovles this problem

Comment 2 Ben Cotton 2020-11-05 16:46:11 UTC

This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 3 Ben Cotton 2020-11-30 15:04:27 UTC

EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.