Re: Autobuilder for maemo extras repository
On Thu, 2008-06-26 at 23:30 +0100, ext Graham Cobb wrote: On Thursday 26 June 2008 23:02:46 Thomas Schmidt wrote: Yes, of course this would work too, but i guess some other people would not be very happy about such a change (*looking at Graham Cobb*) especially as it would require to be at least 1300 seconds in my case. ;-) I think Ed (or someone) told me that I don't have to worry about that timeout (or was it another timer -- I will admit to being confused!). Don't be confused. Timeout is the time between .dsc file modification time and time when package will be rejected. We can easily set it to, say, days if needed and it doesn't mean that other packages have to wait days to being picked up. Of course, once the autobuilder has dependency support I won't care at all! The timers are only used in my hack script which handles dependencies by waiting long times (like an hour or more) between various uploads. I'm working on it. Don't hold you breath though :) Regards, -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-27 at 00:02 +0200, ext Thomas Schmidt wrote: Am Donnerstag, den 26.06.2008, 23:58 +0300 schrieb Ed Bartosh: I'd suggest you to use Maemo Extras Assistant instead of dput: https://garage.maemo.org/extras-assistant/index.php It puts .dsc after all other sources. Yes, this would work, but i would very much prefer dput over any web-interface. :) So it would be very nice if you could change the code just check the mtime of the .changes file, because this file seems to be the last one uploaded by dput. I can't. Autobuilder doesn't use .changes at all It needs only sources, so .dsc is enough for it. Ok, but then it should be at least possible to check the mtime of the tarball and/or .diff.gz - at least one of them should be listed in every .dsc file. No code modifications are needed. We've already increased timeout. If it doesn't help we will increase it even more. Btw: Which one of the scripts checks if the gpg-signatures of the uploads are valid, shouldn't this script check both, the signature in the .dsc and the signature in the .changes files? Current version doesn't work with .changes files. They're just not needed, because all information about source files available from .dsc. In future autobuilder will definitely work with .changes for several reasons, but now it's just not needed. If it's not convenient for you to use web assistant I can just increase timeout. Yes, of course this would work too, but i guess some other people would not be very happy about such a change (*looking at Graham Cobb*) especially as it would require to be at least 1300 seconds in my case. ;-) OK, we will increase it to 1500 then. Niels, can you help with this please? Another way is to change dput. Which dput version do you use, BTW? I am using version 0.9.2.32 from current Debian Lenny, but i would consider changing dput to be able to upload to the autobuilder a very ugly hack. As far as i can see, the autobuilder should be changed to work with the unmodified dput. Furtunately it doesn't have to be changed, timeout is part of the configuration file. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-27 at 00:02 +0200, ext Thomas Schmidt wrote: Am Donnerstag, den 26.06.2008, 23:58 +0300 schrieb Ed Bartosh: [SNIP] If it's not convenient for you to use web assistant I can just increase timeout. Yes, of course this would work too, but i guess some other people would not be very happy about such a change (*looking at Graham Cobb*) especially as it would require to be at least 1300 seconds in my case. ;-) OK, we will increase it to 1500 then. Niels, can you help with this please? Done. -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Thu, Jun 26, 2008 at 9:58 PM, Ed Bartosh [EMAIL PROTECTED] wrote: I'd suggest you to use Maemo Extras Assistant instead of dput: https://garage.maemo.org/extras-assistant/index.php It puts .dsc after all other sources. [snip] Another way is to change dput. Which dput version do you use, BTW? And last solution is to use scp instead of dput. If you're interested I can show my upload script. It's simple and ugly, but it works for me for a long time. With the upcoming refocus of mud[1] to assist with developing, packaging and uploading to the extras auto-builder, one of the requirements I've identified in the new design document is to help people by using scp to upload the files in the right order: https://wiki.maemo.org/User:Jaffa/mud_design#Requirements mud has already made it trivial to re-package and re-upload libgee[2] from an upstream Ubuntu source, and it's already in extras-devel. I'm having a few problems with vim (exposing mud bugs and autobuilder issues), and plan to upload the vala[3] compiler at some point this weekend. Cheers, Andrew [1] https://garage.maemo.org/pipermail/mud-builder-users/2008-June/000255.html [2] http://packages.ubuntu.com/source/hardy/libgee [3] http://live.gnome.org/Vala -- Andrew Flegg -- mailto:[EMAIL PROTECTED] | http://www.bleb.org/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Fred schrieb: I tried to auto-build pwsafe on diablo and I got loads of (111 Connection refused) errors Yes... I once got that. I uploaded the unmodified package later and it build without errors. -- Klaus Rotter * klaus at rotters dot de * www.rotters.de ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Am Sonntag, den 29.06.2008, 14:27 +0200 schrieb Klaus Rotter: Fred schrieb: I tried to auto-build pwsafe on diablo and I got loads of (111 Connection refused) errors Yes... I once got that. I uploaded the unmodified package later and it build without errors. I also got it in the last upload of Gnumeric, the armel build went fine, but while downloading the build-dependencies for x86, almost all downloads failed with (111 Connection refused), seems to be a somehow unreliable repository.maemo.org web-server. I hope this could be improved, maybe with local caching of build-dependencies (apt-proxy, or just (re-)using of the downloaded build-deps)!? Regards, Thomas -- Thomas Schmidt, Debian VDR Team http://pkg-vdr-dvb.alioth.debian.org/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Hi all, I tried to auto-build pwsafe on diablo and I got loads of (111 Connection refused) errors check out : https://garage.maemo.org/builder/diablo/pwsafe_1.3.2/armel.root.log.FAILED.txt Is this problem known ? Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
2008/6/27 koos vriezen [EMAIL PROTECTED]: What should I put in my sources.list to upgrade my scratchbox. Changing only chinook to diablo failed and indeed the deb http://repository.maemo.org/ diablo free non-free extras deb http://repository.maemo.org/extras diablo free non-free deb file:/home/koos/maemo-sdk-nokia-binaries_4.0 diablo explicit aren't there. Ah wait, with some url instrumentation, I found http://tablets-dev.nokia.com/4.1/INSTALL.txt so, its deb http://repository.maemo.org/ maemo4.1/sdk free non-free deb-src http://repository.maemo.org/ maemo4.1/sdk free non-free deb http://repository.maemo.org/ maemo4.1/tools free non-free deb-src http://repository.maemo.org/ maemo4.1/tools free non-free Br. Koos Vriezen ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Hi, Am Freitag, den 06.06.2008, 11:54 +0200 schrieb Niels Breet: Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar.gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Today i tried out the autobuilder the first time for uploading the Build-Dependencies of Gnumeric to the diablo-extras-devel-repository and i hit the same problem a few times, i believe that the code which picks up the files from the incoming queue needs to be changes somehow because as far as i can see from the buildme python code, it checks upload_timeout by investigating the mtime of the .dsc file. Unfortunately the .dsc file is one of the first files uploaded by dput. (I believe the order is: .dsc, .diff.gz (if available), .tar.gz, .changes). And here comes the problem: For bigger .tar.gz files and people with a slow upload bandwidth (16 KByte/sec in my case), it is just not possible to upload larger packages successfully, they will always be picked up and rejected by buildme before they are uploaded completely. (If i understood your comments correctly, it will take 1x or 2x upload_timeout until the upload is considered, which would allow me to upload 2880 (180*16) to 5760 (2*180*16) KByte at best, this also matches my experiences from today, where i needed 3 tries until i was able to successfully upload goffice (about 3200 Kbyte). Unfortunately this is absolutely not enough for the biggest package i am trying to upload (gnumeric, the tarball is over 20 MByte big). So it would be very nice if you could change the code just check the mtime of the .changes file, because this file seems to be the last one uploaded by dput. Please also see: https://garage.maemo.org/pipermail/extras-cauldron-builds/2008q2/000553.html https://garage.maemo.org/pipermail/extras-cauldron-builds/2008q2/000554.html https://garage.maemo.org/pipermail/extras-cauldron-builds/2008q2/000564.html in all cases, the files were rejected before the upload by dput was completed. Regards, Thomas -- Thomas Schmidt, Debian VDR Team http://pkg-vdr-dvb.alioth.debian.org/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Thu, 2008-06-26 at 22:30 +0200, ext Thomas Schmidt wrote: Today i tried out the autobuilder the first time for uploading the Build-Dependencies of Gnumeric to the diablo-extras-devel-repository and i hit the same problem a few times, i believe that the code which picks up the files from the incoming queue needs to be changes somehow because as far as i can see from the buildme python code, it checks upload_timeout by investigating the mtime of the .dsc file. Unfortunately the .dsc file is one of the first files uploaded by dput. (I believe the order is: .dsc, .diff.gz (if available), .tar.gz, .changes). And here comes the problem: For bigger .tar.gz files and people with a slow upload bandwidth (16 KByte/sec in my case), it is just not possible to upload larger packages successfully, they will always be picked up and rejected by buildme before they are uploaded completely. (If i understood your comments correctly, it will take 1x or 2x upload_timeout until the upload is considered, which would allow me to upload 2880 (180*16) to 5760 (2*180*16) KByte at best, this also matches my experiences from today, where i needed 3 tries until i was able to successfully upload goffice (about 3200 Kbyte). Unfortunately this is absolutely not enough for the biggest package i am trying to upload (gnumeric, the tarball is over 20 MByte big). I'd suggest you to use Maemo Extras Assistant instead of dput: https://garage.maemo.org/extras-assistant/index.php It puts .dsc after all other sources. So it would be very nice if you could change the code just check the mtime of the .changes file, because this file seems to be the last one uploaded by dput. I can't. Autobuilder doesn't use .changes at all It needs only sources, so .dsc is enough for it. If it's not convenient for you to use web assistant I can just increase timeout. Another way is to change dput. Which dput version do you use, BTW? And last solution is to use scp instead of dput. If you're interested I can show my upload script. It's simple and ugly, but it works for me for a long time. Regards, --- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Am Donnerstag, den 26.06.2008, 23:58 +0300 schrieb Ed Bartosh: I'd suggest you to use Maemo Extras Assistant instead of dput: https://garage.maemo.org/extras-assistant/index.php It puts .dsc after all other sources. Yes, this would work, but i would very much prefer dput over any web-interface. :) So it would be very nice if you could change the code just check the mtime of the .changes file, because this file seems to be the last one uploaded by dput. I can't. Autobuilder doesn't use .changes at all It needs only sources, so .dsc is enough for it. Ok, but then it should be at least possible to check the mtime of the tarball and/or .diff.gz - at least one of them should be listed in every .dsc file. Btw: Which one of the scripts checks if the gpg-signatures of the uploads are valid, shouldn't this script check both, the signature in the .dsc and the signature in the .changes files? If it's not convenient for you to use web assistant I can just increase timeout. Yes, of course this would work too, but i guess some other people would not be very happy about such a change (*looking at Graham Cobb*) especially as it would require to be at least 1300 seconds in my case. ;-) Another way is to change dput. Which dput version do you use, BTW? I am using version 0.9.2.32 from current Debian Lenny, but i would consider changing dput to be able to upload to the autobuilder a very ugly hack. As far as i can see, the autobuilder should be changed to work with the unmodified dput. And last solution is to use scp instead of dput. If you're interested I can show my upload script. It's simple and ugly, but it works for me for a long time. Yes, this could work too, but as i said allready, i thing the autobuilder, should be fixed instead. (Another workaround i could use would be to upload the package to my webserver and use dput on the server to upload it to garage, but this would make things just overly complicated for everyday usage.) :) Btw: it seems that i am not the only one who is experiencing this problem, Luciano Wolf seems to be hit by it as well, his upload of python2.5 2.5.2-1osso3 was rejected 4 times today: https://garage.maemo.org/pipermail/extras-cauldron-builds/2008q2/000574.html https://garage.maemo.org/pipermail/extras-cauldron-builds/2008q2/000575.html https://garage.maemo.org/pipermail/extras-cauldron-builds/2008q2/000576.html https://garage.maemo.org/pipermail/extras-cauldron-builds/2008q2/000577.html Regards, Thomas -- Thomas Schmidt, Debian VDR Team http://pkg-vdr-dvb.alioth.debian.org/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Thursday 26 June 2008 23:02:46 Thomas Schmidt wrote: Yes, of course this would work too, but i guess some other people would not be very happy about such a change (*looking at Graham Cobb*) especially as it would require to be at least 1300 seconds in my case. ;-) I think Ed (or someone) told me that I don't have to worry about that timeout (or was it another timer -- I will admit to being confused!). Of course, once the autobuilder has dependency support I won't care at all! The timers are only used in my hack script which handles dependencies by waiting long times (like an hour or more) between various uploads. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 19:10 +0100, ext Graham Cobb wrote: On Friday 06 June 2008 14:22:33 Niels Breet wrote: On Fri, 2008-06-06 at 13:56 +0200, ext Niels Breet wrote: This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? 180, so that is pretty low. As it must at least be the time between 2 queue runs? It's 3 minutes. Not that low, I'd say. Let's set it to 240. If it's still not enough then we can increase it even more. I have set this to 240 now, let's see if this is enough to solve the problem. Do I understand this correctly? You are saying that if I upload a package and the autobuilder runs fewer than 4 minutes after I do the upload, that the files will be ignored? So, I may have to wait 9 minutes before the build starts? It's not that bad, don't worry :) If .dsc file is in incoming directory autobuilder will always try to pick it up. If some problems with file found then autobuilder will skip it if file is sitting there less than timeout value or will reject it in opposite case. ___ 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 for maemo extras repository
On Fri, 2008-06-06 at 15:31 +0200, ext Fred wrote: Hi, I try to be able to generate my projects for OS2007 as well as 0S2008 (with a few lines in configure.ac) But with the auto-builder, I have to specify hildon dev packages in debian/control ... which breaks my setup for OS2007 What would you recommend to keep this possibility ? Alternative Build-dependencies should help you in this case. You can read about them here: http://www.debian.org/doc/debian-policy/ch-relationships.html In short: You can specify both OS2007 and OS2008 packages as a build-dependencies. Something like this: Build-Depends: hildon-fm-dev | libhildonfm2-dev, libosso-gnomevfs2-dev | libgnomevfs2-dev But, considering the fact that hildon API was broken between OS2007(bora) and OS2008(chinook)[1] I'm quite sure that this change isn't enough to compile package for both platforms. [1] http://maemo.org/news/announcements/view/1184675758.html -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Neil Jerram a écrit : 2008/6/6 Fred [EMAIL PROTECTED]: Looks like it works ... Can this pb be linked to the fact that I have a passphrase associated with my ssh key and that I may not answer the passphrase question as soon as it arises ? If that is the problem, are you aware of ssh-agent and ssh-add? Neil Thanks a lot : it's exactly what I wanted, I love learning ;) Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Thanks, I'll take a look Fred - Original message - 2008/6/6 Fred [EMAIL PROTECTED]: Looks like it works ... Can this pb be linked to the fact that I have a passphrase associated with my ssh key and that I may not answer the passphrase question as soon as it arises ? If that is the problem, are you aware of ssh-agent and ssh-add? Neil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Hi Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar.gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Hi Hi, Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar.gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Fred -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 09:24 +0200, ext Fred wrote: Hi Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar.gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... Thank you for reporting this. My guess is that autobuilder tries to pick up your package when this tarball is still being uploaded. I'll investigate this. Thank you. --- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 11:54 +0200, ext Niels Breet wrote: Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar.gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? BTW, In which order do you put files into autobuilder incoming queue in Maemo Extras Assistant? The best way to do it is to put all files, than .dsc and .changes --- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 11:54 +0200, ext Niels Breet wrote: Just to let you know that I sometimes get this type of error : [2008-06-06 10:25:01] Processing package gnokii-gconf 0.6.2. Uploader: fredoll, builder: builder1 [2008-06-06 10:25:01] REJECTED: 'File size for /var/www/extras-devel/incoming-builder/chinook/gnokii-gconf_0.6.2.tar .gz does not match that specified in .dsc' It goes away if I retry the dput without changing anything ... This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? 180, so that is pretty low. As it must at least be the time between 2 queue runs? BTW, In which order do you put files into autobuilder incoming queue in Maemo Extras Assistant? The best way to do it is to put all files, than .dsc and .changes That is what I do already. --- Ed - Niels ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 13:56 +0200, ext Niels Breet wrote: This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? 180, so that is pretty low. As it must at least be the time between 2 queue runs? It's 3 minutes. Not that low, I'd say. Let's set it to 240. If it's still not enough then we can increase it even more. -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 14:16 +0200, ext Fred wrote: I managed to get gnokii-gconf to auto-build !!! Thanks a lot Thank you for using autobuilder! Now trying with phonelink ... It stops during the initial phase of configure ... ... checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /scratchbox/tools/bin/install -c configure: error: cannot run /bin/sh ./config.sub make: *** [configure-stamp] Error 1 Any idea ? My guess is that config.sub in your package is symlink which points to nowhere. Try to replace it (and may be some other autotools-related files) with the actual file[s]. -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Fri, 2008-06-06 at 13:56 +0200, ext Niels Breet wrote: This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? 180, so that is pretty low. As it must at least be the time between 2 queue runs? It's 3 minutes. Not that low, I'd say. Let's set it to 240. If it's still not enough then we can increase it even more. I have set this to 240 now, let's see if this is enough to solve the problem. -- Ed - Niels ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Looks like it works ... Can this pb be linked to the fact that I have a passphrase associated with my ssh key and that I may not answer the passphrase question as soon as it arises ? Fred Niels Breet a écrit : On Fri, 2008-06-06 at 13:56 +0200, ext Niels Breet wrote: This is because we process the queue every certain amount of time and we check if we have seen the file before in the last run. A file that has been there for a certain amount of time gets processed. Ed: Do we need to make the upload_timeout a little longer? Yep. That's what I'm thinking of. What is the current value? 180, so that is pretty low. As it must at least be the time between 2 queue runs? It's 3 minutes. Not that low, I'd say. Let's set it to 240. If it's still not enough then we can increase it even more. I have set this to 240 now, let's see if this is enough to solve the problem. -- Ed - Niels ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
I have replaced the links with the actual files and it worked ... Thanks a lot for your support Fred Ed Bartosh a écrit : On Fri, 2008-06-06 at 14:16 +0200, ext Fred wrote: I managed to get gnokii-gconf to auto-build !!! Thanks a lot Thank you for using autobuilder! Now trying with phonelink ... It stops during the initial phase of configure ... ... checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /scratchbox/tools/bin/install -c configure: error: cannot run /bin/sh ./config.sub make: *** [configure-stamp] Error 1 Any idea ? My guess is that config.sub in your package is symlink which points to nowhere. Try to replace it (and may be some other autotools-related files) with the actual file[s]. -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Hi, I try to be able to generate my projects for OS2007 as well as 0S2008 (with a few lines in configure.ac) But with the auto-builder, I have to specify hildon dev packages in debian/control ... which breaks my setup for OS2007 What would you recommend to keep this possibility ? Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Friday 06 June 2008 14:31:21 Fred wrote: I try to be able to generate my projects for OS2007 as well as 0S2008 (with a few lines in configure.ac) But with the auto-builder, I have to specify hildon dev packages in debian/control ... which breaks my setup for OS2007 What would you recommend to keep this possibility ? What I do is to use MUD to prepare my packages. MUD has the capability to modify lines in debian/control and to do it differently for different SDKs (in fact, I added that capability when the autobuilder was created specifically for this problem!). It does mean that I end up creating different source packages for different SDKs, of course. Of course, for now the solution is easy: there is no autobuilder for OS2007 so just set up the line correctly for OS2008 and pity anyone who tries to use your source package to build an OS2007 version! Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Fred wrote: Hi, I try to be able to generate my projects for OS2007 as well as 0S2008 (with a few lines in configure.ac) But with the auto-builder, I have to specify hildon dev packages in debian/control ... which breaks my setup for OS2007 What would you recommend to keep this possibility ? Hello Fred, I know nothing about the syntax of debian/control, but I looked at how others have done it. In maemo-mappers debian/control I found out that it is possible to have or conditions, like this: Build-Depends: hildon-libs-dev | libhildon1-dev, hildon-fm-dev | libhildonfm2-dev Try this out. BR. Julius ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Autobuilder for maemo extras repository
Hi, I'm trying to use the autobuilder : I managed to have gnokii OK but then when I try with an hildon app, configure doesn't find the modules : my configure.ac is like this : # Hildon library dependsncies PKG_CHECK_MODULES(HILDON, hildon-1 hildon-fm-2 hildon-help conbtdialogs,\ AC_DEFINE(HILDON, 1, [Version of hildon libraries]), \ [AC_DEFINE(HILDON, 0, [Version of hildon libraries]) \ PKG_CHECK_MODULES(HILDON, hildon-libs = 0.9.50 hildon-fm libossohelp)]) And I get this report checking for HILDON... no checking for HILDON... configure: error: Package requirements (hildon-libs = 0.9.50 hildon-fm libossohelp) were not met: No package 'hildon-libs' found No package 'hildon-fm' found No package 'libossohelp' found What am I doing wrong ? Thanks Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Thursday 05 June 2008 16:34:47 Fred wrote: Hi, I'm trying to use the autobuilder : I managed to have gnokii OK but then when I try with an hildon app, configure doesn't find the modules You need to list everything in the Build-depends: line in the package control file. Here is the Build-depends list for gpe-calendar, for example: Build-depends: debhelper (= 4), libsoundgen-dev, libmimedir-gnome-dev, libgpevtype-dev, libeventdb-dev, libgpepimc-dev, libgpewidget-dev, libtododb-dev, libxsettings-client-dev, libhandoff-dev, libsoup2.2-dev, libgnutls-dev, libgnutls13, libgcrypt11-dev, libopencdk10-dev, intltool, libhildon1-dev, libhildonfm2-dev, libosso-dev In your case you probably only need to add the last three. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
On Thu, 2008-06-05 at 17:34 +0200, ext Fred wrote: Hi, I'm trying to use the autobuilder : I managed to have gnokii OK but then when I try with an hildon app, configure doesn't find the modules : my configure.ac is like this : # Hildon library dependsncies PKG_CHECK_MODULES(HILDON, hildon-1 hildon-fm-2 hildon-help conbtdialogs,\ AC_DEFINE(HILDON, 1, [Version of hildon libraries]), \ [AC_DEFINE(HILDON, 0, [Version of hildon libraries]) \ PKG_CHECK_MODULES(HILDON, hildon-libs = 0.9.50 hildon-fm libossohelp)]) And I get this report checking for HILDON... no checking for HILDON... configure: error: Package requirements (hildon-libs = 0.9.50 hildon-fm libossohelp) were not met: No package 'hildon-libs' found No package 'hildon-fm' found No package 'libossohelp' found What am I doing wrong ? Wow! Congratulations! You're the first person who is asking about autobuilder here. The rest of community seems not interested in it (no idea why). A bit of explanations why this happened: When autobuilder starts the build it uses so called minimal rootstrap with the minimal list of packages like gcc, libc and similar. The rest of packages required for the build should be mentioned in package's control/Build-Depends* field[s]. So, your package should build-depend on -dev packages, which provide libraries/includes to be able to use them. Only in this case they will be brought to the system and can be used in the build. In your case you can identify missing build-dependencies by looking at .pc files with the same names as modules mentioned in your configure output. Something like this: [sbox-chinook-armel: ~] dpkg -S hildon-1.pc hildon-fm-2.pc hildon-help.pc libhildon1-dev: /usr/lib/pkgconfig/hildon-1.pc libhildonfm2-dev: /usr/lib/pkgconfig/hildon-fm-2.pc libhildonhelp-dev: /usr/lib/pkgconfig/hildon-help.pc So, you should add libhildon1-dev, libhildonfm2-dev and libhildonhelp-dev to your package's Build-depends: and try again :) Thank you for using autobuilder. Don't hesitate to ask more questions if any. BR, -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Autobuilder for maemo extras repository
Thanks Graham and Ed I'll try that tomorrow ;) Fred - Original message - On Thu, 2008-06-05 at 17:34 +0200, ext Fred wrote: Hi, I'm trying to use the autobuilder : I managed to have gnokii OK but then when I try with an hildon app, configure doesn't find the modules : my configure.ac is like this : # Hildon library dependsncies PKG_CHECK_MODULES(HILDON, hildon-1 hildon-fm-2 hildon-help conbtdialogs,\ AC_DEFINE(HILDON, 1, [Version of hildon libraries]), \ [AC_DEFINE(HILDON, 0, [Version of hildon libraries]) \ PKG_CHECK_MODULES(HILDON, hildon-libs = 0.9.50 hildon-fm libossohelp)]) And I get this report checking for HILDON... no checking for HILDON... configure: error: Package requirements (hildon-libs = 0.9.50 hildon-fm libossohelp) were not met: No package 'hildon-libs' found No package 'hildon-fm' found No package 'libossohelp' found What am I doing wrong ? Wow! Congratulations! You're the first person who is asking about autobuilder here. The rest of community seems not interested in it (no idea why). A bit of explanations why this happened: When autobuilder starts the build it uses so called minimal rootstrap with the minimal list of packages like gcc, libc and similar. The rest of packages required for the build should be mentioned in package's control/Build-Depends* field[s]. So, your package should build-depend on -dev packages, which provide libraries/includes to be able to use them. Only in this case they will be brought to the system and can be used in the build. In your case you can identify missing build-dependencies by looking at .pc files with the same names as modules mentioned in your configure output. Something like this: [sbox-chinook-armel: ~] dpkg -S hildon-1.pc hildon-fm-2.pc hildon-help.pc libhildon1-dev: /usr/lib/pkgconfig/hildon-1.pc libhildonfm2-dev: /usr/lib/pkgconfig/hildon-fm-2.pc libhildonhelp-dev: /usr/lib/pkgconfig/hildon-help.pc So, you should add libhildon1-dev, libhildonfm2-dev and libhildonhelp-dev to your package's Build-depends: and try again :) Thank you for using autobuilder. Don't hesitate to ask more questions if any. BR, -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
