Re: Self-nomintation
On Aug 20, 2011, at 12:26, momcilo.ma...@gmail.com wrote: > Hi, > > According to the election terms, the nominations have not started yet. Ooops. I'm early. Oh well, release early, release often. :) > > Nominations open: 00:00, Thursday, 1st September 2011 > Nominations close: 23:59, Wednesday, 15th September 2011 > Voting opens: 00:00, Thursday, 22nd September 2010 > Voting closes: 23:59, Wednesday, 28th September 2010 > > Personally I think Debian rocks, but how do you integrate maemo software > within Debian? Damn good question. And that needs to be answered without a lot of handwaving. The DEX project began as Canonical's CTO identified a bunch of patches in Ubuntu that were relevant to Debian. I wonder if we might have the same? That is to say, I'd mine the Maemo package databases and find packages that were also in Debian, see if they are different from Debian and add the delta back to Debian. Along that path I bet we'll find other useful things for Debian, like changes to Lintian that are maybe appropriate for "vendor" Lintian checks. This is something I could add to my long stalled maemian project. > In addition we have an issue related to the closed sourced binaries? By moving software patches back to Debian, we can also begin to exert pressure on Nokia to supply any patches that they haven't yet added. They no longer have the business case to keep these blobs closed since they're no longer supporting Linux. We can demonstrate that we have the interest to do the work for them and that they have the obligation to provide those changes and that is about all we can do. But that is something. > Which devices would be targeted? I think if we had some interesting middleware from Maemo that ran on things like the OMAP 3 and 4, as well as the Freescale QSB, and Tegra 2 then we could make the case that there is software for tablets and phones as well as other mobile devices. That might be good motivation for people to hack these devices and put a Linux kernel on them, in fact all these chips have a Linux kernel already, so it wouldn't be much work to have a Debian like OS on anything that runs these chips and include Maemo middleware. That alone might persuade developers to continue to develop their software leading to new versions and potentially a completely free telephony stack for ARM. That is what I had in mind anyway. What do you think? What is the feedback from others? Regards, Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Garage Git Push Problem
On 08/09/2011 03:39 PM, Jamie Thompson wrote: On 2011-08-07 11:29 AM, koos vriezen wrote: FWIW I had to run 'git config --global --add http.sslVerify false' before I could push this week. Wasn't so a few months ago IIRC. (See, http.sslVerify option at http://kernel.org/pub/software/scm/git/docs/git-config.html ) Thanks for the reply. Sadly, I'd already found that information and turned it on :( ...and I suspect pulling wouldn't have worked if there were SSL errors as AFAIK pulling and pushing use the same transport? Yes, that is correct. git actually just calls curl to do the network negotiation. I have this in my .git/config for this repo: [http] sslVerify = false I don't know if this will help you but I usually set an environment variable that curl sees; $ export GIT_SSL_NO_VERIFY=true That allows me to not check SSL certs on the opposite end of git. Hope that helps, Regards, Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Nokia and MS
On Fri, Feb 11, 2011 at 09:01:23PM +0100, Klaus Umbach wrote: > On 11.02.11 13:25, Demetris wrote: > > > > How does this affect the future of Maemo on Nokia's devices? > > Maemo is dead and Meego will die, too. Don't be so sure. MeeGo is a set of vertical Linux distros. There are other phone manufacturers interested in the Handset vertical, car companies in the IVI vertical, and there is some serious traction in the TV vertical. MeeGo is hosted at the Linux Foundation, so it has nothing to do with Nokia in the end. This Nokia Microsoft hookup was designed to take the wind out of the sails of MeeGo, it is a serious contender to WinCE and Windows Phone. > Although Maemo is the plattform, that suits my personal needs best of all, > I lost hope, there will be a successor to my N900. I think I just give up > and get an android-phone with a keyboard and learn Java... heh, then you'll be party to the Oracle lawsuit. Plus, there are other languages you can use on Android aside from the Dalvik Java dialect. > Even if the community supports Maemo/Meego, there will be no new hardware > and one day my n900 will be broken... Nokia claims to be releasing a MeeGo device this year. > Why will Meego die? Because Intel doesn't care! They want to sell Hardware, > and will use Android, too. Don't be silly. Intel has to _compete_ with Android - Android doesn't run on x86 hardware! MeeGo is Intel's embedded OS, and they are spending 100 million US to support just the IVI vertical. I think you're barking up the wrong tree here. > This is a sad day for us, but at least a happy day for the Egyptions! (the > term "Maemobarak" just came to my mind, but doesn't really make sense...) w00t! Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: extras-testing delay ?
On Fri, 9 Oct 2009 23:01:20 +0100, gary liquid wrote: > hi, > > how long does a package take from -extras-devel to get to extras-testing It shouldn't take long, it probably depends on the size of the package. But I'll let Niels answer definitively. > > ive got a time sensitive package i would like to have on the system by my > presentation at 12.30 tomorrow. > > hopefully if i can get the liqbase-playground package installed from > extras-testing or extras-devel audience members can share in a little > community experience during our co-creation session at the summit :) Why can't they use the repo you are using? Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Continued problems with python dependencies
On Thu, 2009-06-04 at 13:55 -0400, Anderson Lizardo wrote: > Hi Jeremiah, > > On Thu, Jun 4, 2009 at 1:21 PM, Jeremiah Foster > wrote: > > >Interesting. I will run a script here to check python packages in > > >Diablo that should fail to install in fremantle due to missing > > >dependencies, and check which of these dependencies are related to > > > PyMaemo packages. > > > > What were the results of this? > > Ok, the above looks like a comment of mine :). Actually I didn't > finish this task yet. Once I have done it, I'll report the results > here. Fantastico! :) > > > Currently the state of python packages > > and their dependencies is confusing. It would be really great if you > > guys had a dependency tree, or some form of canonical list. Perhaps > > this page could get fleshed out a little? > > https://garage.maemo.org/plugins/wiki/index.php?PyMaemo%20Modules&id=40&type=g > > Something like this? > > http://wiki.maemo.org/PyMaemo Yes. :-) > > >> - They didn't know the auto-builder would let a package go through > > to > > >> extras-devel with dependencies missing. > > > > > I think the above two shows that the extras-devel system needs to be > > > more documented/promoted ? > > > > Which packages got built without their dependencies? > > The autobuilder does not check for *runtime* dependencies, only *build > time* ones. This is not a big issue (I think autobuilders from other > distros do the same, but I'm not sure), as long as it is > documented/promoted enough as Quim suggested. Build-time dependencies (i.e. build-depends) need to be there for that package to be built. But the Depends field in the control file should pull in those packages that are depended upon at runtime. > > > >> - Some didn't know where the "python-support (>= 0.90.0)" dependency > > >> actually came from. > > > > This I don't understand. Developers have to have all their > > dependencies in order to build the package locally, how would they not > > have all the depdencies? > > This can have a lot of reasons, one of them being that they simply > don't have the extras-devel repository on their local sbox > /etc/apt/sources.list. > > And if it is a runtime dependency problem, the build will finish ok, > although the package will not be installable. If this is the case, it > shows yet another QA issue: that the built packages might not have > been tested for correct installation/removal. Yes - I agree. This is a quality control issue. The dependency chain needs to be managed smoothly for users since they should not have to deal with this. > > > >* python-mokoui : no idea which package is this. Jeremiah/Niels: can > > > it be added the your automatic building task? > > > > This package has been sent to the fremantle autobuilder. > > I think the original maintainer has said that it should not be > necessary anymore and that the package that broke because of it > will/was fixed (if I remember correctly) It does not build in fremantle, at least right now. It is called libmokoui and I am going to try to get the errors fixed. Thanks for your complete and prompt response Anderson, I appreciate it. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Problems with Python dependencies
On May 25, 2009, at 11:45 AM, Soumya Bijjal wrote: > On Mon, 2009-05-25 at 08:17 +0200, Gil Quim (Nokia-D/Helsinki) wrote: > >> fwiw the dependencies missing included osso-gnomevfs-extra, >> python2.5-hildondesktop, python-mokoui & python-support >=0.90.0. >> > > Hi, > > osso-gnomevfs-extra is deprecated in Fremantle. In Beta SDK, > libhildonfm2 was still depending on it. But now, it is removed > internally. > > I have updated the Fremantle roadmap wiki: > http://wiki.maemo.org/Task:Maemo_roadmap/Fremantle#Data_management > Thanks for the update Soumya. I would be great if there were a list of python dependencies so that we do not repeat this type of problem in the future. This is a point of contact between the "open" community and the "closed" corporation that seems to need a tiny bit of oil to be friction free. If there were a clear list of dependencies, the community could also work on satisfying these issues and maybe even save Nokia time. Is there such a list? Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Identifying free/non-free apps (was Re: ... and QA of closed source applications?)
On May 7, 2009, at 12:17 PM, Quim Gil wrote: > > > ext Jeremiah Foster wrote: >> On May 6, 2009, at 17:47, Quim Gil wrote: >> >>> Hi, >>> >>> ext Attila Csipa wrote: >>> To make things worse, the application manager does not display the repository, much less the component an application belongs to. >>> Indeed, more information could be probably put in the "Application >>> details" --> "Summary e.g. the repository branch and there you could >>> see >>> whether it's free or non-free. Do you mind filing an enhancement >>> request? >> >> I am happy to do this if you don't want to Attila. > > Fine, but I please set your work priorities right. Only in the April > sprint you have 8 committed tasks, and the QA process (open & > closed) is > still more relevant that being totally clear with end users about the > license of the software they install. Yes, I will keep this in mind. I just meant I was willing to file an enhancement request, something that might take a couple minutes, not do the determination of free / non-free. > >> Then we really ought to specify two domains, Nokia and Community. > > Done? > >> Inside the Community domain we can specify whether an app is closed >> or >> open source. This way there is no misunderstanding, everything in the >> repos is free as in beer just some things are open source and some >> things are not. > > Maemo is doing this already through the Debian traditional way of > defining free/non-free, or am I missing something? > > >> However we want to implement that is fine, but I think >> the free / non-free distinction and its clumping together in the AM >> has to change, its just too confusing. > > Fine, but one thing are repository structures used by developers and > tools, and another thing are localization strings for end users. Let's > not mix them, please. > >> >> May I submit for your critique: >> >> /repository.maemo.org/extras/name/open/ >> /repository.maemo.org/extras/name/open/testing/ >> /repository.maemo.org/extras/name/open/new/ >> >> /repository.maemo.org/extras/name/closed/ >> /repository.maemo.org/extras/name/closed/testing >> /repository.maemo.org/extras/name/closed/new/ > > open? "free" is the standard and what is currently used. Why change. > closed? "non-free" is the standard and what is currently used. Why > change. > new? This actually sounds fresh and appealing to end users. "devel" is > what is currently used and defines the target and quality quite well. > Why change. Because, as you said yourself, non-free sounds like it costs money. The free / non-free distinction is confusing. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Python App on Maemo
On May 5, 2009, at 1:48 AM, Jey Han Lau wrote: > We are currently trying to build a GUI application on Maemo, and after > listening to suggestions from a few Maemo developers we started > prototyping it with Python and Qt. > > Python and Qt seems easy since the UI code designed from Qt designer > can > be converted into python automatically. But soon we came to realize > that > only the UI code (in xml) is converted, any functions, methods or code > written in C++ for the original Qt application has to be manually > translated into Python. Seems reasonable but now we aren't so sure if > this is the best approach anymore... > > The application we are building isn't too complicated (but will have > quite some number of screens/forms), and will contain SOAP web service > calls, and some file writing/reading. We've got the web service call > working using ZSI, so all that is left to decide is the UI framework > to > be used. Qt seems to be a better choice initially since it comes > with a > designer IDE that allows us to design the GUI more easily. > > Before we move on to spend more time using Python and Qt to develop > our > program, we'd like to hear some comments from you developers : ) If the strength of your development team is in C++, then prototype your application in C++. Qt is built on C++. The python bindings are very useful to prototype quickly if you are strong in python (Qt has other bindings as well, including perl bindings which are a SoC project.) But there is no need to prototype first in python - it gives you no special advantages aside from the fact that most prefer to code in python versus C++ and that some consider prototyping to be much faster in python. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: apt-get update works differently in different targets
On Thu, 2009-04-30 at 12:29 +0300, Claudio Saavedra wrote: > On Thu, 2009-04-30 at 10:53 +0200, Jeremiah Foster wrote: > > Hello, > > > > After installing the fremantle SDK beta, I am trying to get the X86 > > target running. I already have the ARMEL target working, installed the > > Nokia binaries and all but missed the explanation that one cannot run > > anything in the target yet. So I switched to the X86 target with sb- > > menu but once I am in that target I cannot reach the maemo fremantle > > repositories, which I know for a fact are up. ;) I can use apt-get > > perfectly in ARMEL, but it fails in X86. > > What's the error? [sbox-FREMANTLE_X86: ~] > apt-get update Err http://repository.maemo.org fremantle/sdk Release.gpg Temporary failure resolving 'repository.maemo.org' Err http://repository.maemo.org fremantle/tools Release.gpg Temporary failure resolving 'repository.maemo.org' Reading package lists... Done W: Failed to fetch http://repository.maemo.org/dists/fremantle/sdk/Release.gpg Temporary failure resolving 'repository.maemo.org' W: Failed to fetch http://repository.maemo.org/dists/fremantle/tools/Release.gpg Temporary failure resolving 'repository.maemo.org' W: Some index files failed to download, they have been ignored, or old ones used instead. W: You may want to run apt-get update to correct these problems [sbox-FREMANTLE_X86: ~] > Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: scratchbox apt-get update proplems
On Mar 23, 2009, at 11:42 AM, Luo Cheng wrote: Hi all, I got some problems with running apt-get update from my scratchbox, I am having these repositories in my /etc/apt/sources.list file deb http://repository.maemo.org/ diablo/sdk free non-free deb-src http://repository.maemo.org/ diablo/sdk free deb http://repository.maemo.org/ diablo/tools free non-free deb-src http://repository.maemo.org/ diablo/tools free deb file:/home/chengluo/maemo-sdk-nokia-binaries_4.1.1 diablo explicit but every time when i tried fakeroot apt-get update, i only stops at 57% like [sbox-DIABLO_ARMEL: /etc/apt] > fakeroot apt-get update I doubt fakeroot is the problem, but you can do sudo as well. Ign file: diablo Release.gpg This means it is Ignoring the gpg key. Ign file: diablo Release Another ignore line. 57% [Connecting to repository.maemo.org] This looks like a network issue of some kind, can you ping that address? Jeremiah___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Warnings when starting scratchbox (diablo) on debian Lenny
Hello, When I start up my dev environment in scratchbox I call 'af-sb-init.sh start'. I then get this warning; Starting DBUS system bus Starting D-BUS session bus daemon Starting Maemo Launcher: maemo-launcher. defender: died my parent is not who he claims to be maemo-launcher: warning rising the oom shield for pid=8471 status=2816 I assume this is not so serious since everything works, but I would love to know a little more about what is happening here. And shouldn't that be "raising oom shield" instead of "rising"? :) Google tells me other people might have similar questions; http://lists.maemo.org/pipermail/maemo-developers/2008-April/051052.html Google also mentions the Linux Out of Memory killer which may be why the shield is protecting against. Am I right in that assumption? Thanks! Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Lintian for maemo.org
Hello, My understanding is that Nokia has an internal version of lintian, the debian policy checker, which might be of use for maemo.org repositories. The idea is to run lintian over new packages to check conformance to policy in an automated fashion, hopefully improving quality of packages. If possible, can maemo.org get a copy of this modified lintian or better yet a URL pointing to where a development repo exists? Perhaps maemo.org can contribute changes back to the Nokia version. Thanks and warm regards, Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
