Bug 7682 - Prosody needs lua-filesystem to start
Summary: Prosody needs lua-filesystem to start
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Rémy CLOUARD (shikamaru)
QA Contact:
URL:
Whiteboard:
Keywords: PATCH, Triaged
Depends on:
Blocks:
 
Reported: 2012-10-03 10:32 CEST by Alexandr Bezenkov
Modified: 2013-11-23 16:16 CET (History)
2 users (show)

See Also:
Source RPM: prosody
CVE:
Status comment:


Attachments

Description Alexandr Bezenkov 2012-10-03 10:32:30 CEST
Lua-filesystem is not in Prosody dependencies list, but it is required to start.
Components: Prosody 0.8.2

StR:
1. Install Prosody.
2. Try to start it with "systemctl start prosody.service"
3. See the failure message
4. Reveal reason of failure with "systemctl status prosody.service"
5. ?????
6. PROFIT!!!!111oneoneone

To solve problem you can simply install lua-filesystem package with urpmi. However seeing it as Prosody dependency is better solution :)
Comment 1 Thierry Vignaud 2012-10-03 20:45:12 CEST
That doesn't solve anything.
Before & after it fails with the same error:

Starting prosody: lua: /bin/prosody:339: invalid escape sequence near '\s'

CC: (none) => thierry.vignaud

Comment 2 Alexandr Bezenkov 2012-10-04 05:35:24 CEST
Hmmm, that`s strange. I did not have such a message. In my system Prosody started flawlessly after I installed lua-filesystem.
Comment 3 Samuel Verschelde 2013-08-29 12:34:08 CEST
I guess it needs lua-filesystem but there might be another bug that Thierry Vignaud gets when testing (another missing dependency?)

Keywords: (none) => PATCH, Triaged
CC: (none) => stormi
Assignee: bugsquad => shikamaru
Source RPM: (none) => prosody

Comment 4 Manuel Hiebel 2013-10-22 12:20:46 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 5 Manuel Hiebel 2013-11-23 16:16:18 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

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

--
The Mageia Bugsquad

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


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