Closed mferland closed 7 years ago
there are a number of factors that cause this, but it is partly due to dependencies being done in different ways between CCM and Freeswitch: the top-level CCM package for Osmocom currently just depends on FS without specifying a specific version, whereas FS version X specifies that other packages should be the same version. That means that when FS gets upgraded to X the freeswitch-mod-smpp
version required also changes to X, but since freeswitch-mod-smpp
is not built as part of the default FS build, there will not typically be a new version of that package.
We're in the process of fixing this, most likely by just pinning to a specific version of FS.
Nice. Thanks for the feedback.
In the mean time I was able the manually compile the FS deb packages along with the freeswitch-mod-smpp
module and install these manually.
Yeah, manual compilation has been our workaround too.
The issue we were facing was that freeswitch doesn't build mod_smpp and we were releasing it ourselves. However, each time freeswitch would release a new version, our mod_smpp would become uninstallable by apt. After talking with the guys at FS, we are now hosting freeswitch in our repo to give us more control over releases. This should now be fixed
I am currently following the client instructions and when issuing the
apt-get install endaga-osmocom
I get:I gave a quick look at the FreeSwitch package feed and noticed that this package is missing for some reason...