At the end of the process, the bluemarine2 user doesn't exist any longer.
Furthermore, the running service is the old one:
systemctl status bluemarine2-service.service
● bluemarine2-service.service - blueMarine II headless service
Loaded: loaded (/etc/systemd/system/bluemarine2-service.service; enabled)
Active: active (running) since Tue 2016-12-13 15:01:50 UTC; 5min ago
Main PID: 832 (java)
└─832 java -DblueMarine2.workspace=/var/lib/bluemarine2 -Dit.tidalwave.bluemarine2.logFolder=/var/log -jar /opt/bluemarine2/bin/../lib/it-tidalwave-bluemarine2-service-1.0-ALPHA-10.jar
See the console log:
dpkg: warning: downgrading bluemarine-ii-headless-service from 1.0+ALPHA+11~SNAPSHOT to 1.0~ALPHA+11
(Reading database ... 33059 files and directories currently installed.)
Preparing to unpack bluemarine2-service-linux-1.0-ALPHA-11.deb ...
Removed symlink /etc/systemd/system/multi-user.target.wants/bluemarine2-service.service.
The system user `bluemarine2' already exists. Exiting.
Unpacking bluemarine-ii-headless-service (1.0~ALPHA+11) over (1.0+ALPHA+11~SNAPSHOT) ...
Removing user `bluemarine2' ...
Warning: group `nogroup' has no more members.
Files under /var/lib/bluemarine2/ not deleted.
Files under /var/cache/bluemarine2/ not deleted.
Setting up bluemarine-ii-headless-service (1.0~ALPHA+11) ...
Created symlink from /etc/systemd/system/multi-user.target.wants/bluemarine2-service.service to /etc/systemd/system/bluemarine2-service.service.
The service will be automatically started at boot.
Part of the problem is due to BMT-81.