Re: what if a package needs to be "recalled"

To: debian-devel@lists.debian.org
Cc: jidanni@jidanni.org
Subject: Re: what if a package needs to be "recalled"
From: Jonathan Nieder <jrnieder@gmail.com>
Date: Sun, 20 Nov 2011 18:09:58 -0600
Message-id: <[🔎] 20111121000958.GA11473@elie.hsd1.il.comcast.net>
In-reply-to: <[🔎] a2ef74dc-b5c1-4444-a79f-696ecfff1cb4@email.android.com>
References: <[🔎] 8739dil62y.fsf@jidanni.org> <[🔎] a2ef74dc-b5c1-4444-a79f-696ecfff1cb4@email.android.com>

Russell Coker wrote:

> Isn't this one of the reasons for the epoch field?

No.  If chromium 14.0.835.202~r103287-1 actually worked[1], the
thing to do would be to upload a package with version number
15.0.874.106~r107270+really14.0.835.202~r103287-1.  That way,
the blip in version numbering can be only temporary.

[1] Alas, it doesn't work: http://bugs.debian.org/649378

Reply to:

References:
- what if a package needs to be "recalled"
  - From: jidanni@jidanni.org
- Re: what if a package needs to be "recalled"
  - From: Russell Coker <russell@coker.com.au>

Prev by Date: Appreciation
Next by Date: re: what if a package needs to be "recalled"
Previous by thread: Re: what if a package needs to be "recalled"
Next by thread: re: what if a package needs to be "recalled"
Index(es):
- Date
- Thread