On 10/26/07, Laurent MARTIN [EMAIL PROTECTED] wrote:
Thanks for your work. But maybe the easiest way is to download that
VMWare image -
http://maemovmware.garage.maemo.org/
After various tests with various Torrent clients, I'm still not able to
download this VM image. For example, I
I downloaded that image via HTTP successfully. Maybe you should report
to the image creators.
Thank you for your email after having read it, I've realised that I was
downloading version 0.2 of the image from garage
(https://garage.maemo.org/projects/maemovmware/), not from the website
Hello!
* Since Nokia holds most of the infrastructure I fear Nokia has the
burden to supply the technical infrastructure while the community will
support the daily work, the rating and the quality assurance.
Fear? If this doesn't sound like a fair exchange then please suggest
fair
I'm sorry, this is a long one, but I've done my best to be as clear as
possible in order to avoid readers having to go on website and study a new
system just to follow what I wanted to say, if the same concepts were
written with few words as I could have done ;) So, please go with this
Errata:
[...] Of course the reply to his question (The error message shown when
you try to update python2.5-runtime doesn't mention anything about this?)
was no and so I continued using the old Python runtime. [...]
[...] Of course the reply to his answer was no and so I continued
using
Hello!
- Nokia: We want to centralize the development to just make things
easier, simpler and add service - without compromising the open
source idea. (Simplicity, centric)
Centralization doesn't compete with 'the open source idea'. We are
I did meant that (it was meant exactly they
Mathias Uebelacker wrote:
after installation, solving the resolve problem (thanks to Marius) and
installing python via apt-get the basic problem is still the same.
Every
time i call the run-standalone.sh ./myscript.py i get the error:
File ./myscript.py, line 2, in ?
import gtk
Alright, so we seem to agree in the general concepts. Let's go into details.
The question is not the quality of the Quality awareness document
which likely could be improved. The question is, if such a
document is the right way to control quality?
Alright, what about leaving the role of this
According to Eero Tamminen [EMAIL PROTECTED]:
Even better would be if it could build Debian source package on
request. Just by giving it the package name it would fetch the sources
from Debian repository and (try to) build them for Maemo.
While I understand the appeal, this is a really bad
According to Tim Teulings [EMAIL PROTECTED]:
Note that debian FTP master as far as I know only check license stuff
and similar - they do not check the application itself
True.
The Linux community distributions handle quality differently. They use
same small initial checks and then a staged
* Also we need a very easy way to get bug reports (and feature
requests) directly from the device into the bug tracking system.
It is clear the convenience of having an automated way to send crash
reports with traces, but what else would be needed other than that? Do
you mean an option
On 10/27/07, Steve Greenland [EMAIL PROTECTED] wrote:
I also want to point out the classic the perfect is enemy of the
good enough. The processes and documents can, and should, evolve as
the needs of the audience and developers evolve. But almost anything
would be an improvement to the
Hello!
Alright, what about leaving the role of this document in a checkbox developers
check in order to get upload rights to extras, à la terms
conditions. Something like I'm aware of the maemo Quality Awareness
criteria and
I have tested my applications against them before uploading
Hello!
Depends. The guide (aka the Debian Policy Document, aka policy)
distinguishes between musts and shoulds. Violations of musts are
considered Release Critical bugs, violations of shoulds are non-RC
bugs. Specific exceptions for specific packages have been made, when
justified.
In the
On Sat, 2007-10-27 at 21:17 +0300, [EMAIL PROTECTED] wrote:
but at least nobody can say - 'sorry guys, I didn't know my app could brick
the device'.
Requiring any quality control before having a place to put the
alpha/beta-quality stuff will just stop us from getting much software.
Software
Sorry my friend,
but Quim jest right.
There is a number of applications ported to Nokia Tablet,
in my case comoiled for N770, crashing my maemo.
The only solution proposed to me at http://www.internettablettalk.com/forums/
was to reflash my N770 with non-certified OS2007HE.
Having installed 3
I could use some help with my install.
I'm using Suse 10.3 for my development environment and I'm trying to
install the 3.1/3.2 Bora SDK.
Once I get to the step in the install instructions:
3.3 Nokia EUSA licensed binaries
The following bad thing happens. Could someone tell me how to
17 matches
Mail list logo