Maybe uploading updated version of Marble, which reflect dependencies limitation (Monav up to 0.3release-1), is best idea?

It would just require fixing dependencies, so that isn't any much-hassle update (AFAIK). After Monav 0.4 (or any stable release) get released, Marble will most likely be updated again, to reflect file format changes, yes?

So, again AIUI, the most "proper" way would be to fix dependencies in Marble - that doesn't require pinning packages in apt-get or dpkg from user side, and doesn't interfere with Monav updates (Marble installation will require fixed version of Monav, so user won't install higher Monav, even with -devel enabled - due to dependency conflict. Still, development snapshots of Monav would get into -devel, without messing Marble up).

/Estel