Olivier Berger wrote:

era eriksson <[EMAIL PROTECTED]> writes:


In <http://bugs.debian.org/296461>, you write:
> In order to upgrade from a previous twiki installation, the
> upstream script UpgradeTwiki is quite [useful].

If you are using a Debian package, you should not be updating things
in place. dpkg will be rightfully upset if you change an installed
package behind its back.


It's about upgrading the data (i.e. the standard set of pages, the
preferences, the templates, all kind of stuff that twiki uses in order
to work well, beyond the scripts).

/var/lib/twiki/templates is correctly managed by dpkg and there shouldn't be an automatic merge of local changes for the standard set of files.
Instead of changes to these files one should have set up a custom skin.


For the debian package UpgradeTwiki should not handle anything but /var/lib/twiki/data/... and the conffiles (that's all it does I think).
That should be ok with dpkg as it does not manage /var/lib/twiki/data/...


But anyways, this will require a human intervention at all
cases... and a bit of understanding of a diff/merge tool.


What's wrong about running it from postinst on upgrade?

Regards,
   Christopher


-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to