Hi! * Gerfried Fuchs <[EMAIL PROTECTED]> [2005-11-23 10:53]: > * Jeroen van Wolffelaar <[EMAIL PROTECTED]> [2005-11-22 21:06]: >> Should != must. > > But you have to have a good reason to ignore it. I haven't heard any > (real) reason at all for it during the former changes in that respect > which were reverted because there was no reason available, and it still > breaks existing functionality.
And I found out the good reason for it myself, after some thinking.
Sorry for being picky, I'm going to outline the reasoning (at least as I
would see it and accept it) here, for others, like promised in private
discussion:
The ftp team is responsible for the content of the archive, and as
features with new parts get added they should add a check for it. The
best example is the current situation: Signatures created with dpkg-sig
should be checked on upload to avoid BADSIG in the pool. If the check
will be added later, like the current situation is, it is quite an
effort to check the things already in the pool if they might not go with
the standard.
Leaving the bugreport open until the fix gets added, though. :)
Alfie
--
To err is human, to moo bovine.
-- unknown
signature.asc
Description: Digital signature
