This bug was fixed in the package snap-confine - 1.0.43-0ubuntu1~16.04.1
---------------
snap-confine (1.0.43-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
* Backport from 16.10 (LP: #1630040)
snap-confine (1.0.43-0ubuntu1) yakkety; urgency=medium
* New upstream release (LP: #1630479, LP: #1630492, LP: #1628612)
* debian/patches/lp1630789.patch: allow running snaps by non-root users in
LXD containers (LP: #1630789)
snap-confine (1.0.42-0ubuntu3) yakkety; urgency=medium
* allow snap-confine to mount on /dev/pts/ptmx for LXD with /dev/ptmx
symlink
snap-confine (1.0.42-0ubuntu2) yakkety; urgency=medium
* add mmap to AppArmor policy for snap-confine for running snap-confine
under LXD on 4.8 kernels
snap-confine (1.0.42-0ubuntu1) yakkety; urgency=medium
* New upstream release
* Drop patch skip-nsfs-magic-tests-on-old-kernels.patch (applied upstream)
snap-confine (1.0.41-0ubuntu2) yakkety; urgency=medium
* add skip-nsfs-magic-tests-on-old-kernels.patch to disable NSFS tests on
kernels older than 3.19 (LP: #1625565)
snap-confine (1.0.41-0ubuntu1) yakkety; urgency=medium
* New upstream release, full list of issues is available at
https://launchpad.net/snap-confine/+milestone/1.0.41
* Drop all patches (included upstream).
* Add version to apparmor run-time dependency.
snap-confine (1.0.40-1) unstable; urgency=medium
* New upstream release, full list of issues is available at
https://launchpad.net/snap-confine/+milestone/1.0.40
* Drop apparmor profile from the debian/ directory and install it straight
from upstream package. This is now automatically consistent with package
configuration prefix.
* Drop patch: prctl-compatibility.patch(applied upstream)
* Add directory /var/lib/snapd/void to snap-confine
* Add patch: 0001-Don-t-shellcheck-files-spread-prepare-script.patch that
fixes make check due to a mistake upstream.
* Add patch: 0001-Stop-using-deprecated-readdir_r.patch (LP: #1615615)
snap-confine (1.0.39-1) unstable; urgency=medium
* New upstream release.
* Remove d/patches/01_lp1606277.patch, applied upstream.
snap-confine (1.0.38-3) unstable; urgency=medium
* debian/patches/prctl-compatibility.patch: add shadow definitions for
compatibility with older kernel headers.
* drop build-dependency on shellcheck, which is not used at build time
and doesn't exist in trusty.
* make ubuntu-core-launcher "arch:any" to workaround an issue in
rm_conffile which does not deal with changing architectures
* fix log-observer interface regression (LP: #1606277)
snap-confine (1.0.38-2) unstable; urgency=medium
* Fix invocations of rm_conffile.
* Update d/usr.lib.snapd.snap-confine to the latest upstream version to
ensure content-sharing fully works.
snap-confine (1.0.38-1) unstable; urgency=medium
* New upstream release.
-- Jamie Strandboge <ja...@ubuntu.com> Thu, 06 Oct 2016 14:51:26 +0000
** Changed in: snap-confine (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630479
Title:
PATH is not set after namespace is initialized
To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1630479/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
