Changeset 57782e4

Timestamp:

2010-08-17T23:57:50Z (14 years ago)

Author:

Wilmer van der Gaast <wilmer@…>

Branches:

master

Children:

763a3ab

Parents:

5b94e9e

Message:

Alternative way for detecting upgrades: This should make sure that bitlbee
gets restarted, even when upgrading from versions that don't have a separate
-common package.

Location:

debian

Files:

• bitlbee-common.postinst (modified) (1 diff)
• changelog (modified) (2 diffs)

debian/bitlbee-common.postinst

@@ -64 +64 @@
 fi
 
-if [ -n "$2" -a "$BITLBEE_UPGRADE_DONT_RESTART" != "1" ]; then
-        invoke-rc.d bitlbee restart
+# The official way to check if we're upgrading is to check if $2 is
+# non-empty. However, previous versions of BitlBee didn't have a
+# bitlbee-common package so in that case the var will also be empty.
+# Instead, check if the port is in use (if netstat is available). This
+# works since the debconf code will pick a free port on new installs.
+if [ "$BITLBEE_UPGRADE_DONT_RESTART" != "1" ]; then
+        unset IS_UPGRADE
+        if type netstat > /dev/null 2> /dev/null; then
+                netstat -an | grep -q :$PORT\\b.*LISTEN && IS_UPGRADE=1
+        else
+                [ -n "$2" ] && IS_UPGRADE=1
+        fi
+        if [ -n "$IS_UPGRADE" ]; then
+                invoke-rc.d bitlbee restart
+        fi
 fi
 

debian/changelog

@@ -1 @@
-bitlbee (1.3-1) unstable; urgency=low
+bitlbee (1.3-0) unstable; urgency=low
 
   * Setting some bogus version number, fix that later.
@@ -6 +6 @@
     bitlbee-common.
 
- -- Wilmer van der Gaast <wilmer@gaast.net>  Sat, 05 Jun 2010 15:16:38 +0100
+ -- Wilmer van der Gaast <wilmer@gaast.net>  Wed, 18 Aug 2010 00:53:11 +0100
 
 bitlbee (1.2.8-1) unstable; urgency=low