Skip to content

create-usb-image-from-iso uses the wrong version of syslinux

Originally created by @anonym on #16748 (Redmine)

(This is only about my local runs since the results on Jenkins are broken because earlier steps fail, and this feature has inter-scenario dependencies.)

The step “Booting Tails from a USB drive upgraded from USB with persistence enabled” fails with booting looking like this:

I’ve causally looked at the volume in a VM, and it has the appropriate partitions, so only the boot bits seem to have been corrupted (not investigated that at all yet).

I cannot reproduce this manually: I installed to USB, cloned the volume, then booted one of them and upgraded the other, and that worked fine, which is essentially what the test suite does (it doesn’t copy, but redoes the same exact installation (we don’t supply an --old-iso so the same ISO will be used) so it shouldn’t matter).

Feature Branch: bugfix/16748-use-syslinux-from-chroot

Attachments

Related issues

Edited by anonym
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information