[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [debian-devel] Status of mICQ code audit



Gerfried Fuchs wrote:
* Glenn Maynard <g_deb@zewt.org> [2003-04-23 03:30]:

If someone missed a meeting because a program they installed out of
Debian had a time bomb in it, they would be justified in questioning
their use of Debian, not just the application.


 No.  They would be justified in questioning their opinion in their
usage of _un_stable for critical services without a clue about what to
do in such a case (like keeping former version (dpkg-repack) or taking a
look at <http://snapshot.debian.net/> for older packages).

 There were _bader_ breakages in unstable than a single application.

 People depending on services on the one hand and using unstable on the
other hand should never blame the project for anything.

 Get a clue if you plan to live with unstable.
Alfie

The only point of a time bomb is to try to get a broken package into testing and/or stable...[Remember that there was seperate code that checked the current user and disabled the 'easter egg'/'malicious code' if the current user was the Debian maintainer]



Reply to: