Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deb upgrade fails #1158

Open
Philio opened this issue Nov 21, 2023 · 6 comments
Open

Deb upgrade fails #1158

Philio opened this issue Nov 21, 2023 · 6 comments

Comments

@Philio
Copy link

Philio commented Nov 21, 2023

Console log:

jasmin:x:999:
mkdir: cannot create directory ‘/etc/jasmin/store’: File exists
dpkg: error processing package jasmin-sms-gateway (--configure):
 installed jasmin-sms-gateway package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 jasmin-sms-gateway
@Philio
Copy link
Author

Philio commented Nov 21, 2023

Had to move /etc/jasmin/store and /var/log/jasmin re-run the upgrade, then move them back to replace the empty dirs the upgrade created.

@Kisuke-CZE
Copy link
Contributor

Hi,
post installation script is not ideal. I already suggested change in packaging: #1156

You can try generated package from this changed style: jasmin-sms-gateway_0.11.0-2_all.zip

@farirat
Copy link
Contributor

farirat commented Nov 23, 2023

which os is this ?

@Philio
Copy link
Author

Philio commented Nov 23, 2023

which os is this ?

Ubuntu 22.04

@farirat
Copy link
Contributor

farirat commented Nov 23, 2023

Spinned a 22.04 instance and installed jasmin with success, please provide more details for troubleshooting

@Kisuke-CZE
Copy link
Contributor

For me this happened too when upgrading from 0.10.X to 0.11. Problem was in post-install script which was not checking if directories exists - it was just issuing mkdir /etc/jasmin/store. On latest distro versions (on RHEL9 and Ubuntu 22.04) if any command in post-install script returned non-zero exit code, execution of that script was interrupted :(

This should be fixed in updated post-install script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants