Set DEBIAN_FRONTEND=noninteractive when installing packages

The build of the buster container image used for building https-everywhere is getting stuck because a configuration windows for setting up the tango-common package is waiting for input.

added TorBrowserTeam201903R component::applications/rbm owner::boklm priority::medium resolution::fixed severity::normal status::closed tbb-rbm type::defect labels

As buster is still changing a lot, causing some breakages, maybe we could think about building our own python 3.6 on a stable Debian release instead of using buster.

It seems using the -y argument with apt-get install is enough to remove all configuration prompts, but not all of them. We should add the DEBIAN_FRONTEND=noninteractive environment variable, and maybe the -q argument.

Trac:
Owner: tbb-team to boklm
Summary: Build of buster container for https-everywhere is getting stuck to Set DEBIAN_FRONTEND=noninteractive when installing packages
Component: Applications/Tor Browser to Applications/rbm

Trac:
Cc: N/A to tbb-team

In branch bug_29194 I made a patch setting DEBIAN_FRONTEND=noninteractive. However, I didn't fully test it yet, and because it is changing build instructions for all containers, it will require everything to be rebuilt.

With #29235 (moved) we stopped using buster in projects/https-everywhere, however we still use in in projects/tor-browser for android-armv7. Before merging the fix that will require rebuilding everything, I think we could start by fixing it only for projects/tor-browser on android-armv7: https://gitweb.torproject.org/user/boklm/tor-browser-build.git/commit/?h=bug_29194_android&id=c87154eadb5920aa54e52763fd092dea56e97485

And later merge the full fix, after more testing.

Replying to boklm:

In branch bug_29194 I made a patch setting DEBIAN_FRONTEND=noninteractive. However, I didn't fully test it yet, and because it is changing build instructions for all containers, it will require everything to be rebuilt.

With #29235 (moved) we stopped using buster in projects/https-everywhere, however we still use in in projects/tor-browser for android-armv7. Before merging the fix that will require rebuilding everything, I think we could start by fixing it only for projects/tor-browser on android-armv7: https://gitweb.torproject.org/user/boklm/tor-browser-build.git/commit/?h=bug_29194_android&id=c87154eadb5920aa54e52763fd092dea56e97485

And later merge the full fix, after more testing.

What's the plan here? Bite the bullet and merge the full fix for getting everything rebuilt and tested before 8.5 gets stable? Or anything else?

Trac:
Status: new to needs_information

Yes, I think we can merge the full fix now.

There is a patch for rbm in: https://gitweb.torproject.org/user/boklm/rbm.git/commit/?h=bug_29194_v2&id=c61e6940a1824462648064898be0759dd1600414

And one for tor-browser-build: https://gitweb.torproject.org/user/boklm/tor-browser-build.git/commit/?h=bug_29194_v2&id=a4689ee18278443aaf10f72da623efba657a970a

Trac:
Keywords: TorBrowserTeam201901 deleted, TorBrowserTeam201902R added
Status: needs_information to needs_review

February is gone.

Trac:
Keywords: TorBrowserTeam201902R deleted, TorBrowserTeam201903R added

Looks good to me. Merged to rbm's master (commit c61e6940a1824462648064898be0759dd1600414) and tor-browser-build's master (commit 799ccf053e78b385fbd2900e092113849d73c94b).

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

closed

moved to tpo/applications/rbm#29194 (closed)