GitLab

This seems to be the easiest way to avoid the (non-silent) cronjobs
from spamming sysadmins.

Moreover:

 - It helps make our monitoring converge from email+icinga to Icinga.
 - It makes it easier to run the recurring job manually, e.g. for
   dev/debugging purposes, in the exact same environment that's used
   by the production job.

This timer runs twice an hour so it makes sense to randomize
it within 25 minutes intervals.

By now this should have been applied everywhere.

Before this commit, the Puppet agent would run on all our systems
at the same time, which has good potential for overloading
our Puppet master and PuppetDB. Who knows, this might even explain
why PuppetDB regularly crashes with some Java out of memory error.

This reverts commit 8f8a8141,
which unfortunately did not do what I hoped.

More recent git-annex fixed a bug that made it not entirely quiet despite
the --quiet option. I believe that bug is the reason why our "Update local
mirror of" cronjobs are spamming sysadmins.

refs tails#16723

intrigeri authored Jan 04, 2022 and Zen Fu committed Jan 13, 2022

These are autorequires for the file type: "If Puppet is managing any parent
directories of a file, the file resource autorequires them."

refs tails#17652

Severeal crawlers are hitting Weblate in strange ways and causing
several errors like this one:

    Exception Type: DoesNotExist at /translate/tails/index/id/
    Exception Value: Unit matching query does not exist.

By blocking crawlers' access to /translate, we:

    - Avoid them from wasting resources and triggering errors in
      Weblate.

    - Allow for indexing of the Weblate main page.

    - Avoid invalid or unreviewed content from making into search
      engines.

python3-jenkins-job-builder now correctly depends on it,
so we don't need to manage this ourselves.

We've been warned by a Weblate user in the tails-weblate@ list that the
number of contextual strings in Weblate decreased after the migration to
containerized setup. Indeed, that number was wrongfully changed in:

    53f0b07c

This commit only reverts that number back to the value it had previous
to the migration.

We're dropping the feature/tor-nightly-master branch in tails/tails:
while a nice idea in theory, it's never been useful in practice.

refs sysadmin#17877

I've applied this class in Buster and Bullseye when upgrading
survey.lizard VM, and all seems to work fine in these Debian versions.

Otherwise, if they're already installed, they won't ever be upgraded.

Run Puppet once more so integration repository remotes are correctly
configured even though fetching from them fails in the first run.