Re: Stats at Maemo repository
Hi, Am Montag, den 17.05.2010, 00:38 +0300 schrieb Adrian Yanes: > I was thinking in the last weeks, to implement some mechanism/system > to have stats of Maemo Repositories. > > Finally I created some scripts to recollect this data and save it in a > database. > > In some days I will publish a site with some charts / more info. > > I hope that this numbers are useful for someone else. > > Nowadays these are the stats at Maemo Repositories Fremantle & Diablo > (UTC 21:34:51 Sunday 16 May 2010): IMHO it would be way more useful to only list unique packages, because your numbers seem to include all package versions ever uploaded to extras. (Old versions of packages are still not removed from the package indexes afaik.) Apart from that i think your idea is very nice. Regards, Thomas -- Thomas Schmidt, Debian VDR Team http://pkg-vdr-dvb.alioth.debian.org/ signature.asc Description: This is a digitally signed message part ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Diablo Libssl broken in extras-devel
Hi, Am Samstag, den 12.09.2009, 21:35 +0200 schrieb Till Harbaum / Lists: > hey guys, really, this is no fun. Please, PLEASE just delete > osm2go from at least the diablo repository > > I really don't need an inbox filling up because user think > i am responsible for this libssl mess. > > Please do it now!!! I will eventually upload an updated version, > but please remove the current version (0.7.20) immediately. IMHO you should be able to fix the problem by yourself, just by uploading a new version 0.7.20-maemo2 without any changes apart from the new changelog-entry. As long as the broken libssl has been removed from the repository, the new version of osm2go should be built with the correct libssl and should be installable again. btw: I'm just reading your article about Maemo 5 Development in the issue 20/2009 of the c't magazine. :) 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: Where To Upload GPG Key??
Am Donnerstag, den 02.04.2009, 17:44 -0500 schrieb Kenneth Loafman: > I'm getting the following when trying to upload to Fremantle Extras > Builder. Where do they want to find the GPG signing key? I'm on all the > major keyservers, so what's the secret here? Please check http://wiki.maemo.org/Uploading_to_Extras#Pre-requisites You first need to request an "invitation" to be able to upload to extras, then your GPG-Key will be added to the Keyring which is checked by the autobuilders. 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: Lintian for maemo.org
Hi, Am Donnerstag, den 19.02.2009, 16:05 +0100 schrieb Jeremiah C. Foster: > My understanding is that Nokia has an internal version of lintian, > the debian policy checker, which might be of use for maemo.org > repositories. The idea is to run lintian over new packages to check > conformance to policy in an automated fashion, hopefully improving > quality of packages. I would love to see such a version of lintian too, not only on the maemo.org servers, but also for local testing in scratchbox. 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: I can't get the autobuilder to work - Please HELP
Am Montag, den 16.02.2009, 22:08 -0800 schrieb Bruce Forsberg: > I an trying to submit my application to extras and am running it > through the autobuilder. I get the error: > > # commands to compile the package. > /scratchbox/tools/bin/make > make[1]: Entering directory > `/home/builder1/maemo-diablo-armel-extras-devel/work/mileage-1.0' > gcc -O2 -DMAEMO `pkg-config --cflags gtk+-2.0 hildon-1 hildon-help > dbus-1` -ansi -Wall -c car_tab.c > Package gtk+-2.0 was not found in the pkg-config search path. > Perhaps you should add the directory containing `gtk+-2.0.pc' > to the PKG_CONFIG_PATH environment variable > No package 'gtk+-2.0' found > Package hildon-1 was not found in the pkg-config search path. > Perhaps you should add the directory containing `hildon-1.pc' > to the PKG_CONFIG_PATH environment variable > No package 'hildoSn-1' found > Package hildon-help was not found in the pkg-config search path. > Perhaps you should add the directory containing `hildon-help.pc' > to the PKG_CONFIG_PATH environment variable > No package 'hildon-help' found > > > Can someone please tell me what I have done wrong this time? My > project is mileage. The problem is, as Tim already told you, that your package has not specified build-dependencies in debian/control at all. Because your package is using pkg-config, it is really easy to find out the missing build-dependencies, pkg-config looks for the package files in /usr/lib/pkgconfig/. If your package compiles successfuly in your local scratchbox installation, you can determine the missing packages for the autobuilder by calling the following commands in scratchbox: dpkg -S /usr/lib/pkgconfig/gtk+-2.0.pc dpkg -S /usr/lib/pkgconfig/hildon-1.pc ... The package-names you get from dpkg have to be added to the line Build-Depends in debian/control as comma-separated list. (Build-Depends: libgtk2.0-dev, libhildon1-dev, ...)S 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: Removing packages from Diablo extras-devel
Am Dienstag, den 09.12.2008, 13:22 -0600 schrieb tz: > If you want a "do nothing" update, you could repackage a working > version with a newer number than the one currently in extras-devel. You also have the option to leave the version number itself mostly unchanged, by using an so-called epoch [1], which just means that you add a 1: prefix to the version number in your new changelog entries. By increasing the epoch, the package manager will think that the package is newer than the version before, even if the rest of the version is smaller than the version which is already installed, i will give you some examples: "Bad" version installed on device: 1.0-1 "Good" version which should override "bad" one: 0.9-1 Problem: 0.9-1 is smaller than 1.0-1, so neither autobuilder, nor the application manager would use 0.9-1 for an update. Using an epoch: "Good" version will become 1:0.9-1 (only in debian/changelog) Result: 1:0.9-1 is considered newer than 1.0-1 by the autobuilder and the application manager, so the users will see the new version and will be able to "upgrade" to this one. For a detailed explanation about debian version numbers, see link below. Regards, Thomas [1] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version -- 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 problem: '.... set times: No such file or directory'
Hi, Am Montag, den 28.07.2008, 22:34 +0300 schrieb Antonio Aloisio: > This evening I´ve uploaded 2 times the Qt4 source in the extra-devel > repository; the first time I had the same error that I had before. > The second time the source has been uploaded with success, but... > obviously there is a "BUT"... > It has failed to build the sources... :( [ You can see the log below ] > I uploaded the sources for 5 times for 7 hours... What you now see, seems to be the same problem as reported in bug #3486 (https://bugs.maemo.org/show_bug.cgi?id=3486), another very frustrating bug, especially if it takes very long to upload the sources and the build fails because of infrastructure problems and not because of problems with the sources itself. 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 problem: '.... set times: No such file or directory'
Am Montag, den 28.07.2008, 12:22 +0300 schrieb Antonio Aloisio: > I´ll upload it this evening when i come back at home. > I´ll report you if it has worked successfully. If it does not work, you might consider re-opening Bug #3466 (https://bugs.maemo.org/show_bug.cgi?id=3466), which covers this problem. 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 problem: ".... set times: No such file or directory"
Hi, Am Sonntag, den 27.07.2008, 22:41 +0300 schrieb Antonio Aloisio: > Hi, > I've problem to upload my source files to autobuilder. > I tryied 2 times, but I had always the same error. > See below for the log. > Is it a error due to the name of my package? > I guess that the name of my package respect the maemo policy. > Any hints? I also experienced the same problem some weeks ago while trying to upload the tarball of gnumeric (~18 Mbyte), which took me about 20 min, the autobuilder tries to build the package when the .dsc file is in the input-queue for more than 600 seconds (might be another value now), when it tries to build the package, it moves the files .dsc, .tar.gz and .diff.gz into another directory. I even had the impression that this timeout is ignored completely and that the autobuilder always tried to build the package when there was a .dsc-file available in the input-queue. This is also the reason why you will get an email saying that there is a size mismatch in the .tar.gz file - the .tar.gz it moved away was not complete and therefore does not match the size that is specified in the .dsc-file. > 100% 103MB 20.4KB/s 1:26:28 > scp: /var/www/extras-devel/incoming-builder/diablo/qt4-x11_4.4.0.orig.tar.gz: > set times: No such file or directory Yes, definitely the problem described above, your upload took almoast 90 min, currently it seems to work reliable only if the upload takes a lot less than 10 min. (As a workaround i uploaded my package to my own server with scp and i ran dput directly on the server, this way the upload was finished in a few seconds.) 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 target
Hi, Am Mittwoch, den 23.07.2008, 09:05 +0200 schrieb Benoit HERVIER: > Just a question about autobuilder : > > When i specify arch=all on sources packages why does it build only x86 > packages instead of x86 and armel ? Architecture=all means that the package contains only architecture independent data, so it makes sense to build it only on one architecture (preferably on the architecture with most processing power, which should be i386). What you are looking for is Architecture=any, which means that the package contains architecture dependent data, and that the package will be built for all available architectures (i386 and armel in case of maemo). 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: Updated versions of libraries pre-installed on ITOS causing problems with autobuilder
Am Dienstag, den 01.07.2008, 10:20 +0200 schrieb Niels Breet: > The offending package has been removed on request of Luciano Wolf from > indt. You shouldn't have dependecy problems anymore. > > I guess we (as community) need to come up with a procedure to prevent > things like this from happening. Thank you very much for removing the package from the repositories, and special thanks for issuing the two rebuilds of gnumeric. :) 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: Updated versions of libraries pre-installed on ITOS causing problems with autobuilder
Am Dienstag, den 01.07.2008, 11:10 +0300 schrieb Ed Bartosh: > If community would decide to introduce some checks into builder we can > do that. > I already have 2 candidates - check for categories and this one. Yes, both checks seem to be very good candidates. Regarding categories: Whats up with Categories for Closed-Source-Software like boingomobile, this package adds one useless category as well, but nobody from the community can fix this one!? > > btw: Do not get me wrong, i generally like the autobuilder and the > > concept of source-only uploads, it is working mostly well, but it has a > > few rough edges. ;-) > > > Well, many things have rough edges :) Repository full of not buildable > packages without sources is much worse than this issue, IMHO. Full ack. :) 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
Updated versions of libraries pre-installed on ITOS causing problems with autobuilder
Hi, I finally managed to build Gnumeric in the diablo autobuilder, but the package itself is not installable on Diablo because the autobuilder picked up the latest version of libglade2-dev from the extras(-devel) repository (version 1:2.6.2-1indt1). This causes a dependency on libglade2-0 (>= 1:2.6.2-1indt1) in the binary package. The package that presumably will be used for updating the tablets to the next ITOS version, osso-software-version-rx[34]4 depends on fixed versions of all pre-installed libraries, in this case libglade2-0 (=1:2.4.0-1osso2). The application-manager now of course refuses to install the gnumeric package because this would mean that libglade2-0 would have to be updated, this itself would at least work in red-pill-mode, but the next step is that updating libglade2-0 would implicitly cause the removal of osso-software-version-rx[34]4, which is not supported by the application manager and would be most likely a very, very bad idea as it would break updates to the next ITOS. So what can be done to fix this situation!? The only idea i have is to remove all libraries and packages whose installation conflicts with osso-software-version-rx[34]4 from (diablo)-extras(-devel) and reject further uploads of such packages before they get into extras-devel and cause such breakage. Regards, Thomas btw: Do not get me wrong, i generally like the autobuilder and the concept of source-only uploads, it is working mostly well, but it has a few rough edges. ;-) (Being able to at least upload binary packages to diablo-extras-devel would also help a lot in this case.) -- 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: Account does no longer work
Hi, Am Montag, den 30.06.2008, 10:58 +0200 schrieb Niels Breet: > This issue was resolved off-list and was probably a local configuration > error on Johannes' connection. It works for him now. It would be nice if you could tell us more about the configuration error, because it happened to me too from time to time in the last days, a retry a few minutes later allways worked, but today it seems that i am not able to login at all, i am trying to connect to garage since about an hour, it allways fails with: Permission denied (publickey,keyboard-interactive). I did not change anythin in my local configuration, and as i said, i had the same issue allready in the last days, but it allways worked some time later. 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: More autobuilder problems (armel only)
Hi, Am Montag, den 30.06.2008, 20:08 +0100 schrieb Andrew Flegg: > summary.log: > [2008-06-29 19:55:07] Processing package vim 7.0. Uploader: jaffa, > builder: builder1 > [2008-06-29 19:55:07] Building vim 7.0 for target > 'maemo-diablo-armel-extras-devel' > [2008-06-29 19:55:22] FAILED > > armel.root.log.FAILED.txt: > [2008-06-29 19:47:32] ensuring dir > /scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel/state > [2008-06-29 19:47:32] Cleaning Root > [2008-06-29 19:47:32] ensuring dir > /scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel > [2008-06-29 19:47:32] ensuring dir > /scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel/work > [2008-06-29 19:47:32] ensuring dir > /scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel/state > [2008-06-29 19:47:32] ensuring dir > /scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel/result > [2008-06-29 19:47:32] ensuring dir > /scratchbox/users/builder1/home/builder1/maemo-diablo-armel-extras-devel > [2008-06-29 19:47:35] Cleaning up... > [2008-06-29 19:47:37] Removing temporary target... > [2008-06-29 19:47:37] Done. I got the same kind of error yesterday with the second upload of gnumeric 1.8.3-1maemo3, the first one failed because i forgot to sign the package, see: https://garage.maemo.org/builder/diablo/gnumeric_1.8.3-1maemo3/ The "solution" was to just increase the version number and re-upload the package. I have no idea, what this kind of error means, maybe Ed can tell us more about it!? 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
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
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
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: libgsf-1-114 (needed to build Abiword) not found
* Roberto Resoli schrieb am 09.02.08, um 15:16 Uhr: > > There is no need to build libgsf, i built and uploaded it to > > extras-devel on monday because it is required for the Gnumeric package. > > oh nice! > many thx! No problem. > By the way, have you hitten an solved my same issue? I also tried to > build libgsf, but starting from ubuntu gutsy sources... Well, i did not experience these problem, maybe the differences between the ubuntu and debian unstable sources are causing this, see: http://patches.ubuntu.com/libg/libgsf/libgsf_1.14.7-2ubuntu1.patch Another reason might be some missing build-dependancies like liborbit2 (it did build and upload this package to extras-devel too), did you remove some of the Build-Dependancies in debian/control to be able to build libgsf, or were you able to fulfil all build-dependancies? Regards, Thomas -- Thomas Schmidt, Debian VDR Team http://pkg-vdr-dvb.alioth.debian.org/ signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: libgsf-1-114 (needed to build Abiword) not found - info and sources questions
Hi, * Ryan Pavlik schrieb am 07.02.08, um 00:23 Uhr: > Hmm, not sure what's going on here - I haven't touched the sources.list > but here's mine from chinook: > [sbox-CHINOOK_X86: ~] > cat /etc/apt/sources.list > deb http://repository.maemo.org/ bora free non-free > deb-src http://repository.maemo.org/ bora free > deb http://repository.maemo.org/extras bora free non-free > > deb file:/home/maemo/maemo-sdk-nokia-binaries_4.0 chinook explicit I guess you should really try to avoid using Bora repositories in the sources.list of your Chinook scratchbox target. (And on a tablet running OS2008 too.) > Perhaps that has something to do with why I can build it and you can't? > In such case, it should be a simple affair then of apt-get source > libgsf-1-114 with a bora source repository available, then > dpkg-buildpackage -rfakeroot from inside the directory in a Chinook > scratchbox. Could this (apparently) wrong list of sources be > introducing bugs in my Chinook packages of abiword? As i wrote to Roberto in my last mail, i built libgsf allready, it is available in extras-devel. So you should remove the lines containing bora from you sources.list and replace them with something like: deb http://repository.maemo.org/ chinook free non-free deb-src http://repository.maemo.org/ chinook free deb file:/home/chelli/maemo-sdk-nokia-binaries_4.0 chinook explicit deb http://repository.maemo.org/extras chinook free non-free deb-src http://repository.maemo.org/extras chinook free non-free deb http://repository.maemo.org/extras-devel chinook free non-free deb-src http://repository.maemo.org/extras-devel chinook free non-free deb-src http://ftp2.de.debian.org/debian/ etch main contrib non-free deb-src http://ftp2.de.debian.org/debian/ unstable main contrib non-free With this sources.list i get the following: [sbox-CHINOOK_X86: ~] > apt-cache policy libgsf-1-114 libgsf-1-114: Installed: 1.14.7-2chinook2 Candidate: 1.14.7-2chinook2 Version table: *** 1.14.7-2chinook2 0 500 http://repository.maemo.org chinook/free Packages 100 /var/lib/dpkg/status > So I guess I answer a question with what works for me and another > question :) :) Regards, Thomas -- Thomas Schmidt, Debian VDR Team http://pkg-vdr-dvb.alioth.debian.org/ signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: libgsf-1-114 (needed to build Abiword) not found
Hi, * Roberto Resoli schrieb am 06.02.08, um 23:27 Uhr: > Hello, > I'm trying to find > > libgsf-1-114 > libgsf-1-dev > > packages, needed to build Abiword, but they are not available in current > chinook > repository. > I have also tried to build from source, using the instructions found here: > > http://www.cleardefinition.com/page/Building_libgsf_for_Maemo/ > > but the package build fails right after compilation, during the > dh_install phase (log follows) There is no need to build libgsf, i built and uploaded it to extras-devel on monday because it is required for the Gnumeric package. I have the following in the sources.list of my scratchbox: deb http://repository.maemo.org/ chinook free non-free deb-src http://repository.maemo.org/ chinook free deb file:/home/chelli/maemo-sdk-nokia-binaries_4.0 chinook explicit deb http://repository.maemo.org/extras chinook free non-free deb-src http://repository.maemo.org/extras chinook free non-free deb http://repository.maemo.org/extras-devel chinook free non-free deb-src http://repository.maemo.org/extras-devel chinook free non-free deb-src http://ftp2.de.debian.org/debian/ etch main contrib non-free deb-src http://ftp2.de.debian.org/debian/ unstable main contrib non-free The last two lines are there to make it easier to get the sources of debian packages just with "apt-get source packagename" (the libgsf-package was built from the official debian source). Regards, Thomas -- Thomas Schmidt, Debian VDR Team http://pkg-vdr-dvb.alioth.debian.org/ signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
svn-buildpackage broken!?
Hi, is there anyone successfully using svn-buildpackage, which seems to be part of the maemo3-tools devkit? I only get the following errors when trying to use it: [sbox-CHINOOK_X86: ~] > svn-buildpackage Can't load '/scratchbox/devkits/maemo3-tools/lib/perl5/site_perl/5.8.4/i686-linux-thread-multi/auto/SVN/_Core/_Core.so' for module SVN::_Core: /scratchbox/devkits/maemo3-tools/lib/libsvn_ra_dav-1.so.0: undefined symbol: RAND_status at /scratchbox/tools/lib/perl5/5.8.4/i686-linux-thread-multi/DynaLoader.pm line 230. at /scratchbox/devkits/maemo3-tools/lib/perl5/site_perl/5.8.4/i686-linux-thread-multi/SVN/Base.pm line 59 BEGIN failed--compilation aborted at /scratchbox/devkits/maemo3-tools/lib/perl5/site_perl/5.8.4/i686-linux-thread-multi/SVN/Core.pm line 5. Compilation failed in require at /scratchbox/devkits/maemo3-tools/lib/perl5/site_perl/5.8.4/i686-linux-thread-multi/SVN/Client.pm line 4. BEGIN failed--compilation aborted at /scratchbox/devkits/maemo3-tools/lib/perl5/site_perl/5.8.4/i686-linux-thread-multi/SVN/Client.pm line 4. Compilation failed in require at /scratchbox/devkits/maemo3-tools/share/perl5/SDCommon.pm line 10. BEGIN failed--compilation aborted at /scratchbox/devkits/maemo3-tools/share/perl5/SDCommon.pm line 10. Compilation failed in require at /scratchbox/devkits/maemo3-tools/bin/svn-buildpackage line 105. BEGIN failed--compilation aborted at /scratchbox/devkits/maemo3-tools/bin/svn-buildpackage line 105. The same happens when i try to use the other tools belonging to svn-buildpackage (svn-inject, svn-upgrade...). I would really appreciate any hint that could lead to a working svn-buildpackage. (I tried to find a solution by myself, but scratchbox is still more or less like a mysterious black box for me.) :) Regards, Thomas -- Thomas Schmidt, Debian VDR Team http://pkg-vdr-dvb.alioth.debian.org/ signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
