Re: DAK (2)

2002-12-10 Thread James Troup
Brian May <[EMAIL PROTECTED]> writes: > On Wed, Dec 11, 2002 at 01:11:08AM +, James Troup wrote: > > Err, bullshit, there's doc/*.1.sgml and --help for most of the key > > scripts. > > [1106] [snoopy:unstable:bam] ~/cvswork/dak >helena --help helena is not a key script. Try again. grep -lir

Re: DAK (2)

2002-12-10 Thread James Troup
Brian May <[EMAIL PROTECTED]> writes: > 5. What is the dsync-flist used by mkchecksums, and where can I get it > from? Google search returns nothing. http://cvs.debian.org/?cvsroot=dsync -- James

Re: DAK (2)

2002-12-10 Thread Brian May
On Wed, Dec 11, 2002 at 01:11:08AM +, James Troup wrote: > Err, bullshit, there's doc/*.1.sgml and --help for most of the key > scripts. [1106] [snoopy:unstable:bam] ~/cvswork/dak >helena --help Traceback (most recent call last): File "helena", line 206, in ? main(); File "helena", lin

Re: DAK (2)

2002-12-10 Thread James Troup
Brian May <[EMAIL PROTECTED]> writes: > If I were to clean things up and make DAK easier to use for private > archives (eg. by isolating all Debian specific stuff, ideally into > a limited number *.conf files), would somebody be willing > to commit the changes to CVS? No one sane agrees to pre-co

Re: DAK (2)

2002-12-09 Thread Brian May
On Tue, Dec 10, 2002 at 10:08:16AM +1100, Brian May wrote: > 1. For package installations, DAK will inform both the uploader and the >maintainer. For private archives should it inform the maintainer? >Maybe a message "Your package has been installed in the private >archive at http://...

Re: DAK (2)

2002-12-09 Thread Brian May
On Mon, Dec 09, 2002 at 01:21:09AM +, James Troup wrote: > Brian May <[EMAIL PROTECTED]> writes: > > > I looked at katie; it seemed to be a complicated and undocumented > > mess that was a total overkill for my purpose (eg. I don't need a > > database). > > That "complicated and undocumented