Documentation: dgit(1): Remove some obsolete caveats from BUGS.

diff --git a/debian/changelog b/debian/changelog
index d55f8ff20eae68023fe5cbf464ad33cce65a43db..610322e0c88a40e31ec4005fed45da5451b33bbc 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,12 @@
 dgit (0.31~~) unstable; urgency=low
 
+  Documentation:
+  * dgit(1): Remove some obsolete caveats from BUGS.
+
   Infrastructure:
   * Provide for mirroring git updates to a different server.
 
- -- Ian Jackson <ijackson@chiark.greenend.org.uk>  Sat, 11 Jul 2015 14:26:07 +0100
+ -- Ian Jackson <ijackson@chiark.greenend.org.uk>  Sat, 11 Jul 2015 14:30:19 +0100
 
 dgit (0.30) unstable; urgency=high
 

diff --git a/dgit.1 b/dgit.1
index 1c87e9a1f089cb2593f4a910745e58d466594a73..c569347e658bb6480e12072b0985c5dcef4670e1 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -637,25 +637,8 @@ and other subprograms and modules used by dgit are affected by various
 environment variables.  Consult the documentaton for those programs
 for details.
 .SH BUGS
-We should be using some kind of vhost/vpath setup for the git repos on
-alioth, so that they can be moved later if and when this turns out to
-be a good idea.
-
-dgit push should perhaps do `git push origin', or something similar,
-by default.
-
-Debian does not have a working rmadison server, so to find out what
-version of a package is in the archive, or to canonicalise suite
-names, we ssh directly into the ftpmaster server and run psql there to
-access the database.
-
-The mechanism for checking for and creating per-package repos on
-alioth is a hideous bodge.  One consequence is that dgit currently
-only works for people with push access.
-
-Debian Maintainers are currently not able to push, as there is not
-currently any mechanism for determining and honouring the archive's
-ideas about access control.  Currently only DDs can push.
+Debian Maintainers are currently not able to push, as the project
+lacks a list of their ssh keys (!)
 
 dgit's git representation of format `3.0 (quilt)' source packages does
 not represent the patch stack as git commits.  Currently the patch
@@ -689,10 +672,6 @@ remote tracking suite branch.
 
 The option parser requires values to be cuddled to the option name.
 
-dgit assumes knowledge of the archive database.  (The information dgit
-needs is not currently available via any public online service with a
-well-defined interface, let alone a secure one.)
-
 --dry-run does not always work properly, as not doing some of the git
 fetches may result in subsequent actions being different.  Doing a
 non-dry-run dgit fetch first will help.