data: fix shellcheck warnings in snapd.sh.in

[jelovac]

While troubleshooting why snapd is not added to path in Linux Mint LMDE 4 I noticed some shellcheck warnings.

This tiny fix resolves them.

Update

Signed the CLA and added the git email address to the launchpad account.

[bboozzoo]

Thanks!

[mvo5]

Thank you! Nice catch

[anonymouse64]

The CLA check seems to be broken:

Could not determine commit range: expected two parents, but got ['3cd9d3635dd4639b14a6eb8010ee607c05339952']
##[error]Process completed with exit code 1.

[jelovac]

The CLA check seems to be broken:

Could not determine commit range: expected two parents, but got ['3cd9d3635dd4639b14a6eb8010ee607c05339952']
##[error]Process completed with exit code 1.

Indeed.

I signed the CLA after the creation of pull request, could be related.

[stolowski]

The CLA check seems to be broken:

Could not determine commit range: expected two parents, but got ['3cd9d3635dd4639b14a6eb8010ee607c05339952']
##[error]Process completed with exit code 1.

Indeed.

I signed the CLA after the creation of pull request, could be related.

I think it is something else, the cla-check looks for two "parent ..." entries reported by git cat-file -p @, but for this PR there is only one. I suspect this might be because you haven't worked in a branch created from master, but simply pushed to your master directory (but maybe this explanation is nonsense...)

[bboozzoo]

Perhaps merging master to this branch and pushing will fix it.

[jelovac]

The CLA check seems to be broken:

Could not determine commit range: expected two parents, but got ['3cd9d3635dd4639b14a6eb8010ee607c05339952']
##[error]Process completed with exit code 1.

Indeed.
I signed the CLA after the creation of pull request, could be related.

I think it is something else, the cla-check looks for two "parent ..." entries reported by git cat-file -p @, but for this PR there is only one. I suspect this might be because you haven't worked in a branch created from master, but simply pushed to your master directory (but maybe this explanation is nonsense...)

Yes, I didn't create another branch from master on the fork, I simply committed on the forked master and then created a pull request.

So what should I do? Merge the snapcore:master into my forked master and try to push again?

[mvo5]

@jelovac Please try this, if that does not work we will find another way to fix it :)

[stolowski]

Yay, it worked :)

[jelovac]

yeah :)

[bboozzoo]

@mvo5 we can merge this now, the test failures are unrelated.

[bboozzoo]

@jelovac can you merge master once more and push. Or please enable edits from maintainers, so that I can push the merge myself.

[jelovac]

@bboozzoo merged.

Option "Allow edits by maintainers" was already enabled.