Comments

Anytime I install an app, warehouse becomes unresponsive. The OS says that the app is not responding anymore and I can choose between closing it or waiting. Updates rarely finish because of this; at least the successful finish is not displayed (the update itself seems to have worked since the app updated is available in a newer version).

You should name application with "harbour-" or "com.yourname.appdomain-" prefix to avoid conflicts with default system apps.
"ne" name is too short name, causing sailfishos PackageKit subsystem(which is used by Warehouse), to process all packages to find a reliable installed and available versions on the phone to show the details.

I have a problem with warehouse. Today it told me something like: "opening self-update-window"

After that, it seemed like nothing had changed but many icons weren't loaded. After restarting warehouse the icons are loaded properly but all my enabled repositories are gone. I am able to add new ones but the old ones are gone. When I run "ssu lr" it shows only the ones I added afterwards. No disabled repos or stuff like that.

In addition I have a feature request (not that much of a new request): There was the request of adding the possibility of commenting and rating from within Warehouse. If it's not on your priority list, perhaps adding the possibility of visiting the corresponding page on openrepos.net will be an easy to implement fix.

I installed Sailfish on Nexus 5 and updated to 2.0.0.10. I want to use Warehouse, but I see this after first run or when checking updates. can you help me? I tried some solutions posted to TJC, but no effect.

Hello, since January i will say, every time I install or update a program with warehouse, it is slow during the download or during the installation many time sailfish propose to wait or turn of the application. Does anyone have the problem or have an idea how to fix it ?
Thanks

Feature request: In case some dependencie can't be found while installing a package search at all openrepos repos (the ones that are disabled at the client) and if it's found: Ask the user to enable the missing repo.

//EDIT: This will most likely need some API from openrepos.net as temporary adding and removing repos might be way to slow client side.

This will not be implement as this is major security issue: hijack package by major version via enabling repository. One of future updates will disable all publisher repositories as main source of applicationa, and every application will be in self-contained repository: with dependencies automatically detected(packages listed and uploaded by same publisher, or manually selected by the publisher.

While you got a point here that's the reason I said "Ask the user to enable the missing repo." - So the user is still responsible for the enabled repos.
Anyhow, seems like you alredy have a better solution in the pipeline. Thanks for the info. :)
Just one last question: How will your solution handle duplicates. Let's say package A from repo X has library C from repo Y as a dependency. Now package B from repo Z has has library C as a dependency, too, but it wants it from repo W. Now the user wants to install A and B, with what library C will he end up? The one installed first, the one with the highest version number (what if both are equal - what if package A explicy says it wants a lower version), ...? Also what happens if library C gets updated in Y while A from X needs a special version (so after the update there's a version missmatch) ?

Default(automatic) dependencies will be filled based on package dependencies list (from deb/rpm), if any of those packages are preset at publisher own repository. After that, you can manually cherry-pick any package to be pulled from any other repository to your application repository.
If you have multiple application depending on same library, which is provided by different repositories, it's package manager job to resolve conflicts and finding apropriate versions.