Bug #12494

Update Tails Verification extension release process documentation: check for amd64 IDF

Added by sajolida 2017-04-29 18:16:18 . Updated 2018-02-04 19:20:17 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Installation
Target version:
Start date:
2017-04-29
Due date:
% Done:

100%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Verification Extension
Deliverable for:

Description

Once we ship an amd64 ISO only, we should change DAVE to download the IDF on https://tails.boum.org/install/v1/Tails/amd64/stable/latest.yml instead of https://tails.boum.org/install/v1/Tails/i386/stable/latest.yml.

See Bug #11962#note-7.

Apparently the needed change is a mere s/i386/amd64/ in conf.json.

This should happen after 3.0.


Subtasks


Related issues

Related to Tails - Bug #12495: Create a copy of the 3.0 IDF on both 'amd64' and 'i386' paths Resolved 2017-04-29
Related to Tails - Bug #12572: Create a copy of the 3.0~rc1 IDF on both 'amd64' and 'i386' paths Rejected 2017-04-29
Blocks Tails - Bug #12496: Update download page to force a Tails Verification version that checks the amd64 IDF Resolved 2017-04-29

History

#1 Updated by sajolida 2017-04-29 18:17:48

  • related to Bug #12495: Create a copy of the 3.0 IDF on both 'amd64' and 'i386' paths added

#2 Updated by sajolida 2017-04-29 18:20:31

  • blocks Bug #12496: Update download page to force a Tails Verification version that checks the amd64 IDF added

#3 Updated by intrigeri 2017-05-19 21:47:25

  • related to Bug #12572: Create a copy of the 3.0~rc1 IDF on both 'amd64' and 'i386' paths added

#4 Updated by intrigeri 2017-06-12 06:55:09

  • Status changed from Confirmed to In Progress

Applied in changeset commit:d221e6b92ee57cdf59f605d7c57b1a36dc09d029.

#5 Updated by intrigeri 2017-06-12 06:57:07

Once this is done, commit:d221e6b92ee57cdf59f605d7c57b1a36dc09d029 shall be reverted.

#6 Updated by anonym 2017-07-06 14:15:07

  • Target version changed from Tails_3.1 to Tails_3.2

#7 Updated by intrigeri 2017-09-07 08:23:11

  • Priority changed from Normal to Elevated
  • Target version changed from Tails_3.2 to Tails_3.3

I suggest you ignore DAVE until the 3.2 release and then put it on your list of top priorities for the 3.3 cycle.

#8 Updated by intrigeri 2017-11-06 15:33:18

  • Target version changed from Tails_3.3 to Tails_3.5

I’m not sure if it’ll still be relevant with DAVE v2 and in any case it can wait.

#9 Updated by intrigeri 2017-11-18 10:54:30

  • Subject changed from Change DAVE to check for amd64 IDF to Change the Tails Verification extension to check for amd64 IDF
  • Affected tool changed from Download and Verification Extension to Verification Extension

#10 Updated by Anonymous 2018-01-15 16:33:09

  • Status changed from In Progress to Rejected

This is already the case in DAVE2.

scripts/contentscript/conf.js:  descriptor: 'https://tails.boum.org/install/v1/Tails/amd64/stable/latest.yml',

#11 Updated by intrigeri 2018-01-15 17:06:48

  • Status changed from Rejected to In Progress

> This is already the case in DAVE2.

Cool! So we only need to update our release process doc to stop generating the i386 one and we’ll be done :)

#12 Updated by Anonymous 2018-01-16 08:27:40

  • Subject changed from Change the Tails Verification extension to check for amd64 IDF to Update Tails Verification extension release process documentation: check for amd64 IDF

#13 Updated by Anonymous 2018-01-16 08:27:53

  • Type of work changed from Code to Contributors documentation

#14 Updated by anonym 2018-01-23 19:52:43

  • Target version changed from Tails_3.5 to Tails_3.6

#15 Updated by anonym 2018-02-02 14:11:18

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • QA Check set to Pass

intrigeri wrote:
> u wrote:
>> This is already the case in DAVE2.
> Cool! So we only need to update our release process doc to stop generating the i386 one and we’ll be done :)

Fixed in commit:ba9f729e6babd977e3ae36ba63b7efed1f74dd88 (master).

#16 Updated by sajolida 2018-02-04 19:20:17

  • Status changed from Fix committed to Resolved

This has been applied on master so it can be marked as “Resolved”.