group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1628612@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package snap-confine - 1.0.43-0ubuntu1

---------------
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)

 -- Jamie Strandboge <jamie@xxxxxxxxxx>  Thu, 06 Oct 2016 12:29:59 +0000

** Changed in: snap-confine (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1628612

Title:
  prefer "core" rather than "ubuntu-core" if installed

Status in Snappy Launcher:
  Fix Released
Status in snap-confine package in Ubuntu:
  Fix Released
Status in snap-confine source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  snap-confine uses the "core" snap as the root filesystem of the
  environment where snap applications execute. In the past that was
  always "ubuntu-core". The core snap has now been renamed to just
  "core" and snap-confine needs to handle this case gracefully.

  If both snaps are preset (core and ubuntu-core) then core is preferred
  and used. The apparmor profile was adjusted so that both "core" and
  "ubuntu-core" names are allowed and internally the code uses two new
  functions to find the location of the preferred core snap (one in the
  internal filesystem layout and one in the external filesystem layout)

  For more information about the execution environment, please see this
  article http://www.zygoon.pl/2016/08/snap-execution-environment.html

  [Test Case]

  The test case can be found here:

  https://github.com/snapcore/snap-confine/tree/master/spread-tests/main
  /core-is-preferred

  The test case is ran automatically for each pull request and for each final release. It can be reproduced manually by executing the shell commands listed in the prepare/execute/restore phases manually.
  The commands there assume that snapd and snap-confine are installed.
  No other additional setup is necessary.

  [Regression Potential]

   * Regression potential is minimal and mainly depends on what is
  published to the store as the "core" snap. If the core snap would
  somehow contain totally bogus content then obviously snaps would cease
  to work correctly.

  [Other Info]

  * snap-confine is technically an integral part of snapd which has an
  SRU exception and is allowed to introduce new features and take
  advantage of accelerated procedure. For more information see
  https://wiki.ubuntu.com/SnapdUpdates

  == # Pre-SRU bug description follows # ==

  The system may run with more than one core snap, by default all snaps
  should run against the "core" snap but for compatibility the system
  should fall back to the "ubuntu-core" snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1628612/+subscriptions