PDF rendering library for Qt
Hello, I am developing an application in Qt, for maemo5, in which I want to render a PDF. What library can I use for this? I have already tried poppler, it does not have its Qt binding available for maemo. I tried to port it, but faced lot of problems, so please suggest me some other library. OR are you aware of some PDF viewer for maemo 5 which is developed in Qt? Thanks, Akshey ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Autobuilder apt-get problems = failing builds
Hi, Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.root.log.FAILED.txt -8- The following packages have unmet dependencies: debconf: PreDepends: perl-base (= 5.6.1-4) but it is not going to be installed debhelper: Depends: perl (= 5.6.0-16) but it is not going to be installed Depends: coreutils but it is not going to be installed Depends: file (= 3.23-1) but it is not going to be installed Depends: html2text but it is not going to be installed Depends: binutils but it is not going to be installed dpkg-dev: Depends: dpkg (= 1.14.6) but it is not going to be installed Depends: perl5 Depends: cpio (= 2.4.2-2) but it is not going to be installed Depends: bzip2 but it is not going to be installed Depends: patch (= 2.2-1) but it is not going to be installed Depends: make but it is not going to be installed Depends: binutils but it is not going to be installed intltool-debian: Depends: perl but it is not going to be installed Depends: gettext but it is not going to be installed libtimedate-perl: Depends: perl (= 5.6.0-16) but it is not going to be installed maemo-optify: Depends: perl but it is not going to be installed mini-rc: Depends: ifupdown but it is not going to be installed osso-core-config: Depends: passwd but it is not going to be installed Depends: busybox but it is not installable or coreutils but it is not going to be installed PreDepends: base-passwd (= 3.5.7.osso2) but it is not going to be installed perl-modules: Depends: perl (= 5.8.3-1) but it is not going to be installed po-debconf: Depends: perl but it is not going to be installed Depends: gettext (= 0.12) but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). 8- This doesn't sound good. Known issue? My fault? Thanks in advance, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Unmap default action of hardwarbuttons [was Fremantle fullscreen mode]
Cornelius Hald gave the following tip: They key constants for the +/- keys are the same as on Diablo. But before you can use them you first have to unmap the default action, which is sound volume up/down. How do I unmap the default action?? I could not find it in the documentation:-( Thanks a lot Detlef ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
On Friday 01 January 2010 09:03:06 Andrew Flegg wrote: Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: [tons of missing deps] I think it happened because someone uploaded debconf and somehow it got pulled into the mix. I haven't looked deeply into it though. -Jeff ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
2010/1/1 Andrew Flegg and...@bleb.org: Hi, Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.root.log.FAILED.txt Should be fixed now: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/ Thanks for pointing out to this. Somebody's changed sbdmock configuration on the build host. I don't know why, because it was working just fine before. This reminds me aphorisms like 'Too many cooks spoil the broth' or 'Many commanders sink the ship. I like better Russian one 'Seven babysitters have a child without eye'. Autobuilder reminds me that child sometimes. -- BR, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
On Jan 1, 2010, at 15:00, Ed Bartosh wrote: 2010/1/1 Andrew Flegg and...@bleb.org: Hi, Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.root.log.FAILED.txt Should be fixed now: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/ Thanks for pointing out to this. Somebody's changed sbdmock configuration on the build host. I don't know why, because it was working just fine before. This reminds me aphorisms like 'Too many cooks spoil the broth' or 'Many commanders sink the ship. I like better Russian one 'Seven babysitters have a child without eye'. Autobuilder reminds me that child sometimes. Funny, I was thinking the exact opposite. If more people had access, then more than one person could fix it. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
2010/1/1 Jeremiah Foster jerem...@jeremiahfoster.com: On Jan 1, 2010, at 15:00, Ed Bartosh wrote: 2010/1/1 Andrew Flegg and...@bleb.org: Hi, Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.root.log.FAILED.txt Should be fixed now: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/ Thanks for pointing out to this. Somebody's changed sbdmock configuration on the build host. I don't know why, because it was working just fine before. This reminds me aphorisms like 'Too many cooks spoil the broth' or 'Many commanders sink the ship. I like better Russian one 'Seven babysitters have a child without eye'. Autobuilder reminds me that child sometimes. Funny, I was thinking the exact opposite. If more people had access, then more than one person could fix it. I doubt that. What I can see is that more people can break it. If you need a proof - give everyone root access to that box :) -- BR, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
On Friday 01 January 2010 11:12:47 Ed Bartosh wrote: 2010/1/1 Jeremiah Foster jerem...@jeremiahfoster.com: On Jan 1, 2010, at 15:00, Ed Bartosh wrote: 2010/1/1 Andrew Flegg and...@bleb.org: Hi, Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.root.l og.FAILED.txt Should be fixed now: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/ Thanks for pointing out to this. Somebody's changed sbdmock configuration on the build host. I don't know why, because it was working just fine before. This reminds me aphorisms like 'Too many cooks spoil the broth' or 'Many commanders sink the ship. I like better Russian one 'Seven babysitters have a child without eye'. Autobuilder reminds me that child sometimes. Funny, I was thinking the exact opposite. If more people had access, then more than one person could fix it. I doubt that. What I can see is that more people can break it. If you need a proof - give everyone root access to that box :) Starting with me. :) Though I must say things seem down an awfully lot and we just sit around waiting for someone to fix it. How does Fedora do it? I imagine they have a number of people with access. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
2010/1/1 Jeff Moe m...@blagblagblag.org: On Friday 01 January 2010 11:12:47 Ed Bartosh wrote: 2010/1/1 Jeremiah Foster jerem...@jeremiahfoster.com: On Jan 1, 2010, at 15:00, Ed Bartosh wrote: 2010/1/1 Andrew Flegg and...@bleb.org: Hi, Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.root.l og.FAILED.txt Should be fixed now: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/ Thanks for pointing out to this. Somebody's changed sbdmock configuration on the build host. I don't know why, because it was working just fine before. This reminds me aphorisms like 'Too many cooks spoil the broth' or 'Many commanders sink the ship. I like better Russian one 'Seven babysitters have a child without eye'. Autobuilder reminds me that child sometimes. Funny, I was thinking the exact opposite. If more people had access, then more than one person could fix it. I doubt that. What I can see is that more people can break it. If you need a proof - give everyone root access to that box :) Starting with me. :) Though I must say things seem down an awfully lot and we just sit around waiting for someone to fix it. How does Fedora do it? I imagine they have a number of people with access. OK, let's look at this particular case. Autobuilder was broken for about 15 hours. There were about 40 packages uploaded and failed during that time. Before that change builder was working fine. I really doubt that it would be better to have doesns of people to break this than 1-2 to fix. Even if those who can breake it could fix it. Anyway it was not working for a long time and people became confused. And now I'm restarting all those 40 builds manually. -- BR, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
2010/1/1 Ed Bartosh bart...@gmail.com: 2010/1/1 Jeff Moe m...@blagblagblag.org: On Friday 01 January 2010 11:12:47 Ed Bartosh wrote: 2010/1/1 Jeremiah Foster jerem...@jeremiahfoster.com: On Jan 1, 2010, at 15:00, Ed Bartosh wrote: 2010/1/1 Andrew Flegg and...@bleb.org: Hi, Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.root.l og.FAILED.txt Should be fixed now: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/ Thanks for pointing out to this. Somebody's changed sbdmock configuration on the build host. I don't know why, because it was working just fine before. This reminds me aphorisms like 'Too many cooks spoil the broth' or 'Many commanders sink the ship. I like better Russian one 'Seven babysitters have a child without eye'. Autobuilder reminds me that child sometimes. Funny, I was thinking the exact opposite. If more people had access, then more than one person could fix it. I doubt that. What I can see is that more people can break it. If you need a proof - give everyone root access to that box :) Starting with me. :) Though I must say things seem down an awfully lot and we just sit around waiting for someone to fix it. How does Fedora do it? I imagine they have a number of people with access. OK, let's look at this particular case. Autobuilder was broken for about 15 hours. There were about 40 packages uploaded and failed during that time. Before that change builder was working fine. Sorry, I was wrong. It was down for about 24 hours and there were about 50 failed package builds. -- BR, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
On Friday 01 January 2010 11:37:24 you wrote: 2010/1/1 Jeff Moe m...@blagblagblag.org: On Friday 01 January 2010 11:12:47 Ed Bartosh wrote: 2010/1/1 Jeremiah Foster jerem...@jeremiahfoster.com: On Jan 1, 2010, at 15:00, Ed Bartosh wrote: 2010/1/1 Andrew Flegg and...@bleb.org: Hi, Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.roo t.l og.FAILED.txt Should be fixed now: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/ Thanks for pointing out to this. Somebody's changed sbdmock configuration on the build host. I don't know why, because it was working just fine before. This reminds me aphorisms like 'Too many cooks spoil the broth' or 'Many commanders sink the ship. I like better Russian one 'Seven babysitters have a child without eye'. Autobuilder reminds me that child sometimes. Funny, I was thinking the exact opposite. If more people had access, then more than one person could fix it. I doubt that. What I can see is that more people can break it. If you need a proof - give everyone root access to that box :) Starting with me. :) Though I must say things seem down an awfully lot and we just sit around waiting for someone to fix it. How does Fedora do it? I imagine they have a number of people with access. OK, let's look at this particular case. Autobuilder was broken for about 15 hours. There were about 40 packages uploaded and failed during that time. Before that change builder was working fine. I really doubt that it would be better to have doesns of people to break this than 1-2 to fix. Even if those who can breake it could fix it. Well, you'd have a better case if things worked more reliably. Anyway it was not working for a long time and people became confused. And now I'm restarting all those 40 builds manually. I think we should look to Fedora since they have a similar arrangement: community distribution with corporate overlord. This is how they do it: * IRC channel of admin issues: #fedora-admin and #fedora-noc where you can watch things live. * Standard Operating Procedure for outages: https://fedoraproject.org/wiki/Outage_Infrastructure_SOP * *PAGER* access, available to the public, where you can page one of 9 admins (a bit unbelievable, actually): https://admin.fedoraproject.org/pager * More people would know how the whole *.maemo.org infrastructure actually worked if information about it was public. The joke is that it runs on a N700. But people can make this joke because the actual server set up is known by only a few. Compare that to this dream: https://fedoraproject.org/wiki/Category:Infrastructure_SOPs Anyway, they are doing things far better and I don't see people griping about outages over there much at all. What's the procedure for Maemo? Dive into #maemo-devel and hope someone knows WTF is up? Their answer is usually wait for x-fade. Post to talk.m.o.? Hit reload on qaiku? Post a comment there? Add more here? https://bugs.maemo.org/show_bug.cgi?id=5818 Surprisingly I was told by an @nokian that reporting to that bug *was* the correct place to report outages (!). Anyway, there are organizations all around the world that run servers 24/7/365 with minimal outages that have more than 2 admins with access. That is obvious. The maemo infrastructure is no where near approaching 99% uptime (let alone .999s). A mere 40 submitted builds is also a loss of time and momentum of many developers... -Jeff ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: New optification issues in extras-testing
Till Harbaum / Lists wrote: Hi, Am Mittwoch 30 Dezember 2009 schrieb Alberto Mardegan: This is my goal, but please move them in the 32GB storage. :-) Oh, i see what you mean. Urgh ... that's a tricky one as moving them for one app will break the other one. I don't think it's such a big problem: in the post-install script of the updated applications we can have a test that checks if the old tile directory exists (and is a regular dir, not a symlink) and if so copies all the tiles into the new location, and then removes the old dir and makes it a symbolic link to the new location. (the 32GB storage is FAT32 so it cannot have symlinks, but /home is ext3 so it should work) Ciao, Alberto -- http://www.mardy.it - geek in un lingua international! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Uploading software to Maemo repos
Hi Bryan, My name is Jeremiah Foster and I am the debmaster at maemo.org. I have seen a lot of your uploads recently which duplicate what already exists in the maemo repositories. In fact, some of these things, like debconf for example, might conflict with the development environment. Can you tell me your intentions? What are you trying to build? And have you read the appropriate documentation? Thanks, Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
On Jan 1, 2010, at 15:12, Ed Bartosh wrote: 2010/1/1 Jeremiah Foster jerem...@jeremiahfoster.com: On Jan 1, 2010, at 15:00, Ed Bartosh wrote: 2010/1/1 Andrew Flegg and...@bleb.org: now why, because it was working just fine before. This reminds me aphorisms like 'Too many cooks spoil the broth' or 'Many commanders sink the ship. I like better Russian one 'Seven babysitters have a child without eye'. Autobuilder reminds me that child sometimes. Funny, I was thinking the exact opposite. If more people had access, then more than one person could fix it. I doubt that. What I can see is that more people can break it. If you need a proof - give everyone root access to that box :) Seems to work for debian. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Uploading software to Maemo repos
On Jan 1, 2010, at 16:22, Bryan Jacobs wrote: Jeremiah, I needed ss-dev, debconf-utils, and a few other packages which *were* built from the Nokia official sources but which *were not* present in any repository I could find. The packages I built which are also in the official Nokia repository (e2fsprogs and debconf) are unmodified and constructed via apt-get source; dpkg-buildpackage. They will not go through - there is a check on the builder that prevents that sort of thing from happening, though the check sometimes fails. Do you read your build logs? Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Uploading software to Maemo repos
Jeremiah, 1. Why will they not go through? What is so special that they aren't allowed? 2. Is their a list of packages that are not allowed, and why isn't it linked to on the main upload page. Nathan. -Original Message- From: maemo-developers-boun...@maemo.org [mailto:maemo-developers-boun...@maemo.org] On Behalf Of Jeremiah Foster Sent: Friday, January 01, 2010 9:24 AM To: Bryan Jacobs Cc: maemo-developers mailing-list Subject: Re: Uploading software to Maemo repos On Jan 1, 2010, at 16:22, Bryan Jacobs wrote: Jeremiah, I needed ss-dev, debconf-utils, and a few other packages which *were* built from the Nokia official sources but which *were not* present in any repository I could find. The packages I built which are also in the official Nokia repository (e2fsprogs and debconf) are unmodified and constructed via apt-get source; dpkg-buildpackage. They will not go through - there is a check on the builder that prevents that sort of thing from happening, though the check sometimes fails. Do you read your build logs? Jeremiah ___ 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
Re: Autobuilder apt-get problems = failing builds
On Jan 1, 2010, at 16:00, Jeff Moe wrote: On Friday 01 January 2010 11:37:24 you wrote: 2010/1/1 Jeff Moe m...@blagblagblag.org: On Friday 01 January 2010 11:12:47 Ed Bartosh wrote: 2010/1/1 Jeremiah Foster jerem...@jeremiahfoster.com: On Jan 1, 2010, at 15:00, Ed Bartosh wrote: 2010/1/1 Andrew Flegg and...@bleb.org: Hi, Attempting to upload a new version of vim to the Fremantle auto-builder, I get the following failure: https://garage.maemo.org/builder/fremantle/vim_7.2-0maemo6/armel.roo t.l og.FAILED.txt Well, you'd have a better case if things worked more reliably. Anyway it was not working for a long time and people became confused. And now I'm restarting all those 40 builds manually. I think we should look to Fedora since they have a similar arrangement: community distribution with corporate overlord. This is how they do it: * IRC channel of admin issues: #fedora-admin and #fedora-noc where you can watch things live. Good idea. * Standard Operating Procedure for outages: https://fedoraproject.org/wiki/Outage_Infrastructure_SOP Really good idea, we should have an SOP for that. * *PAGER* access, available to the public, where you can page one of 9 admins (a bit unbelievable, actually): https://admin.fedoraproject.org/pager I don't want to wear a pager, and I don't think it is necessary, but still. * More people would know how the whole *.maemo.org infrastructure actually worked if information about it was public. The joke is that it runs on a N700. It's no joke. /sarcasm Nokia is doing a lot to address the infrastructure problem. Part of it comes from the open / not open split and how a International Corporation deals with integrating Free Software developers into a corporate workflow. Nokia is not perfect, but they are willing to learn and work hard, so I thin being patient here is worth your while. Red Hat has not been prefect here either. But people can make this joke because the actual server set up is known by only a few. Compare that to this dream: https://fedoraproject.org/wiki/Category:Infrastructure_SOPs This is awesome, I think this is a good idea. Part of the problem has been critical mass - we haven't had enough developers willing to take on these kind of issues, Nokia has had to provide it or recruit people. We have grown a lot in 2009 so maybe we can get teams from the community to do this sort of work. Anyway, they are doing things far better and I don't see people griping about outages over there much at all. Different project, different goals, they've been around a lot longer (they were once Red Hat remember) and they have a lot of experience. You have to give credit to Nokia and the people who work hard on the infrastructure - they do a lot of really hard work and this whole experiment is fairly new for Nokia. I am confident the whole process will improve. What's the procedure for Maemo? Dive into #maemo-devel and hope someone knows WTF is up? Their answer is usually wait for x-fade. Post to talk.m.o.? Hit reload on qaiku? Post a comment there? Add more here? https://bugs.maemo.org/show_bug.cgi?id=5818 Surprisingly I was told by an @nokian that reporting to that bug *was* the correct place to report outages (!). I think it would be less than honest to not say this is suboptimal. Anyway, there are organizations all around the world that run servers 24/7/365 with minimal outages that have more than 2 admins with access. That is obvious. The maemo infrastructure is no where near approaching 99% uptime (let alone .999s). A mere 40 submitted builds is also a loss of time and momentum of many developers... Nokia is a handset maker. They are not a company that does a lot of public facing internet server work. That is changing. Constructive criticism from the community will help, like the good examples you have linked to. We as a community need to continue to show a good example and demonstrate to Nokia that we are reliable and reasonable, then we can build out maemo into something we are proud of. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder apt-get problems = failing builds
On Friday 01 January 2010 12:18:53 Jeremiah Foster wrote: On Jan 1, 2010, at 15:12, Ed Bartosh wrote: 2010/1/1 Jeremiah Foster jerem...@jeremiahfoster.com: On Jan 1, 2010, at 15:00, Ed Bartosh wrote: 2010/1/1 Andrew Flegg and...@bleb.org: now why, because it was working just fine before. This reminds me aphorisms like 'Too many cooks spoil the broth' or 'Many commanders sink the ship. I like better Russian one 'Seven babysitters have a child without eye'. Autobuilder reminds me that child sometimes. Funny, I was thinking the exact opposite. If more people had access, then more than one person could fix it. I doubt that. What I can see is that more people can break it. If you need a proof - give everyone root access to that box :) Seems to work for debian. And Fedora, and... According to Fedora's Nigel Jones, a well-known-fedoraista and admin: G: jebba: I think it stands at about 15 unique people that can cover buildsys issues G: jebba: and that spans US, Europe and Australia/NZ (I am the latter) G: jebba: it is mostly US, but if I'm not around or the ones in Europe (I think it's still only 1 but I'm not 100% sure) then there is people in US that can be paged G: (not all people on the pager can fix buildsys issues) -Jeff http://wiki.maemo.org/User:Jebba ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Packages using cdbs broken?
Hello all! I cannot seem to build any Debian package using cdbs in my Fremantle scratchbox. The output I get always looks like this: dpkg-buildpackage: source package is heimdal dpkg-buildpackage: source version is 1.2.dfsg.1-2.1maemo1 dpkg-buildpackage: source changed by Bryan Jacobs b...@q3q.us dpkg-buildpackage: host architecture armel dpkg-buildpackage: source version without epoch 1.2.dfsg.1-2.1maemo1 : Using Scratchbox tools to satisfy builddeps : Dependency provided by Scratchbox: bison : Dependency provided by Scratchbox: cdbs : Dependency provided by Scratchbox: texinfo : Dependency provided by Scratchbox: python fakeroot debian/rules clean test -x debian/rules make: *** [testdir] Error 1 Obviously, Error 1 doesn't tell me anything. I'm pretty sure it's cdbs that's causing the issue as this happens with 100% of the packages I've tried making use of it and 0% of packages not using it. Any help? Bryan Jacobs signature.asc Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Packages using cdbs broken?
That does it! Note to self: use the tar 'p' option for sources. I'm puzzled by why *any* of my builds have worked without this. Bryan Jacobs On Fri, 1 Jan 2010 16:24:10 + Faheem Pervez tripp...@gmail.com wrote: And you're sure debian/rules is marked as executable? On Fri, Jan 1, 2010 at 4:14 PM, Bryan Jacobs n...@landwarsin.asia wrote: Hello all! I cannot seem to build any Debian package using cdbs in my Fremantle scratchbox. The output I get always looks like this: dpkg-buildpackage: source package is heimdal dpkg-buildpackage: source version is 1.2.dfsg.1-2.1maemo1 dpkg-buildpackage: source changed by Bryan Jacobs b...@q3q.us dpkg-buildpackage: host architecture armel dpkg-buildpackage: source version without epoch 1.2.dfsg.1-2.1maemo1 : Using Scratchbox tools to satisfy builddeps : Dependency provided by Scratchbox: bison : Dependency provided by Scratchbox: cdbs : Dependency provided by Scratchbox: texinfo : Dependency provided by Scratchbox: python fakeroot debian/rules clean test -x debian/rules make: *** [testdir] Error 1 Obviously, Error 1 doesn't tell me anything. I'm pretty sure it's cdbs that's causing the issue as this happens with 100% of the packages I've tried making use of it and 0% of packages not using it. Any help? Bryan Jacobs ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers signature.asc Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Uploading software to Maemo repos
Jeremiah, I'm not trying to be at all argumentive, I just would like to know the reasons. 1. Why will they not go through? What is so special that they aren't allowed? Because there are other versions which are needed to build other packages. Yes, but the build server should reset to known good config; why would someone building a newer version of debconf break it? 2. Is their a list of packages that are not allowed, and why isn't it linked to on the main upload page. Have you read the wiki? Or any other development documentation? Yes, in fact I've edited the docs when I've found things wrong. But I don't ever recall reading anything about building debconf breaking the builder and that I should not attempt to build it. Can you point to which wiki document has the info on bad packages not to build. I'd like to know so if in the future I can avoid them. (And as a recommendation, I would recommend someone add that as a link to the main package upload page) Nathan. -Original Message- From: maemo-developers-boun...@maemo.org [mailto:maemo-developers-boun...@maemo.org] On Behalf Of Jeremiah Foster Sent: Friday, January 01, 2010 9:24 AM To: Bryan Jacobs Cc: maemo-developers mailing-list Subject: Re: Uploading software to Maemo repos On Jan 1, 2010, at 16:22, Bryan Jacobs wrote: Jeremiah, I needed ss-dev, debconf-utils, and a few other packages which *were* built from the Nokia official sources but which *were not* present in any repository I could find. The packages I built which are also in the official Nokia repository (e2fsprogs and debconf) are unmodified and constructed via apt-get source; dpkg-buildpackage. They will not go through - there is a check on the builder that prevents that sort of thing from happening, though the check sometimes fails. Do you read your build logs? Jeremiah ___ 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Unmap default action of hardwarbuttons [was Fremantle fullscreen mode]
Hi, you have to set an XAtom on your window. This is how I do it in Python: self.__window.window.property_change(_HILDON_ZOOM_KEY_ATOM, XA_INTEGER, 32, gtk.gdk.PROP_MODE_REPLACE, [1]) Martin 2010/1/1, ds d...@physik.de: Cornelius Hald gave the following tip: They key constants for the +/- keys are the same as on Diablo. But before you can use them you first have to unmap the default action, which is sound volume up/down. How do I unmap the default action?? I could not find it in the documentation:-( Thanks a lot Detlef ___ 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
Re: New optification issues in extras-testing
Hi, Am Freitag 01 Januar 2010 schrieb Alberto Mardegan: directory exists (and is a regular dir, not a symlink) and if so copies all the tiles into the new location, and then removes the old dir and makes it a symbolic link to the new location. Yes, that what i also came up with after some thinking. The only issue: This may take some time. I e.g. have ~150MB in that directory. The user may think the installation hangs if i move that much data. So some dialog has to be presented to the user. Ciao, Till ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Where to find sources of gtk+ 2:2.14.7-1maemo15?
Hi Maemo5 repository contains sources of GTK+ 2.14.17-1maemo12 but newest hildon-desktop requires maemo15 version (crashes with maemo12 in SDK). Where I can find development tree with Maemo5 gtk+? Regards, -- JID: h...@jabber.org Website: http://marcin.juszkiewicz.com.pl/ LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Where to find sources of gtk+ 2:2.14.7-1maemo15?
Dnia sobota, 2 stycznia 2010 o 07:22:30 Marcin Juszkiewicz napisał(a): Hi Maemo5 repository contains sources of GTK+ 2.14.17-1maemo12 but newest hildon-desktop requires maemo15 version (crashes with maemo12 in SDK). Where I can find development tree with Maemo5 gtk+? Thanks to villager from #maemo-devel I am fetching maemo22 version now from SVN. Regards, -- JID: h...@jabber.org Website: http://marcin.juszkiewicz.com.pl/ LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
