#1026 prosody-modules from Debian isn't compatible to Prosody's apt repo prosody

Reporter Ricardo Panaggio
Owner Nobody
Stars ★★ (2)  
  • Status-New
  • Priority-Medium
  • Type-Defect
  1. Ricardo Panaggio on

    What steps will reproduce the problem? 1. Add prosody apt repo 2. Install prosody 3. Try to install prosody-modules What is the expected output? prosody-modules should be installer without any issue What do you see instead? $ sudo apt install prosody-modules Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: lua-ldap The following NEW packages will be installed: lua-ldap prosody-modules 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/201 kB of archives. After this operation, 537 kB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously unselected package lua-ldap:amd64. (Reading database ... 44049 files and directories currently installed.) Preparing to unpack .../lua-ldap_1.1.0-1-geeac494-6+b2_amd64.deb ... Unpacking lua-ldap:amd64 (1.1.0-1-geeac494-6+b2) ... Preparing to unpack .../prosody-modules_0.0~hg20170123.3ed504b944e5+dfsg-1_all.deb ... Unpacking prosody-modules (0.0~hg20170123.3ed504b944e5+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/prosody-modules_0.0~hg20170123.3ed504b944e5+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua', which is also in package prosody 0.10.0-1~stretch4 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/prosody-modules_0.0~hg20170123.3ed504b944e5+dfsg-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) What version of the product are you using? On what operating system? Prosody 0.10. Debian stable (with Prosody apt repo). Please provide any additional information below. Add prosody-modules package to Prosody's apt repository is the only solution I can think of, as some non-core modules became core from 0.9 to 0.10, and conflict will happen.

New comment