1 I am pleased to announce dgit 1.0, which can be used, as applicable,
2 by all contributors and downstreams.
4 dgit allows you to treat the Debian archive as if it were a git
5 repository, and get a git view of any package. If you have the
6 appropriate access rights you can do builds and uploads from git, and
7 other dgit users will see your git history.
9 (dgit's git histories are often disjoint from the maintainer's
10 history; this is because the dgit git tree has exactly the same
11 content as the archive, which maintainers' histories often don't.)
17 dgit 1.0 was just uploaded to unstable.
19 The source (latest found in sid) can be obtained via
22 The last dgitish upload of dgit itself can be found here
23 w3m https://browse.dgit.debian.org/dgit.git/
24 git clone https://git.dgit.debian.org/dgit
25 (but note that this would not reflect any NMUs not done with dgit.)
31 All existing users who are not running dgit 0.30 or later must
32 upgrade. dgit << 0.30 will not cope with git histories manipulated by
33 later dgit, and will crash trying to access now-moved-aside git
34 repositories on alioth. New versions of dgit accept old histories
35 (and fix them up if necessary).
38 Anonymous read-only access
39 --------------------------
41 dgit 1.0 can be used by anyone to get the source for packages in the
42 Debian archive. Changes can then be made in git, and binary packages
43 built using your favourite build tools. You can share changes made in
44 git in the normal gitish ways.
50 At the moment, the Debian Project lacks a database listing the public
51 ssh keys of DMs. The dgit push infrastructure requires the user's ssh
54 For now, this will be done manually. If you are a DM and would like
55 to use `dgit push', please send a GPG-signed copy of your ssh public
56 key to dgit-owner@debian.org.
62 The dgit 1.0 binary package which I have just uploaded to sid is
63 installable (simply with dpkg -i), and useable back to at least
66 The source builds on wheezy as-is. I hope that a formal backport will
70 Exciting uses of some of the dgit-repos on alioth
71 -------------------------------------------------
73 The previous location for the dgit git repositories was on alioth, in
74 /git/dgit-repos/repos, where they were writeable by the scm_collab-qa
75 and Debian groups. It appears that some contributors took advantage
76 of this (deliberately or perhaps accidentally) to store various
77 ancillary git branches and tags in the dgit git repos.
79 These extra branches and tags have not been reproduced in the new dgit
80 git service. (I intend for the dgit git service to become a general
81 purpose git server with access control similar to that of the Debian
82 archive, but for now it is not possible to manipulate the refs in the
83 dgit git service other than via dgit push.)
85 To prevent old dgits from accidentally operating on stale history, I
86 have moved these old repos on alioth aside, to
87 /git/dgit-repos/repos.now-on-gideon.
89 If you were using these as general-purpose git remotes, please copy
90 (or move) the data elsewhere.
96 I would like to thank DSA and ftpmaster.
98 ftpmaster have provided the new archive data API service, which
99 supports the anonymous queries needed for readonly use of dgit.
101 DSA have provided hosting for both the main dgit git service, and the
102 mirror used for read access. The support I have had from the DSA
103 team, and particularly Peter Palfrader, has been both excellent and
104 invaluable. Without their help none of this would have been possible.