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 *
(new) developers-reference-de_3.4.5_all.deb optional doc
guidelines and information for Debian developers, in German
This package contains the German translation of Debian Developer's
Reference (package: developers-reference), a set of guidelines and
best practices which has been established by
developers-reference_3.4.5_amd64.changes uploaded successfully to localhost
along with the files:
developers-reference_3.4.5.dsc
developers-reference_3.4.5.tar.bz2
developers-reference_3.4.5_all.deb
developers-reference-de_3.4.5_all.deb
developers-reference-fr_3.4.5_all.deb
developers-r
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
5 matches
Mail list logo