It seems that marking /etc/sbackup.conf and /etc/cron.d/sbackup as conffiles 
was a packaging mistake. I will create a small update and see if MOTU will let 
it enter Edgy. It is in a freeze after all.
Newer sbackup can handle configuration files from older versions and will 
update it when the configurator is run.

** Changed in: sbackup (Ubuntu)
     Assignee: (unassigned) => Aigars Mahinovs
       Status: Unconfirmed => Confirmed

-- 
Dapper -> Edgy failure: sbackup configuration file has conflicts
https://launchpad.net/bugs/63354

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to