Re: problem replacing package
On Mon, Sep 09, 2002 at 08:06:58PM +0200, Matus fantomas Uhlar wrote:
> -> > -> That would require versioned dependencies on virtual packages (versioned
> -> > -> Provides:) to work, but they don't. You'll probably have to use
> -> > -> something like a high epoch instead.
> -> >
> -> > Pardon? Does that mean there's no possibility to provide one package bye
> -> > another one, for other packages' dependencies to work? hmmm :(
> ->
> -> Not if other packages declare *versioned* dependencies on it.
>
> hmmm should I now blame someone or is it unexpected situation that is not
> expected to happen and there is no solution now (except the one below)?
Or alternatively, someone could just fix the versioned dependencies in
dpkg/apt. But then, i suppose nobody was enough interrested by it.
> -> > And what do you mean 'high epoch'?
> ->
> -> Something like 'Version: 9:1.0.0-1'. The epoch forces that version
> -> number to compare higher than any version number with a lower epoch or
> -> no epoch. See policy section 4 ("Version numbering").
>
> OK, I will try, even if it's not exactly what I meaned.
Well, you could also use the ugly :
Provides: package_name-1.0.0 or something such.
Friendly,
Sven Luther
Reply to: