Privoxy

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

No, I'm just saying user.config and user.filter are overwritten
Thanks, I followed the instructions somewhere getting only the "current"
part.

Thanks for the report.

I think the script you are looking for is:
http://ijbswa.cvs.sourceforge.net/viewvc/*checkout*/ijbswa/winsetup/privoxy_winthreads.nsi

Quote:
; save files the user might have changed
; config.txt match-all.action trust.txt user.action
user.filter
; NOTE: rename fails if the destination file already exists
;
[...]

Are you saying this worked for all files but user.action?

3.0.16 still overwrites user.action

http://config.privoxy.org/user-manual/actions-file.html says
user.action - ... will not be upgraded.
This means in my opinion, no overwriting, conclusion: it's a bug.

I could take the installation for windows (I've good knowledge in NSIS)
but the install script is not part of the cvs-repository.

Sigh; that OS/2 comment was me. Forgot to sign in after navigating here
from email.

I went through this issue with OS/2. The way I ended up handling it is to
have the various default config files copied in as 'whatever.new,' then the
installer copies 'whatever.new' over to 'whatever' if 'whatever' didn't
exist before. If there was a prior installation, and there is a
depreciated (and now fatal) keyword, Privoxy doesn't start any more. Or
you get complaints in the log. But at least nobody's changes are
overwritten, and you have the .new files you can look at to find out how
things changed.

I'd leave the status as open.

I agree that the current behavior isn't a bug, but it would be nice if the
installer at least preserved the old files by renaming them.

> If the internal format of 'config.txt' has not changed

I wouldn't even try to do that. Not everyone upgrades when a new version
is released, so you'd first have to figure out what version of Privoxy is
installed before deciding if the old config.txt was compatable with the
version of Privoxy being installed. But if you can figure out how to do
that ... patches are welcome :)

Lee

The installation process is documented to work that way on platforms
without a proper package infrastructure:
http://config.privoxy.org/user-manual/whatsnew.html#UPGRADERSNOTE

Patches are welcome of course, but I don't consider this a Privoxy bug.

Leaving the request open for now, in case Lee disagrees.