Unable to configure scalarizr while installing deb in Ubuntu. Proposed Patch for postinst.

41 views
Skip to first unread message

ian_dic...@symantec40.com

unread,
Aug 1, 2016, 5:46:05 PM8/1/16
to scalr-discuss
Hi,

I get the following output when I'm installing scalarizr on Ubuntu 14.04

===
Selecting previously unselected package scalarizr-ec2.
Preparing to unpack .../scalarizr-ec2_4.9.5-1_amd64.deb ...
Unpacking scalarizr-ec2 (4.9.5-1) ...
Setting up scalarizr (4.9.5-1) ...
/var/lib/dpkg/info/scalarizr.postinst: line 33: insserv: command not found
/var/lib/dpkg/info/scalarizr.postinst: line 34: insserv: command not found
/var/lib/dpkg/info/scalarizr.postinst: line 35: insserv: command not found
 * Stopping Scalarizr scalarizr
Thank you for installing scalarizr!
Setting up scalarizr-ec2 (4.9.5-1) ...
===

The messages about 'insserv' are issued, because we have our own message in the '/etc/issue.net'
and the script fails to detect that it is being run on Ubuntu.

I guess it is better to check /etc/os-release or /etc/lsb-release for the presence of 'Ubuntu' string.
I was wondering if you could fix .deb with the following patch.

diff -du postinst.orig postinst
--- postinst.orig 2016-08-01 16:04:29.000000000 +0000
+++ postinst 2016-08-01 21:19:43.786677729 +0000
@@ -13,7 +13,7 @@
 if test -e /etc/debian_version; then
     FAMILY='debian'
     DIST='debian'
-    if grep 'Ubuntu' /etc/issue.net; then
+    if grep 'Ubuntu' /etc/lsb-release; then
         DIST='ubuntu'
     fi
 else

============
Thank you in advance,
Ian

Marat Komarov

unread,
Aug 2, 2016, 9:33:04 AM8/2/16
to scalr-discuss
Ian,

Thank you for patch and report. We'll correct postinst script behavior.

Regards,
Marat

ian_dic...@symantec40.com

unread,
Aug 2, 2016, 1:12:30 PM8/2/16
to scalr-discuss
Great! Thanks!

Do you have any ETA when the fixed packages will be released? 1-2..7 days?

Thank again,
Ian

Marat Komarov

unread,
Aug 3, 2016, 6:20:10 AM8/3/16
to scalr-discuss
We've created in internal ticket to revise postinst. Patch fixes only the single use case, and we can't apply it as is.
So the answer is - soon.


On Tuesday, August 2, 2016 at 12:46:05 AM UTC+3, ian_dic...@symantec40.com wrote:
Reply all
Reply to author
Forward
0 new messages