Package: bilibop-common Severity: important Version: 0.5.2 Hi,
this is about this bug that affects Tails 3.0~beta4: https://labs.riseup.net/code/issues/12501 Tails' incremental upgrade system uses aufs to stack SquashFS deltas. A system with no such delta applied, i.e. one single read-only aufs branch (filesystem.squashfs), works fine: it gets the correct /dev/bilibop symlink. A system with one such delta applies, i.e. 2 read-only aufs branches (filesystem.squashfs and 3.0~beta3.squashfs), doesn't work correctly: it doesn't get any /dev/bilibop symlink. I'm attaching the output of `sh -x /lib/bilibop/test /dev/sda 2>&1' to this bug report. This part seems very suspicious to me: + local dir=/lib/live/mount/rootfs/3.0~beta3.squashfs /lib/live/mount/rootfs/filesystem.squashfs + device_id_of_file /lib/live/mount/rootfs/3.0~beta3.squashfs /lib/live/mount/rootfs/filesystem.squashfs + false + [ -d /lib/live/mount/rootfs/3.0~beta3.squashfs /lib/live/mount/rootfs/filesystem.squashfs ] + udevadm info --device-id-of-file /lib/live/mount/rootfs/3.0~beta3.squashfs /lib/live/mount/rootfs It seems that some part of bilibop got confused and we get a string with two paths separated by a newline, where there should be only one path, no? Downgrading to Jessie's bilibop fixes the problem… but it might introduce other problems, can't it? I'll try it anyway in a week or so, if a proper solution to this problem isn't found in the meantime. Let me know if I can provide additional info to help pinpoint the problem. Thanks in advance! Cheers, -- intrigeri
