Bug #16631

Disable man-db.timer on Buster

Added by intrigeri 2019-04-05 06:59:33 . Updated 2019-04-05 10:15:30 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_4.0
Start date:
Due date:
% Done:

0%

Feature Branch:
https://salsa.debian.org/tails-team/tails/merge_requests/5
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

It’s about “Daily man-db regeneration” which we don’t care about in Tails. This service causes test failures due to “The system is not fully running yet”.

Subtasks

History

#1 Updated by intrigeri 2019-04-05 07:01:26

  • Subject changed from Disable man-db.service on Buster to Disable man-db.service and man-db.timer on Buster

#2 Updated by hefee 2019-04-05 07:17:50

  • Status changed from Confirmed to In Progress
  • Assignee set to hefee

#3 Updated by hefee 2019-04-05 08:57:37

  • Subject changed from Disable man-db.service and man-db.timer on Buster to Disable man-db.timer on Buster
  • QA Check set to Ready for QA
  • Feature Branch set to https://salsa.debian.org/tails-team/tails/merge_requests/5

As man-db.service is only triggered by man-db.timer, it is enough to mask man-db.timer in systemctl.

#4 Updated by intrigeri 2019-04-05 09:16:36

  • Assignee changed from hefee to intrigeri

#5 Updated by intrigeri 2019-04-05 09:51:07

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|4e9e6dcc094bc97d203d9093d69d1a211a83da82.

#6 Updated by intrigeri 2019-04-05 10:15:30

  • Assignee deleted (intrigeri)
  • % Done changed from 100 to 0
  • QA Check changed from Ready for QA to Pass