Bug #16407

release_process: lost TZ=UTC setting

Added by CyrilBrulebois 2019-01-29 10:29:10 . Updated 2019-02-13 08:54:01 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.12.1
Start date:
2019-01-29
Due date:
% Done:

0%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Spotted while checking the latest commits before starting the 3.12 release process:

[13:49:23] kibi: are we losing TZ=UTC on purpose?

-TZ=UTC gpg --no-options --keyid-format 0xlong --verify tails-amd64-3.11.iso.sig tails-amd64-3.11.iso
+gpg --no-options --keyid-format long --verify tails-amd64-3.12.iso.sig tails-amd64-3.12.iso

This might be a buggy conflict resolution, with relevant commits being commit:ead6e4584fd12fa2ee323535e8e8d87463360e12 about 0xlong and commit:d238be5b362ef2484273824810720fb759c3f537 about TZ=UTC (thanks to intrigeri for the Git archeology).

We probably want TZ=UTC with long (instead of 0xlong); the former helps users verify the exact, expected output that we document.

Subtasks

History

#1 Updated by CyrilBrulebois 2019-02-12 16:01:46

FWIW: Worked around for 3.12.1 by editing the command in-place in release_process.mdwn when I checked the diff after setting RELEASE_DATE.

#2 Updated by anonym 2019-02-13 08:54:01

  • Status changed from Confirmed to Resolved
  • Assignee deleted (anonym)
  • Target version set to Tails_3.12.1