rpm 5.x in Th

[Elan Ruusamäe]

On 23/09/12 18:48, Jeffrey Johnson wrote:
> On Sep 23, 2012, at 4:43 AM, Tomasz Pala<gotar at polanet.pl>  wrote:
>
>> >
>> >Well, I might be wrong, but I think Lukasz expects something like
>> >rpm -Uvh/var/spool/repackage/[date range reversed]*/* --force --nomd5
>> >only - i.e. not actual transactions rollback, but package set restore
>> >(in proper order, thus preserving dependencies).
>> >
> One might expect whatever outcome one wishes …
> \
>> >Restoring filesystem state (including things altered by triggers etc.)
>> >is indeed dm/filesystem/backup software job and there's no point simulating
>> >it on one more level.
>> >
> … but triggers are executed as part of package management,
> changing file system state, and are not simply invertible.
>
> I do not understand your distinction.
>
> How is --rollback to be performed if operations are
> only partially reversed?
>

i'm sure people want just to get old package back, to revert human 
mistake of upgrading or some other reason for downgrade, because package 
is misbehaving, not wanting perfect rollback like filesystem rollback.

rolling back filesystem state really assumes nothing else happens in 
your filesystem than rpm packages. this is rarely true, there are logs, 
other writable data that you expect not to be "rolled back" if you just 
downgrade package.

call it something else than "rollback", if it hurts your perfect world

i my world, where i deploy software with rpm packages, i do poldek -u 
package-old-version --downgrade as i do have old versions available in 
package manager repository. but distro packages are not available that 
easily, therefore people look into /var/spool/repackage dir

-- 
glen