Please allow the mysterymentor snap (also mysterymentor-dev and mysterymentor-staging) to use classic confinement.
mysterymentor is the client of the service https://mysterymentor.io, which helps developers work together with their mentors.
mysterymentor uses the current user directory to detect with which project the user works.
Also, for the first time, mysterymentor creates some git-hooks to intercept the user actions with git.
After that, mysterymentor send the user code to the service https://mysterymentor.io.
I’ve tried to use confinement: strict with the home interface, but it doesn’t work for me.
mysterymentor always need to detect the directory from which the user launches the mysterymentor.
When the mysterymentor launches in isolated space, it can’t do that.
While in development, use confinement: devmode; once everything is working, if you’re having trouble dropping it to strict, we’ll be more than happy to help you figure it out.
void is the working directory of the strictly-confined snap app, if the user’s working directory is not visible to the confined app.
Adding the home interface should help.
I already use the home interface in the snap, but I can’t understand how I can get the current user directory from my application?
I launch the application and want to get the directory in which the user now.
In the example above, I want to get the /root directory when I launch my application, but I got /var/lib/snapd/void.
I built your program, and ran it from inside a strictly-confined snap that has the home interface, and it printed the current directory of the user (both as a regular user, and root).
Thank you. I’ve found a bug in the docker container where I tested.
Now, when I push the snap I see the following error:
Pushing mm-dev_0.99.0-3-gf05cea9.snap
After pushing, an attempt will be made to release to 'stable'
Preparing to push '/Users/mgrachev/dev/go/src/github.com/evrone/mm-cli/scripts/tmp/dist/development/mm-dev_0.99.0-3-gf05cea9.snap' to the store.
Found cached source snap /Users/mgrachev/.cache/snapcraft/projects/mysterymentor-dev/snap_hashes/amd64/7751bd07d9903ddbed238e3064fb4b43f7c37a33e9ed5db11643ff81b73ef9c3958fad634abaf3a73af636be67806008.
Generating xdelta3 delta for mm-dev_0.99.0-3-gf05cea9.snap.
Pushing delta /Users/mgrachev/dev/go/src/github.com/evrone/mm-cli/scripts/tmp/dist/development/mm-dev_0.99.0-3-gf05cea9.snap.xdelta3.
Pushing mm-dev_0.99.0-3-gf05cea9.snap.xdelta3 [=========================================================================================================================================================================================] 100%
Processing...|
Will need manual review...
The Store automatic review failed.
A human will soon review your snap, but if you can't wait please write in the snapcraft forum asking for the manual review explicitly.
If you need to disable confinement, please consider using devmode, but note that devmode revision will only be allowed to be released in edge and beta channels.
Please check the errors and some hints below:
- unknown entries in snap.yaml: 'parts'
that’s not the issue at all. The problem is that there is a parts block in snap.yaml - parts is a snapcraft.yaml build-time definition that should not propagate into snap.yaml.
I use the special tool for creating snaps - goreleaser, which uses the command snapcraft pack to make the snap file. How can I fix that to use parts in my snap file?