smstools_3.1.6-1~bpo50+1_i386.changes is NEW
(new) smstools_3.1.6-1~bpo50+1.diff.gz optional comm
(new) smstools_3.1.6-1~bpo50+1.dsc optional comm
(new) smstools_3.1.6-1~bpo50+1_i386.deb optional comm
SMS server tools for GSM modems
The SMS server tools allow setting up a central SMS gateway. It
sends and receives SMS messages using a simple file-based
interface. It can accommodate up to 20,000 messages a month.
.
It supports an event-handler option that allows calling customized
programs or scripts after sending or receiving SMS messages.
.
The SMS Server Tools use one or more (max. 32) GSM modems to send and
receive SMS messages. Some modems may be equipped with SIM cards such
as Vodafone or Telmi ones. All messages are sorted in queues by the
provider. If one modem fails, it will be deactivated for one hour
before the software retries, while other modems run without any
restriction. The status information and alarms are logged with
syslog.
(new) smstools_3.1.6.orig.tar.gz optional comm
Changes: smstools (3.1.6-1~bpo50+1) lenny-backports; urgency=low
.
* Rebuild for lenny-backports.
.
smstools (3.1.6-1) unstable; urgency=low
.
* New upstream version
(Closes: #494274)
* Remove patch to fix modem timeouts; upstream includes changes that
obsolete it
* Switch to debhelper 7 and minimize the rules file
* Add a file debian/manpage for manpage installation
* Add a debian/install file for files which need to be installed
* Add an ignore.d.server file for logcheck (Closes: #516158)
* [INTL:ja] Add Japanese po-debconf template translation
(ja.po); thanks to Hideki Yamane
(Closes: #558073)
* Change my email address at some places
* Make ucf call on purge conditional, so that purge does not fail if
ucf is not installed.
* Fix pathname of smsd configuration in ucf call (its smsd.conf not
smstools.conf)
* Remove the last changed header from smsd.conf because its annoying
on every upgrade
* Fix a bug in the init script, that would cause the daemon to not
properly run, if /var/run/smstools does not exist, because it
wouldn't respect its user settings anymore.
* Make sure a symlink from /var/log/smsd.log to /var/log/smstools/smsd.log
is created on upgrades, if /var/log/smsd.log exists.
* Change the logfile path in the default configuration to
/var/log/smstools/smsd.log
.
smstools (3.1.3-4) unstable; urgency=low
.
* Merge changes from 3.1-2+lenny1
.
smstools (3.1.3-3) unstable; urgency=low
.
* Add missing changelog entry from stable version (3.1-2)
(Closes: #522376)
* Don't create /var/run/smstools in postinst nor during the build process,
because its created in the init script. Thanks lintian.
* Update Standards-Version
* Remove patch for disabling of functions that are not thread-safe,
because it has been applied upstream.
.
smstools (3.1.3-2) unstable; urgency=low
.
* Upload to unstable
* Added code to init script that recreates /var/run/smstools with proper
permissions (taken from dpkg-statoverride) if it went missing.
(Closes: #510494)
* Update spanish debconf translation. Thanks to Francisco Javier
Cuadrado (Closes: #511481)
* Added swedish debconf translation. Thanks to Martin Bagge (Closes:
#510555)
* Added --debconf-ok option to ucf call to fix warning during upgrade
and for this to work properly also added a versioned ucf dependency.
.
smstools (3.1.3-1) experimental; urgency=low
.
* New upstream release
* Upload to experimental because lenny is in freeze
* Replace errornous $i with the actual path in dpkg-statoverride call for
/var/log/smsd_stats, to fix the wrong permissions for that directory
* Call dpkg-statoverride on /var/log/smstools/smsd_stats instead of
calling it for /var/log/smsd_stats
* Fix my email address in the Uploaders field.
* Add a 'set -e' to all maintainer scripts, so that they exit with an error
if anything goes wrong
* Make dpkg-statoverride in post-removal maintainer script conditional, so
that it does not fail, if no override exists
Override entries for your package:
Announcing to backports-changes@lists.backports.org
Your package contains new components which requires manual editing of
the override file. It is ok otherwise, so please be patient. New
packages are usually added to the override file about once a week.
You may have gotten the distribution wrong. You'll get warnings above
if files already exist in other distributions.
Reply to: