group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1625565@xxxxxxxxxxxxxxxxxx>]

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 <jamie@xxxxxxxxxx>  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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1625565

Title:
  1.0.41-0ubuntu1 ftbfs on amd64, i386

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

Bug description:
  [Impact]

  snap-confine contains sanity unit tests that check if the kernel
  behaves in a certain, particular way that subsequent runtime behaviour
  depends on. As it happens to be launchpad package building machinery
  runs on an older kernel with a xenial/yakkety chroot and the sanity
  test fails.

  The relevant unit tests now check and parse kernel version and unless
  a recent enough version is available, those tests are skipped.

  [Test Case]

  N/A

  Technically if someone wants to verify this change then it is
  sufficient to rebuild the package on 14.04 release (not the LTS
  updated) kernel like 3.19.

  [Regression Potential]

  None, this only affects unit tests in a safe way.

  [Other Info]

  * This bug is a part of a major SRU that brings snap-confine in Ubuntu
  16.04 in line with the current upstream release 1.0.42.

  * 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 # ==

  Probably because of the old kernel version, a test fails like this:

  /ns/sc_init_ns_group: OK
  /ns/sc_lock_unlock_ns_mutex: OK
  **
  ERROR:ns-support-test.c:323:test_nsfs_fs_id: assertion failed (buf.f_type == NSFS_MAGIC): (40864 == 1853056627)
  /ns/nsfs_fs_id: FAIL

  12:44 < mwhudson> 40864 seems to be PROC_SUPER_MAGIC
  12:44 < mwhudson> zyga: https://bugs.launchpad.net/ubuntu/+source/snap-confine/+bug/1625565
  12:44 < zyga> mwhudson: thanks
  12:45 < mwhudson> and NSFS_MAGIC was only added to the kernel in a commit from Sat Nov 1 10:57:28 2014 -0400
  12:45 < mwhudson> so that's not going to be in the 14.04 release kernel
  12:46 < mwhudson> 3.19+
  12:46 < zyga> mwhudson: so even the kernel headers have that macro, the relevant files in the kernel don't use it?
  12:47 < mwhudson> zyga: well the kernel headers you are building against are from yakkety presumably
  12:47 < zyga> mwhudson: yes, I just checked that :/
  12:47 < zyga> mwhudson: the mount namespace file in the kernel is indeed procfs
  12:47 < zyga> mwhudson: I guess this test needs to be skipped
  12:47 < zyga> mwhudson: and we might need a separate check for this in snap-confine proper
  12:48 < zyga> so that if we open and see PROC_SUPER_MAGIC we can die()

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