Feature #13505

Update Whisperback text files

Added by xin 2017-07-22 21:04:31 . Updated 2018-01-09 20:51:29 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Target version:
Tails_3.4
Start date:
2017-07-22
Due date:
% Done:

100%

Feature Branch:
xin:update_text_files, feature/13505-update-whisperback-text-files
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
WhisperBack
Deliverable for:

Description

I found few errors in Whisperback text files.

Subtasks

History

#1 Updated by intrigeri 2017-07-25 09:43:33

  • Priority changed from Low to Normal

#2 Updated by bertagaz 2017-07-28 10:31:14

  • % Done changed from 50 to 70
  • Feature Branch changed from xin:update_text_files to xin:update_text_files, feature/13505-update-whisperback-text-files

Built the package and uploaded it in a dedicated APT overlay. Will let Jenkins give it a try. Given the scope of the change it should work fine. Thanks for the fixes!

#3 Updated by bertagaz 2017-07-31 10:13:50

  • Status changed from In Progress to Fix committed
  • Assignee deleted (bertagaz)
  • % Done changed from 70 to 100
  • QA Check changed from Ready for QA to Pass

bertagaz wrote:
> Built the package and uploaded it in a dedicated APT overlay. Will let Jenkins give it a try. Given the scope of the change it should work fine. Thanks for the fixes!

Seems to work fine as expected, merged into stable and devel, congrats!

#4 Updated by bertagaz 2017-08-09 12:38:27

  • Status changed from Fix committed to Resolved

#5 Updated by xin 2017-09-29 00:40:08

  • Status changed from Resolved to In Progress
  • Assignee set to anonym
  • Target version changed from Tails_3.1 to Tails_3.3
  • % Done changed from 100 to 70

These changes appear in 3.1 (Whisperback version 1.7.12) but not in 3.2 (Whisperback version 1.7.13).
What happened?

#6 Updated by intrigeri 2017-09-29 08:36:25

> These changes appear in 3.1 (Whisperback version 1.7.12) but not in 3.2 (Whisperback version 1.7.13). What happened?

I see neither 1.7.12 nor 1.7.13 in Git, so I suspect that the person who prepared 1.7.12 failed to push, and then the person who prepared 1.7.13 could not pull and base 1.7.13 on top of 1.7.12. anonym, can you please sort this out?

#7 Updated by intrigeri 2017-11-06 16:03:56

  • Assignee changed from anonym to bertagaz
  • Priority changed from Normal to High

bertagaz, can you please push 1.7.12 and then reassign to anonym, asking him to push 1.7.13?

#8 Updated by anonym 2017-11-15 11:30:54

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

#9 Updated by intrigeri 2017-12-23 08:44:21

  • Assignee changed from bertagaz to anonym

intrigeri wrote:
> bertagaz, can you please push 1.7.12 and then reassign to anonym, asking him to push 1.7.13?

bertagaz pushed and told me a couple weeks ago he was going to reassign to anonym, but this did not happen yet. One of these cases when it’s cheaper for me to do it myself than to track progress.

So anonym, please push 1.7.13 to Git.

#10 Updated by anonym 2017-12-28 16:31:02

  • Status changed from In Progress to Resolved
  • Assignee deleted (anonym)
  • % Done changed from 70 to 100

Done!

#11 Updated by intrigeri 2017-12-29 09:41:38

  • Status changed from Resolved to Fix committed

This will be resolved once a new WhisperBack release (with the fixes, this time) is uploaded.

#12 Updated by intrigeri 2018-01-04 18:26:35

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

#13 Updated by anonym 2018-01-09 20:51:29

  • Status changed from Fix committed to Resolved