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

Re: Remove fwupdate from the archive

<Mario.Limonciello@dell.com> writes:
> On Sep 2, 2019 11:06, Steve McIntyre <steve@einval.com> wrote:
> On Mon, Sep 02, 2019 at 09:34:27AM +0200, Ansgar wrote:
>>Scott Kitterman writes:
>>> You can override the version of particular binaries.  Here's an
>>> example (IIRC gcc-defaults is another):
>>Or you can just built the transitional package from src:fwupdate.
> Nod, that's possibly easiest for now...
> If built from that source then it can't really be removed from the
> archive anymore though can it?

The fwupdate source package would get replaced with an empty husk, so it
is practically gone.  It can be removed once the transitional binary can
go away.

I did something similar when "clive" was replaced by "cclive": the
"clive" package became a transitional package with 2.3.3+cclive; it also
included a wrapper asking people to use "cclive" instead of "clive" in
the future.  Just as with fwupdate -> fwupd the replacement (cclive) had
a lower version number.

See `dget -x http://archive.debian.org/debian/pool/main/c/clive/clive_2.3.3+cclive.dsc`

This allows to not bother with epochs or messing with some packages
getting a different version number which is fragile and easy to get


Reply to: