Comment 2 for bug 317822

I have attached the diff. If I decompress the tellico archives, I get
the same content, but if I run the diff over the binaries, they are
different. Not sure why.

Thanx for looking into this.

On Fri, Jan 16, 2009 at 2:42 PM, Peter Antoniac
<email address hidden> wrote:
> I tried to reproduce the bug without success. I even created a new Book collection just to make sure...
> I am using 1.3.2.
> Can you please do this test:
> 1. copy the file before opening it in tellico
> 2. open tellico, browse only, and close (so you need to save as you said)
> 3. then run a diff -Naur old new and report back...
>
> ** Tags added: regression
>
> --
> tellico always want to save the collection
> https://bugs.launchpad.net/bugs/317822
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "tellico" source package in Ubuntu: New
>
> Bug description:
> Binary package hint: tellico
>
> 1. Ubuntu 8.10
>
> 2. tellico:
> Installed: 1.3.3-1ubuntu1~8.10prevu1
> Candidate: 1.3.3-1ubuntu1~8.10prevu1
> Version table:
> *** 1.3.3-1ubuntu1~8.10prevu1 0
> 500 file: ./ Packages
> 100 /var/lib/dpkg/status
> 1.3.2.1-1ubuntu1 0
> 500 http://de.archive.ubuntu.com intrepid/universe Packages
>
> 3. open a tellico book collection, browse some items, close tellico
>
> 4. if I browse the collection, the collection is marked as changed and I get a dialog asking me if I want to save the changes when I try to close tellico. This should not happen, unless I really change something like editing, adding or removing an item or changing the collection fields. Simply browsing should not mark the collection as 'dirty'. This is annoying, shorten the life of my hardware (if I keep my collection on an USB stick, saving the collection all the time can shorten its life), produce unwanted saves (if I save all the time, just to be sure nothing important is lost) or produce data loss (if I don't save because I forgot I really changed something).
>
> The collection is not marked if I simply open it, but not browse it. This bug is present in both 1.3.2 and 1.3.3.
>