Bug #12537

Killall is not installed in the VM

Added by arnaud 2017-05-12 00:56:22 . Updated 2017-05-12 09:46:18 .

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2017-05-12
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The commit 75060eee (on the branch feature/stretch) introduce the command killall, see the diff here:

https://labs.riseup.net/code/projects/tails/repository/revisions/75060eeee5f87e1aac472ebeb4596b2a7e3df2f3/diff/vagrant/provision/assets/build-tails

However killall is not installed on the VM, hence the failure:

+ sudo killall -q gpg-agent
sudo: killall: command not found
rake aborted!

Either it needs to be installed, either pkill should be use instead.

Subtasks

Related issues

Related to Tails - Bug #12527: Duplicate gpg-agent killing code introduced in the build-tails script Resolved 2017-05-10

History

#1 Updated by arnaud 2017-05-12 00:58:34

It tried replacing killall by pkill and it works fine.

#2 Updated by intrigeri 2017-05-12 07:52:41

  • Assignee set to bertagaz

That was fixed yesterday, wasn’t it?

#3 Updated by bertagaz 2017-05-12 08:50:48

  • Status changed from New to Duplicate
  • Assignee deleted (bertagaz)

intrigeri wrote:
> That was fixed yesterday, wasn’t it?

Yes, I’ll merge that today. Thanks arnaud for noticing and reporting.

#4 Updated by bertagaz 2017-05-12 08:52:32

  • related to Bug #12527: Duplicate gpg-agent killing code introduced in the build-tails script added

#5 Updated by bertagaz 2017-05-12 09:11:59

  • Status changed from Duplicate to New
  • Assignee set to arnaud
  • QA Check set to Info Needed

arnaud wrote:
> However killall is not installed on the VM, hence the failure:

Wait, now I’m wondering just in case: do you remember which branch you were building when you saw this failure?

#6 Updated by arnaud 2017-05-12 09:32:33

Yes,, it was on `feature/stretch`.

#7 Updated by intrigeri 2017-05-12 09:34:05

  • Assignee changed from arnaud to bertagaz

> Wait, now I’m wondering just in case: do you remember which branch you were building when you saw this failure?

See the ticket description.

#8 Updated by bertagaz 2017-05-12 09:46:18

  • Status changed from New to Duplicate
  • Assignee deleted (bertagaz)
  • QA Check deleted (Info Needed)

intrigeri wrote:
> > Wait, now I’m wondering just in case: do you remember which branch you were building when you saw this failure?
>
> See the ticket description.

Right! Not enough coffee yet I guess, thanks! :)