Bug #8704

reprepro's GnuPG keyring is not automatically updated

Added by intrigeri 2015-01-15 05:46:21 . Updated 2015-03-28 10:57:34 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_1.3.2
Start date:
2015-01-15
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Whenever a key that’s in reprepro’s keyring has its expiration date reached and postponed, the corresponding contributor is denied write access to our APT repository.

Subtasks

History

#1 Updated by intrigeri 2015-03-16 18:17:17

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to bertagaz
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

Done in tails::reprepro, with a systemd unit file that manages a parcimonie instance running as the reprepro user. sudo journalctl -u parcimonie-reprepro.service confirms it works fine, and has already refreshed one expired key.

#2 Updated by bertagaz 2015-03-28 10:57:34

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

I’m not very teased by the unit file content being in the manifest, and not in a dedicated file sourced by the manifest, but I guess for such a tiny snippet, that’s enough.
I’ve fixed a typo in the Debian version test, but otherwise it seems to work, so I close this bug.