Opened 9 years ago

Closed 8 years ago

#23970 closed defect (fixed)

Updating privoxy deletes all customization

Reported by: lagrave+bugs+macosforge.org@… Owned by: kimuraw (kimura wataru)
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc:
Port: privoxy

Description (last modified by jmroot (Joshua Root))

I just updated all installed ports, including privoxy, using this command:

% port -c upgrade installed

Running this generated the following output:

--->  Verifying checksum(s) for privoxy
--->  Extracting privoxy
--->  Configuring privoxy
--->  Building privoxy
--->  Staging privoxy into destroot
--->  Creating launchd control script
###########################################################
# A startup item has been generated that will aid in
# starting privoxy with launchd. It is disabled
# by default. Execute the following command to start it,
# and to cause it to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/org.macports.Privoxy.plist
###########################################################
--->  Deactivating privoxy @3.0.12_0+darwin
--->  Computing dependencies for privoxy
--->  Installing privoxy @3.0.16_0+darwin
--->  Activating privoxy @3.0.16_0+darwin
Error: Target org.macports.activate returned: error copying "/opt/local/etc/privoxy/config.new": no such file or directory

After the update was finished I tried to run the launchctl command described above but privoxy didn't start. I then

% ls /opt/local/etc/privoxy/

config.new-dist         match-all.action.new    user.action.new-dist
default.action          templates/              user.filter.new-dist
default.filter          trust.new-dist

I had modified user.action and user.filter heavily and now they seem to have been deleted when updating. Besides, "config" is also missing after this update which prevents privoxy from starting.

To me, the update script seems really broken.

Change History (4)

comment:2 Changed 9 years ago by jmroot (Joshua Root)

Description: modified (diff)
Keywords: updating privoxy removed

comment:3 Changed 9 years ago by hoanqui@…

Same thing here. Looks like the existing config files were renamed to *.new-dist, and later the script tried to rename them again from *.new - so it fails. However, I tried changing that in the script and it still failed; maybe because of the state in which the installation had been stopped. Finally I managed to install and start Privoxy again after some barrage of uninstalls and installs and unloads and loads. No detailed fix, sorry.

comment:4 Changed 8 years ago by kimuraw (kimura wataru)

Owner: changed from macports-tickets@… to kimuraw@…
Status: newassigned

I surveyed this problem.

default privoxy installation:

  • NEW -> install config files under etc/privoxy/ without suffix
  • UPG -> install config files under etc/privoxy/ with suffix ".new" (keep previous config files)

macports' privoxy installation:

  • NEW -> install config files under etc/privoxy/ without suffix
  • UPG1 -> install config files under etc/privoxy/ with suffix ".new-dist" (delete config files without suffix)
  • UPG2 -> install config files under etc/privoxy/ with suffix ".new-dist" (NOT delete config files without suffix)

MacPorts always should install config files with suffix ".new" and copy to config files without suffix when the files do not exist.

comment:5 Changed 8 years ago by kimuraw (kimura wataru)

Resolution: fixed
Status: assignedclosed

I fixed this problem at r75015.

port:privoxy always installs .new config files as same as default privoxy installation.

if port:privoxy was installed before this fix, macports backups config files with suffix .mp_backup and restore the files at activate.

Note: See TracTickets for help on using tickets.