[maemo-developers] More autobuilder problems (armel only)
From: Ed Bartosh eduard.bartosh at nokia.comDate: Tue Jul 1 14:27:10 EEST 2008
- Previous message: More autobuilder problems (armel only)
- Next message: Wiki page of the day: "USB networking" and "USB networking with Debian"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 2008-07-01 at 11:54 +0100, ext Andrew Flegg wrote: > On Tue, Jul 1, 2008 at 10:26 AM, Ed Bartosh <eduard.bartosh at nokia.com> wrote: > > On Mon, 2008-06-30 at 20:08 +0100, ext Andrew Flegg wrote: > >> > >> https://garage.maemo.org/builder/diablo/vim_7.0/sources/ > >> > > I tried to build your package in clean diablo(4.1 rootstrap + vim > > build-depends only) and found this issue: [snip] > > OK, thanks for that, I'll give it a go. Apart from removing all > packages not in the rootstrap, is there a way of identifying missing > build-depends apart from the "suck it and see" approach? > You can create separate target and install rootstrap + build-deps there. It's much more easy and clean approach then removing packages. I'd suggest to use autobuilder root.log to see how packages were installed and which repos were used. Here is example from latest gnumeric root log: [2008-07-01 13:47:36] Extracting rootstrap /scratchbox/packages/maemo-sdk-rootstrap_4.1_armel.tgz [2008-07-01 13:47:47] fakeroot apt-get -y -q -o APT::Get::AllowUnauthenticated=1 update </dev/null [2008-07-01 13:48:10] fakeroot apt-get -y -q -o APT::Get::AllowUnauthenticated=1 install --no-remove zlib1g-dev libglib2.0-dev libgsf-1-dev libgoffice-0-6-dev libxml2-dev libpango1.0-dev libgtk2.0-dev libglade2-dev libart-2.0-dev libgconf2-dev libgsf-gnome-1-dev libosso-dev libhildon1-dev libhildonfm2-dev </dev/null So, if you create new target, install rootstrap there and copy/paste two apt-get commands from the log you will have your building environment. You can also use sbdmock[1]. It will do all of above mentioned actions for you transparently. Autobuilder uses sbdmock to perform the builds, so using sbdmock is the best way to reproduce autobuilder environment. > > In future versions of autobuilder I'll try to introduce build timeout > > and just kill builds after timeout is expired. I'll add this to > > autobuilder todo. > > Sounds good. Last thing you want is someone uploading a fork bomb :-/ > Yep. [1] sbdmock - builder for debian packages inside Scratchbox http://www.bifh.org/wiki/sbdmock Regards, --- Ed
- Previous message: More autobuilder problems (armel only)
- Next message: Wiki page of the day: "USB networking" and "USB networking with Debian"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]