GitLab

... and disable it by default.

We have already masked apt-daily.timer (#12390), but apt-daily-upgrade.timer was
left enabled. AFAICT it's a no-op by default, but better safe than sorry.

Finally, drop masking of apt-daily.timer: APT::Periodic::Enable effectively
makes apt-daily*.timer no-ops.

refs: #17278

In some cases, the previous code would overwrite a non-empty backup file with an
empty one, making it harder to recover from the already painful #10976.

For example, if the permissions get wrong and we run
disable_and_create_empty_persistence_conf_file(), but the user does _not_
immediately fix the problem, then next time they unlock their persistence,
the (non-empty) backup gets overwritten by live-persist which replaces it with
the new, empty config file it created during last boot.

Filling all memory often leads to the VM crashing. So why fill all
memory? Back when Tails was 32-bit (or mixed with 64-bit) there were
some of uncertainty around the 4 GiB limit, which motivated us to fill
a larger region than 4 GiB, so without much thought we might have just
gone ahead and filled all of it. But, AFAICT, if we went with the
approach I describe above and allocated >4 GiB then the test would
still have done what we wanted.

In today's fully 64-bit world we have no reason for allocating >4 GiB,
so we could go with 128 MiB like the other tests arbitrarily (?) do.

Will-fix: #17104

This will avoid some confusion e.g. while using "git grep".

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Themes#Documentation
says that "Lightweight themes have been deprecated", which explains why our old,
custom lightweight theme is ignored.

The only options to fix this are:

 - Create our own theme, get it automatically signed by Mozilla on AMO, download
   the resulting XPI, and somehow make it available at build time.

 - Use an existing theme with a GPL-3+ compliant license.

I've chosen the latter option: this theme is almost identical to the one we
had before.

The XPI is 7.7K so I don't think it's worth devising a more complicated
solution than just adding it to Git.

I add this function to a new file systemd.sh instead of tor.sh, to make
it clear that this uses the systemd unit instead of communicating with
the Tor control socket (which is what tor.sh does).

This function should be used over tor_is_working() from tor.sh in
scripts which don't already communicate with the Tor control socket.

Replace all calls to config/chroot_local-includes/usr/local/sbin/tor-has-bootstrapped
with `/bin/systemctl --quiet is-active tails-tor-has-bootstrapped.target`.

Currently translated at 17.7% (11 of 62 strings)

Translation: Tails/wiki/src/news/version_3.14.1.*.po
Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_3141po/pt/

Currently translated at 39.0% (16 of 41 strings)

Translation: Tails/wiki/src/news/version_3.11.*.po
Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_311po/it/

Assigning _ to gettext.gettext in the module to make syntax checkers
happy was rendering the version provided by gettext.install
inaccessible.

Will-fix: #16601

It seems like the perl library which previously nicely handled the tps
command-line arguments now doesn't support taking dashes instead of
underscores anymore.

This way tails-additional-software-notify will open a browser with
propoer "GNOME" environment no matter who calls it.

We lacked sufficient environment for AT-SPI to work for the browser
child processes started for browsing the docs.

This fixes dialog width and height on Buster:
https://gitlab.gnome.org/GNOME/zenity/commit/3b64d05e8a1aae1581d2bec7288d80ac4699e1b1

People get confused by the use of pal/neutral/foe: they think we need
to particularly trust members of the "pal" pool, which is incorrect
and can lead to useless controversy.

So let's fix this by renaming the pools and clarifying our design doc.

Will-fix: #15983

Convert packages names to set as map objects sometimes don't
behave as expected.

Will-fix: #15983

Will-fix: #15838

Will-Fix: #15838

assert is only evaluated if __debug__ is True and should not be used to check
for conditions.

Will-fix: #15838

Will-fix: #15838

Will-fix: #15838

Will-fil: #15838

this comments appear on the translation files and help translators do
their work.

This reverts commit 268e3f78.

Will-fix: #15879

Use a set instead of map object to restore intended behaviour of filter and
intersection.

Will-fix: #15822

Will-fix: #15822

Will-fix: #15822