Your message dated Thu, 30 Jul 2015 09:34:56 +0000
with message-id <[email protected]>
and subject line Bug#778497: fixed in bilibop 0.5.0
has caused the Debian Bug report #778497,
regarding bilibop: Lacks support for overlay filesystem
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
778497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778497
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bilibop
Severity: important
Hi,
the aufs patch set is going away from Debian, e.g. it's been removed
in Linux 3.18 as found in experimental. It's being superseded by
overlay FS.
On a Debian Live system with Linux 3.18 and union=overlayfs,
/lib/bilibop/test fails to identify the (USB) boot device as being on
the same underlying device as the root FS, and in turn bilibop fails
to tweak the ownership of the device nodes as it's supposed to do.
I've only tested with bilibop 0.4.21~bpo70+1, as that's what we're
using, and I've not seen any obviously related change in the
newest releases.
This is one of the blockers for Tails to upgrade its kernel to 3.18+.
For your convenience, a test ISO will soon be available there:
http://nightly.tails.boum.org/build_Tails_ISO_feature-linux-3.18/
To reproduce, install it to a USB stick with Tails Installer, or just
`dd' it to a USB stick (it's a hybrid ISO). I've not tested the
latter, but I guess it'll produce the same results.
In case it may help, here's the output of "DEBUG=true sh -x
/lib/bilibop/test /dev/sda" (/dev/sda is the boot device):
+ set -e
+ . /lib/bilibop/common.sh
+ [ true = true ]
+ has_udevadm=false
+ IFS=:
+ echo /usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin
+ [ -x /usr/local/sbin/udevadm ]
+ [ -x /usr/local/bin/udevadm ]
+ [ -x /usr/sbin/udevadm ]
+ [ -x /usr/bin/udevadm ]
+ [ -x /sbin/udevadm ]
+ has_udevadm=true
+ break
+ [ true = true ]
+ unset has_udevadm d
+ get_udev_root
+ true
+ echo > get_udev_root
> get_udev_root
+ [ -f /etc/udev/udev.conf ]
+ . /etc/udev/udev.conf
+ udev_root=
+ udev_root=/dev
+ physical_hard_disk /
+ true
+ echo > physical_hard_disk /
> physical_hard_disk /
+ [ -z / ]
+ local blk dev disk=
+ [ -b / -a -e /sys/class/block/ -a ! -e /sys/devices/virtual/block/ ]
+ underlying_partition /
+ true
+ echo > underlying_partition /
> underlying_partition /
+ underlying_device /
+ true
+ echo > underlying_device /
> underlying_device /
+ local dev target=/
+ [ -b / ]
+ [ -f / -o -d / ]
+ underlying_device_from_file /
+ true
+ echo > underlying_device_from_file /
> underlying_device_from_file /
+ device_id_of_file /
+ true
+ echo > device_id_of_file /
> device_id_of_file /
+ udevadm info --device-id-of-file /
+ local id=0:19 dev mntpnt
+ [ 0 = 0 ]
+ find_mountpoint /
+ true
+ echo > find_mountpoint /
> find_mountpoint /
+ df+ sed -ne $s,.* \([^[:blank:]]\+\)$,\1,p
/
+ mntpnt=/
+ is_aufs_mountpoint -q /
+ true
+ echo > is_aufs_mountpoint -q /
> is_aufs_mountpoint -q /
+ local opt=
+ opt=-q
+ shift
+ canonical /
+ true
+ echo > canonical /
> canonical /
+ echo /
+ grep -q ^[^ ]\+ / aufs /proc/mounts
+ return 1
+ dev=
+ local dev=
+ local old new=
+ true
+ return 1
+ dev=
+ DISK=
+ exit 1
Cheers,
--
intrigeri
--- End Message ---
--- Begin Message ---
Source: bilibop
Source-Version: 0.5.0
We believe that the bug you reported is fixed in the latest version of
bilibop, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yann Amar <[email protected]> (supplier of updated bilibop package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
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 <[email protected]>
Changed-By: Yann Amar <[email protected]>
Description:
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
Changes:
bilibop (0.5.0) unstable; urgency=medium
.
* bilibop-common: add support for overlayfs (in mainline kernel since 3.18).
Closes: #778497; new funcions in common.sh:
- 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 common.sh:
- is_btrfs_mountpoint()
- underlying_device_from_btrfs()
Also modify underlying_device_from_file() to call the previous one.
* bilibop-common: modify other functions in common.sh:
- 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 common.sh
* 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 lockfs.sh. 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.
Checksums-Sha1:
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
Checksums-Sha256:
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
Files:
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
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVuenhAAoJEA3CYk+oqzcepUIQAMBk2DzK2qcnz5v/LrUXt3PG
hfOLvaDKls8xkX+/h5kohVQSILq2i6CV7E2Ig40MF0hTav8AB+qDdRUgPZZFXuPL
7O6nMlqf1/KVdcq8U3R9YU0RFbXEqZuCZipo8RzDeHXyig563e/7/ddXEK0xKlYz
Z45b5t6dvb+Nj5TVRdN7o0JYZa+co4nRMCoqjfe6FtdJOl3NKJnv3EzPE6n/XRG+
SXk4/Fk6O0Ad8q25lEvuTeeRyZOk2GcUzVNVkp/h8704L+aqWqilmBShbEGzOPbT
rN99i3Ef0sgwYiW/py9W+93V/Mr4iZiDD1sz/6lAs16/GJuUlg6756bvZnS42Tv6
HJatDzCgYHK25+iEOQny1atByOdezIcq6yvkhgyDrvUn+BxAylHvysIV58PC6k9U
oIkF2HMC8mpcQXyjfK+q0q8gwGFwe/OwWxYvleSb5zFN+7vGMe0ZplBHdiniSev3
95SAgTKUD+UqJ5wbTrJpsnJ5rAJiY9dIhZN1A8bdPdiMZDInEgXTxOy7vu6p8Byo
pTJEyhz6anqjmSwRffnAPf/nB8bKMDG4kMHO1uO+ivOdOYXWeKxy6rsQITHHZ4Pk
jJd6LWffW2rmnx8WEsmjgZavqZnJS0BWDoKrVLJJUXAHwTbGc0safnQEAw6TIJjt
e7vGNDeEUOWLMDImx9CQ
=mYDN
-----END PGP SIGNATURE-----
--- End Message ---
