Feature #13513
Replace syslinux:i386 with syslinux:amd64 in the ISO9660 filesystem
100%
Description
We include a copy of the syslinux binary (config/binary_local-hooks/40-include_syslinux_in_ISO_filesystem
) in the ISO filesystem. It’s used by Tails Installer when run from inside Tails (UUI uses a win32 binary, and Tails Installer on Debian uses the system’s syslinux executable). So far we’ve been shipping the 32-bit binary (so that one could use Tails 2.x to install Tails 3.x) + libc6-i386 (so that the installer still works when run from a 64-bit Tails). If we dropped that 32-bit binary + libc6-i386 and included the 64-bit one instead, Feature #12605 would be trivial to solve. This should be done once Tails 2.x users have had enough time to “Upgrade from ISO” to 3.x. I believe Tails 3.2, i.e. 4 months after the Tails 3.0 release, is the right time to do the switch. I think that the only needed changes are in tails.git, and the Installer doesn’t need to be modified.
Subtasks
Related issues
Related to Tails - |
Resolved | 2016-10-11 | |
Blocks Tails - |
Resolved | 2017-06-29 | |
Blocks Tails - |
Resolved | 2017-05-26 |
History
#1 Updated by intrigeri 2017-07-25 09:08:34
- blocks
Feature #13234: Core work 2017Q3: Foundations Team added
#2 Updated by intrigeri 2017-07-25 09:08:42
- blocks
Feature #12605: APT snapshots: drop i386 architecture added
#3 Updated by intrigeri 2017-07-25 09:10:18
- Category set to Installation
#4 Updated by intrigeri 2017-07-25 09:16:26
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 10
- Feature Branch set to feature/13513-64-bit-syslinux
#5 Updated by intrigeri 2017-07-25 09:24:34
- related to
Bug #11873: "Upgrade from ISO" fails from 32-bit Tails with 64-bit ISO added
#6 Updated by intrigeri 2017-07-27 17:50:24
- Assignee changed from intrigeri to anonym
- Priority changed from Normal to Elevated
- % Done changed from 10 to 50
- QA Check set to Ready for QA
feature/usb_*.feature
entirely passed locally, and I could successfully install an ISO built from this branch with Tails Installer (not that it should be affected, but still).
Note: this blocks urgent sysadmin work, so it really has to go into 3.2, so it would be nice if it could be reviewed early in the cycle, so I have time to fix whatever needs to be.
#7 Updated by anonym 2017-08-15 14:16:10
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
#8 Updated by anonym 2017-09-28 18:49:03
- Status changed from Fix committed to Resolved