Re: RFC: allow new upstream into stable when it's the only way to fix security issues.

To: Roland Rosenfeld <roland@spinnaker.de>
Cc: debian-devel@lists.debian.org
Subject: Re: RFC: allow new upstream into stable when it's the only way to fix security issues.
From: "W. Borgert" <debacle@debian.org>
Date: Mon, 1 Aug 2005 07:03:28 +0000
Message-id: <[🔎] 20050801070328.GA4112@k6.in-berlin.de>
Reply-to: debacle@debian.org
In-reply-to: <dcji2e$7de$1@luv.sail.spinnaker.de>
References: <200507312310.11473@sercond.localdomain> <200507312310.11473@sercond.localdomain> <20050731205045.GA4855@k6.in-berlin.de> <dcji2e$7de$1@luv.sail.spinnaker.de>

On Sun, Jul 31, 2005 at 10:07:10PM +0000, Roland Rosenfeld wrote:
> But how do you push the users to remove the package from their
> systems?  In reality they will keep the broken version installed and
> so you have (1) again :-(

Empty package with a higher version number?

Cheers, WB

Reply to:

Follow-Ups:
- Re: RFC: allow new upstream into stable when it's the only way to fix security issues.
  - From: md@Linux.IT (Marco d'Itri)

Prev by Date: Re: Public service announcement about Policy 10.4
Next by Date: Bug#320744: ITP: libphp5-memcache -- memcached extensions module for php5
Previous by thread: Re: RFC: allow new upstream into stable when it's the only way to fix security issues.
Next by thread: Re: RFC: allow new upstream into stable when it's the only way to fix security issues.
Index(es):
- Date
- Thread