Dear Maintainer,

If more the one copy of Cherry Tree is open at a time

- Auto save sometimes fails.

- Changes to the the 2nd instance of Cherry Tree are not always saved to disk,
even though the save button was clicked, and Cherry Tree was closed out.

- Given the above, the program should not allow more then one instance of
Cherry Tree per session.

Dear submitter,

as the package cherrytree has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/947338

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

A new version of cherrytree is available in Debian unstable, it would
be great if you could check to see if it fixes the issues above.

control: severity 867787 important

Hello,

The highlighted problems with running more than one instance of
CherryTree are important, but I do not think they are serious enough to
keep CherryTree from appearing in the next Debian release. Moreover,
CherryTree has since been rewritten in C++ and the issue may have been
solved on the way. To repeat Paul, it would be great if you could check
if the issue is still there.

In any way I believe this issue is not Debian-specific. Thus if it
persists, it should be reported and solved upstream, either by locking
CherryTree file by one of the instances, or by forbidding running more
than one instance of CherryTree.

Best,
Andrius

The submitter has stated off the bug that they don't wish to risk
losing their database by upgrading to the latest version.

So someone else who uses CherryTree needs to test this.

Hello,

I have tried reproducing your bug report [1] using cherrytree v0.99.25
(newest release at the time of writing). 2nd instance now seems to be
able to save changes, and the 1st instance fails trying to autosave on
top of the changed document due to SQLite constraint.

AFAIK, not all changes may result in SQLite constraint failures, and
surely there are other formats to store data than SQLite. However,
ability to save changes in 2nd instance is an improvement, although I
think that running multiple instances should still be forbidden.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867787

Best,
Andrius