Hi, after a long time there is a new problem with skrooge I've got.
New version (beta repository 1.7.4-0ubuntu1~beta1) comes with a new dependency on "libqjson"
this library is not included in regular repositories of kubuntu 12.04 LTS (not a trouble)
problem is when I've add a repo (kubuntu/backports) the library is call libqjson0 so package manager don't allow to install skrooge.
This is a huge problem. One of my machines is set to autoclean packages that aren't complete and because system tries but fails on installing skrooge-common, it also uninstalls skrooge. This way I've lost skrooge application and I'm unable to install it back.
Only version I'm able to get is 1.2.0-2, which is nice, but skrooge can only open documents created in current or past versions. Which in this case is impossible since my actual document is created by 1.7.2 (in which case version 1.7.1 in a stable won't really help)

What I'm asking for:
repair dependency, help me with dependency problem, or do something else with dependency to solve the problem
(in a meantime of repair) leave one version back in the repository, so it is possible to force install one version back (in a beta this should be "a must have") or
move a previous beta to stable (same solution as two versions in beta)

Thanks for great job you doing and for fast solution.

What error / notice does the package manager give when you try to install the newer version of Skrooge which depends on libqjson?

following packages have unmet dependencies:
skrooge : depends on: libqjson but it can't be installed

maybe little different, this is translation of my localized return message of apt-get install

in fact the package name on my system will be probably "libqjson0" which is installable and probably same thing. But I don't want to ruin my current installation (and only way to use current skrooge document) by trying to edit the skrooge deb packages dependecy configuration.

Do the Skrooge and libqjson packages come from the same repository?

Obviously not. Skrooge has it's own repository as newer version is available only there. I'm also a translator of skrooge, thus I need newer versions to see what's new.
I'm using beta repository. This still isn't a problem.
I know, I'm using possibly unstable version, but the problem is not in application itself. It is in a dependecy management. As I mentioned before, for me the very easy solution is to leave more versions in a beta repository. This way it is possible, even for beta users, to easily go back some versions which worked for them.
Biggest problem for me in this is dependency. Let's have package A with support lib A1 newer version would be B and B1, problem in here is B cannot be installed but B1 can, A cannot work with B1, so in the end after upgrade you end up with just B1 because A has to be removed and B cannot be installed.
A = skrooge, A1 = skrooge-common both 1.7.2
B = skrooge, B1 = skrooge-common both 1.7.4
I fully understand the logic of this. But cannot understand the innability to go back (A and A1 isn't in a repository anymore).

In conclusion:
I have no problem with this application intself.
I simply cannot installl newer version due to dependency problem.
I lost last (beta) version instalation because support package (scrooge-common) for the newer one can be installed.
I cannot instal older version (meaning the one I've lost).

EDIT:
I've even try to build skrooge (latest beta) and it works fine. So only thing I'm pointing out is different/wrong dependency name (could it be that ubuntu repos have different naming polict than kubuntu repository) and possibility to easily downgrade (keep more then on version in beta repository).

Hi,

I repackaged skrooge for ubuntu 12.04 with a prerequisits on libqjson0 instead of libqjson.

Great,
thanks a lot it is working now. (as expected)
Is that really a solution to that problem? I have no idea what is the name of that package (libqjson) in other debian based distros (.deb packages and repositories), this could cause problems elsewhere.
Sadly, I have no clue how to solve that properly (more repositories, meta packages,...)
And what about the possibility of more than one version of skrooge in beta repository, for example as many versions back as the latest stable version. Also why every new version changes a skrooge document unreadable for older versions (I understand other versions of sqlite do stuff differently, but is it allways the case).
Is it possible to make a tool for "degrading" skrooge document for older versions.

I know all this is requests for features regular user will never need, but...

Thanks again for such short response and for working on skrooge.

schunka wrote:Great,
thanks a lot it is working now. (as expected)
Is that really a solution to that problem? I have no idea what is the name of that package (libqjson) in other debian based distros (.deb packages and repositories), this could cause problems elsewhere.

The problem was not in Skrooge.
The problem was in the packaging of Skrooge for ubuntu because in 12.04 the package for QJson is libqjson0 and for 12.10 and 13.04 is libqjson.
So, no issue for other distribution.

schunka wrote:Sadly, I have no clue how to solve that properly (more repositories, meta packages,...)
And what about the possibility of more than one version of skrooge in beta repository, for example as many versions back as the latest stable version. Also why every new version changes a skrooge document unreadable for older versions (I understand other versions of sqlite do stuff differently, but is it allways the case).

In fact, the version of the document is not always link to the version of Skrooge.
The version of the document changes each time I need to change it for new feature, bug correction or performances.
The change is done automatically when the document is opened with the new version of Skooge.

schunka wrote:Is it possible to make a tool for "degrading" skrooge document for older versions.

This is too complex because how an old version of Skrooge (example: 1.6.0) can be able to manage correctly manage document produced by a future version of Skrooge (exemple: 2.5.0) not existing yet.

The solution is to export data with the new version and import in old version.

schunka wrote:
I know all this is requests for features regular user will never need, but...

Thanks again for such short response and for working on skrooge.