summaryrefslogtreecommitdiff
path: root/infra/README.Debian-NEW
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2015-03-17 21:56:41 +0000
committerIan Jackson <ijackson@chiark.greenend.org.uk>2015-03-22 15:18:54 +0000
commit379f4be6fc6ce15641bd7412dce3e71ca11ece00 (patch)
treee5e06b7485cf0b1f9362e898e00bf4112beaea71 /infra/README.Debian-NEW
parentbd14b12dc5968943106f05f1a869afd290c2e2a5 (diff)
WIP Debian policy
More notes and also some code
Diffstat (limited to 'infra/README.Debian-NEW')
-rw-r--r--infra/README.Debian-NEW41
1 files changed, 16 insertions, 25 deletions
diff --git a/infra/README.Debian-NEW b/infra/README.Debian-NEW
index 50112bf..da7fd59 100644
--- a/infra/README.Debian-NEW
+++ b/infra/README.Debian-NEW
@@ -1,36 +1,27 @@
-let us assume that it is not possible for new to have a version older than sid
-
-
-Whenever pushing, check for
- source-package-local tainted history
- global tainted history
- can be overridded by --deliberately except for an admin prohib taint
+======
-ALL of the following apply only if history is secret
+policy hooks:
-if NEW has a version which is in our history[1]
- (on push only)
- require explicit specification of one of
- --deliberately-include-questionable-history
- --deliberately-not-fast-forward
- (will taint old NEW version --d-i-q-h)
- (otherwise)
- leave it be
+ - cron check thing
+ implement `(always)' above
+ - in dispatch, on check or push, during package selection
+ implement `(always)' above
-if NEW has no version, or a version which is not in our history[1]
- (always)
- check all suites
- if any suite's version is in our history[1], publish our history
- otherwise discard our history,
- tainting --deliberately-include-questionable-history
+ - in dgit-repos-server, run policy hook after parsing tag
+ but before ff check; passing policy hook the deliberatelies
+ policy hook may:
+ - if appropriate blow away existing repo, copy old taints and add taints
+ - check taints
+ - fail if unused deliberatelies
+ - indicate to parent whether to disregard ff check
+ - remove taints which were overridden
-[1] looking for the relevant git tag for the version number and not
- caring what that tag looks for
+on push encode --deliberately in tag as lines
+ [dgit --deliberately-blah]
======
-
Want some invariants or properties
- .dsc of published dgit package will have corresponding publicly