Re: How to resolve network connectivity without using Qt Mobility in Qt?
Well, that's certainly not the general understanding (inside Nokia) of how it should work. Do you care to elaborate so that we can escalate the issue (with the understanding that it's holiday period...)? Definitely qtmobility is to be usable for Ovi store applications, and same applies for all the other packages that can be downloaded from nokia repos. If this is not currently the case, the process is broken at the moment. You should not change your apps design because of this glitch. - Original message - Hi Ville, Yes, this is what I thought too, but apparently Ovi Store is NOT using a repository for paid apps. So it simply using dpgk to install the deb files and therefore it's not able to install dependencies. It's frankly quite shocking, but this is the situation. Cheers, Sascha On Thu, Jul 22, 2010 at 15:54, Ville M. Vainio vivai...@gmail.com wrote: Qt mobility is in official nokia repo (not extras). It's ok to depend on those packages when publishing at ovi store. - Original message - Hi, After struggling for about a month with my app and the Ovi Store QA, this is what I found out: apparently Ovi Store is not using a repository, at least for paid apps, and therefore cannot install dependencies. However, at the same time their QA team requires quite a few things when dealing with network connectivity. Obviously these requirements are not published anywhere, otherwise this would be much too easy! Anyway, this is what I think they want: 1. Detectect if the device is Offline and give appropriate warning. 2. Detect if the device is connected and if not establish the connection. 3. If the connection is set to manual, the app needs to give the necessary prompt. 4. If the connection is set to automatic, it should connect without any prompt. So these, I believe, are the requirements of the Ovi Store QA regarding network connectivity. Now the question is how can this be done without using Qt Mobility (or any other library that is not included with PR1.2)? Is it even possible? It would be nice if there would be a Wiki page or something where a sample code that would pass Ovi Store's QA would be available. I understands that most of the competing platforms have these sample codes freely available, so to prevent the need for devs to reinvent the wheel. It's about time Nokia would have something similar. Currently it seems that while Nokia is recommending Qt for everyone with great enthusiasm, their QA team seems to be out of touch what is currently possible to do with it and what not. Cheers, Sascha ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
Hi Ville, Let me just copy and paste here a few emails I got from Publish To Ovi Support: As a matter of fact, this app is failed in QA because of feature of application manager direct installing from deb file cause that installing will complain two dependence library: 'libqtm-bearer and libqtm-systeminfo are missing.', quoted from internal communication with our back-end. The reason is that Nokia hasn't yet embedded Qt Mobility on N900. Although it will happen soon, currently developers have to manually package the Qt Mobility package with their apps. You may find the Qt Mobility package and its individual packages here: http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/. Files ending with _armel.deb are those ones that should be pre-installed on N900 devices, whereas _i386.deb ones are for PC environment. To be specific, for your case, you should at least package the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-bearer_1.0.0-maemo1+0m5_armel.deb and the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-systeminfo_1.0.0-maemo1+0m5_armel.debinto your final build. And here is a other one: 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. 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. And here is the final one: You can always try to build the Qt Mobility source with your app. The source package can be downloaded at http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/qt-mobility_1.0.2-maemo1.tar.gz; or you can use apt-get source libqtm-bearer to acquire. I'm also working on possible other solutions. Packaging a deb file into another looks like having some trouble currently. I'll let you know if I've made any progress. Sorry for the inconvenience. As you can see what I'm told by them, it seems that they are not using a repository for paid apps. Do you have other information? Cheers, Sascha On Thu, Jul 22, 2010 at 16:16, Ville M. Vainio vivai...@gmail.com wrote: Well, that's certainly not the general understanding (inside Nokia) of how it should work. Do you care to elaborate so that we can escalate the issue (with the understanding that it's holiday period...)? Definitely qtmobility is to be usable for Ovi store applications, and same applies for all the other packages that can be downloaded from nokia repos. If this is not currently the case, the process is broken at the moment. You should not change your apps design because of this glitch. - Original message - Hi Ville, Yes, this is what I thought too, but apparently Ovi Store is NOT using a repository for paid apps. So it simply using dpgk to install the deb files and therefore it's not able to install dependencies. It's frankly quite shocking, but this is the situation. Cheers, Sascha On Thu, Jul 22, 2010 at 15:54, Ville M. Vainio vivai...@gmail.com wrote: Qt mobility is in official nokia repo (not extras). It's ok to depend on those packages when publishing at ovi store. - Original message - Hi, After struggling for about a month with my app and the Ovi Store QA, this is what I found out: apparently Ovi Store is not using a repository, at least for paid apps, and therefore cannot install dependencies. However, at the same time their QA team requires quite a few things when dealing with network connectivity. Obviously these requirements are not published anywhere, otherwise this would be much too easy! Anyway, this is what I think they want: 1. Detectect if the device is Offline and give appropriate warning. 2. Detect if the device is connected and if not establish the connection. 3. If the connection is set to manual, the app needs to give the necessary prompt. 4. If the connection is set to automatic, it should connect without any prompt. So these, I believe, are the requirements of the Ovi Store QA regarding network connectivity. Now the question is how can this be done without using Qt Mobility (or any other library that is not included with PR1.2)? Is it even possible? It would be nice if there would be a Wiki page or something where a sample code that would pass Ovi Store's QA would be available. I understands that most of the competing platforms have these sample codes freely available, so to prevent the need for devs to reinvent the wheel. It's about time Nokia would have something similar. Currently it seems that while Nokia is recommending Qt for everyone with great enthusiasm, their QA team seems to be out of touch what is currently possible to do with it and what not. Cheers, Sascha
Re: How to resolve network connectivity without using Qt Mobility in Qt?
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. Advice them of this. - Original message - Hi Ville, Let me just copy and paste here a few emails I got from Publish To Ovi Support: As a matter of fact, this app is failed in QA because of feature of application manager direct installing from deb file cause that installing will complain two dependence library: 'libqtm-bearer and libqtm-systeminfo are missing.', quoted from internal communication with our back-end. The reason is that Nokia hasn't yet embedded Qt Mobility on N900. Although it will happen soon, currently developers have to manually package the Qt Mobility package with their apps. You may find the Qt Mobility package and its individual packages here: http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/. Files ending with _armel.deb are those ones that should be pre-installed on N900 devices, whereas _i386.deb ones are for PC environment. To be specific, for your case, you should at least package the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-bearer_1.0.0-maemo1+0m5_armel.deb and the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-systeminfo_1.0.0-maemo1+0m5_armel.debinto your final build. And here is a other one: 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. 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. And here is the final one: You can always try to build the Qt Mobility source with your app. The source package can be downloaded at http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/qt-mobility_1.0.2-maemo1.tar.gz; or you can use apt-get source libqtm-bearer to acquire. I'm also working on possible other solutions. Packaging a deb file into another looks like having some trouble currently. I'll let you know if I've made any progress. Sorry for the inconvenience. As you can see what I'm told by them, it seems that they are not using a repository for paid apps. Do you have other information? Cheers, Sascha On Thu, Jul 22, 2010 at 16:16, Ville M. Vainio vivai...@gmail.com wrote: Well, that's certainly not the general understanding (inside Nokia) of how it should work. Do you care to elaborate so that we can escalate the issue (with the understanding that it's holiday period...)? Definitely qtmobility is to be usable for Ovi store applications, and same applies for all the other packages that can be downloaded from nokia repos. If this is not currently the case, the process is broken at the moment. You should not change your apps design because of this glitch. - Original message - Hi Ville, Yes, this is what I thought too, but apparently Ovi Store is NOT using a repository for paid apps. So it simply using dpgk to install the deb files and therefore it's not able to install dependencies. It's frankly quite shocking, but this is the situation. Cheers, Sascha On Thu, Jul 22, 2010 at 15:54, Ville M. Vainio vivai...@gmail.com wrote: Qt mobility is in official nokia repo (not extras). It's ok to depend on those packages when publishing at ovi store. - Original message - Hi, After struggling for about a month with my app and the Ovi Store QA, this is what I found out: apparently Ovi Store is not using a repository, at least for paid apps, and therefore cannot install dependencies. However, at the same time their QA team requires quite a few things when dealing with network connectivity. Obviously these requirements are not published anywhere, otherwise this would be much too easy! Anyway, this is what I think they want: 1. Detectect if the device is Offline and give appropriate warning. 2. Detect if the device is connected and if not establish the connection. 3. If the connection is set to manual, the app needs to give the necessary prompt. 4. If the connection is set to automatic, it should connect without any prompt. So these, I believe, are the requirements of the Ovi Store QA regarding network connectivity. Now the question is how can this be done without using Qt Mobility (or any other library that is not included with PR1.2)? Is it even possible? It would be nice if there would be a Wiki page or something where a sample code that would pass Ovi Store's QA would be available. I understands that most of the competing
Re: How to resolve network connectivity without using Qt Mobility in Qt?
Hi Ville! Unfortunately what Sascha is saying is true. You cannot use Qt Mobility in paid applications. See this thread for a details: http://lists.maemo.org/pipermail/maemo-developers/2010-July/027109.html Thanks, Daniil. On Thu, Jul 22, 2010 at 4:54 PM, Ville M. Vainio vivai...@gmail.com wrote: 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. Advice them of this. - Original message - Hi Ville, Let me just copy and paste here a few emails I got from Publish To Ovi Support: As a matter of fact, this app is failed in QA because of feature of application manager direct installing from deb file cause that installing will complain two dependence library: 'libqtm-bearer and libqtm-systeminfo are missing.', quoted from internal communication with our back-end. The reason is that Nokia hasn't yet embedded Qt Mobility on N900. Although it will happen soon, currently developers have to manually package the Qt Mobility package with their apps. You may find the Qt Mobility package and its individual packages here: http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/. Files ending with _armel.deb are those ones that should be pre-installed on N900 devices, whereas _i386.deb ones are for PC environment. To be specific, for your case, you should at least package the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-bearer_1.0.0-maemo1+0m5_armel.deb and the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-systeminfo_1.0.0-maemo1+0m5_armel.debinto your final build. And here is a other one: 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. 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. And here is the final one: You can always try to build the Qt Mobility source with your app. The source package can be downloaded at http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/qt-mobility_1.0.2-maemo1.tar.gz; or you can use apt-get source libqtm-bearer to acquire. I'm also working on possible other solutions. Packaging a deb file into another looks like having some trouble currently. I'll let you know if I've made any progress. Sorry for the inconvenience. As you can see what I'm told by them, it seems that they are not using a repository for paid apps. Do you have other information? Cheers, Sascha On Thu, Jul 22, 2010 at 16:16, Ville M. Vainio vivai...@gmail.com wrote: Well, that's certainly not the general understanding (inside Nokia) of how it should work. Do you care to elaborate so that we can escalate the issue (with the understanding that it's holiday period...)? Definitely qtmobility is to be usable for Ovi store applications, and same applies for all the other packages that can be downloaded from nokia repos. If this is not currently the case, the process is broken at the moment. You should not change your apps design because of this glitch. - Original message - Hi Ville, Yes, this is what I thought too, but apparently Ovi Store is NOT using a repository for paid apps. So it simply using dpgk to install the deb files and therefore it's not able to install dependencies. It's frankly quite shocking, but this is the situation. Cheers, Sascha On Thu, Jul 22, 2010 at 15:54, Ville M. Vainio vivai...@gmail.com wrote: Qt mobility is in official nokia repo (not extras). It's ok to depend on those packages when publishing at ovi store. - Original message - Hi, After struggling for about a month with my app and the Ovi Store QA, this is what I found out: apparently Ovi Store is not using a repository, at least for paid apps, and therefore cannot install dependencies. However, at the same time their QA team requires quite a few things when dealing with network connectivity. Obviously these requirements are not published anywhere, otherwise this would be much too easy! Anyway, this is what I think they want: 1. Detectect if the device is Offline and give appropriate warning. 2. Detect if the device is connected and if not establish the connection. 3. If the connection is set to manual, the app needs to give the necessary prompt. 4. If the connection is set to automatic, it should connect without any prompt. So these, I believe, are the requirements of the Ovi Store QA regarding network connectivity. Now the question is how can this be done without using Qt Mobility
Re: How to resolve network connectivity without using Qt Mobility in Qt?
Hi Ville, I did that and this is the response I got: 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. 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. 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? Cheers, Sascha On Thu, Jul 22, 2010 at 16:54, Ville M. Vainio vivai...@gmail.com wrote: 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. Advice them of this. - Original message - Hi Ville, Let me just copy and paste here a few emails I got from Publish To Ovi Support: As a matter of fact, this app is failed in QA because of feature of application manager direct installing from deb file cause that installing will complain two dependence library: 'libqtm-bearer and libqtm-systeminfo are missing.', quoted from internal communication with our back-end. The reason is that Nokia hasn't yet embedded Qt Mobility on N900. Although it will happen soon, currently developers have to manually package the Qt Mobility package with their apps. You may find the Qt Mobility package and its individual packages here: http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/. Files ending with _armel.deb are those ones that should be pre-installed on N900 devices, whereas _i386.deb ones are for PC environment. To be specific, for your case, you should at least package the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-bearer_1.0.0-maemo1+0m5_armel.deb and the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-systeminfo_1.0.0-maemo1+0m5_armel.debinto your final build. And here is a other one: 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. 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. And here is the final one: You can always try to build the Qt Mobility source with your app. The source package can be downloaded at http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/qt-mobility_1.0.2-maemo1.tar.gz; or you can use apt-get source libqtm-bearer to acquire. I'm also working on possible other solutions. Packaging a deb file into another looks like having some trouble currently. I'll let you know if I've made any progress. Sorry for the inconvenience. As you can see what I'm told by them, it seems that they are not using a repository for paid apps. Do you have other information? Cheers, Sascha On Thu, Jul 22, 2010 at 16:16, Ville M. Vainio vivai...@gmail.com wrote: Well, that's certainly not the general understanding (inside Nokia) of how it should work. Do you care to elaborate so that we can escalate the issue (with the understanding that it's holiday period...)? Definitely qtmobility is to be usable for Ovi store applications, and same applies for all the other packages that can be downloaded from nokia repos. If this is not currently the case, the process is broken at the moment. You should not change your apps design because of this glitch. - Original message - Hi Ville, Yes, this is what I thought too, but apparently Ovi Store is NOT using a repository for paid apps. So it simply using dpgk to install the deb files and therefore it's not able to install dependencies. It's frankly quite shocking, but this is the situation. Cheers, Sascha On Thu, Jul 22, 2010 at 15:54, Ville M. Vainio vivai...@gmail.com wrote: Qt mobility is in official nokia repo (not extras). It's ok to depend on those packages when publishing at ovi store. - Original message - Hi, After struggling for about a month with my app and the Ovi Store QA, this is what I found out: apparently Ovi Store is not using a repository, at least for paid apps, and therefore cannot install dependencies. However, at the same time their QA team requires quite a few things when dealing with network connectivity. Obviously these requirements are not published anywhere, otherwise this would be much too easy! Anyway, this is what I think they want: 1. Detectect
Re: How to resolve network connectivity without using Qt Mobility in Qt?
That comment doesn't apply since applications are downloaded from repository, triggered by .install file (unless there is a terrible misunderstanding somewhere). Daniil, if you are not on holiday please priorize clarifying this issue with ovi guys. - Original message - Hi Ville! Unfortunately what Sascha is saying is true. You cannot use Qt Mobility in paid applications. See this thread for a details: http://lists.maemo.org/pipermail/maemo-developers/2010-July/027109.html Thanks, Daniil. On Thu, Jul 22, 2010 at 4:54 PM, Ville M. Vainio vivai...@gmail.com wrote: 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. Advice them of this. - Original message - Hi Ville, Let me just copy and paste here a few emails I got from Publish To Ovi Support: As a matter of fact, this app is failed in QA because of feature of application manager direct installing from deb file cause that installing will complain two dependence library: 'libqtm-bearer and libqtm-systeminfo are missing.', quoted from internal communication with our back-end. The reason is that Nokia hasn't yet embedded Qt Mobility on N900. Although it will happen soon, currently developers have to manually package the Qt Mobility package with their apps. You may find the Qt Mobility package and its individual packages here: http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/. Files ending with _armel.deb are those ones that should be pre-installed on N900 devices, whereas _i386.deb ones are for PC environment. To be specific, for your case, you should at least package the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-bearer_1.0.0-maemo1+0m5_armel.deb and the http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/libqtm-systeminfo_1.0.0-maemo1+0m5_armel.debinto your final build. And here is a other one: 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. 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. And here is the final one: You can always try to build the Qt Mobility source with your app. The source package can be downloaded at http://repository.maemo.org/pool/fremantle/free/q/qt-mobility/qt-mobility_1.0.2-maemo1.tar.gz; or you can use apt-get source libqtm-bearer to acquire. I'm also working on possible other solutions. Packaging a deb file into another looks like having some trouble currently. I'll let you know if I've made any progress. Sorry for the inconvenience. As you can see what I'm told by them, it seems that they are not using a repository for paid apps. Do you have other information? Cheers, Sascha On Thu, Jul 22, 2010 at 16:16, Ville M. Vainio vivai...@gmail.com wrote: Well, that's certainly not the general understanding (inside Nokia) of how it should work. Do you care to elaborate so that we can escalate the issue (with the understanding that it's holiday period...)? Definitely qtmobility is to be usable for Ovi store applications, and same applies for all the other packages that can be downloaded from nokia repos. If this is not currently the case, the process is broken at the moment. You should not change your apps design because of this glitch. - Original message - Hi Ville, Yes, this is what I thought too, but apparently Ovi Store is NOT using a repository for paid apps. So it simply using dpgk to install the deb files and therefore it's not able to install dependencies. It's frankly quite shocking, but this is the situation. Cheers, Sascha On Thu, Jul 22, 2010 at 15:54, Ville M. Vainio vivai...@gmail.com wrote: Qt mobility is in official nokia repo (not extras). It's ok to depend on those packages when publishing at ovi store. - Original message - Hi, After struggling for about a month with my app and the Ovi Store QA, this is what I found out: apparently Ovi Store is not using a repository, at least for paid apps, and therefore cannot install dependencies. However, at the same time their QA team requires quite a few things when dealing with network connectivity. Obviously these requirements are not published anywhere, otherwise this would be much too
Re: How to resolve network connectivity without using Qt Mobility in Qt?
ext Ville M. Vainio vivai...@gmail.com writes: Well, that's certainly not the general understanding (inside Nokia) of how it should work. Do you care to elaborate so that we can escalate the issue (with the understanding that it's holiday period...)? Ville, if you escalate this, the right thing IMO would be to fix the Application Manager, make a new Maemo 5 release with it, and somehow 'force' people to update to it when they install a package from Ovi Store that needs dependencies resolved. I am here this week only, so let's find some time to get this going. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
Hi Ville, Well this is indeed weird. I'm beginning to think that all the Memo guys of Ovi Store are in holidays and the ones left have no idea how to publish my app for Maemo. The funny thing is that in our Ovi Store publishing site the status of my app is Passed and has been for about a week now. It's just not published. Only when I wrote to inquire when will it be published was I informed about this issue with Qt Mobility. Very strange... Cheers, Sascha On Thu, Jul 22, 2010 at 17:16, Ville M. Vainio vivai...@gmail.com wrote: Yes, my understanding is indeed that repository is used for paid applications (weird as it sounds). ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
Hi Marius, So according your opinion, should I wait for this issue to be resolved at Nokia's end or should I try to make changes to my app? The one suggestion I've been given several times is to statically include Qt Mobility, but I'm not so sure if that is a great idea and even if it was, I don't know how to do that. Cheers, Sascha On Thu, Jul 22, 2010 at 10:33, Marius Vollmer marius.voll...@nokia.comwrote: ext Ville M. Vainio vivai...@gmail.com writes: Well, that's certainly not the general understanding (inside Nokia) of how it should work. Do you care to elaborate so that we can escalate the issue (with the understanding that it's holiday period...)? Ville, if you escalate this, the right thing IMO would be to fix the Application Manager, make a new Maemo 5 release with it, and somehow 'force' people to update to it when they install a package from Ovi Store that needs dependencies resolved. I am here this week only, so let's find some time to get this going. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
ext Ville M. Vainio vivai...@gmail.com writes: That comment doesn't apply since applications are downloaded from repository, triggered by .install file (unless there is a terrible misunderstanding somewhere). This is true for gratis packages, but paid packages are downloaded as Debian packages, not as .install files. (I confirmed that now by paying EUR 1 for angryman. :) The Application Manager has been 'optimized' for repositories, and the code for dealing with Debian package files has been neglected. Now with the Ovi Store using standalone Debian packages, we should finally fix that. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
On 22/07/2010 10:10, Marius Vollmer wrote: The Application Manager has been 'optimized' for repositories, and the code for dealing with Debian package files has been neglected. Now with the Ovi Store using standalone Debian packages, we should finally fix that. Again, wouldn't it be easier and smarter (at least technically) to fix ovi store? What's the point of (basically) running dpkg -i instead of apt-get install? Cheers, -- Yves-Alexis ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
Hi Yves-Alexis! The point is security as these are paid applications. Thanks, Daniil. On Thu, Jul 22, 2010 at 11:21 AM, Yves-Alexis Perez cor...@debian.org wrote: On 22/07/2010 10:10, Marius Vollmer wrote: The Application Manager has been 'optimized' for repositories, and the code for dealing with Debian package files has been neglected. Now with the Ovi Store using standalone Debian packages, we should finally fix that. Again, wouldn't it be easier and smarter (at least technically) to fix ovi store? What's the point of (basically) running dpkg -i instead of apt-get install? Cheers, -- Yves-Alexis ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
keys when long pressed should give the blue symbol/number
Hi, From https://bugs.maemo.org/show_bug.cgi?id=5421 I know that long press key gives blue character, but I can only get blue one when run Gtk+/Hildon based applications, my own Qt based apps and manually installed Qt based apps are all failed to get blue character, I can just get white characters repeatedly. Shall I do some further work to deal with hildon-input-method-plugins 3.9.51-1+0m5 hildon-input-method-framework 1:2.1.44-1+0m5 hildon-input-method 1:2.1.39-1+0m5 see comment #23 of URL mentioned above. Anyone can help me? -- Best regards, Pawpaw Young ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
ext Sascha Mäkelä sascha.mak...@gmail.com writes: So according your opinion, should I wait for this issue to be resolved at Nokia's end or should I try to make changes to my app? Don't wait for us, try to work around the problem on your side. The one suggestion I've been given several times is to statically include Qt Mobility, but I'm not so sure if that is a great idea and even if it was, I don't know how to do that. I would do what you have started this thread for: do without QtMobility. I'll reply to your original mail with some hints. When statically linking QtMobility, there might also be license issues. QtMobility is LGPLv2.1 (unless you have a commercial Qt license which I assume you don't), and that means that you can't really copy code out of it into your sources (which I assume are non-free), and even if you distribute QtMobility in your package, you need to satisfy the LGPL: static linking is not allowed (unless the user can do it, too), you need to provide source for QtMobility upon request, etc. Maybe Nokia gives an exception that allows static linking of QtMobility, and Nokia isn't likely to sue you over this anyway, but still, Nokia shouldn't really make the suggestion to statically link QtMobility without clearly stating that they give permission for that eventhough the license of QtMobility forbids it. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
On 22/07/2010 10:24, Daniil Ivanov wrote: Hi Yves-Alexis! (please don't CC: me, I'm subscribed) The point is security as these are paid applications. This is not “security” anyway. And I fail to see how this can help paid applications, but as we don't really have details on Ovi store infrastructure, I guess I lack some information. Anyway, I'm pretty sure there are better ways to do that without “abusing” HAM. Cheers, -- Yves-Alexis ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
On Thu, Jul 22, 2010 at 10:47 AM, Sascha Mäkelä sascha.mak...@gmail.com wrote: So according your opinion, should I wait for this issue to be resolved at Nokia's end or should I try to make changes to my app? The one suggestion I've been given several times is to statically include Qt Mobility, but I'm not so sure if that is a great idea and even if it was, I don't know how to do that. As it appears, rabbit hole goes deeper than initially expected, so don't hold your breath on getting the issue fixed in reasonable timeframe :-/. -- Ville M. Vainio @@ Forum Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
ext Sascha Mäkelä sascha.mak...@gmail.com writes: 1. Detectect if the device is Offline and give appropriate warning. 2. Detect if the device is connected and if not establish the connection. 3. If the connection is set to manual, the app needs to give the necessary prompt. 4. If the connection is set to automatic, it should connect without any prompt. These services are provided by libconic. There should be a libconic0-doc package in the Maemo 5 SDK repositories with the API documentation for it. So these, I believe, are the requirements of the Ovi Store QA regarding network connectivity. Now the question is how can this be done without using Qt Mobility (or any other library that is not included with PR1.2)? Is it even possible? Sure. QtMobility isn't part of the OS, which is causing all the pain here, and the bundled applications like the browser have to do the same thing, of course, without QtMobility. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
Well, I think I'll just do my original version again which basically only detects if the connection exist or not. If there is no connection it will just prompt the user to manually connect. After all, my only needs the internet connection for data updates that are not even necessary for the app to function properly. I just hope there are some reasonable people in the QA team who would understand the current situation. I certainly do not want any licenses difficulties. Cheers, Sascha ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: keys when long pressed should give the blue symbol/number
Am Donnerstag, den 22.07.2010, 16:30 +0800 schrieb Richard Young: From https://bugs.maemo.org/show_bug.cgi?id=5421 I know that long press key gives blue character, but I can only get blue one when run Gtk+/Hildon based applications, my own Qt based apps and manually installed Qt based apps are all failed to get blue character, I can just get white characters repeatedly. A concrete example would have been welcome, however I can reproduce this with the address field in CuteExplorer (which is written in Qt). So it's probably either a bug in hildon-input-* (which would be bugs.maemo.org) or in Qt (which would be http://bugreports.qt.nokia.com ). Probably the latter as there are already tickets like http://bugreports.qt.nokia.com/browse/QTBUG-7512 . andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
ext Yves-Alexis Perez cor...@debian.org writes: On 22/07/2010 10:10, Marius Vollmer wrote: The Application Manager has been 'optimized' for repositories, and the code for dealing with Debian package files has been neglected. Now with the Ovi Store using standalone Debian packages, we should finally fix that. Again, wouldn't it be easier and smarter (at least technically) to fix ovi store? Don't know. We are doing this for Harmattan, and it isn't really that easy or fast... What's the point of (basically) running dpkg -i instead of apt-get install? If you use apt-get unmodified, you need to provide permanent download URLs for the packages, and my understanding is that the Ovi Store can not provide those _and_ control their accesses. They protect against unauthorized downloads by using random, temporary URLs. Another issue is scalability: we don't want to download the meta data for the whole Ovi Store during apt-get update. For Harmattan, we are putting a Ovi Store Adaptor into place which makes the Ovi Store look like a regular repository. The apt-cache search will find your paid packages and you can update them with apt-get upgrade, etc. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
Hi Marius, On Thu, Jul 22, 2010 at 11:59 AM, Marius Vollmer marius.voll...@nokia.com wrote: For Harmattan, we are putting a Ovi Store Adaptor into place which makes the Ovi Store look like a regular repository. The apt-cache search will find your paid packages and you can update them with apt-get upgrade, etc. How is preventing unauthorized downloads maintained through this strategy ? Sivan ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
On 22/07/2010 10:59, Marius Vollmer wrote: ext Yves-Alexis Perez cor...@debian.org writes: (no need to CC: me, I'm subcribed) On 22/07/2010 10:10, Marius Vollmer wrote: The Application Manager has been 'optimized' for repositories, and the code for dealing with Debian package files has been neglected. Now with the Ovi Store using standalone Debian packages, we should finally fix that. Again, wouldn't it be easier and smarter (at least technically) to fix ovi store? Don't know. We are doing this for Harmattan, and it isn't really that easy or fast... What's the point of (basically) running dpkg -i instead of apt-get install? If you use apt-get unmodified, you need to provide permanent download URLs for the packages, and my understanding is that the Ovi Store can not provide those _and_ control their accesses. They protect against unauthorized downloads by using random, temporary URLs. That looks over-engineered. Using authenticated https to download packages should work and fix the various problem using reliable (well, considering TLS is reliable) ways. Not sure how much the libapt version in Fremantle supports https, but... Another issue is scalability: we don't want to download the meta data for the whole Ovi Store during apt-get update. Well, at least that would mean we could browse Ovi Store from HAM, not the browser, which is more consistent for user experience, imho. Did you try pdiffs support, too? -- Yves-Alexis ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
ext Sivan Greenberg si...@omniqueue.com writes: Hi Marius, On Thu, Jul 22, 2010 at 11:59 AM, Marius Vollmer marius.voll...@nokia.com wrote: For Harmattan, we are putting a Ovi Store Adaptor into place which makes the Ovi Store look like a regular repository. The apt-cache search will find your paid packages and you can update them with apt-get upgrade, etc. How is preventing unauthorized downloads maintained through this strategy ? When downloading a package, apt-get will also do that via the adaptor. The adaptor will do whatever is necearry to retrieve the temporary URL from the Ovi Store, and then immediately use that. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
ext Yves-Alexis Perez cor...@debian.org writes: If you use apt-get unmodified, you need to provide permanent download URLs for the packages, and my understanding is that the Ovi Store can not provide those _and_ control their accesses. They protect against unauthorized downloads by using random, temporary URLs. That looks over-engineered. Using authenticated https to download packages should work and fix the various problem using reliable (well, considering TLS is reliable) ways. Not sure how much the libapt version in Fremantle supports https, but... I really can't say anything about the Ovi Store infrastructure... Another issue is scalability: we don't want to download the meta data for the whole Ovi Store during apt-get update. Well, at least that would mean we could browse Ovi Store from HAM, not the browser, which is more consistent for user experience, imho. Did you try pdiffs support, too? It's not only the download time, it is also the size of the meta data that is stored locally and needs to be processed. I am thinking about making apt's cache updates fully incremental, so that the whole apt-get update is proportional to the size of the pdiffs, and we also use pdiffs for changes to /var/lib/dpkg/status... But that's more on the crazy side anbd the cache would still be quite big. Anyway, the device should support pdiffs just fine. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo QA process
On Thursday 22 July 2010 02:35:47 Ian Stirling wrote: Note that since not long ago we also have super-testers, people with proven track records, it's enough to get three of their votes if your package is stuck and you're good to go. Where is the super-testers list? I've tested a few apps - though I need to get back into the pile of apps. We have no separate list for the super-testers, we (ab)use the testing-squad list[0] for those purposes. For more deails on the super-testers, see https://garage.maemo.org/pipermail/testingsquad-list/2010-July/89.html [0] https://garage.maemo.org/mail/?group_id=1273 Regards, Attila ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
On Thu, Jul 22, 2010 at 10:33 AM, Marius Vollmer marius.voll...@nokia.com wrote: Ville, if you escalate this, the right thing IMO would be to fix the Application Manager, make a new Maemo 5 release with it, and somehow 'force' people to update to it when they install a package from Ovi Store that needs dependencies resolved. I am here this week only, so let's find some time to get this going. I was thinking of small scale escalation (i.e. fix test suite the Ovi QA guys are using). Getting an updated version of app manager out there is a whole different matter, unfortunately, and probably in the realm of confidential Nokia matters like the PR release schedules. -- Ville M. Vainio @@ Forum Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
On Thursday 22 July 2010 10:40:51 Ville M. Vainio wrote: As it appears, rabbit hole goes deeper than initially expected, so don't hold your breath on getting the issue fixed in reasonable timeframe :-/. Just as a side-note - can we work on making at least the Ovi QA criteria public so that we do not get minefield issues like this one ? I understand Maemo5 is fairly new and small in the Ovi story, but it would greatly help if we could see the criteria - in the worst case, adapt to it without wasting any more time than necessary, and in the best case, working with Ovi/Nokia to improve the process to the benefit of all involved parties (seeing Nokians jump in this discussions helping clarify the issue is always a plus). As it is now, the Ovi publishing guide has a meager one-liner about publishing Qt apps and that one point to a (Maemo/MeeGo-wise) not too descriptive page on Forum Nokia. I would even attach my community stamp to this if needed - even though this is largely related to commercial apps, the question of QA (and through it any potential Extras-Ovi cooperation, as dreamy as that may sound) and general app availabilty is something that touches on the community as a whole. Best regards, Attila ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo QA process
Servus! 2010/7/21 Roman Morawek li...@morawek.at: [...] Actually, I think in the early lifetime of a SW project there will probably be a release every few months, which could permanently block the tool's promotion to extras. If there are enough users / testers, releasing every month is no problem. I have the same situation with my app (a new release nearly every month), and with enough testers, I usually get enough votes in the first ten days (quarantine time), so even if you have, say, a bi-weekly release cycle, it would still be enough to get new upgrades into Extras before the next version is released. If you have a blog, create a maemo category/tag and let it be syndicated on the Planet (planet.maemo.org) and announce your releases there - it helps getting attention, and with some screenshots will also describe the app to potential new users/testers (you already have a very informative web page, which is very good - some apps don't even have something like that). I've reviewed your app and posted a comment on the testing page - please have a look :) Greetings, Thomas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to resolve network connectivity without using Qt Mobility in Qt?
Just as a side-note - can we work on making at least the Ovi QA criteria public so that we do not get minefield issues like this one ? I understand Maemo5 is fairly new and small in the Ovi story, but it would greatly help if we could see the criteria - in the worst case, adapt to it without wasting any more time than necessary, and in the best case, working with Ovi/Nokia to improve the process to the benefit of all involved parties (seeing Nokians jump in this discussions helping clarify the issue is always a plus). As it is now, the Ovi publishing guide has a meager one-liner about publishing Qt apps and that one point to a (Maemo/MeeGo-wise) not too descriptive page on Forum Nokia. I would even attach my community stamp to this if needed - even though this is largely related to commercial apps, the question of QA (and through it any potential Extras-Ovi cooperation, as dreamy as that may sound) and general app availabilty is something that touches on the community as a whole. Best regards, Attila I fully agree with this one. Currently the only why to find out what is needed to pass the QA is simply to submit the app and wait for the reply of all the issues. Then fix them and submit it again and find out of some other requirements. And so on... This is a very slow process and is not benefiting anyone. I hope at least this could be corrected as soon as possible. Cheers, Sascha ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo QA process
2010/7/22 Ville M. Vainio vivai...@gmail.com: How about a system where developers could convince other developers to test drive their application by voting on theirs? I.e. being able to give a conditional vote that is realized only after the receiver votes up/down on your application? Wouldn't this slow down the whole process even more? Instead of getting one vote right away, you have to wait for the return vote to be completed, and only then the vote gets counted. A download assistant app (as discussed earlier in this thread) sounds more useful to me than complicating the QA process. Add some incentive (i.e. a monthly posting of the Top 10 Testers to maemo-community, so testers get a feeling of their importance) and make the UI of the testing app really easy to use (What's new section, single sign on, Latest votes, Newest uploads, filter out already-tested apps, show new versions of apps for which the user has voted on at least one older version before, ...), and I think more users will test apps on their devices. Right now, it's very diffcult to browse around and find apps to test (well, http://maemo.org/packages/ works kind-of, but screenshots and better descriptions would help the tester decide whether or not to spend time downloading and testing the app). Another idea would be to add a new section to MWKN (mwkn.net) called Testing Spotlight where three apps in Testing are described and promoted, and readers are asked to at least test these three apps during the week - this should make it possible to have three apps get enough votes during one week. Visibility and promotion of the apps are the problems, I think (searching for apps is tedious, so nobody does it) - the conditional vote idea sounds like a technical solution (enforced policy, added restrictions) to a social problem (non-popular apps don't get enough exposure and consequently testers). HTH. Thomas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo QA process
Hi all, do you think that the possibility to vote (UP/DOWN) applications and send feedback directly from N900 could help the process? It's just an idea eh... Another feature I'd like to see on Application Manager is the possibility to know if an application I see comes from maemo-extras, extras-testing or extras-devel. There's no way to know it at the moment. This information should be clearly visible with a color for example: green for extras, orange for testing and red for devel. There should be the possibility ti configure username/password of maemo.org directly in N900 settings, so the user can automatically send feedback without having to login. Is this too much effort? Please let me know what you think about. -- Andrea Grandi email: a.grandi [AT] gmail [DOT] com website: http://www.andreagrandi.it PGP Key: http://www.andreagrandi.it/pgp_key.asc ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo QA process
On Thursday 22 July 2010 00:19:20 Felipe Crochik wrote: I added a message to the download assistant thread but never received a reply. http://talk.maemo.org/showpost.php?p=717824postcount=17 Maybe someone knows the maintainer or what is behind the scenes and can find out if it is a viable solution or not. AFAIK that effort is done by Daniel Wilms on a community basis. I wanted to chip in to that project myself, but am severy limited on time :( Regards, Attila ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo QA process
On Thu, Jul 22, 2010 at 2:02 PM, Thomas Perl th.p...@gmail.com wrote: Wouldn't this slow down the whole process even more? Instead of getting one vote right away, you have to wait for the return vote to be completed, and only then the vote gets counted. A download People could still give unconditinal votes (they would be passed around by people that don't need votes, i.e. have no apps). It would only slow down the process for those that are not willing to test other applications. I'm certainly in favor of improving the testing experience on all fronts (and in fact suggested an app for this purpose months ago, so I'm not expecting anyone to jump in and do one now). However, what I'm proposing here is a direct incentive for developers to start helping each other. enough votes during one week. Visibility and promotion of the apps are the problems, I think (searching for apps is tedious, so nobody does it) - the conditional vote idea sounds like a technical solution (enforced policy, added restrictions) to a social problem (non-popular apps don't get enough exposure and consequently testers). Technical solution is the best solution for a social problem ;-). It cuts through the bullshit, to parahprase an 80's movie. Other solutions would appear to require continuing effort from several parties (all of whom are probably overloaded). However, here are some softer solutions: - Put a sticky post at applications forum on TMO, linking to the vote page - Don't fret too much about QA checklist ( http://wiki.maemo.org/Extras-testing/QA_Checklist ): - Not everybody should check for optification, it should be automatic - Doesn't missing bugtracker link prevent promotion to e-t anyway? -- Ville M. Vainio @@ Forum Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo QA process
Hi, Personnaly i didn't care anymore about extras. If people need to use my apps i just ask them to use my repository. No QA Hassle ... :) And if someone want to package it to maemo extras repo he can ... but in three month this didn't happen. Best regards, 2010/7/21 Roman Morawek li...@morawek.at: Hello, I like to share my thoughts on the QA strategy of Maemo. I am the owner of an N900 program and promoted my package to extras-testing ca. 2 months ago. Right now there are only 2 votes on it. I wonder how many more months it will take until 10 persons vote for it such that I can promote it to extras (given that the votes are positive). I already have a bunch of improvements ready since several weeks. However, I do not dare to upload them because my package will start the evaluation sequence then again from scratch. I think this is a big disadvantage for the community, because the tool could already be much better. Actually, I think in the early lifetime of a SW project there will probably be a release every few months, which could permanently block the tool's promotion to extras. I personally see my program as very useful - well, otherwise I wouldn't have spent the time for development. I assume that just nobody is aware of it, since everybody just looks at the available programs in extras. At least this is what I did to search for useful tools. From my perspective, the current QA process should be reconsidered. Maybe an automatic promotion after 4 weeks would make sense, given its actual package karma is positive? Best regards, Roman P.S.: You are welcome to evaluate and vote on my package: http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/babyphone/0.1-2/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Benoît HERVIER, Khertan Software - http://khertan.net/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: How to to manually package Qt Mobility?
On Wednesday 21 July 2010 19:24:03 Felipe Crochik wrote: I have compiled the contacts module and it is quite simple using scratchbox. I distribute with my application a custom contacts backend (I dont distribute the contacts module just the backend) I don't know the licence on the code you are re-using but I presume you are distributing source anyway. I am sure the QtMobility licence won't allow the code to be incorporated into a non-free application. I presume Nokia owns the copyright, so it could add an alternative licence just for this use, of course, but it is a real pain not using the real library. If I was faced with this I would (after shouting, screaming and stamping my foot a lot about how Nokia has STILL not created a working app store for paid Maemo apps!), create a free package which depends on all your dependencies and tell people they have to install that before they can use the app. If you are really helpful, you could create your app such that it will run even if the libraries are not there and produce a useful error message telling people what they have to install to make it work. You would have to give a useful name (something like Support files for AppX) and description and it would have to either be in the free Ovi repository or in Extras so it could drag in the dependencies. I suppose you could even make it a free/demo/trial version of your non-free app. Alternatively, if this problem is likely to be faced by other apps, you could see if the QtMobility people would create a wrapper library which did that work. The free package would then be called QtMobility support files and your documentation would tell people they have to install that before your app works. You would not link with the real QtMobility library but with the wrapper, which would try to load the real library and, if that fails, display a message to tell people they need to install the QtMobility support files package. There would be a small performance impact, of course, which would go away once Ovi fix the problem properly (e.g. next millennium). Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo website - Package promotion System BUG
Am Donnerstag, den 22.07.2010, 22:35 +0200 schrieb Luigi Cotignano: Hi Niels, I want to report a bug For future reference, the bugtracker is at bugs.maemo.org, specifically https://bugs.maemo.org/enter_bug.cgi?product=maemo.org%20Websitecomponent=Promoter andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
R: Maemo website - Package promotion System BUG
Hi Andre, thanks for your prompt reply. I have just added that issue to the bugs tracking system. Regards, Luigi -Messaggio originale- Da: maemo-developers-boun...@maemo.org [mailto:maemo-developers-boun...@maemo.org] Per conto di Andre Klapper Inviato: giovedì 22 luglio 2010 22.47 A: maemo-developers@maemo.org Oggetto: Re: Maemo website - Package promotion System BUG Am Donnerstag, den 22.07.2010, 22:35 +0200 schrieb Luigi Cotignano: Hi Niels, I want to report a bug For future reference, the bugtracker is at bugs.maemo.org, specifically https://bugs.maemo.org/enter_bug.cgi?product=maemo.org%20Websitecomponent=P romoter andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
