How to manage security issues when the maintainer is not the developer

To: debian-devel@lists.debian.org
Subject: How to manage security issues when the maintainer is not the developer
From: "Andrea De Iacovo" <andrea.de.iacovo@gmail.com>
Date: Wed, 16 Apr 2008 13:55:51 +0200
Message-id: <[🔎] fe088fa40804160455i67611674x7e4d78707f0ec75b@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all.

How do you think a maintainer should manage security issues when he is
not the package developer? Should he/she either work alone to make
patches or wait for the upstream patches/relases that solve the bug?

Andrea De Iacovo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIBejnMXahCK22/rwRAhl3AJ9/rP8FFSVqvz1+8bQu1PZHCLGjGQCfZQJ7
zCofl8Z64XpvIRBQklhQ3gQ=
=WToO
-----END PGP SIGNATURE-----

Reply to:

Follow-Ups:
- Re: How to manage security issues when the maintainer is not the developer
  - From: Mark Brown <broonie@sirena.org.uk>
- Re: How to manage security issues when the maintainer is not the developer
  - From: Neil Williams <codehelp@debian.org>
- Re: How to manage security issues when the maintainer is not the developer
  - From: Lars Wirzenius <liw@liw.fi>

Prev by Date: Re: uploading new binary packages from a DM approved source package
Next by Date: Re: How to manage security issues when the maintainer is not the developer
Previous by thread: Re: Should DMs be allowed to upload to NEW
Next by thread: Re: How to manage security issues when the maintainer is not the developer
Index(es):
- Date
- Thread