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
Release for Ubuntu Bionic #97
Comments
@sidprak, I'll need a package for Bionic eventually myself. I suggest that we switch from the "deb" to "snaps", though. Consider #94. In that ticket, we were somewhat blocked from releasing a new ".deb" because we depended on a fix in a newer version of dependency that would be shipped by Ubuntu, not by us. With the "snap" format, we bundle our own dependencies, we could address problems like that. I confirmed that there are examples of Perl scripts being packaged in the Snap format: https://github.com/ubuntu/snappy-playpen/blob/master/kpcli/snapcraft.yaml Anyone is allowed to publish to the "snapcraft.io" repo, so you are welcome to publish a "snap" of the package that works on Ubuntu 18.04 there. |
@sidprak Please try this snap release:
I built it on Bionic, so your odds of it working should be good. It's my first Snap package, though. It would be nice to improve the "confinement" setting so we don't have to publish it in "devmode". You are welcome to work on that. However, the permissions it has in devmode are the same as it has in the So, it's no less secure, it's just that Snaps enable the possibility of being more secure by further limiting the filesystem access of your packages. |
I've tried out the snap (on Ubuntu 18.04) and got the following error:
I've fixed it by rebuilding the snap with the following change:
Seems to be working fine now - thanks for the great tool. |
@spither Thanks for the report. This issue was resolved in the 0.71 Snap release. |
Would it be possible to get a release for Ubuntu Bionic? It looks like the Alestic PPA currently only goes up to Ubuntu Yakkety. I'm happy to help orchestrate it if there's something I can do there.
The text was updated successfully, but these errors were encountered: