Hi Ville,<div><br></div><div>I did that and this is the response I got:</div><div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">In fact, the issue is not we cannot install the missing libraries on our own; it is that we cannot assume that end-users/consumers have this knowledge to install the dependencies by themselves.</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">Thus, the current workaround for this is to package the dependencies into the app build so that end-users/consumers do not have to handle this hassle.</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div></blockquote><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><div>
<font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div>Are you saying that Ovi Store is, after all, using a proper repository even for paid apps? Could it be that all the people who know anything about Maemo are currently on holidays and therefore I got this? </span></font><div>
<font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse; "><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Cheers,</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Sascha</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font><div><br><div class="gmail_quote">On Thu, Jul 22, 2010 at 16:54, Ville M. Vainio <span dir="ltr"><<a href="mailto:vivainio@gmail.com">vivainio@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<p>I believed this is a misunderstanding or bad test case on ovi QA side. They are trying dpkg -i to ensure dependencies on "clean" environment, without awareness that dependencies to nokia repositories are ok.
<br>
<br>Advice them of this.
<br></p><div><div></div><div class="h5">
<br>
<br>
<br>----- Original message -----
<br>> Hi Ville,
<br>>
<br>> Let me just copy and paste here a few emails I got from Publish To Ovi
<br>> Support:
<br>>
<br>> As a matter of fact, this app is failed in QA because of "feature of
<br>> application manager direct installing from deb file cause that installing
<br>> will complain two dependence library: 'libqtm-bearer and
<br>> libqtm-systeminfo are missing.'", quoted from internal communication
<br>> with our back-end.
<br>>
<br>> The reason is that Nokia hasn't yet embedded Qt Mobility on N900.
<br>> Although it will happen soon, currently developers have to manually
<br>> package the Qt Mobility package with their apps.
<br>>
<br>> You may find the Qt Mobility package and its individual packages here:
<br>> <a href="http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/" target="_blank">http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/</a>.
<br>>
<br>> Files ending with _armel.deb are those ones that should be pre-installed
<br>> on N900 devices, whereas _i386.deb ones are for PC environment.
<br>>
<br>> To be specific, for your case, you should at least package the
<br>> <a href="http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-bearer_1.0.0-maemo1+0m5_armel.deb" target="_blank">http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-bearer_1.0.0-maemo1+0m5_armel.deb</a>
<br>> and
<br>> the
<br>> <a href="http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-systeminfo_1.0.0-maemo1+0m5_armel.debinto" target="_blank">http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-systeminfo_1.0.0-maemo1+0m5_armel.debinto</a>
<br>> your final build.
<br>>
<br>>
<br>>
<br>> And here is a other one:
<br>>
<br>> In fact, the issue is not we cannot install the missing libraries on our
<br>> own; it is that we cannot assume that end-users/consumers have this
<br>> knowledge to install the dependencies by themselves.
<br>>
<br>> Thus, the current workaround for this is to package the dependencies into
<br>> the app build so that end-users/consumers do not have to handle this
<br>> hassle.
<br>>
<br>>
<br>>
<br>> And here is the final one:
<br>>
<br>> You can always try to build the Qt Mobility source with your app. The
<br>> source package can be downloaded at
<br>> <a href="http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/qt-mobility_1.0.2-maemo1.tar.gz" target="_blank">http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/qt-mobility_1.0.2-maemo1.tar.gz</a>;
<br>> or you can use apt-get source libqtm-bearer to acquire.
<br>>
<br>> I'm also working on possible other solutions. Packaging a deb file into
<br>> another looks like having some trouble currently. I'll let you know if
<br>> I've made any progress. Sorry for the inconvenience.
<br>>
<br>>
<br>>
<br>> As you can see what I'm told by them, it seems that they are not using a
<br>> repository for paid apps. Do you have other information?
<br>>
<br>> Cheers,
<br>>
<br>> Sascha
<br>>
<br>>
<br>>
<br>> On Thu, Jul 22, 2010 at 16:16, Ville M. Vainio <<a href="mailto:vivainio@gmail.com" target="_blank">vivainio@gmail.com</a>>
<br>> wrote:
<br>>
<br>> > Well, that's certainly not the general understanding (inside Nokia) of
<br>> > how it should work. Do you care to elaborate so that we can escalate
<br>> > the issue (with the understanding that it's holiday period...)?
<br>> >
<br>> > Definitely qtmobility is to be usable for Ovi store applications, and
<br>> > same applies for all the other packages that can be downloaded from
<br>> > nokia repos. If this is not currently the case, the process is broken
<br>> > at the moment. You should not change your apps design because of this
<br>> > glitch.
<br>> >
<br>> > ----- Original message -----
<br>> > > Hi Ville,
<br>> > >
<br>> > > Yes, this is what I thought too, but apparently Ovi Store is NOT
<br>> > > using a repository for paid apps. So it simply using "dpgk" to
<br>> > > install the deb files and therefore it's not able to install
<br>> > > dependencies. It's frankly quite shocking, but this is the situation.
<br>> > >
<br>> > > Cheers,
<br>> > >
<br>> > > Sascha
<br>> > >
<br>> > > On Thu, Jul 22, 2010 at 15:54, Ville M. Vainio <<a href="mailto:vivainio@gmail.com" target="_blank">vivainio@gmail.com</a>>
<br>> > > wrote:
<br>> > >
<br>> > > > Qt mobility is in official nokia repo (not extras). It's ok to
<br>> > > > depend on those packages when publishing at ovi store.
<br>> > > >
<br>> > > > ----- Original message -----
<br>> > > > > Hi,
<br>> > > > >
<br>> > > > > After struggling for about a month with my app and the Ovi Store
<br>> > > > > QA, this is what I found out: apparently Ovi Store is not using a
<br>> > > > > repository, at least for paid apps, and therefore cannot install
<br>> > > > > dependencies. However, at the same time their QA team requires
<br>> > > > > quite a few things when dealing with network connectivity.
<br>> > > > > Obviously these requirements are not published anywhere,
<br>> > > > > otherwise this would be much
<br>> >
<br>> > > > > too easy!
<br>> > > > >
<br>> > > > > Anyway, this is what I think they want:
<br>> > > > >
<br>> > > > > 1. Detectect if the device is Offline and give appropriate
<br>> > > > > warning. 2. Detect if the device is connected and if not
<br>> > > > > establish the connection.
<br>> > > >
<br>> > > > > 3. If the connection is set to manual, the app needs to give the
<br>> > > > > necessary prompt.
<br>> > > > > 4. If the connection is set to automatic, it should connect
<br>> > > > > without any prompt.
<br>> > > > >
<br>> > > > > So these, I believe, are the requirements of the Ovi Store
<br>> > > > > QA regarding network connectivity. Now the question is how can
<br>> > > > > this be done without using Qt Mobility (or any other library
<br>> > > > > that is not included with PR1.2)? Is it even possible?
<br>> > > > >
<br>> > > > > It would be nice if there would be a Wiki page or something
<br>> > > > > where a sample code that would pass Ovi Store's QA would be
<br>> > > > > available. I understands that most of the competing platforms
<br>> > > > > have these sample codes freely available, so to prevent the need
<br>> > > > > for devs to reinvent the wheel. It's about time Nokia would have
<br>> > > > > something similar. Currently it seems that while Nokia is
<br>> > > > > recommending Qt for everyone with great enthusiasm, their QA
<br>> > > > > team seems to be out of touch what is currently possible to do
<br>> > > > > with it and what not.
<br>> > > > >
<br>> > > > > Cheers,
<br>> > > > >
<br>> > > > > Sascha
<br>> > > >
<br>> > > >
<br>> >
<br>> >
<br><br></div></div><p></p>
</div>
</blockquote></div><br></div></div>