Feature #12605
APT snapshots: drop i386 architecture
100%
Description
This would save us lots of disk space!
At least config/binary_local-hooks/40-include_syslinux_in_ISO_filesystem
depends on it though: we could ensure our custom APT repo has the correct i386 version of syslinux, but I’m not sure if it’ll be enough: the apt-get update
we run after enabling i386 there might fail given no i386 indices will be available for most APT sources. Worst case, we can simply publish somewhere the i386 /usr/bin/syslinux
binary we need, and download+check it without using APT.
I could find no other blocker.
Subtasks
Related issues
Related to Tails - |
Resolved | 2016-11-13 | |
Blocked by Tails - |
Resolved | 2015-09-27 | |
Blocked by Tails - |
Resolved | 2017-07-25 | |
Blocked by Tails - |
Resolved | 2017-09-29 | |
Blocks Tails - Feature #13242: Core work: Sysadmin (Maintain our already existing services) | Confirmed | 2017-06-29 |
History
#1 Updated by intrigeri 2017-05-26 07:30:51
- blocked by
Bug #10289: Tails based on Debian Stretch added
#2 Updated by intrigeri 2017-05-26 07:31:00
- related to
Feature #11912: Purge Jessie time-based APT snapshots added
#3 Updated by intrigeri 2017-05-26 07:32:08
- Description updated
> I could find no other blocker.
anonym, bertagaz: any other blocker you can find / think of?
#4 Updated by intrigeri 2017-05-26 08:56:05
intrigeri wrote:
> This would save us lots of disk space!
>
> At least config/binary_local-hooks/40-include_syslinux_in_ISO_filesystem
depends on it though: we could ensure our custom APT repo has the correct i386 version of syslinux, but I’m not sure if it’ll be enough: the apt-get update
we run after enabling i386 there might fail given no i386 indices will be available for most APT sources. Worst case, we can simply publish somewhere the i386 /usr/bin/syslinux
binary we need, and download+check it without using APT.
… or temporarily disable all APT sources except the one for our custom APT repo, apt-get download syslinux:i386
, and revert the APT sources changes.
#5 Updated by intrigeri 2017-06-05 17:38:04
- Target version changed from Tails_3.5 to Tails_3.2
I suspect we’ll need that disk space earlier.
#6 Updated by intrigeri 2017-06-29 10:23:39
- blocks
Feature #13234: Core work 2017Q3: Foundations Team added
#7 Updated by intrigeri 2017-06-29 10:23:48
- blocks
Feature #13233: Core work 2017Q3: Sysadmin (Maintain our already existing services) added
#8 Updated by intrigeri 2017-07-25 09:08:43
- blocked by
Feature #13513: Replace syslinux:i386 with syslinux:amd64 in the ISO9660 filesystem added
#9 Updated by intrigeri 2017-07-25 09:10:46
- Type of work changed from Code to Sysadmin
Actually I’ll deal with the syslinux:i386 issue simply by replacing it with the 64-bit version: see Feature #13513 for details. And then this ticket becomes purely sysadmin.
#10 Updated by intrigeri 2017-07-25 09:10:54
- blocked by deleted (
)Feature #13234: Core work 2017Q3: Foundations Team
#11 Updated by intrigeri 2017-07-25 09:17:59
- Target version changed from Tails_3.2 to Tails_3.3
… and thus I can only do that after we have no active branch that needs syslinux:i386, i.e. after Tails 3.2 has been released.
#12 Updated by intrigeri 2017-07-30 13:26:13
- blocked by deleted (
)Feature #13233: Core work 2017Q3: Sysadmin (Maintain our already existing services)
#13 Updated by intrigeri 2017-07-30 13:26:22
- blocks Feature #13242: Core work: Sysadmin (Maintain our already existing services) added
#14 Updated by intrigeri 2017-09-29 10:14:16
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 10
Deploying, running reprepro clearvanished
on all repos. Then I’ll need to check what’s the deal with reprepro snapshots, likely I’ll have to delete the i386 ones manually.
#15 Updated by intrigeri 2017-09-29 10:32:35
intrigeri wrote:
> Deploying, running reprepro clearvanished
on all repos.
Done, next reprepro updates should take the new config into account. Fingers crossed!
> Then I’ll need to check what’s the deal with reprepro snapshots, likely I’ll have to delete the i386 ones manually.
I’ll let our automatic GC drop them and will check after a while (once our snapshot with i386 enabled that has will expire last has expired, i.e. after Nov 24) that there’s no *_i386.deb
left, nor references to i386 in the reprepro DB, nor nor anything i386 in dists/
.
#16 Updated by intrigeri 2017-09-29 13:04:41
- blocked by
Bug #14735: stable branch FTBFS since the 3.2 release added
#17 Updated by intrigeri 2017-09-29 13:53:57
- % Done changed from 10 to 20
Seen a successful build from devel that used a Debian APT snapshot generated after deploying this change. Waiting for Bug #14735 to be fixed before I can do the same for stable. Then I’ll postpone to the release after Nov 24 (i.e. 3.4) to handle the reprepro snapshots garbage collection stuff explained above.
#18 Updated by intrigeri 2017-09-30 10:01:31
- Target version changed from Tails_3.3 to Tails_3.5
- % Done changed from 20 to 50
stable branch has just built fine on Jenkins.
#19 Updated by intrigeri 2017-11-18 11:55:55
- Target version changed from Tails_3.5 to Tails_3.7
Well, the APT snapshots used by our Vagrant build system (2017091504) have i386, and they will only be bumped for our next major release (early March), so I can’t complete this earlier. Until then we’ll keep some i386 binary packages. If I really need the disk space (e.g. to make progress on ARM support) I’ll speed this up.
#20 Updated by intrigeri 2018-01-01 16:43:05
- blocked by deleted (
Feature #13242: Core work: Sysadmin (Maintain our already existing services))
#21 Updated by intrigeri 2018-01-01 16:43:34
- blocks
Feature #13243: Core work 2018Q1: Sysadmin (Maintain our already existing services) added
#22 Updated by intrigeri 2018-01-19 11:49:07
- blocks Feature #13242: Core work: Sysadmin (Maintain our already existing services) added
#23 Updated by intrigeri 2018-01-19 11:49:25
- blocked by deleted (
)Feature #13243: Core work 2018Q1: Sysadmin (Maintain our already existing services)
#24 Updated by intrigeri 2018-03-21 16:22:29
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
intrigeri wrote:
> I’ll let our automatic GC drop them and will check after a while (once our snapshot with i386 enabled that has will expire last has expired, i.e. after Nov 24) that there’s no *_i386.deb
left, nor references to i386 in the reprepro DB, nor nor anything i386 in dists/
.
All the pre-conditions were finally met since the 3.6 release => done!