Re: How to use MySQL with Maemo 5?
have you tried to install libqt4 mysql plugin ? This should help in case you havent already seen it http://doc.trolltech.com/4.6/sql-driver.html#qmysql http://doc.trolltech.com/4.6/sql-driver.html#qmysql http://doc.trolltech.com/4.6/sql-driver.html#qmysql - Original Message - From: Sascha Mäkelä Sent: 03/30/10 06:57 AM To: maemo-developers Subject: How to use MySQL with Maemo 5? I'm trying to retrieve data from a MySQL server. I use the following example code (with some slight modifications): Code: QSqlDatabase db = QSqlDatabase::addDatabase(QMYSQL); db.setHostName(bigblue); db.setDatabaseName(flightdb); db.setUserName(acarlson); db.setPassword(1uTbSbAs); bool ok = db.open();But I get the following error: Quote: QSqlDatabase: QMYSQL driver not loaded QSqlDatabase: available drivers: QSQLITEIs MySQL even supported in Maemo or am I doing something wrong? I also found the following two links: http://qt.nokia.com/doc/4.6/sql-driver.html http://qt.nokia.com/doc/4.6/sql-driver.html http://qt.nokia.com/doc/4.6/install-x11.html http://qt.nokia.com/doc/4.6/install-x11.html But I'm not quite sure where I should install these drivers. Should I install them in my Windows computer, where I'm using MADDE and Qt Creator (well, actually I'm using now the Qt Creator 2.0 Technology Preview, so I'm not quite sure if it's using MADDE any more)? Or should I install them on the target N900? Or both? Or am I completely on the wrong tracks here? Any help would be greatly appreciated. Cheers, Sascha ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to use MySQL with Maemo 5?
sorry I didnt read the message below your error :p please ignore my message, will post when I get a chance to see it in detail. I've used sqllite on Linux and its just a matter of installing the plugins required for dev/runtime env. - Original Message - From: Ram Kurvakat Sent: 03/30/10 07:52 AM To: Sascha Mäkelä, maemo-developers Subject: Re: How to use MySQL with Maemo 5? have you tried to install libqt4 mysql plugin ? This should help in case you havent already seen it http://doc.trolltech.com/4.6/sql-driver.html#qmysql http://doc.trolltech.com/4.6/sql-driver.html#qmysql http://doc.trolltech.com/4.6/sql-driver.html#qmysql - Original Message - From: Sascha Mäkelä Sent: 03/30/10 06:57 AM To: maemo-developers Subject: How to use MySQL with Maemo 5? I'm trying to retrieve data from a MySQL server. I use the following example code (with some slight modifications): Code: QSqlDatabase db = QSqlDatabase::addDatabase(QMYSQL); db.setHostName(bigblue); db.setDatabaseName(flightdb); db.setUserName(acarlson); db.setPassword(1uTbSbAs); bool ok = db.open();But I get the following error: Quote: QSqlDatabase: QMYSQL driver not loaded QSqlDatabase: available drivers: QSQLITEIs MySQL even supported in Maemo or am I doing something wrong? I also found the following two links: http://qt.nokia.com/doc/4.6/sql-driver.html http://qt.nokia.com/doc/4.6/sql-driver.html http://qt.nokia.com/doc/4.6/install-x11.html http://qt.nokia.com/doc/4.6/install-x11.html But I'm not quite sure where I should install these drivers. Should I install them in my Windows computer, where I'm using MADDE and Qt Creator (well, actually I'm using now the Qt Creator 2.0 Technology Preview, so I'm not quite sure if it's using MADDE any more)? Or should I install them on the target N900? Or both? Or am I completely on the wrong tracks here? Any help would be greatly appreciated. Cheers, Sascha ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Mixing audio streams
Hello, What I'm trying to get is an application (or two separate apps, doesn't really matter) that will be able to output two streams (from fmradio and mic) separately (so some operations may be performed on them). So far I'm trying to user fmradio and maemo-recorder to achieve this. Running fmradio and setting Input Select (in alsamixer -c0) to Digital, let me hear both fm output and mic at the same time. The problem is that those are the same stream for the application, so I cannot manipulate them separately. With this setting, however, maemo-recorder is able to record only mic (without fm stream). What stuns me is that both fmradio (giving both mic and fm) and maemo-recorder (giving just mic) use pulsesrc in gstreamer. Any ides how this (two separate streams) can be done? Link to post at tmo: http://talk.maemo.org/showthread.php?t=48457highlight=fmradio I would really appreciate some help with this (part of a larger project, blocking others). Best regards / Med venlig hilsen / Z poważaniem, Arek --- Believe nothing, no matter where you read it, or who said it, no matter if I have said it, unless it agrees with your own reason and your own common sense. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to include glib-object.h
Hi, thanks a bunch for the helpful info. Will try either of them as soon I solved another problem :) . Best regards, ce ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
OT: Cannot select targets - where's the session PID file?
Hi, a bit off-topic, but I hope someone has seen such an issue before. When I do an sb-conf select FREMANTLE_X86 sb-conf complains You must close your other Scratchbox sessions first There is no other session open, though. I guess I closed a shell window yesterday without logging out properly from scratchbox, so a session PID file (or similar) remained in place. Does anyone know whether I can fix this issue by removing some file manually? Best regards, ce ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
ext Marcin Juszkiewicz mar...@juszkiewicz.com.pl writes:
Is there a way of specifiying to use the older packages?
No such option.
The problem are the automatic generated dependencies, if I understand
things right.
I.e., you build against libqt4-core version 4.6.2~git20100224, and the
resulting package ends up having this:
Depends: libqt4-core (= 4.6.2~git20100224)
(Among others, of course.) This originates from this in your source
package:
Depends: ${shlibs:Depends}
The text libqt4-core (= 4.6.2~git20100224) comes from the libqt4-core
package itself that is installed while building. But: You can overwrite
it if you know better what dependency you want to have.
You do this by putting a debian/shlibs.local file into your source
package. It might look like this:
libQtCore 4 libqt4-core (= WHATEVER-YOU-WANT)
ETC...
Of course, this only changes the text in the Depends field of your
package. You must make sure that your program actually runs with the
older version of Qt even when it has been compiled against the newer
version.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: OT: Cannot select targets - where's the session PID file?
log out of all your scratchbox env except one. type sb-menu. select kill all processes in scratch box. then try it :-) - Original Message - From: Christoph Eckert Sent: 03/30/10 10:59 AM To: maemo-developers@maemo.org Subject: OT: Cannot select targets - where's the session PID file? Hi, a bit off-topic, but I hope someone has seen such an issue before. When I do an sb-conf select FREMANTLE_X86 sb-conf complains You must close your other Scratchbox sessions first There is no other session open, though. I guess I closed a shell window yesterday without logging out properly from scratchbox, so a session PID file (or similar) remained in place. Does anyone know whether I can fix this issue by removing some file manually? Best regards, ce ___ 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 Theme Maker failed to produce Debian package
Hi all! I'm trying to produce sample theme package using Maemo Theme Maker 1.2.9: https://garage.maemo.org/projects/thememaker/ I'm selecting backgrounds-template.png as Theme Background and nuvo-fremantle-template.png as Theme Source Image. Maemo Theme Maker produces the folder with package files and then fails with a message: Control file creation failed. =!CLEANUP START!= === cleanup: piu === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/startup-wizard === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/rtcom-messaging-ui deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/rtcom-messaging-ui/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/mediaplayer deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/mediaplayer/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/call-ui deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/call-ui/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/gtk-2.0 deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/gtk-2.0/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/images deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/images/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/css deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/css/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/backgrounds deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/backgrounds/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable/hildon deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable/hildon/.DS_Store deleted recursive:/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/__MACOSX === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox2 deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox2/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/dropdown === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/checkbox === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/scrollbar === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/active_element === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/active_element_out_of_view === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/push_button === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/edit === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/radio_button === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/scrollbar_knob === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/resize_corner === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/debian deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/debian/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/calendar deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/calendar/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox/.DS_Store tar:/opt/themes/ passing: /opt/themes tar:/opt/themes/piu/ passing: /opt/themes/piu tar:/opt/themes/piu/startup-wizard/ passing: /opt/themes/piu/startup-wizard tar:/opt/themes/piu/rtcom-messaging-ui/ passing: /opt/themes/piu/rtcom-messaging-ui tar:/opt/themes/piu/mediaplayer/ passing: /opt/themes/piu/mediaplayer tar:/opt/themes/piu/call-ui/ passing: /opt/themes/piu/call-ui tar:/opt/themes/piu/gtk-2.0/ passing: /opt/themes/piu/gtk-2.0 tar:/opt/themes/piu/images/ passing: /opt/themes/piu/images tar:/opt/themes/piu/css/ passing: /opt/themes/piu/css tar:/opt/themes/piu/backgrounds/ passing: /opt/themes/piu/backgrounds tar:/opt/themes/piu/matchbox2/ passing: /opt/themes/piu/matchbox2 tar:/opt/themes/piu/opera/ passing: /opt/themes/piu/opera tar:/opt/themes/piu/opera/dropdown/ passing:
Re: How to use MySQL with Maemo 5?
Hi Sascha! You should install libqt4-maemo5-sql-mysql package on the device. Also you should install mysql plugin on you PC, if you want to debug there. Thanks, Daniil. On Tue, Mar 30, 2010 at 11:54 AM, Sascha Mäkelä sascha.mak...@gmail.comwrote: So basically I should somehow install the plugin somewhere under /madde on the N900, right? Has anyone done this and how? I'm not that familiar with Linux. Thank you for your help, Sascha On Tue, Mar 30, 2010 at 09:59, Ram Kurvakat rkma...@gmx.com wrote: sorry I didnt read the message below your error :p please ignore my message, will post when I get a chance to see it in detail. I've used sqllite on Linux and its just a matter of installing the plugins required for dev/runtime env. - Original Message - From: Ram Kurvakat Sent: 03/30/10 07:52 AM To: Sascha Mäkelä, maemo-developers Subject: Re: How to use MySQL with Maemo 5? have you tried to install libqt4 mysql plugin ? This should help in case you havent already seen it http://doc.trolltech.com/4.6/sql-driver.html#qmysql http://doc.trolltech.com/4.6/sql-driver.html#qmysql - Original Message - From: Sascha Mäkelä Sent: 03/30/10 06:57 AM To: maemo-developers Subject: How to use MySQL with Maemo 5? I'm trying to retrieve data from a MySQL server. I use the following example code (with some slight modifications): Code: QSqlDatabase db = QSqlDatabase::addDatabase(QMYSQL); db.setHostName(bigblue); db.setDatabaseName(flightdb); db.setUserName(acarlson); db.setPassword(1uTbSbAs); bool ok = db.open(); But I get the following error: Quote: QSqlDatabase: QMYSQL driver not loaded QSqlDatabase: available drivers: QSQLITE Is MySQL even supported in Maemo or am I doing something wrong? I also found the following two links: http://qt.nokia.com/doc/4.6/sql-driver.html http://qt.nokia.com/doc/4.6/install-x11.html But I'm not quite sure where I should install these drivers. Should I install them in my Windows computer, where I'm using MADDE and Qt Creator (well, actually I'm using now the Qt Creator 2.0 Technology Preview, so I'm not quite sure if it's using MADDE any more)? Or should I install them on the target N900? Or both? Or am I completely on the wrong tracks here? Any help would be greatly appreciated. Cheers, Sascha ___ 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: OT: Cannot select targets - where's the session PID file?
On Tue, Mar 30, 2010 at 1:19 PM, Ram Kurvakat rkma...@gmx.com wrote: log out of all your scratchbox env except one. type sb-menu. select kill all processes in scratch box. You often need to specify signal 9 as well. You can save some time by executing sb-conf ka -s 9. -- Ville M. Vainio http://tinyurl.com/vainio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Theme Maker failed to produce Debian package
On Mar 30, 2010, at 12:54 PM, Daniil Ivanov wrote: Hi all! Hi there! I'm trying to produce sample theme package using Maemo Theme Maker 1.2.9: https://garage.maemo.org/projects/thememaker/ I haven't use that tool before unfortunately, so I can't give you any advice except to contact the developer. It looks like it uses Java which is a pretty odd language to use to build debian packages seeing that debian is not necessarily consider the greatest Java platform in the world. I have a suspicion that creating a package following the wiki might be easier: http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing There are also other tools in Maemo you might want to try; mud and py2deb, and perhaps others I am missing. Jeremiah I'm selecting backgrounds-template.png as Theme Background and nuvo-fremantle-template.png as Theme Source Image. Maemo Theme Maker produces the folder with package files and then fails with a message: Control file creation failed. =!CLEANUP START!= === cleanup: piu === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/startup-wizard === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/rtcom-messaging-ui deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/rtcom-messaging-ui/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/mediaplayer deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/mediaplayer/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/call-ui deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/call-ui/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/gtk-2.0 deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/gtk-2.0/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/images deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/images/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/css deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/css/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/backgrounds deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/backgrounds/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable/hildon deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable/hildon/.DS_Store deleted recursive:/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/__MACOSX === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox2 deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox2/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/dropdown === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/checkbox === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/scrollbar === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/active_element === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/active_element_out_of_view === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/push_button === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/edit === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/radio_button === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/scrollbar_knob === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/resize_corner === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/debian deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/debian/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/calendar deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/calendar/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox/.DS_Store tar:/opt/themes/ passing: /opt/themes
Re: Maemo Theme Maker failed to produce Debian package
Hi! I've failed to contact developer. I believe Java was choosen due to its cross platform nature. I've modified the sources to allow better logging in exception handlers. Now it looks like DEBIAN folder is not created at some point: [skipped] Control file creation failed:/home/divanov/thememaker/ThemeMaker1.2.9/piu/DEBIAN/control (No such file or directory) =!CLEANUP START!= === cleanup: piu === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/startup-wizard === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/rtcom-messaging-ui deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/rtcom-messaging-ui/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/mediaplayer deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/mediaplayer/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/call-ui deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/call-ui/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/gtk-2.0 deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/gtk-2.0/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/images deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/images/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/css deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/css/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/backgrounds deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/backgrounds/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable/hildon deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/icons/scalable/hildon/.DS_Store deleted recursive:/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/__MACOSX === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox2 deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox2/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/dropdown === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/checkbox === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/scrollbar === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/active_element === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/active_element_out_of_view === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/push_button === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/edit === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/radio_button === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/scrollbar_knob === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/opera/resize_corner === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/debian deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/debian/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/calendar deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/calendar/.DS_Store === cleanup: /home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox deleted/home/divanov/thememaker/ThemeMaker1.2.9/piu/opt/themes/piu/matchbox/.DS_Store tar:/opt/themes/ passing: /opt/themes tar:/opt/themes/piu/ passing: /opt/themes/piu tar:/opt/themes/piu/startup-wizard/ passing: /opt/themes/piu/startup-wizard tar:/opt/themes/piu/rtcom-messaging-ui/ passing: /opt/themes/piu/rtcom-messaging-ui tar:/opt/themes/piu/mediaplayer/ passing: /opt/themes/piu/mediaplayer tar:/opt/themes/piu/call-ui/ passing: /opt/themes/piu/call-ui tar:/opt/themes/piu/gtk-2.0/ passing: /opt/themes/piu/gtk-2.0 tar:/opt/themes/piu/images/ passing: /opt/themes/piu/images tar:/opt/themes/piu/css/ passing: /opt/themes/piu/css tar:/opt/themes/piu/backgrounds/ passing: /opt/themes/piu/backgrounds tar:/opt/themes/piu/matchbox2/ passing: /opt/themes/piu/matchbox2 tar:/opt/themes/piu/opera/ passing: /opt/themes/piu/opera tar:/opt/themes/piu/opera/dropdown/ passing:
Re: Maemo Theme Maker failed to produce Debian package
Hi! Sorry, I forgot to mention pretty relevant information, that I'm searching for a one-button-press solution, which will be used on Windows by people with no Linux experience, so manual package creation is a no go solution. Thanks, Daniil. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Theme Maker failed to produce Debian package
On Mar 30, 2010, at 2:24 PM, Daniil Ivanov wrote: Hi! Sorry, I forgot to mention pretty relevant information, that I'm searching for a one-button-press solution, which will be used on Windows by people with no Linux experience, so manual package creation is a no go solution. Then why not just submit your sources to OBS? Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Theme Maker failed to produce Debian package
Hiya, On Tue, Mar 30, 2010 at 1:24 PM, Daniil Ivanov daniil.iva...@gmail.com wrote: Sorry, I forgot to mention pretty relevant information, that I'm searching for a one-button-press solution, which will be used on Windows by people with no Linux experience, so manual package creation is a no go solution. This is not a one-click solution, but I understand http://wiki.maemo.org/MADDE/Theme_building is popular among Windows-using themers, with many of the themes available in Extras-devel built using MADDE. Best Regards, Faheem ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
Yes, that's what I ended up doing, since I'm building using MADDE it's
qt 4.5 anyway. Package was built OK by the extras build server and I
was able to install the package on the device. However it is unstable
and seems to crash for no apparent reason. I was able to install the
386 version on scratchbox and that runs OK. Weird.
The other weird thing is that on the device I saw there were some
updates installable through command line that installed the 4.6
packages but this doesn't look like it does anything.
- ianaré sévi
2010/3/30 Marius Vollmer marius.voll...@nokia.com:
ext Marcin Juszkiewicz mar...@juszkiewicz.com.pl writes:
Is there a way of specifiying to use the older packages?
No such option.
The problem are the automatic generated dependencies, if I understand
things right.
I.e., you build against libqt4-core version 4.6.2~git20100224, and the
resulting package ends up having this:
Depends: libqt4-core (= 4.6.2~git20100224)
(Among others, of course.) This originates from this in your source
package:
Depends: ${shlibs:Depends}
The text libqt4-core (= 4.6.2~git20100224) comes from the libqt4-core
package itself that is installed while building. But: You can overwrite
it if you know better what dependency you want to have.
You do this by putting a debian/shlibs.local file into your source
package. It might look like this:
libQtCore 4 libqt4-core (= WHATEVER-YOU-WANT)
ETC...
Of course, this only changes the text in the Depends field of your
package. You must make sure that your program actually runs with the
older version of Qt even when it has been compiled against the newer
version.
___
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: Dependency problems after PR 1.2 update to extras builder
On Mon, Mar 29, 2010 at 15:37, ianaré sévi ian...@gmail.com wrote: After making some updates to my package and putting it up on extras-devel, it won't update on the device from the repository. I was able to install it on scratchbox (both prior to and after updating the SDK). So, AIUI (and others did too), the autobuilder would be upgraded to PR1.2's SDK and start publishing to fremantle-1.2 (rather than the current fremantle). However, yesterday on IRC, there were some complaints that the auto-generated components for things in fremantle extras-devel had incorrect dependencies: http://mg.pov.lt/maemo-irclog/%23maemo.2010-03-29.log.html#t2010-03-29T08:01:18 (see conversation primarily between Jaffa, Stskeeps, DocScrutinizer and Chiku|dc) I thought the fremantle extras-devel should now be fixed, so how are things with incorrect dependencies getting in? Niels, could it'd've been a race condition during the switch; or is it a bug; or are we corrupting fremantle extras-devel? 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
Re: Builder now runs PR1.2 SDK with Qt 4.6 support
On Wed, Mar 24, 2010 at 14:07, Niels Breet ni...@maemo.org wrote: I've installed the new PR1.2 SDK on the maemo.org Extras autobuilder. Developers are encouraged to test their application in the PR1.2 SDK to see if everything still works as expected. Following some confusion[1][2], I've had a chat with Niels today and the following wasn't clear (to me): * The plan[3] affects Extras only; not -devel and not -testing. * Extras-devel is now being fed from the PR1.2 SDK. * This means that auto-generated libhildon dependencies are being specified too tightly to install on devices and SDKs lower than PR1.2 (due to the introduction of new symbols for livesearch[4]) Niels is looking at a fix for the libhildon dependencies[6]. In the meantime, whilst waiting for PR1.2: * Updates to software in -devel will result in it not being installable; and the old package will no longer be available. * Things can be pushed to -devel and -testing, testing in Scratchbox so that software using the new features can be in Extras when PR1.2 finally lands. Matan Ziv-Av mentioned the replacement of extras-devel three days ago but didn't elaborate, and it sounded like misunderstanding. Hope that helps, Andrew [1] http://lists.maemo.org/pipermail/maemo-developers/2010-March/025627.html [2] http://mg.pov.lt/maemo-irclog/%23maemo.2010-03-29.log.html#t2010-03-29T08:01:18 [3] http://lists.maemo.org/pipermail/maemo-developers/2010-February/024876.html [4] http://people.gnome.org/~csaavedra/news-2009-12.html#D22 [5] http://maemo.gitorious.org/hildon/hildon/blobs/master/examples/hildon-live-search-example.c [6] http://mg.pov.lt/maemo-irclog/%23maemo.2010-03-30.log.html#t2010-03-30T17:13:33 -- 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
Re: Dependency problems after PR 1.2 update to extras builder
On Tue, March 30, 2010 15:56, Andrew Flegg wrote: On Mon, Mar 29, 2010 at 15:37, ianaré sévi ian...@gmail.com wrote: After making some updates to my package and putting it up on extras-devel, it won't update on the device from the repository. I was able to install it on scratchbox (both prior to and after updating the SDK). So, AIUI (and others did too), the autobuilder would be upgraded to PR1.2's SDK and start publishing to fremantle-1.2 (rather than the current fremantle). It will for Extras, but not for extras-devel and testing. However, yesterday on IRC, there were some complaints that the auto-generated components for things in fremantle extras-devel had incorrect dependencies: It depends on your definition of incorrect ;) They are correct for running on PR1.2. I thought the fremantle extras-devel should now be fixed, so how are things with incorrect dependencies getting in? Niels, could it'd've been a race condition during the switch; or is it a bug; or are we corrupting fremantle extras-devel? Some time ago, when I noticed the issues with upcoming PR1.2 and saw the trouble with PR1.1, I tried to find a solution which could be implemented on a short term. The first priority was to protect the repository which is enabled on every device and is used by end-users. Extras will have a fremantle and a fremantle-1.2 repository, so old device users won't see the new dependencies and PR1.2 users will see the correct dependencies. Then it became clear that the PR1.2 SDK would be available before the firmware release. This is something developers asked for a lot and the idea was to give them the opportunity to get their applications ready for PR1.2 before it actually shipped. By enabling it on the builder, developers can get their updated app in extras-devel and check if everything builds against the PR1.2 SDK. The issue people see is that they are then trying to install the PR1.2 built application on a pre PR1.2 device. This might or might not work, depending on which dependencies are specified. In the short time there was between the time I knew about the PR1.2 consequences and the actual release of the SDK, there was not enough time to develop a cleaner solution for extras-devel and extras-testing. Extras-devel is expected to be running against the latest and greatest and always had the disclaimer about breaking your device. I hate the fact that it now actually does prevent applications from being installed though. Creating a separate fremantle-1.2 -devel and testing QA queue would probably have given more confusion and frustration than it would prevent and would have been hard to do within the available time. So, how to on go from here from my POV: * Hope that PR1.2 will be out soon, so people can test it on their own device. * Update the Packages interface with knowledge about the PR1.2 rootfs, so promotions to testing can happen. * Encourage all people with access to PR1.2 devices to test applications from the testing QA queue on their devices and give feedback to developers, so we can get those applications in fremantle-1.2 as soon as possible. * Look at the possibility of adding a hacked libhildon package in the builder, so it generates 'correct' dependencies and applications can be installed on PR1.1 if they don't use the new livesearch api. (Probably most of them) * Discuss how we can improve this situation for the next SSU. * Make a case for Nokia to convince them to give developers early access to PR1.2 images. Trying to do the right thing, I have the feeling that it backfired. :( Thanks in advance, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
Thanks for the clarifications. I can certainly sympathize with your situation, but in the future it might be better to hold off on updating the autobuilder until you get a firm release date from Nokia. The present situation would be much better if we knew how long we had to wait until our packages are installable again. - ianaré sévi 2010/3/30 Niels Breet ni...@maemo.org: On Tue, March 30, 2010 15:56, Andrew Flegg wrote: On Mon, Mar 29, 2010 at 15:37, ianaré sévi ian...@gmail.com wrote: After making some updates to my package and putting it up on extras-devel, it won't update on the device from the repository. I was able to install it on scratchbox (both prior to and after updating the SDK). So, AIUI (and others did too), the autobuilder would be upgraded to PR1.2's SDK and start publishing to fremantle-1.2 (rather than the current fremantle). It will for Extras, but not for extras-devel and testing. However, yesterday on IRC, there were some complaints that the auto-generated components for things in fremantle extras-devel had incorrect dependencies: It depends on your definition of incorrect ;) They are correct for running on PR1.2. I thought the fremantle extras-devel should now be fixed, so how are things with incorrect dependencies getting in? Niels, could it'd've been a race condition during the switch; or is it a bug; or are we corrupting fremantle extras-devel? Some time ago, when I noticed the issues with upcoming PR1.2 and saw the trouble with PR1.1, I tried to find a solution which could be implemented on a short term. The first priority was to protect the repository which is enabled on every device and is used by end-users. Extras will have a fremantle and a fremantle-1.2 repository, so old device users won't see the new dependencies and PR1.2 users will see the correct dependencies. Then it became clear that the PR1.2 SDK would be available before the firmware release. This is something developers asked for a lot and the idea was to give them the opportunity to get their applications ready for PR1.2 before it actually shipped. By enabling it on the builder, developers can get their updated app in extras-devel and check if everything builds against the PR1.2 SDK. The issue people see is that they are then trying to install the PR1.2 built application on a pre PR1.2 device. This might or might not work, depending on which dependencies are specified. In the short time there was between the time I knew about the PR1.2 consequences and the actual release of the SDK, there was not enough time to develop a cleaner solution for extras-devel and extras-testing. Extras-devel is expected to be running against the latest and greatest and always had the disclaimer about breaking your device. I hate the fact that it now actually does prevent applications from being installed though. Creating a separate fremantle-1.2 -devel and testing QA queue would probably have given more confusion and frustration than it would prevent and would have been hard to do within the available time. So, how to on go from here from my POV: * Hope that PR1.2 will be out soon, so people can test it on their own device. * Update the Packages interface with knowledge about the PR1.2 rootfs, so promotions to testing can happen. * Encourage all people with access to PR1.2 devices to test applications from the testing QA queue on their devices and give feedback to developers, so we can get those applications in fremantle-1.2 as soon as possible. * Look at the possibility of adding a hacked libhildon package in the builder, so it generates 'correct' dependencies and applications can be installed on PR1.1 if they don't use the new livesearch api. (Probably most of them) * Discuss how we can improve this situation for the next SSU. * Make a case for Nokia to convince them to give developers early access to PR1.2 images. Trying to do the right thing, I have the feeling that it backfired. :( Thanks in advance, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
Hi, Niels Breet wrote: The issue people see is that they are then trying to install the PR1.2 built application on a pre PR1.2 device. This might or might not work, depending on which dependencies are specified. To summarise, from the point of view of a developer: * If I upload a new verrsion of an app which is in Extras, the new version will be built with PR 1.2, and will go into Extras-devel. The old version will no longer be installable from Extras on a PR 1.1.1 device * If I try to test my application from Extras-devel on a PR 1.1.1 device, there is a good chance the application will not install, or will break * The only solution if I want my app to continue being available in Extras is to wait for the PR 1.2 firmware to be released, and not upload any updates Is that correct? And from the point of view of a user, an application which was previously available is no longer available if the developer has tried to update it recently? I don't really understand why uploading an app to extras-devel has hidden the app which is in extras (PR 1.1.1). Isn't that a bit like if I uploaded a package to Squeeze no-one could download it for Lenny any more? If I don't understand the issue correctly, excuse me, but I'm unclear how you expected things to happen with the autobuilder change. Was the idea that there would be a short period between the SDK and the firmware release, and thus developers could start getting their apps into extras for PR 1.2 before the firmware got released? But in that case, they would need a way to test apps promote them from extras-devel to -testing -extras-1.2, no? * Look at the possibility of adding a hacked libhildon package in the builder, so it generates 'correct' dependencies and applications can be installed on PR1.1 if they don't use the new livesearch api. (Probably most of them) I don't understand this - perhaps you could explain? * Discuss how we can improve this situation for the next SSU. How about separate repositories? How difficult would it be to have 2 auto-builder targets, and 2 different extras, extras-testing extras-devel repositories? The defaults wouldn't change for developers, and to test building against the new SDK, you'd just upload to the new autobuilder (where internal Nokia testers could test promote)? Trying to do the right thing, I have the feeling that it backfired. :( These things happen - perhaps if we understood the goals you were trying to achieve, there's a way to mitigate against this for the next time. Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
On Tue, Mar 30, 2010 at 4:12 PM, ianaré sévi ian...@gmail.com wrote: Thanks for the clarifications. I can certainly sympathize with your situation, but in the future it might be better to hold off on updating the autobuilder until you get a firm release date from Nokia. Unfortunately, they won't give dates (by their usual policy), so that's not really going to be possible. Logic would lead to a conclusion that a final release can't be *too* far off, though, with the SDK now being publically available. The present situation would be much better if we knew how long we had to wait until our packages are installable again. This really is a damned if you do, damned if you don't type situation that shouldn't be quite so painful in the future. Things as I understand it: - Qt 4.5 on Maemo5 had no API/ABI compatibility guarentees. - Qt 4.6 took liberal advantage of that to change and fix some rather suboptimal parts. - This means, if the builder wasn't updated, then there would be other pain in the form of stuff not working once PR1.2 was released. To the best of my knowledge (from talking to Qt on Maemo folks), there is now API/ABI stability, and as such, this shouldn't cause issues again. In short, I think the action taken is probably the lesser of the evils, even if it definitely is far from ideal. Robin Burchell mob: +447702671419 msn: m...@viroteck.net irc: w00t @ irc.freenode.net twr: http://twitter.com/w00teh lac: http://identi.ca/w00t ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
On Tue, Mar 30, 2010 at 16:20, Dave Neary dne...@maemo.org wrote: [snip] And from the point of view of a user, an application which was previously available is no longer available if the developer has tried to update it recently? I don't really understand why uploading an app to extras-devel has hidden the app which is in extras (PR 1.1.1). Isn't that a bit like if I uploaded a package to Squeeze no-one could download it for Lenny any more? If the user only has Extras enabled, they can still get the PR1.1 app which is in Extras. However, if they have -devel enabled (and it has a newer version), HAM will only show the newest version. If the developer then promotes the -devel version to -testing, the testers will only be able to install it on a PR1.2 device. So if there are any promotions to -testing now, we will have a mixed PR1.1 and PR1.2 queue. However, if promoted from -testing to Extras proper, the package will go into a *different* Extras (fremantle-1.2). Extras is separate, -testing and -devel are not. Cheers, 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
Re: Dependency problems after PR 1.2 update to extras builder
On Tue, Mar 30, 2010 at 16:23, Robin Burchell virot...@viroteck.net wrote: [snip] To the best of my knowledge (from talking to Qt on Maemo folks), there is now API/ABI stability, and as such, this shouldn't cause issues again. This isn't an issue only affecting Qt apps, though - as Qt isn't the only change in PR1.2. Indeed, Hildon has had new symbols added to support HildonLiveSearch[1][2] and this is what causes the libhildon (= 2.2.10) Depends. Cheers, Andrew [1] http://people.gnome.org/~csaavedra/news-2009-12.html#D22 [2] http://maemo.gitorious.org/hildon/hildon/blobs/master/examples/hildon-live-search-example.c -- 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
Re: Dependency problems after PR 1.2 update to extras builder
On Tue, Mar 30, 2010 at 4:26 PM, Andrew Flegg and...@bleb.org wrote: This isn't an issue only affecting Qt apps, though - as Qt isn't the only change in PR1.2. Indeed, Hildon has had new symbols added to support HildonLiveSearch[1][2] and this is what causes the libhildon (= 2.2.10) Depends. Right, but at least as far as I understand, at least one big reason for the early update of the builder was down to the upcoming Qt changes[1] - even if it has since had other consequences. If this isn't the case, would it not have made more sense to delay upgrades until PR1.2 was publically available? [1]: http://lists.maemo.org/pipermail/maemo-developers/2010-March/025512.html ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Builder now runs PR1.2 SDK with Qt 4.6 support
On Tuesday 30 March 2010 15:28:04 Andrew Flegg wrote: * This means that auto-generated libhildon dependencies are being specified too tightly to install on devices and SDKs lower than PR1.2 (due to the introduction of new symbols for livesearch[4]) This is the killer. When Niels presented his plan, I didn't realise that anything other than Qt apps would be significantly affected. There has to be an absolute rule for SDK updates: if libhildon version dependencies are being increased, the release **has** to be given a new codename and a separate builder queue and all repositories. We can discuss how long the older version autobuilder is still supported, and we can discuss populating the new repositories from the existing ones, but there should be no question of using the updated SDK in the existing autobuilder and repository. And once Qt apps start shipping to Extras (i.e. for any future releases) this has to apply to Qt as well! And, of course, other libraries that most apps use (glib, etc.). Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Builder now runs PR1.2 SDK with Qt 4.6 support
FWIW, it's not just libhildon that is causing a problem. Look at http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/callerid-widget/0.2-4/ and the libtelepathy-glib0 dependency, for example. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Dependency problems after PR 1.2 update to extras builder
replying to my own message since it didnt interest anybody :) Ive just been confirmed that this works for now as a temporary workaround for developers using QT4.6 on a PR1.2 SDK and uploading to extras devel/testing. It would still work on the device. - Original Message - From: Ram Kurvakat Sent: 03/29/10 06:07 PM To: ianaré sévi, Dave Neary Subject: Re: Dependency problems after PR 1.2 update to extras builder would building QT4.6 apps by linking with libqt4-maemo5* still work ? AFAIK , these libqt4-maemo5* are still being kept for QT4.7 development. Now if that is true, atleast for the QT4.6 apps still in extras-devel we can still upload to the repository and it will work on the device as well. Im aware they cant be promoted to extras-testing due to the bloack but atleast users and developers using the app from extras-devel will be able to use it this way. Once PR1.2 is on the device we can link these back to libqt4-* as they will be version 4.6 then on the device. Anybody tried it yet or is this not possible ? - Original Message - From: ianaré sévi Sent: 03/29/10 05:58 PM To: Dave Neary Subject: Re: Dependency problems after PR 1.2 update to extras builder OK got it to work, I simply set the Qt dependencies to 4.5 (instead of 4.6) manually instead on relying on the builder scripts ... - ianaré sévi 2010/3/29 Dave Neary dne...@maemo.org: Hi, Marcin Juszkiewicz wrote: No, I am not kidding. It was discussed here on mailing list and announced that Extras autobuilder will be updated to PR 1.2 compatible SDK and that resulting packages will be installable only on devices owned by Nokia employed people (and some from cooperating companies). Other users (and developers) have to wait for next firmware drop (which does not have release date as usual so it can be tomorrow or in next year). Now now Marcin, that's not what was said. what was said was that software built with the PR 1.2 SDK would probably only install on devices with PR 1.2 installed. That's not the same thing. ianaré, normally all you have to do is upgrade the firmware on your N900 to PR 1.2, as I understand it. Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers 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: Maemo Theme Maker failed to produce Debian package
Hi Faheem! Thanks for pointing out the MADDE-based solution. I was able to build Debian source package without any problems. However, I didn't manage to build binary package as MADDE doesn't have some required dependencies. Using extras-devel is not an option in this particular case. I have to figure out how to install additional packages into MADDE. Thanks, Daniil. On Tue, Mar 30, 2010 at 3:28 PM, Faheem Pervez tripp...@gmail.com wrote: Hiya, On Tue, Mar 30, 2010 at 1:24 PM, Daniil Ivanov daniil.iva...@gmail.com wrote: Sorry, I forgot to mention pretty relevant information, that I'm searching for a one-button-press solution, which will be used on Windows by people with no Linux experience, so manual package creation is a no go solution. This is not a one-click solution, but I understand http://wiki.maemo.org/MADDE/Theme_building is popular among Windows-using themers, with many of the themes available in Extras-devel built using MADDE. Best Regards, Faheem ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: refinding the syncing question
On Wed, 2010-03-31 at 00:00 +0100, Graham Cobb wrote: On Saturday 27 March 2010 11:39:10 Carsten Munk wrote: 2010/3/27 Graham Cobb g+...@cobb.uk.net: On Saturday 27 March 2010 07:46:58 Ville M. Vainio wrote: Implementing one by yourself is a huge task, which you probably don't want to do. Current n900 endpoint is using modified version of funambol (syncml server) which is a nontrivial amount of code. Ah, that's interesting. Where do I find that modified code? I think Nokia's funambol is licensed through funambol commercial license, so closed source Can we add it to the components requested to be opened up? I would be interested to look to see if we could extend it for some additional syncs (e.g. for GPE, etc.). Graham According to this page: https://www.forge.funambol.org/download/ It looks like the source code is available. Not sure about licensing, though. Aniello ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: refinding the syncing question
On Tue, 2010-03-30 at 17:19 -0700, Aniello Del Sorbo wrote: On Wed, 2010-03-31 at 00:00 +0100, Graham Cobb wrote: On Saturday 27 March 2010 11:39:10 Carsten Munk wrote: 2010/3/27 Graham Cobb g+...@cobb.uk.net: On Saturday 27 March 2010 07:46:58 Ville M. Vainio wrote: Implementing one by yourself is a huge task, which you probably don't want to do. Current n900 endpoint is using modified version of funambol (syncml server) which is a nontrivial amount of code. Ah, that's interesting. Where do I find that modified code? I think Nokia's funambol is licensed through funambol commercial license, so closed source Can we add it to the components requested to be opened up? I would be interested to look to see if we could extend it for some additional syncs (e.g. for GPE, etc.). Graham According to this page: https://www.forge.funambol.org/download/ It looks like the source code is available. Not sure about licensing, though. Actually the licensing looks pretty straightforward: https://www.forge.funambol.org/learn/licensing.html Aniello ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
