[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Remote command interface for dak



Hi,

we need a remote control interface for dak if we want to move
DM-Upload-Allowed from the source package to just a field in a database
that developers can change.  It's also useful for ppas ;)

I suggest to implement a command file interface as we already use that
channel for uploads and queued already has a command file interface.

The command file (.dak-control?) will be moved by queued to unchecked
and be process by a to-be-written dak tool there.  The file itself would
follow the usual deb822 syntax and could look like this:

--8<---------------cut here---------------start------------->8---
Archive: ftp.debian.org

Action: dm
Fingerprint: [...]
Allow:
 a-source
 another-source
Deny:
 yet-another-source
Reason:
 Maybe we want people to say why they changed that.

Action: dm
Fingerprint: [...]
Deny:
 yet-another-source

Action: move
From: experimental
To: unstable
Source:
 some-package_0.1-1

Action: remove
From: ppa/test
Source:
 foo_0.1-1
Package:
 bar_0.2-1 i386
Reason:
 I don't like these packages.
--8<---------------cut here---------------end--------------->8---

The first section with the Archive field is there to prevent uploading
the command file to another installation if one uses the same key.

All other sections have a Action field to select what one wants to do.
The other fields depend on the action.

To prevent replays we can record the signature id and reject files we
see twice.

Ansgar


Reply to: