Thanks for taking your time to report this issue and help making Ubuntu better.
I realize this was filed quite some time ago, but do you remember if you answered "No" to configuring the database at the beginning of the installation? I looked a bit at this issue and wonder if it might be the same issue as described in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=826903. When testing a bit, I got the following results: * Ubuntu 16.04 installing version 1.2.3-6build1, selecting "No" to configuring the database at the start of installation: same error message as towards the end in the attached DpkgTerminalLog.txt. * Same version, selecting "Yes" and configuring the database at the start of the installation: installs without any error messages. * Ubuntu 16.10 with version 1.2.3-9, selecting "No" to configuring the database at the start of installation: no error messages during installation. Note that this version includes the fix for the issue I linked to above. If this is the same issue as the Debian bug above, the good news is that the issue is fixed in newer versions and the fix looks small enough that it might be possibly to apply it to older Ubuntu releases as well. However, (if you remember), it would be great to know if this error occured after answering "No" at the start of the installation process, or if it might be an unrelated issue with similar result. ** Bug watch added: Debian Bug tracker #826903 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826903 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1399990 Title: package biomaj 1.2.3-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/biomaj/+bug/1399990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
