@SysInclude{docf}
@SysInclude{tbl}
@Use { @BasicSetup
- @InitialFont { Times Base 20p }
+ @InitialFont { Times Base 18p }
}
@Use { @DocumentSetup
@PageOrientation { Landscape }
@Cell D }
bformat { @StartHSpan @Cell A | @HSpan | @HSpan | @HSpan }
{
-@Rowb A { dgit access to Debian for various classes of user //2vx }
-@Rowa A { } B { DD } C { DM } D { anonymous }
+@Rowb A { dgit access to Debian for various classes of user //1vx }
+@Rowa A { } B { DD |10m } C { DM } D { anonymous }
@Rowa
ruleabove { yes }
A { "fetch/" //1vx "clone" }
- B { {@Ding a19} @Sup 1 }
+ B { {@Ding a19} @Sup @Dagger,@DaggerDbl }
C { red @Colour { Needs projectb data service } //1vx
- "#727702", "#720590" }
+ "#727702", "#720590", @Dagger }
D { red @Colour { Needs projectb data service } //1vx
"#727702", "#720590" //1vx
red @Colour { Needs move to new git server } //1vx
@Rowa
ruleabove { yes }
A { "push" }
- B { {@Ding a19} @Sup 1 }
+ B { {@Ding a19} @Sup @Dagger,@DaggerDbl }
C { red @Colour { Needs move to new git server } //1vx
"#720173", DSA RT
}
- D { Not desired }
+ D { grey @Colour { Not desirable } }
}
@LP
@LP
Notes
@LP
-1. User must have alioth account; requirement will be abolished
+@Dagger. User must have alioth account; requirement will be abolished
after move to new git server.
+//1vx
+@DaggerDbl.
+
+{Courier Base 12p} @Font {
+"| ssh 'iwj@mirror.ftp-master.debian.org' 'export LANG=C; psql -A service=projectb -c '\\''" //1vx
+" SELECT source.version, component.name, files.filename, files.sha256sum" //1vx
+" FROM source" //1vx
+" JOIN src_associations ON source.id = src_associations.source" //1vx
+" JOIN suite ON suite.id = src_associations.suite" //1vx
+" JOIN dsc_files ON dsc_files.source = source.id" //1vx
+" ..."
+}
+
@End @Text
(QUILTY WORKFLOW)
+[ synthetic patch example ]
+
At the moment, dgit doesn't attempt to do anything clever with `3.0
(quilt)' source packages.
Overall this means that currently when you work on a quilty package in
dgit, you don't interact with the quilt patch stack. This is less
-than ideal and I intend to improve this, perhaps by having dgit use
-git-dpm as a bidirectional gateway between `3.0 (quilt)' and git.
+than ideal.
+
+I intend to improve this, perhaps by having dgit use git-dpm as a
+bidirectional gateway between `3.0 (quilt)' and git.
This will generate a rebasing-style git branch. After a patch series
has been edited with rebase, dgit push will have to generate a `fake
[table]
+Probably the biggest problem with dgit right now is that it is only
+useable for DDs. This is particularly galling for a tool which is
+especially useful for users, downstreams, mentees, and so forth.
+
+There are two obstacles to widening the access, relating to the
+archive and to the git server.
+
+Firstly, dgit needs to query the archive to find the current version
+of the package and obtain a copy of the .dsc. At the moment there is
+no official interface which provides this data. There is the rmadison
+server but it sometimes serves stale or wrong data and there is no
+authentication - that is, there is no way for the client to tell that
+the data is accurate. So what dgit does right now is ssh to coccia
+and run SQL commands against its mirror of the ftpmaster database.
+This is obviously mad. ftpmaster have promised me a proper query
+service API (via HTTP and TLS).
+
+Secondly, dgit is currently using alioth as its git server, and the
+collab-maint group there for authentication. This is not ideal for a
+number of reasons. Alioth does a lot of other things and is therefore
+less secure and reliable than would be ideal. dgit's required
+authentication model is not a very good fit for alioth's
+infrastructure. We intend to move this to a VM of its own - I've
+spoken to DSA (in the person of Tollef) about this.
-
- works well for DDs
- works badly for everyone else :-/
- serious problem, needs escalating
-
- access limitations
-
- ssh cocca psql -c SELECT BLAH
-
- ftpmaster have a plan to help with this but has not been implemented
-
- alioth collab-maint
-
- push by signed tag
-
- need to abandon alioth because of collab-maint security issues
-
-
-xxx adoption