On Mon, Jul 07, 2003 at 02:07:34PM +0800, Niall Young wrote:
> > > How about a postrm::downgrade hook to reverse any changes made in the
> > > new version's preinst::upgrade so that when the old version's
> > > preinst::upgrade
> > > is a
age with some testing
> machine and only put in in the used archive when it suites your needs.
Agreed, I meant in *addition* to pre-deployment testing - say if testing
didn't pick up all bugs and you discover fatal problems post deployment.
> > How about a postrm::downgrade hook to rev
Andreas Metzler wrote:
> possible anyway, new packages, might use new file-formats which can be
> converted from the old-version but not back again.
Strictly speaking, any automatic conversion done during upgrades needs to be
injective and thus (theoretically) reversible for being correct.
Of cours
On Wednesday 02 July 2003 08:18, Niall Young wrote:
> How about a postrm::downgrade hook to reverse any changes made in the
> new version's preinst::upgrade so that when the old version's
> preinst::upgrade is applied you're not left with a potential mix of
> configur
aced.
>
> How about a postrm::downgrade hook to reverse any changes made in the
> new version's preinst::upgrade so that when the old version's preinst::upgrade
> is applied you're not left with a potential mix of configuration?
>
> I'm using a custom package po
aced.
>
> How about a postrm::downgrade hook to reverse any changes made in the
> new version's preinst::upgrade so that when the old version's preinst::upgrade
> is applied you're not left with a potential mix of configuration?
>
> I'm using a custom package po
* Niall Young <[EMAIL PROTECTED]> [030702 16:53]:
> I'm using a custom package pool for deploying software, but we need to
> cleanly rollback if an upgrade doesn't go as expected.
In easy cases it is possible to first test a package with some testing
machine and only put in in the used archive w
I'm aware you can downgrade packages with
`apt-get --force-yes install package=version-revision`
but this doesn't seem to apply any postrm processing on the existing
version of the package being replaced.
How about a postrm::downgrade hook to reverse any changes made in the
new
8 matches
Mail list logo
