Package: prosody
Version: 0.11.2-1
Severity: normal

Dear Maintainer,

the ejabberd2prosody script, which imports ejabberd data into prosody
with the goal of migrating from ejabberd to prosody, crashes. The
crash can be reproduced as followed:

0. Have ejabberd running with some users and their contacts.

1. Dump the existing ejabberd database:

 # ejabberdctl dump /tmp/dump.txt

2. Stop ejabberd and start prosody instead.

3. Try to import the dump.txt file with ejabberd2prosody:

 # ejabberd2prosody /tmp/dump.txt

The script then crashes with this error message:

   lua: /usr/lib/prosody/util/stanza.lua:27: module 'util.encodings' not found:
           no field package.preload['util.encodings']
           no file '/usr/local/share/lua/5.2/util/encodings.lua'
           no file '/usr/local/share/lua/5.2/util/encodings/init.lua'
           no file '/usr/local/lib/lua/5.2/util/encodings.lua'
           no file '/usr/local/lib/lua/5.2/util/encodings/init.lua'
           no file '/usr/share/lua/5.2/util/encodings.lua'
           no file '/usr/share/lua/5.2/util/encodings/init.lua'
           no file './util/encodings.lua'
           no file '/usr/lib/prosody/util/util/encodings.lua'
           no file '/usr/lib/prosody/util/encodings.lua'
           no file '/usr/bin/../util/encodings.lua'
           no file '/usr/bin/util/encodings.lua'
           no file '/usr/local/lib/lua/5.2/util/encodings.so'
           no file '/usr/lib/aarch64-linux-gnu/lua/5.2/util/encodings.so'
           no file '/usr/lib/lua/5.2/util/encodings.so'
           no file '/usr/local/lib/lua/5.2/loadall.so'
           no file './util/encodings.so'
           no file '/usr/bin/../util/encodings.so'
           no file '/usr/local/lib/lua/5.2/util.so'
           no file '/usr/lib/aarch64-linux-gnu/lua/5.2/util.so'
           no file '/usr/lib/lua/5.2/util.so'
           no file '/usr/local/lib/lua/5.2/loadall.so'
           no file './util.so'
           no file '/usr/bin/../util.so'
   stack traceback:
           [C]: in function 'require'
           /usr/lib/prosody/util/stanza.lua:27: in main chunk
           [C]: in function 'require'
           /usr/bin/ejabberd2prosody:28: in main chunk
           [C]: in ?

Expected result is that the script does not crash, but instead imports
the data into prosody successfully.

This was run on my Raspberry Pi 3B on an arm64 system.

-- System Information:
Debian Release: 10.3
 APT prefers stable-updates
 APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 4.19.0-8-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages prosody depends on:
ii  adduser                             3.118
ii  libc6                               2.28-10
ii  libidn11                            1.33-2.2
ii  libssl1.1                           1.1.1d-0+deb10u2
ii  lsb-base                            10.2019051400
ii  lua-bitop [lua5.2-bitop]            1.0.2-5
ii  lua-expat [lua5.2-expat]            1.3.0-4
ii  lua-filesystem [lua5.2-filesystem]  1.6.3-1
ii  lua-sec [lua5.2-sec]                0.7-1
ii  lua-socket [lua5.2-socket]          3.0~rc1+git+ac3201d-4
ii  lua5.2                              5.2.4-1.1+b2
ii  ssl-cert                            1.0.39

Versions of packages prosody recommends:
ii  lua-event [lua5.2-event]  0.4.6-1

Versions of packages prosody suggests:
pn  lua-dbi-mysql       <none>
pn  lua-dbi-postgresql  <none>
pn  lua-dbi-sqlite3     <none>
pn  lua-zlib            <none>

-- Configuration Files:
/etc/prosody/conf.avail/example.com.cfg.lua [Errno 13] Keine Berechtigung: 
'/etc/prosody/conf.avail/example.com.cfg.lua'
/etc/prosody/conf.avail/localhost.cfg.lua [Errno 13] Keine Berechtigung: 
'/etc/prosody/conf.avail/localhost.cfg.lua'
/etc/prosody/prosody.cfg.lua [Errno 13] Keine Berechtigung: 
'/etc/prosody/prosody.cfg.lua'

-- no debconf information

Reply via email to