I hadn't seen that, thanks. However, I consider it an iceowl issue
rather than an iceowl-extension issue since a user may want to switch to
some other stand alone calendar program rather than to
iceowl-extension. In that case, he would need to export the iceowl
calendars to a standard format so that it could be imported to the other
program.
On 04/10/2012 07:55 AM, Olivier Berger wrote:
Hi.
On Tue, Apr 10, 2012 at 06:58:37AM -0400, Neil Roeth wrote:
Thanks, I didn't realize standalone iceowl had been removed from
Debian. I successfully switched to iceowl-extension. In order to
do that, I had to install iceowl and the older version of
calendar-timezones, export the calendars, then install
iceowl-extension and the newer version of calendar-timezones and
import the calendars. This is not something I would think a typical
user would be capable of doing. I expect some users will be
surprised when they upgrade to the next Debian release and they have
no way to retrieve any of their iceowl calendar data. It would be
nice if there were some way to alert them to export their calendars
before calendar-timezones is upgraded and makes iceowl unusable.
Maybe a transitional iceowl package with a pre-conf step that just
gives them the choice to either quit so they can export their
calendars, or continue?
You may also see #655703 which deals with that very same issue.
Hope this helps.
Best regards,
--
Neil Roeth
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
