Bug 7096 – Upgrade from 7.0-16819 to 7.0.1-17424 deletes settings

Bug 7096 - Upgrade from 7.0-16819 to 7.0.1-17424 deletes settings

Summary:

Upgrade from 7.0-16819 to 7.0.1-17424 deletes settings

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Misc
Version:	7.0
Platform:	PC Debian Linux

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-02-12 10:53 UTC by Me
Modified:	2008-02-12 12:06 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Me 2008-02-12 10:53:50 UTC

I upgraded from 7.0-16819 to 7.0.1-17424 today using apt-get.  It deleted all my settings without warning, and I had to go through the setup wizard etc. again.

  Fetched 18.9MB in 51s (365kB/s)
  (Reading database ... 47046 files and directories currently installed.)
  Preparing to replace squeezecenter 7.0-16819 (using .../squeezecenter_7.0.1-17424_all.deb) ...
  Stopping SqueezeCenter Audio Server.
  Unpacking replacement squeezecenter ...
  dpkg: warning - unable to delete old directory `/var/cache/squeezecenter': Directory not empty
  Setting up squeezecenter (7.0.1-17424) ...
  Installing new version of config file /etc/init.d/squeezecenter ...
  changed ownership of `/var/lib/squeezecenter/Plugins' to squeezecenter:nogroup
  changed ownership of `/var/lib/squeezecenter/prefs' to squeezecenter:nogroup
  changed ownership of `/var/lib/squeezecenter/cache' to squeezecenter:nogroup
  changed ownership of `/var/lib/squeezecenter' to squeezecenter:nogroup
  Starting SqueezeCenter Audio Server.

I am using vanilla Debian testing.

Comment 1 KDF 2008-02-12 11:25:14 UTC

upgrade paths within 7.0 builds is not considered critical, so adjusting severity.

Comment 2 Matt Wise 2008-02-12 11:28:06 UTC

This is a known issue. The build you upgraded from had its perference files in a different location. Upgrades from 7.0 (builds 17000+) will not cause this problem again.