Raphael Hertzog wrote:
> -maintainer_script_alternative(pkg, PRERMFILE, "pre-removal", cidir,
> cidirrest,
> - "upgrade", "failed-upgrade");
> +if (versioncompare(&pkg->available.version,
> + &pkg->installed.version) > 0) /* Upgrade *
Raphael Hertzog writes:
> I would thus like to discuss 2 ideas:
> 1/ I'd argue that in the case of downgrade, dpkg should not try to run
>the failed-upgrade fallback because there's no way the oldest version
>can be aware of how to work-around a problem in a prerm script of a
>newer
Hi,
On Sat, 18 Jun 2011, Jonathan Nieder wrote:
> Raphael Hertzog wrote:
> > 1/ I'd argue that in the case of downgrade, dpkg should not try to run
> >the failed-upgrade fallback because there's no way the oldest version
> >can be aware of how to work-around a problem in a prerm script of
Hi Raphael,
Raphael Hertzog wrote:
> 1/ I'd argue that in the case of downgrade, dpkg should not try to run
>the failed-upgrade fallback because there's no way the oldest version
>can be aware of how to work-around a problem in a prerm script of a
>newer version that did not exist at
Hi,
to better understand this mail you can refer to this diagram
http://people.debian.org/~srivasta/MaintainerScripts.html#sec-3.4.3
During an upgrade from V1 to V2, if "V1->prerm upgrade V2" fails, dpkg tries
to run "V2->prerm failed-upgrade V1" and if it works the upgrade
continues normally.
T
5 matches
Mail list logo