Opened 2 years ago

Last modified 3 months ago

#26238 new task

Move from Debian Wheezy to Debian Buster for our Linux builds

Reported by: gk Owned by: tbb-team
Priority: High Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-rbm, TorBrowserTeam202009, gitlab-tb-tor-browser-build
Cc: boklm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Debian Wheezy is about to get unsupported and we should move to Debian Jessie for our Linux builds. This has the additional advantage that we don't have different Debian versions anymore to build bundles for all of our supported platforms: We are then using Debian Jessie everywhere.

The only worrying situation is the CentOS one. We should think about whether we still can and want support CentOS 6 (which we need to do anyway while switching to Firefox ESR 60 which requires GTK3) and what the CentOS 7 situation is if we start building using Jessie.

Child Tickets

Change History (12)

comment:1 Changed 2 years ago by gk

Keywords: TorBrowserTeam201806 added; TorBrowserTeam201805 removed

Moving our tickets to June 2018

comment:2 Changed 2 years ago by boklm

Debian Jessie includes glibc version 2.19, while Centos 7 has version 2.17.

This page has some information about glibc abi compatibility: https://abi-laboratory.pro/tracker/timeline/glibc/

comment:3 Changed 2 years ago by gk

Keywords: TorBrowserTeam201807 added; TorBrowserTeam201806 removed

Moving first batch of tickets to July 2018

comment:4 Changed 2 years ago by gk

Keywords: TorBrowserTeam201808 added; TorBrowserTeam201807 removed

Move our tickets to August.

comment:5 Changed 2 years ago by gk

Keywords: TorBrowserTeam201809 added; TorBrowserTeam201808 removed

Moving our tickets to September 2018

comment:6 Changed 7 months ago by sysrqb

Keywords: TorBrowserTeam202009 added; TorBrowserTeam201809 removed
Summary: Move from Debian Wheezy to Debian Jessie for our Linux buildsMove from Debian Wheezy to Debian Buster for our Linux builds

CentOS 6 reaches its EOL in November (2020-11-30). We can move the Linux builds to a Buster container around that time. #31127 is tracking all of the other platforms. (If we work on this in September, then it can ride the train for release in November.)

comment:7 Changed 7 months ago by sysrqb

Actually I'm not sure. If CentOS ships glibc 2.17, then I'm not sure which Debian version we'll use. Jessie hits EOL this June, and Stretch shipped 2.24. Version 2.24 only added 9 new symbols since 2.17 and zero symbols were removed, so that's probably okay? Buster has version 2.28, and that lost 5 symbols since 2.17. I wonder if it'll still work.

comment:8 in reply to:  7 Changed 7 months ago by gk

Replying to sysrqb:

Actually I'm not sure. If CentOS ships glibc 2.17, then I'm not sure which Debian version we'll use. Jessie hits EOL this June, and Stretch shipped 2.24. Version 2.24 only added 9 new symbols since 2.17 and zero symbols were removed, so that's probably okay? Buster has version 2.28, and that lost 5 symbols since 2.17. I wonder if it'll still work.

Yes, that's one of the big problems which is why the title was saying Debian Jessie and not Buster: it's not even clear that CentOS 7 would work with Jessie out of the box and, given our past experiences, I doubt this will play well with Debian Buster.

comment:9 Changed 7 months ago by gk

So, to add to this: it's still worthwhile to play with the switch to Jessie (like we do use Wheezy right now) to be sure to have something available for CentOS folks as Buster might require to much changes). Additionally, it's worth thinking generally about that problem because the CentOS <-> Debian drift will not stop but, rather, continue: we need a better solution longer term than what we have right now.

Version 0, edited 7 months ago by gk (next)

comment:10 Changed 7 months ago by boklm

Note: when we switch away from wheezy, we can remove the vsyscall=emulate workaround from README.BUILD_ERRORS (#33345).

comment:11 in reply to:  7 Changed 7 months ago by boklm

Replying to sysrqb:

Version 2.24 only added 9 new symbols since 2.17 and zero symbols were removed, so that's probably okay?

I'm not sure that it's okay as if the binaries we generate are using any of those 9 new symbols, then it won't work with older glibc versions.

Looking at glibc versions, switching to buster would probably break Tor Browser on Centos 6 & 7, but also on Ubuntu 18.04 LTS (glibc 2.27), Debian olstable, openSUSE 15.1 (glibc 2.26), NixOS 19.09 (glibc 2.27), and probably other still supported distributions. So I think it's too early to use buster, and we should rather use jessie or stretch.

comment:12 Changed 3 months ago by gk

Keywords: gitlab-tb-tor-browser-build added

Add magic gitlab keyword.

Note: See TracTickets for help on using tickets.