X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=setup%2FREADME;h=d53fb229a945a48a39a3819340c402aea889e5ff;hb=4f3c7874fd19d380b106a9d4bbab0403ed089359;hp=140ead9192b88a07faa830c632f86f98b9755e9f;hpb=d765a7525626d13bfdeb4fc56e5f264a7ac86ce8;p=dak.git

diff --git a/setup/README b/setup/README
index 140ead91..d53fb229 100644
--- a/setup/README
+++ b/setup/README
@@ -2,14 +2,14 @@ Initialising a dak database schema
 ==================================
 
 The following packages are needed for the database:
- * postgresql-9.1 postgresql-client-9.1 postgresql-9.1-debversion
+ * postgresql-9.4 postgresql-client-9.4 postgresql-9.4-debversion
 and the following packages for dak itself:
  * python-psycopg2 python-sqlalchemy python-apt gnupg dpkg-dev lintian
    binutils-multiarch python-yaml less python-ldap python-pyrss2gen python-rrdtool
-   symlinks python-debian
+   symlinks python-debian python-debianbts
 
 (the schema assumes at least postgresql 9.1; ftpmaster in Debian currently uses
-the squeeze postgresql 9.1 backport)
+the postgresql 9.4 version from Debian 8)
 
 The following roles are assumed to exist:
  * dak: database superuser: needs to be an actual user
@@ -20,8 +20,8 @@ The following roles are assumed to exist:
 For the purposes of this document, we'll be working in /srv/dak
 
 Set up the dak user:
-# sudo addgroup --system ftpmaster
-# sudo adduser --system dak --ingroup ftpmaster --shell /bin/bash
+# sudo addgroup ftpmaster
+# sudo adduser dak --disabled-login --ingroup ftpmaster --shell /bin/bash
 
 Create postgres roles and database:
 # sudo -u postgres psql
@@ -100,6 +100,9 @@ Add a suite (origin=, label= and codename= are optional)
 signingkey= will ensure that Release files are signed
 # dak admin suite add-all-arches unstable x.y.z origin=MyDistro label=Master codename=sid signingkey=DDDDDDDD
 
+Add the components to the suite
+# dak admin s-c add unstable main contrib non-free
+
 Re-run dak init-dirs to add new suite directories to /srv/dak
 # dak init-dirs
 
@@ -112,41 +115,27 @@ for AMD64 and copied it into /srv/dak/queue/unchecked.
 
 We start by performing initial package checks which will
 result in the package being moved to NEW
-# cd /srv/dak/queue/unchecked
-# dak process-upload *.changes
+# dak process-upload -d /srv/dak/queue/unchecked
 
 -----------------------------------------------------------------------
 hello_2.6-1_amd64.changes
-NEW for unstable
-
 
-(new) hello_2.6-1.debian.tar.gz optional devel
-(new) hello_2.6-1.dsc optional devel
-(new) hello_2.6-1_amd64.deb optional devel
-The classic greeting, and a good example
- The GNU hello program produces a familiar, friendly greeting.  It
- allows non-programmers to use a classic computer science tool which
- would otherwise be unavailable to them.
+hello (2.6-1) unstable; urgency=low
  .
- Seriously, though: this is an example of how to do a Debian package.
- It is the Debian version of the GNU Project's `hello world' program
- (which is itself an example for the GNU Project).
-(new) hello_2.6.orig.tar.gz optional devel
-Changes: hello (2.6-1) unstable; urgency=low
- .
-  * New upstream release.
-  * Drop unused INSTALL_PROGRAM stuff.
-  * Switch to 3.0 (quilt) source format.
-  * Standards-Version: 3.9.1 (no special changes for this).
-
+   * New upstream release.
+   * Drop unused INSTALL_PROGRAM stuff.
+   * Switch to 3.0 (quilt) source format.
+   * Standards-Version: 3.9.1 (no special changes for this).
 
-Override entries for your package:
+source:hello
+binary:hello
 
-Announcing to debian-devel-changes@lists.debian.org
+binary:hello is NEW.
+source:hello is NEW.
 
-[N]ew, Skip, Quit ?N
-Moving to NEW queue.
-Sending new ack.
+[N]ew, Skip, Quit ? N
+ACCEPT-TO-NEW
+Installed 1 package set, 646 KB.
 -----------------------------------------------------------------------
 
 We can now look at the NEW queue-report
@@ -155,29 +144,33 @@ We can now look at the NEW queue-report
 NEW
 ---
 
-hello | 2.6-1 | source amd64 | 5 seconds old
+hello | 2.6-1 | source amd64 | 42 seconds old
 
-1 new source package / 1 new package in total.
+1 new source package / 1 new package in total / 0 new package to be processed.
 -----------------------------------------------------------------------
 
 And we can then process the NEW queue:
-# cd /srv/dak/queue/new
-# dak process-new *.changes
+# dak process-new
 
 -----------------------------------------------------------------------
 hello_2.6-1_amd64.changes
+-------------------------
+
+   Target:     unstable
+   Changed-By: Santiago Vila <sanvila@debian.org>
+
 NEW
 
 hello                optional             devel
+dsc:hello            extra                misc
 Add overrides, Edit overrides, Check, Manual reject, Note edit, Prod, [S]kip, Quit ?A
-ACCEPT
+PENDING ACCEPT
 -----------------------------------------------------------------------
 
 At this stage, the package has been marked as ACCEPTed from NEW.
 We now need to process the NEW policy queue:
 
 # dak process-policy new
-
 -----------------------------------------------------------------------
 Processing changes file: hello_2.6-1_amd64.changes
   ACCEPT
@@ -205,6 +198,8 @@ And finally, we can generate the signed Release files:
 # dak generate-release
 
 -----------------------------------------------------------------------
+Processing new
+Processing byhand
 Processing unstable
 -----------------------------------------------------------------------
 (Look at /srv/dak/ftp/dists/unstable/Release, Release.gpg and InRelease)