kernel-packages team mailing list archive

[Kyle Fazzari <kyle@xxxxxxxxxxxxx>]

Public bug reported:

[Impact]

 * The Snappy packaging format will soon move to utilizing a squashfs
image per package. However, when that change happens such snaps will
fail to install on the Mako due to squashfs support not being enabled.

[Test Case]

 1. Install squashfs-tools.
 2. Create a directory containing generic data (e.g. a text file).
 3. Turn that directory into a squashfs image:

    $ mksquashfs <dir> foo.sqsh

 4. Attempt to mount that directory:

    $ sudo mount foo.sqsh /mnt

 5. Notice that without this patch, the mount fails due to an unknown
filesystem type, whereas it succeeds with this patch applied, and
contains the content created in step (2).

[Regression Potential]

 * None known; this only enables squashfs.

[Other Info]

 * These flags were simply copied from the current trusty config.

** Affects: linux-mako (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-mako in Ubuntu.
https://bugs.launchpad.net/bugs/1513207

Title:
  [SRU] Enable squashfs support

Status in linux-mako package in Ubuntu:
  New

Bug description:
  [Impact]

   * The Snappy packaging format will soon move to utilizing a squashfs
  image per package. However, when that change happens such snaps will
  fail to install on the Mako due to squashfs support not being enabled.

  [Test Case]

   1. Install squashfs-tools.
   2. Create a directory containing generic data (e.g. a text file).
   3. Turn that directory into a squashfs image:

      $ mksquashfs <dir> foo.sqsh

   4. Attempt to mount that directory:

      $ sudo mount foo.sqsh /mnt

   5. Notice that without this patch, the mount fails due to an unknown
  filesystem type, whereas it succeeds with this patch applied, and
  contains the content created in step (2).

  [Regression Potential]

   * None known; this only enables squashfs.

  [Other Info]

   * These flags were simply copied from the current trusty config.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-mako/+bug/1513207/+subscriptions