[Tails-l10n] Build failed in Jenkins: check_PO_master #5479

Borrar esta mensaxe

Responder a esta mensaxe
Autor: tails-ci
Data:  
Para: tails-l10n
Temas antigos: [Tails-l10n] Build failed in Jenkins: check_PO_master #5478
Temas novos: [Tails-l10n] Build failed in Jenkins: check_PO_master #5480
Asunto: [Tails-l10n] Build failed in Jenkins: check_PO_master #5479
See <https://jenkins.tails.boum.org/job/check_PO_master/5479/display/redirect?page=changes>

Changes:

[segfault] Make Thunderbird support TLS 1.3 (refs: #17333)

[ckb] Add dummy changelog entry for 4.3.

[intrigeri] Upgrade Tor Browser to 9.0.4-build1 (refs: #17411)

[intrigeri] Fetch Tor Browser from our own archive (refs: #17411)

[ckb] Update PO files.

[ckb] Update changelog for 4.2.1.

[ckb] Update version and date for 4.2.1.

[ckb] Updating SquashFS sort file

[ckb] Mark Tails 4.2.1 as released.

[sajolida] Write release notes for 4.2.1

[sajolida] Say update consistently in this section

[ckb] Fix version number for the next (scheduled) release.

[ckb] Update upgrade-description files.

[ckb] Update IDF file for Tails Verification.

[intrigeri] Update upgrade-description files.

[ckb] Revert "Update upgrade-description files."

[ckb] Update upgrade-description files.

[intrigeri] IUK generation: don't make all files in the SquashFS diff owned by root

[intrigeri] Release process: building IUKs does take a long time

[intrigeri] Release process: fix IUKs hashes file generation

[intrigeri] Update upgrade-description files.

[intrigeri] Release process: also copy UDF for $VERSION to the test channel (Closes:

[intrigeri] Test suite: add steps to the integration test to reproduce bug (refs:

[intrigeri] Upgrader test suite: add steps to reproduce bug (refs: #17425)

[intrigeri] Upgrader: don't assume that all offered upgrades are relevant (refs:

[intrigeri] Add dummy changelog entry for next version

[intrigeri] Avoid 2 minutes delay while rebooting after applying an automatic

[intrigeri] Abort 4.2.1 release due to #17425

[intrigeri] Drop test upgrade descriptions to 4.2.1

[intrigeri] Update Changelog for 4.2.2

[intrigeri] Update PO files.

[intrigeri] Update Changelog for 4.2.2

[intrigeri] Update version and date for 4.2.2.

[intrigeri] Mark Tails 4.2.2 as released.

[anonym] Update upgrade-description files.

[anonym] IUK: various fixes.

[anonym] Update IDF file for Tails Verification.

[intrigeri] Release process: ensure we don't generate UDFs/IUKs about 4.2.1

[intrigeri] Update various website source files for 4.2.2

[intrigeri] Add security advisory for 4.2.2

[intrigeri] Remove 4.2.1 UDFs: it was never released

[sajolida] Write release notes for 4.2.2

[intrigeri] Reuse phrasing from the release notes

[intrigeri] Use shortcut instead of hard-coding link

[intrigeri] Releasing version 4.2.2


------------------------------------------
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on isobuilder3 in workspace <https://jenkins.tails.boum.org/job/check_PO_master/ws/>
No credentials specified
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository gitolite3@???:tails
> git init <https://jenkins.tails.boum.org/job/check_PO_master/ws/> # timeout=10

Fetching upstream changes from gitolite3@???:tails
> git --version # timeout=10
> git fetch --tags --progress -- gitolite3@???:tails +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url gitolite3@???:tails # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url gitolite3@???:tails # timeout=10

Fetching upstream changes from gitolite3@???:tails
> git fetch --tags --progress -- gitolite3@???:tails +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit} # timeout=10

Checking out Revision 1d505dae46e8a0ff44aff6504da8c6c583fd7953 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 1d505dae46e8a0ff44aff6504da8c6c583fd7953

Commit message: "Merge remote-tracking branch 'origin/web/release-4.2.2'"
> git rev-list --no-walk 3e8a08d2fe9704daac5e5ea3da1baa92ac9e11de # timeout=10

[check_PO_master] $ /bin/sh -xe /tmp/jenkins7611950587004774695.sh
+ /var/lib/jenkins/tools/slaves/check_po
ERROR: wiki/src/news/plans_for_2020.fr.po:
    i18nspector is not happy:
        E: inconsistent-trailing-newlines msgid 'Currently, many have to learn how to disable Secure Boot on their\ncomputer. This process is slightly different on every computer, is very\ncomplicated to learn on your own, and can lead to scary problems on\nWindows computers, for example [[!tails_ticket 15016#note-19\ndesc="*BitLocker* asking you for a recovery key"]].\n'
checked files are not clean.
Build step 'Execute shell' marked build as failure