diff options
author | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2015-07-11 14:30:27 +0100 |
---|---|---|
committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2015-07-11 19:31:09 +0100 |
commit | 8ee9e3edb66cb7af5aab96e44a2cfa0ff84b529a (patch) | |
tree | 1ff89937cd741968e75823696b9cb6afd2e9621c /dgit.1 | |
parent | 9184953b37fef6964d1545fda3832e8eaaba986d (diff) |
Documentation: dgit(1): Remove some obsolete caveats from BUGS.
Diffstat (limited to 'dgit.1')
-rw-r--r-- | dgit.1 | 25 |
1 files changed, 2 insertions, 23 deletions
@@ -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. |