Back to bilibop PTS page

Accepted bilibop 0.5.0 (source amd64) into unstable

Hash: SHA512

Format: 1.8
Date: Tue, 14 Jul 2015 17:11:52 +0000
Source: bilibop
Binary: bilibop bilibop-common bilibop-lockfs bilibop-rules bilibop-udev
Architecture: source amd64
Version: 0.5.0
Distribution: unstable
Urgency: medium
Maintainer: Yann Amar <>
Changed-By: Yann Amar <>
 bilibop    - run Debian GNU/Linux from external media - metapackage
 bilibop-common - shell functions for bilibop scripts
 bilibop-lockfs - lock filesystems and write changes into RAM
 bilibop-rules - device management rules for OS running from external media
 bilibop-udev - minimal udev rule for Debian GNU/Linux running from external medi
Closes: 772187 778497
 bilibop (0.5.0) unstable; urgency=medium
   * bilibop-common: add support for overlayfs (in mainline kernel since 3.18).
     Closes: #778497; new funcions in
     - canonpath(): clean field separators in an arbitrary filepath
     - is_overlay_mountpoint(): grep /proc/mounts for 'overlay' filesystem
     - overlay_mountpoints(): doing the same as aufs_mountpoints()
     - overlay_lowerdir(): output the cleaned value of lowerdir= mount option
     - overlay_upperdir(): output the cleaned value of upperdir= mount option
     - overlay_workdir()
     - underlying_device_from_overlayfs(): find the underlying device from the
       'lowerdir' value; fallback to live-boot (5.0~a1-1) usecases.
     Also modify underlying_device_from_file() to call the previous one.
   * bilibop-common: add support for btrfs. A file on a btrfs mountpoint is not
     directly mapped to the underlying block device: 'stat -c %D FILE' shows
     that the file seems to be on some kind of ramfs (major=0). So add two
     functions in
     - is_btrfs_mountpoint()
     - underlying_device_from_btrfs()
     Also modify underlying_device_from_file() to call the previous one.
   * bilibop-common: modify other functions in
     - underlying_device_from_aufs(): do not fail if the underlying device
       contains btrfs; now use aufs_readonly_branch() instead of aufs_dirs(),
       and call underlying_device_from_file() if the major number of the
       underlying device is 0 (be aware of a possible endless loop)
     - aufs_dirs(), aufs_readonly_branch() and aufs_writable_branch(): replace
       occurencies of glob pattern 'br*' by 'br?' to skip brid[01] files
     - underlying_device_from_file(), do not return 1 too early; let the last
       test say if the funcion failed or not
     - underlying_device_from_loop(): for the case the backing file itself is
       on btrfs, aufs or overlay, i.e. call underlying_device_from_file() from
       there too
     - find_mountpoint() and device_id_of_file(): to work around overlayfs
       specific design (files and dirs are not treated the same way)
     - underlying_device(): remove unneeded local variable assignment
   * bilibop-common: update copyright, README section and physical_hard_disk()
     dependency tree in
   * bilibop-common: update README.Debian, bilibop(7) and bilibop.conf(5).
   * bilibop-lockfs: add support for overlayfs.
     - Modify local-bottom/bilibop-lockfs initramfs script: define $METHOD as
       the aufs or overlay module that is supported by the kernel, and use
       its value to setup specific mount options and mount points. Allow one to
       override the default directory name by setting BILIBOP_LOCKFS_PATH_PREFIX
     - Modify initramfs hook (+ manual_add_module overlay)
       Improve the part of the script related to mount commands (mount -t tmpfs,
       mount -o bind, mount -o move, ...). Make sure the paths of the branches
       used to build the union fs will be consistent at runtime (for both
       overlay, and aufs with brs=0), as the only one places to get those paths
       (e.g. mount options field in /proc/mounts) is out of sync.
     - Rewrite lockfs_mount_helper script, according to the initramfs script;
       prepare directory trees and add/modify comments. Change mount order; now
       the tmpfs mountpoint is set BEFORE the readonly branch, the last one
       being, by design (bilibop), a subdirectory of the first one. Introduce
       a new tunable variable BILIBOP_LOCKFS_PATH_SCHEME to choose the
       directory structure of the lower and upper branches.
     - Also modify lockfs-notify accordingly to support overlay filesystem
   * bilibop-lockfs: modify blacklist_bilibop_devices() in Manually
     add lvm-pv-uuid-* symlink to the list, as the udev rules creating it are
     not included into the initramdisk.
   * bilibop-lockfs: update README.Debian and lockfs_mount_helper(8)
   * bilibop-rules: modify initramfs script. The busybox's readlink
     implementation does not work as expected (with -f flag) and does not
     resolve the target of a broken symlink; so replace the readlink call by a
     'ls -l | sed' command.
   * bilibop-rules: modify lsbilibop. Remove '\n' in echo, as it is not
     supported by all shells, and call echo again to print an empty line
     (closes: #772187).
   * bilibop-rules: update lsbilibop(8)
   * bilibop-udev: update README.Debian
   * debian/control: bump Standards-Version to 3.9.6 (no changes needed).
     Update extended descriptions.
   * debian: modify bilibop-{lockfs,rules}.post{inst,rm}: use 'which' to test
     availability of update-initramfs command instead of testing its full path,
     to avoid a lintian warning.
 359329de269d5144decb45f4288e0a0738642007 1747 bilibop_0.5.0.dsc
 02ef0b3cdfc23b5b8c1beb20aad1aa32b78ccb25 130900 bilibop_0.5.0.tar.xz
 bed83706eadc184f2fcb8d0fa49346d2e2685787 73044 bilibop-common_0.5.0_amd64.deb
 6661ec1bc7186e98dde059496f75f18f125c60dd 48644 bilibop-lockfs_0.5.0_amd64.deb
 51371ff40f47c5c9f09dfc49c81c6ff103e442c8 74392 bilibop-rules_0.5.0_amd64.deb
 34c807672ce3558915b8c96440166ba42745971b 17764 bilibop-udev_0.5.0_amd64.deb
 84ea3196f5a13e7537c810a8d5a0c2d51e715bd2 15612 bilibop_0.5.0_amd64.deb
 6676f01532a904eb5f59c4db3619b9bc00adcba22d153c2812cbc7fd1fb554d5 1747 bilibop_0.5.0.dsc
 06aa93632373ca2217bcb5e926c940aadbf91f6bb78c893405267a3d76a02fc7 130900 bilibop_0.5.0.tar.xz
 d581d088481b63185d4823e62f26e28a60bea816031e68accc7e6e475bde4389 73044 bilibop-common_0.5.0_amd64.deb
 34a0f26ddd1c23829361f8cbed4d4b3dbebe1edba380bfe2de87788a66f5cb73 48644 bilibop-lockfs_0.5.0_amd64.deb
 0c86b0b54618770095765faf6090335a098343c5bd2e8bab1cfd1577ab855a87 74392 bilibop-rules_0.5.0_amd64.deb
 ca01bc47adb7b4d241ce2e1bf9d2f64561273d2cf3ba9884f1571400011bb8f4 17764 bilibop-udev_0.5.0_amd64.deb
 dff04ce3def1304f603a5f627d912a4ba0dade9f9552c8a9af86600b6eda83a3 15612 bilibop_0.5.0_amd64.deb
 894e8ad5ef68677aa65c0c789a72dfe8 1747 admin optional bilibop_0.5.0.dsc
 34e0c36132499134f56cb20ea5a9b841 130900 admin optional bilibop_0.5.0.tar.xz
 082f214d2e9f4e1c0476dcfe231b76c5 73044 admin optional bilibop-common_0.5.0_amd64.deb
 f1e577bc5c8378d7af368ba1cd57190c 48644 admin optional bilibop-lockfs_0.5.0_amd64.deb
 1e89c6165e12ceedc01d0980a896c253 74392 admin extra bilibop-rules_0.5.0_amd64.deb
 f80e63f505d42a99fc22a4570ac630af 17764 admin optional bilibop-udev_0.5.0_amd64.deb
 b38042ff690939f5f7d1c1aef7315352 15612 metapackages extra bilibop_0.5.0_amd64.deb