Yes, Trunk:Handset, Trunk:IVI and Trunk:Netbook build against both Trunk and Trunk:Testing on OBS. In this tool, we just check the build against Trunk:Testing by default. And we reuse “osc build” tool to implement the local build work, then the repos it pulls from should be OBS download repository like http://download.meego.com/live/Trunk:/Testing/standard/, http://download.meego.com/live/Trunk:/Netbook/Testing/ .... , user can’t specify the repos currently.
Thanks Vivian From: Selbak, Rolla N Sent: Friday, November 19, 2010 12:35 AM To: Zhang, Vivian; meego-packaging Subject: Re: [meego-packaging] localcheckbuild, a tool to check if your upgrade break other MeeGo stuff You’re right, all the repos in the official Trunk:Testing url are built against Trunk:Testing: http://download.meego.com/testing/trunk/ So is that where localcheckbuild pulls from by default? Is there a flag where you specify repos to pull from? If you look in OBS at the Trunk:Handset, Trunk:IVI and Trunk:Netbook projects, they build against both Trunk and Trunk:Testing.... rs On 11/18/10 6:11 AM, "Zhang, Vivian" <[email protected]> wrote: Hi, rolla: Trunk:Netbook, Trunk:Handset, Trunk:IVI repos will be built against Trunk:Testing by default since I assume the latest packages are in Trunk:Testing. If there is any case to request checking build against Trunk , I can add it to todo list. Thanks vivian From: Selbak, Rolla N Sent: Thursday, November 18, 2010 9:38 PM To: Zhang, Vivian; meego-packaging Subject: Re: [meego-packaging] localcheckbuild, a tool to check if your upgrade break other MeeGo stuff Great Vivian, thanks! Question (and I haven’t tried the tool yet so maybe this is already obvious): Are the Trunk:Netbook, Trunk:Handset, Trunk:IVI repos that are used the ones built against ‘Trunk’ or built against ‘Trunk:Testing’? Is this something that can be toggled somehow or what’s the default? Thanks, rs On 11/18/10 12:52 AM, "Zhang, Vivian" <[email protected]> wrote: Hi: localcheckbuild tool is a new osc plugin which is used to list the dependant package list and local-build them with the new update packages to ensure the update works fine. All the build work will implement in your local machine, it doesn’t create any linking/copying on Server side. http://moblin.intel.com/wiki/Local_build_check_tool Workflow: 1. Check packages in projects Trunk:Testing, Trunk:Netbook, Trunk:Handset, Trunk:IVI to get the package list which depends on the one you want to check; 2. Download new RPMs of your updated package and check out the sources of packages in dependant list; 3. Running “osc build �Cprefer-pkgs=xxx” to build the package and check the result in the list one by one( --prefer-pkgs option ensures it uses the new updated RPMs when installing the build-root). Installation: 1．Ensure the build tool works in the silent mode, please add below lines to your /etc/sudoers Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY" $YOUR_USERNAME ALL=(ALL) NOPASSWD: /usr/bin/build 2．Download and install/upgrade below packages to the latest version http://download.meego.com/live/devel:/tools:/building <http://download.meego.com/live/devel:/tools:/building><http://download.meego.com/live/devel:/tools:/building> ) osc meego-osc-plugins build Optional: Enable arm arch support for localcheckbuild. Ubuntu: install package qemu-kvm-extras-static. Opensuse: install package qemu-svn. (http://download.opensuse.org/repositories/openSUSE:/Tools <http://download.opensuse.org/repositories/openSUSE:/Tools><http://download.opensuse.org/repositories/openSUSE:/Tools> ) Fedora: install package qemu-svn. (This package doesn't include in fedora repo, you can install it from opensuse repos. Eg: qemu-svn-0.11git2009.08.10.0340-12.7.i586.rpm from http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/i586 <http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/i586><http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/i586> ) Usage: osc localcheckbuild [-r] [-y] [--repourl=TEXT] [--excludepkgs=TEXT] [--buildpkgs=TEXT] PRJECTNAME PACKAGENAME REPOSITORY ARCH #The arguments REPOSITORY and ARCH are the first two columns in the 'osc repos' output. Example: # osc localcheckbuild devel:multimedia pulseaudio testing i586 ...... There are 18 packages in the dependant list. Packages in the to-be-built list : 16 * Trunk:Netbook : 3 gnome-media gnome-settings-daemon meego-panel-devices * Trunk:Handset : 2 meego-handset-statusindicators meegotouchcp-bluetooth * Trunk:Testing : 8 audiomanager phonon pavucontrol tone-generator libcanberra qt-mobility pulseaudio-modules-meego monitor-call-audio-setting-mfld * Trunk:IVI : 3 hfdialer audio_manager speech-dispatcher Packages in the skip list : 2 * 2 packages have been in the project devel:multimedia, please check the build result on OBS directly. alsa-plugins gst-plugin-good Total: 18, To be built: 16, Skip: 2. ...... Build finished. Log file: /var/tmp/buildcheck-pulseaudio-i586/buildcheck-pulseaudio.log. Total: 16, success: 16, fail: 0 Be noted that it may take a few hours to implement the build work which depends on the length of the dependant package list and your network speed. To-do list: 1. Support the option of excluding or specifying a specific project in OBS 2. Better analysis and sum-up for the build failure result. Any comments are welcomed. Thanks vivian
_______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
