#829 mod_mam_muc does not work outside of a prosody-modules checkout
Reporter
Dennis Schridde
Owner
Zash
Created
Updated
Stars
★ (1)
Tags
Status-Fixed
Type-Defect
Priority-Medium
Dennis Schridde
on
What steps will reproduce the problem?
1. Enable mam_muc
2. Try to start prosody
What is the expected output? What do you see instead?
```
modulemanager: Error initializing module 'mam_muc' on '$MUC_DOMAIN': /usr/lib64/prosody/core/moduleapi.lua:140: Failed to load plugin library 'mod_mam/rsm', error: /usr/lib64/prosody/modules/mod_mam/rsm.lib.lua: No such file or directory
stack traceback:
/usr/lib64/prosody/core/modulemanager.lua:31: in function </usr/lib64/prosody/core/modulemanager.lua:31>
[C]: in function 'error'
/usr/lib64/prosody/core/moduleapi.lua:140: in function 'require'
/usr/lib64/prosody/modules/mod_mam_muc/mod_mam_muc.lua:17: in main chunk
[C]: in function 'pcall'
/usr/lib64/prosody/core/modulemanager.lua:176: in function 'do_load_module'
/usr/lib64/prosody/core/modulemanager.lua:254: in function 'load'
/usr/lib64/prosody/core/modulemanager.lua:76: in function </usr/lib64/prosody/core/modulemanager.lua:48>
/usr/lib64/prosody/util/events.lua:78: in function 'fire_event'
/usr/lib64/prosody/core/hostmanager.lua:113: in function 'activate'
/usr/lib64/prosody/core/hostmanager.lua:59: in function </usr/lib64/prosody/core/hostmanager.lua:50>
/usr/lib64/prosody/util/events.lua:78: in function 'fire_event'
/usr/bin/prosody:354: in function 'prepare_to_start'
/usr/bin/prosody:423: in main chunk
[C]: at 0x6a51b818f0
```
What version of the product are you using? On what operating system?
prosody 0.10 hg from today with prosody-modules hg.
Please provide any additional information below.
I assume prosody-modules/mod_mam_muc needs something similar to https://hg.prosody.im/0.10/rev/1017a4f8929d
Dennis Schridde
on
Indeed, replacing `module:require"mod_mam/rsm"` with `require"util.rsm"` solves the issue.
Zash
on
The way it is now is because it expects that you have the rest of the prosody-modules repo.
Dennis Schridde
on
But I cannot install the full prosody-modules alongside prosody 0.10... Would it be possible to align the directory layout of prosody-modules to that used in prosody 0.10, so that I can just delete mod_mam/ and util/rsm.lua from prosody-modules and install it alongside prosody 0.10?
Zash
on
Since mod_mam_muc isn't supported with 0.9, it should be safe to make it use the util.rsm that is now included in 0.10.
Changes
owner Zash
titleError initializing module 'mam_muc' on '$MUC_DOMAIN': /usr/lib64/prosody/core/moduleapi.lua:140: Failed to load plugin library 'mod_mam/rsm', error: /usr/lib64/prosody/modules/mod_mam/rsm.lib.lua: No such file or directory mod_mam_muc does not work outside of a prosody-modules checkout
What steps will reproduce the problem? 1. Enable mam_muc 2. Try to start prosody What is the expected output? What do you see instead? ``` modulemanager: Error initializing module 'mam_muc' on '$MUC_DOMAIN': /usr/lib64/prosody/core/moduleapi.lua:140: Failed to load plugin library 'mod_mam/rsm', error: /usr/lib64/prosody/modules/mod_mam/rsm.lib.lua: No such file or directory stack traceback: /usr/lib64/prosody/core/modulemanager.lua:31: in function </usr/lib64/prosody/core/modulemanager.lua:31> [C]: in function 'error' /usr/lib64/prosody/core/moduleapi.lua:140: in function 'require' /usr/lib64/prosody/modules/mod_mam_muc/mod_mam_muc.lua:17: in main chunk [C]: in function 'pcall' /usr/lib64/prosody/core/modulemanager.lua:176: in function 'do_load_module' /usr/lib64/prosody/core/modulemanager.lua:254: in function 'load' /usr/lib64/prosody/core/modulemanager.lua:76: in function </usr/lib64/prosody/core/modulemanager.lua:48> /usr/lib64/prosody/util/events.lua:78: in function 'fire_event' /usr/lib64/prosody/core/hostmanager.lua:113: in function 'activate' /usr/lib64/prosody/core/hostmanager.lua:59: in function </usr/lib64/prosody/core/hostmanager.lua:50> /usr/lib64/prosody/util/events.lua:78: in function 'fire_event' /usr/bin/prosody:354: in function 'prepare_to_start' /usr/bin/prosody:423: in main chunk [C]: at 0x6a51b818f0 ``` What version of the product are you using? On what operating system? prosody 0.10 hg from today with prosody-modules hg. Please provide any additional information below. I assume prosody-modules/mod_mam_muc needs something similar to https://hg.prosody.im/0.10/rev/1017a4f8929d
Indeed, replacing `module:require"mod_mam/rsm"` with `require"util.rsm"` solves the issue.
The way it is now is because it expects that you have the rest of the prosody-modules repo.
But I cannot install the full prosody-modules alongside prosody 0.10... Would it be possible to align the directory layout of prosody-modules to that used in prosody 0.10, so that I can just delete mod_mam/ and util/rsm.lua from prosody-modules and install it alongside prosody 0.10?
Since mod_mam_muc isn't supported with 0.9, it should be safe to make it use the util.rsm that is now included in 0.10.
ChangesError initializing module 'mam_muc' on '$MUC_DOMAIN': /usr/lib64/prosody/core/moduleapi.lua:140: Failed to load plugin library 'mod_mam/rsm', error: /usr/lib64/prosody/modules/mod_mam/rsm.lib.lua: No such file or directorymod_mam_muc does not work outside of a prosody-modules checkoutShould be fixed in https://hg.prosody.im/prosody-modules/rev/c6761ebe613b
Changes