* No need to keep patches for our own modules. Patches are just
for changes We need on upstream modules. That helps us to upgrade
faster and keep our changes in a clean way
Change-Id: I0c006b758e0a891aa67cc0216635a0342282969b
- mod_carbons
- mod_csi
- mod_man
- mod_websocket
* debian/control:
we want prosody 0.11 version
remove ngcp-system-tools from dependences, not called
since removal of postinst
remove modules merged upstream from description
Change-Id: I83f5fd48ba17fe4c91763177fed7dee69ca02db1
This package needs modifications to adapt to the versions in Debian buster
(0.11), it is unknown if it works in 0.10, so to be on the safe side change the
dependency to the known version in which it works.
Change-Id: I4441732fe98c3951a259a2a2b3dfdc482db20bd1
This reverts commit 039086e505.
The are modules not adapted for the new version of prosody shipping with buster
(0.11), so we have to keep using prosody 0.9 from stretch until this is sorted
out.
Thus reverting the commit, with a minor adaptation for another change that
creates a conflict (switching dependencies from debhelper>=10 to
debhelper-compat=12).
Change-Id: I6abd1e81dd432f4f1033c85490a232f0a0675412
- Correct MIT license name from MIT/X11.
- Fix typos in License field names.
- Move catch all Files stanza to the beginning, as more general matches
should go first.
- Reformat field contents.
- Add an actual License stanza for MIT.
Change-Id: I6795a9d761ea38db93f86a8702594acca5caf6e8
The prosody version in Debian/buster already provides module,
we're trying to ship here.
Therefore failing to install e.g. with:
| trying to overwrite '/usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua', which is also in package prosody 0.10.2-1
Install the conflicting modules only on Debian 9, AKA stretch.
Change-Id: I4535b8c2963f40d5b2093922e6050404855b5004
We are in the process of removing the obsolete init scripts, so trying
to use them directly will make these operations not work at all.
In addition these actions are always denied on NGCP via our permanent
policy-rc.d, so there is no point in even trying.
Change-Id: I0ef824b419f8e48c06c240889626fb3fea43d61e
This is more like a hack working around the unknown root cause of
why the storage driver is returning trailing garbage for some of
the entries of the key column.
It doesn't happen on the mysql client, so maybe lua related?
Change-Id: I4a5d0b27f0c6dbf9d220e86f1ab6d9e929ad2d89
- Bump Standards-Version to 3.9.8.
- Bump debhelper compatibility version 10.
- Switch from Priority extra to optional.
- Canonicalize Homepage URL.
- Add a debian/.gitignore file.
Change-Id: I0df02c5252fc686c7c40808aa0dcb69636a8af86
* sipwise app needs 'urn:xmpp:mam:1' at disco result
* upstream did implement supporting urn:xmpp_mam:[0-2] slightly different
looking through the code y noticed that if the disco has no 'to' it shows
the versions of mam supported
<!-- Out Fri 07 Apr 2017 10:53:38 AM CEST -->
<iq type='get'
id='info1'>
<query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
<!-- In Fri 07 Apr 2017 10:53:38 AM CEST -->
<iq id='info1' type='result' to='vseva@sipwise.com/Gajim' from='vseva@sipwise.com'>
<query xmlns='http://jabber.org/protocol/disco#info';>
<feature var='urn:xmpp:mam:0'/>
<feature var='urn:xmpp:mam:1'/>
<feature var='urn:xmpp:mam:2'/>
<feature var='urn:xmpp:sid:0'/>
<identity type='pep' category='pubsub'/>
<feature var='http://jabber.org/protocol/pubsub#publish'/>
</query>
</iq>
That is not what the XEP 0313 says:
<quote>
7. Determining support
If a server or other entity hosts archives and supports MAM queries, it MUST
advertise the 'urn:xmpp:mam:2' feature in response to Service Discovery
(XEP-0030) [15] requests made to archiving JIDs
(i.e. JIDs hosting an archive, such as users' bare JIDs):
</quote>
Change-Id: I1e69f4ce0270b79d3940c8806d4b30ae55aadd98