On Wed, 7 May 1997, Christian Schwarz wrote:
> I'm thinking of two situations that we had several times now:
>
> - wrong distribution fields (forgotten frozen, etc.)
> - uploads for new packages that other people are already working on (this
> was the case for tetex, do you remember?)
>
> These things can be fixed before dinstall installs the package if one is
> fast enough--this wasn't a problem in the past.
Maybe we ought to get dinstall to confirm an upload by email for
priority=low uploads (medium and high go through automatically).
> Perhaps you can split dinstall into two scripts: One script that is run,
> say once an hour, that just checks incoming for new uploads and posts the
> .changes files in the appropriate lists. This script could check for
> missing files, bad md5sums, bad pgp signs, etc.
Here's my idea:-
* Script 1 (darchive or something) will check the changes files,
look at the md5sums, PGP signatures, etc., and then ask for
confirmation by maintainers for priority low uploads. Priority
medium and high will automatically be passed to the second
script. This script will also send announcements to the lists.
* Script 2 (dqueue) will queue an archive installation. This is
run as a mail filter, and also by script 1 for medium and high
priority uploads. This script could also produce the reports,
and do some clever stuff, like merge the changelogs for multiple
versions of one package, then delete old files.
* Script 3 (dinstall) will run once per day, and simply installs
all the queued packages.
--
Tom Lees <tom@lpsg.demon.co.uk> http://www.lpsg.demon.co.uk/
PGP ID 87D4D065, fingerprint 2A 66 86 9D 02 4D A6 1E B8 A2 17 9D 4F 9B 89 D6
finger tom@master.debian.org for full public key (also available on keyservers)
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .