MeeGo wiki - User contributions [en]

Image Creation For Beginners

2011-02-15T12:35:18Z

Z1x2y3121:

__TOC__

== Creating a MeeGo Image ==

Here are the simple steps on how to create a MeeGo image.

For more in-depth information, go to the main Image Creator developer's guide: [[Image Creation]]

'''STEP 1 - Download Meego Image Creator (MIC)'''

MeeGo Image Creator is the tool we use to create MeeGo images. To get it you can:

* Download MIC source from Gitorious:
http://meego.gitorious.org/meego-developer-tools/image-creator
* Or, for Debian Squeeze, add the following line to /etc/apt/sources.list and install (using apt-get) ''mic2'':
deb <nowiki>http://repo.meego.com/tools/repos/debian/5.0/</nowiki> /

More on installation dependencies and options on downloading MIC, go to the 'Installation' section here: [[Image_Creation#Requirements]]

'''STEP 2 - Get MeeGo .ks File'''

KickStart (.ks) configuration files are passed to MIC to create images. KickStart files specify what repos to pull from, what packages to include, what post-scripts to run and what type of images to create.

*The official MeeGo .ks files for ARM based Nokia N900 are here: http://repo.meego.com/MeeGo/builds/trunk/ <version>/handset/images/meego-handset-armv7l-n900/
*The official MeeGo .ks files for Intel Atom based netbook and handset (Moorestown) are here: http://repo.meego.com/MeeGo/builds/trunk/ <version>/{netbook,handset,ivi}/images

You can download and use them as a base for the MeeGo images you create. Modify these .ks files as you wish to create tailored images.

We will use the netbook kickstart file to create a MeeGo netbook image: http://repo.meego.com/MeeGo/builds/trunk/1.1.80.7.20101119.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.7.20101119.1.ks (This is the latest file on November 19, 2010 hence please adjust the URL to get the latest version!)

It seems that the "@Core" and "@Base" have been renamed to "@Meego Core" and "@Meego Base" so i suggest you to edit the .ks file to rename the package with the good name.

'''STEP 3 - Create MeeGo Livecd Image'''

MIC has to be run with root privileges using 'sudo'.

Here is the command to create a MeeGo livecd image you can burn onto a CD.

<pre>
sudo mic-image-creator --config=default.ks --format=livecd --cache=mycache
</pre>

A file named meego-1.0-default-XX.iso is created. This ISO image is a hybrid image and can be either written to a disk device or burned onto a cd.

'''STEP 4 - Create MeeGo LiveUSB Image'''

To create a MeeGo liveusb image that you can transfer to a USB stick.

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --cache=mycache
</pre>

A file named meego-1.0-default-XX.usbimg will be created. To burn it onto a USB stick, run the following command:

<pre>
sudo mic-image-writer meego-1.0-default-XX.usbimg
</pre>

This image has a FAT file system and can be mounted easily on Windows and other OSes.

'''---FOR ADDITIONAL INFORMATION ON MIC, PLEASE VISIT THE MIC DEVELOPER'S GUIDE HERE: [[Image Creation]]---'''

== Configure Proxy and Other Variables ==

~/.mic2.conf is a configuration file that can make your life easier by specifying proxy settings, cache directories, and other variables that you normally would have to re-type in your command-line.

Copy and paste this into a file called: ~/.mic2.conf

Replace with your own relevant values.

<pre>
[main]
cachedir=/home/user1/mycache
tmpdir=/home/user1/mystorage/tmp
outdir=/home/user1/mystorage
proxy=http://my.proxy.com:911/
no_proxy=localhost,127.0.0.0/8,.mysite.com,172.16.0.0/16
</pre>

''cachedir'' = directory where the cached repo(s) will reside. With this variable set, you do not need to pass the --cache flag in the command-line.

''tmpdir'' = temporary directory used by mic2 when creating images. With this variable set, you do not need to pass the --tmpdir flag in the command-line.

''outdir'' = where your images will reside once they are created. With this variable set, you do not need to pass the --outdir flag in the command-line.

''proxy'' = specify your proxy if you're behind a behind a firewall.

''no_proxy'' = specify what domains should not sure the proxy setting.

'''Note:''' When specifying proxy and no_proxy, you do not need to use the --proxy flag in your .ks files when referring to repos.

'''---FOR ADDITIONAL INFORMATION ON MIC, PLEASE VISIT THE MIC DEVELOPER'S GUIDE HERE: [[Image_Creation]]---'''

== Another language version of this page ==

* [[适合新手的镜像制作-_-简体中文]]

适合新手的镜像制作- -简体中文

2011-02-15T12:32:19Z

Z1x2y3121:

__TOC__

== 制作一个Meego镜像 ==

这里是怎样制作一个Meego镜像的简单步骤。

想要获得更多的深入的信息，参照主要的镜像制作开发者指南：[[Image Creation]]

'''第一步 - 下载 Meego Image Create (MIC)'''

MeeGo Image Creator 是我们用于制作MeeGo镜像的工具。要获得它，你可以：

* 从Gitorious下载MIC源码:
http://meego.gitorious.org/meego-developer-tools/image-creator
* 或者，对于Debian Squuuze，将下面的一行加入/etc/apt/sources.list并且安装（使用apt-get）''mic2''：
deb <nowiki>http://repo.meego.com/tools/repos/debian/5.0/</nowiki> /

更多的安装需要和在下载MIC时的选项，参照这的'Installation'部分：[[Image_Creation#Requirements]]

'''第二步 - 获取MeeGo .ks文件'''

MIC通过KickStart (.ks)配置文件制作镜像.KickStart文件指定由哪些repo获取，包含哪些包，运行哪些后台脚本和制作哪种类型的镜像

*基于Nokia N900的ARM官方MeeGo .ks文件在这：http://repo.meego.com/MeeGo/builds/trunk/ <版本>/handset/images/meego-handset-armv7l-n900/
*基于上网本和手机(Moorestown)的Intel Atom官方MeeGo .ks文件在这：http://repo.meego.com/MeeGo/builds/trunk/ <版本>/{netbook,handset,ivi}/images

你可以下载和使用它们作为你制作MeeGo镜像的基础，通过修改这些.ks文件来制作你需要的镜像.

我们将使用上网本的kickstart文件去制作一个MeeGo上网本镜像：http://repo.meego.com/MeeGo/builds/trunk/1.1.80.7.20101119.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.7.20101119.1.ks (这是2010/11/19最新的文件，请调整网址获取最新的版本!)

好像”@Core”和”Base”已经被重命名为”@MeeGo Core”和”@MeeGo Base”，所以我建议你编辑.ks文件来以合适的名字重命名这些包.

'''第三步 - 制作MeeGo Livecd镜像

MIC必须使用root权限执行，使用'sudo'.

这里是制作一个你可以烧录到CD上的MeeGo livecd镜像.

<pre>
sudo mic-image-creator --config=default.ks --format=livecd --cache=mycache
</pre>

生成一个名字为meego-1.0-default-XX.iso的文件.这个ISO镜像是一个混合的镜像，可以被写入磁盘设备或者烧录到CD盘上.

'''第四步 - 制作LiveUSB镜像'''

制作一个可以转移到usb存储器中的MeeGo liveusb镜像.

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --cache=mycache
</pre>

将会生成一个名字为meego-1.0-default-XX.usbimg的文件. 要将它烧到USB存储器中，执行以下命令：

<pre>
sudo mic-image-writer meego-1.0-default-XX.usbimg
</pre>

这个镜像含有一个FAT文件系统，可以很容易的在Windows和其他系统中挂载.

'''---要获取更多关于MIC的信息，请访问MIC开发者指南:[[Image Creation]]---'''

== 配置Proxy和其他变量 ==

~/.mic2.conf是一个配置文件，它使得你更简单的指定proxy设置，缓冲目录和其它通常必须在命令行再次输入的变量

复制和粘贴这些到~/.mic2.conf文件中.

用你自己的值替换相关的变量

<pre>
[main]
cachedir=/home/user1/mycache
tmpdir=/home/user1/mystorage/tmp
outdir=/home/user1/mystorage
proxy=http://my.proxy.com:911/
no_proxy=localhost,127.0.0.0/8,.mysite.com,172.16.0.0/16
</pre>

''cachedir'' = 存放缓存仓库的目录.有了这个变量设置，你就不需要在命令行使用--cache标记.

''tmpdir'' = 当制作镜像时mic2所使用的临时目录.有了这个变量设置，你就不需要在命令行使用--tmpdir标记.

''outdir'' = 存放生成镜像的目录.有了这个变量设置，你就不需要在命令行使用--outdir标记.

''proxy'' = 如果你是工作在防火墙后的话,指定你的代理.

''no_proxy'' = 指定那些不确定代理设置的域.

'''注意：'''指定了proxy和no_proxy后，你不需要在.ks文件中的repos部分使用--proxy标记.

'''------要获取更多关于MIC的信息，请访问MIC开发者指南:[[Image Creation]]---'''

适合初学者的镜像制作- -简体中文

2011-02-15T12:31:15Z

Z1x2y3121: moved 适合初学者的镜像制作- -简体中文 to 适合新手的镜像制作- -简体中文

#REDIRECT [[适合新手的镜像制作- -简体中文]]

适合新手的镜像制作- -简体中文

2011-02-15T12:31:15Z

Z1x2y3121: moved 适合初学者的镜像制作- -简体中文 to 适合新手的镜像制作- -简体中文

__TOC__

== 制作一个Meego镜像 ==

这里是怎样制作一个Meego镜像的简单步骤。

想要获得更多的深入的信息，参照主要的镜像制作开发者指南：[[Image Creation]]

'''第一步 - 下载 Meego Image Create (MIc)'''

MeeGo Image Creator 是我们用于制作MeeGo镜像的工具。要获得它，你可以：

* 从Gitorious下载MIC源码:
http://meego.gitorious.org/meego-developer-tools/image-creator
* 或者，对于Debian Squuuze，将下面的一行加入/etc/apt/sources.list并且安装（使用apt-get）''mic2''：
deb <nowiki>http://repo.meego.com/tools/repos/debian/5.0/</nowiki> /

更多的安装需要和在下载MIC时的选项，参照这的'Installation'部分：[[Image_Creation#Requirements]]

'''第二步 - 获取MeeGo .ks文件'''

MIC通过KickStart (.ks)配置文件制作镜像.KickStart文件指定由哪些repo获取，包含哪些包，运行哪些后台脚本和制作哪种类型的镜像

*基于Nokia N900的ARM官方MeeGo .ks文件在这：http://repo.meego.com/MeeGo/builds/trunk/ <版本>/handset/images/meego-handset-armv7l-n900/
*基于上网本和手机(Moorestown)的Intel Atom官方MeeGo .ks文件在这：http://repo.meego.com/MeeGo/builds/trunk/ <版本>/{netbook,handset,ivi}/images

你可以下载和使用它们作为你制作MeeGo镜像的基础，通过修改这些.ks文件来制作你需要的镜像.

我们将使用上网本的kickstart文件去制作一个MeeGo上网本镜像：http://repo.meego.com/MeeGo/builds/trunk/1.1.80.7.20101119.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.7.20101119.1.ks (这是2010/11/19最新的文件，请调整网址获取最新的版本!)

好像”@Core”和”Base”已经被重命名为”@MeeGo Core”和”@MeeGo Base”，所以我建议你编辑.ks文件来以合适的名字重命名这些包.

'''第三步 - 制作MeeGo Livecd镜像

MIC必须使用root权限执行，使用'sudo'.

这里是制作一个你可以烧录到CD上的MeeGo livecd镜像.

<pre>
sudo mic-image-creator --config=default.ks --format=livecd --cache=mycache
</pre>

生成一个名字为meego-1.0-default-XX.iso的文件.这个ISO镜像是一个混合的镜像，可以被写入磁盘设备或者烧录到CD盘上.

'''第四步 - 制作LiveUSB镜像'''

制作一个可以转移到usb存储器中的MeeGo liveusb镜像.

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --cache=mycache
</pre>

将会生成一个名字为meego-1.0-default-XX.usbimg的文件. 要将它烧到USB存储器中，执行以下命令：

<pre>
sudo mic-image-writer meego-1.0-default-XX.usbimg
</pre>

这个镜像含有一个FAT文件系统，可以很容易的在Windows和其他系统中挂载.

'''---要获取更多关于MIC的信息，请访问MIC开发者指南:[[Image Creation]]---'''

== 配置Proxy和其他变量 ==

~/.mic2.conf是一个配置文件，它使得你更简单的指定proxy设置，缓冲目录和其它通常必须在命令行再次输入的变量

复制和粘贴这些到~/.mic2.conf文件中.

用你自己的值替换相关的变量

<pre>
[main]
cachedir=/home/user1/mycache
tmpdir=/home/user1/mystorage/tmp
outdir=/home/user1/mystorage
proxy=http://my.proxy.com:911/
no_proxy=localhost,127.0.0.0/8,.mysite.com,172.16.0.0/16
</pre>

''cachedir'' = 存放缓存仓库的目录.有了这个变量设置，你就不需要在命令行使用--cache标记.

''tmpdir'' = 当制作镜像时mic2所使用的临时目录.有了这个变量设置，你就不需要在命令行使用--tmpdir标记.

''outdir'' = 存放生成镜像的目录.有了这个变量设置，你就不需要在命令行使用--outdir标记.

''proxy'' = 如果你是工作在防火墙后的话,指定你的代理.

''no_proxy'' = 指定那些不确定代理设置的域.

'''注意：'''指定了proxy和no_proxy后，你不需要在.ks文件中的repos部分使用--proxy标记.

'''------要获取更多关于MIC的信息，请访问MIC开发者指南:[[Image Creation]]---'''

适合新手的镜像制作- -简体中文

2011-02-15T12:30:54Z

Z1x2y3121:

适合新手的镜像制作- -简体中文

2011-02-15T12:30:19Z

Z1x2y3121: Created page with "__TOC__ == 制作一个Meego镜像 == == Creating a MeeGo Image == 这里是怎样制作一个Meego镜像的简单步骤。想要获得更多的深入的信息，参照主要…"

__TOC__

== 制作一个Meego镜像 ==
== Creating a MeeGo Image ==

这里是怎样制作一个Meego镜像的简单步骤。

想要获得更多的深入的信息，参照主要的镜像制作开发者指南：[[Image Creation]]

'''第一步 - 下载 Meego Image Create (MIc)'''

MeeGo Image Creator 是我们用于制作MeeGo镜像的工具。要获得它，你可以：

* 从Gitorious下载MIC源码:
http://meego.gitorious.org/meego-developer-tools/image-creator
* 或者，对于Debian Squuuze，将下面的一行加入/etc/apt/sources.list并且安装（使用apt-get）''mic2''：
deb <nowiki>http://repo.meego.com/tools/repos/debian/5.0/</nowiki> /

更多的安装需要和在下载MIC时的选项，参照这的'Installation'部分：[[Image_Creation#Requirements]]

'''第二步 - 获取MeeGo .ks文件'''

MIC通过KickStart (.ks)配置文件制作镜像.KickStart文件指定由哪些repo获取，包含哪些包，运行哪些后台脚本和制作哪种类型的镜像

*基于Nokia N900的ARM官方MeeGo .ks文件在这：http://repo.meego.com/MeeGo/builds/trunk/ <版本>/handset/images/meego-handset-armv7l-n900/
*基于上网本和手机(Moorestown)的Intel Atom官方MeeGo .ks文件在这：http://repo.meego.com/MeeGo/builds/trunk/ <版本>/{netbook,handset,ivi}/images

你可以下载和使用它们作为你制作MeeGo镜像的基础，通过修改这些.ks文件来制作你需要的镜像.

我们将使用上网本的kickstart文件去制作一个MeeGo上网本镜像：http://repo.meego.com/MeeGo/builds/trunk/1.1.80.7.20101119.1/netbook/images/meego-netbook-ia32/meego-netbook-ia32-1.1.80.7.20101119.1.ks (这是2010/11/19最新的文件，请调整网址获取最新的版本!)

好像”@Core”和”Base”已经被重命名为”@MeeGo Core”和”@MeeGo Base”，所以我建议你编辑.ks文件来以合适的名字重命名这些包.

'''第三步 - 制作MeeGo Livecd镜像

MIC必须使用root权限执行，使用'sudo'.

这里是制作一个你可以烧录到CD上的MeeGo livecd镜像.

<pre>
sudo mic-image-creator --config=default.ks --format=livecd --cache=mycache
</pre>

生成一个名字为meego-1.0-default-XX.iso的文件.这个ISO镜像是一个混合的镜像，可以被写入磁盘设备或者烧录到CD盘上.

'''第四步 - 制作LiveUSB镜像'''

制作一个可以转移到usb存储器中的MeeGo liveusb镜像.

<pre>
sudo mic-image-creator --config=default.ks --format=liveusb --cache=mycache
</pre>

将会生成一个名字为meego-1.0-default-XX.usbimg的文件. 要将它烧到USB存储器中，执行以下命令：

<pre>
sudo mic-image-writer meego-1.0-default-XX.usbimg
</pre>

这个镜像含有一个FAT文件系统，可以很容易的在Windows和其他系统中挂载.

'''---要获取更多关于MIC的信息，请访问MIC开发者指南:[[Image Creation]]---'''

== 配置Proxy和其他变量 ==

~/.mic2.conf是一个配置文件，它使得你更简单的指定proxy设置，缓冲目录和其它通常必须在命令行再次输入的变量

复制和粘贴这些到~/.mic2.conf文件中.

用你自己的值替换相关的变量

<pre>
[main]
cachedir=/home/user1/mycache
tmpdir=/home/user1/mystorage/tmp
outdir=/home/user1/mystorage
proxy=http://my.proxy.com:911/
no_proxy=localhost,127.0.0.0/8,.mysite.com,172.16.0.0/16
</pre>

''cachedir'' = 存放缓存仓库的目录.有了这个变量设置，你就不需要在命令行使用--cache标记.

''tmpdir'' = 当制作镜像时mic2所使用的临时目录.有了这个变量设置，你就不需要在命令行使用--tmpdir标记.

''outdir'' = 存放生成镜像的目录.有了这个变量设置，你就不需要在命令行使用--outdir标记.

''proxy'' = 如果你是工作在防火墙后的话,指定你的代理.

''no_proxy'' = 指定那些不确定代理设置的域.

'''注意：'''指定了proxy和no_proxy后，你不需要在.ks文件中的repos部分使用--proxy标记.

'''------要获取更多关于MIC的信息，请访问MIC开发者指南:[[Image Creation]]---'''

Build Infrastructure/Sysadmin Distro/OBS setup openSUSE114

2011-02-15T08:43:09Z

Z1x2y3121:

Please check http://gitorious.org/opensuse/build-service/blobs/master/dist/README.SETUP
for the latest setup instructions!
<p>
These steps are to setup Open Build Service 1.7.5 on an openSuSE 11.2 installation. Currently this document describes how to setup an evaluation/test setup and is not meant as a production setup.
</p>
<p>
Most users won't need to install their own OBS and can just use an account on a publicly accessible OBS. Once public access is allowed to the global MeeGo OBS, there will be a link to obtain access.
</p>
<p>
There are cases where vendors may rather have full control of their builds and keep source private due to licensing restrictions, etc. These instructions are for these special cases.
</p>
<p>
MeeGo will switch to version 2.1 of the Build Service which is to be released soon. These instructions will be updated for the new version as soon as possible.
</p>

<h2>Add Repositories</h2>

First, we have to add the openSUSE:Tools repository to zypper for qemu-svn and other updated tools.

<code>
cd /etc/zypp/repos.d/;
wget http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
</code>

Accept the trust key.

<h2>Setup the Client</h2>
<h3>Install the Client Packages</h3>

*For obs worker:
<code>
zypper in obs-worker qemu-svn mount-static bash-static
</code>

<h3>Point To The Server</h3>
<p>
Edit the file /etc/sysconfig/obs-worker in order to point to correct repository server. (The example server is 192.168.1.1)
</p>
<code>
# vi /etc/sysconfig/obs-worker
OBS_SRC_SERVER="192.168.1.1:5352"
OBS_REPO_SERVERS="192.168.1.1:5252"
</code>

<h3>Start the Client</h3>
<p>Start the worker service
</p>
<code>
chkconfig --add obsworker
rcobsworker start
</code>

<h2>Setup the server</h2>

<h3>Install the Server packages</h3>

*For server:
<code>
zypper in obs-server obs-signd obs-utils createrepo nfs-client obs-api memcached lighttpd
</code>

<h3>MySQL Setup</h3>
Start daemon by default:
<code>
chkconfig --add mysql
rcmysql start
</code>

Secure the installation
<code>
/usr/bin/mysql_secure_installation
</code>

Create the databases:
<code>
mysql -u root -p
mysql> create database api_production;
mysql> create database webui_production;
</code>

Add the obs user for these databases (substitute the correct password in):

<code>
GRANT all privileges
ON api_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
GRANT all privileges
ON webui_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
FLUSH PRIVILEGES;
</code>

Now, configure OBS to use MySQL, first the API server.

<code>
vi /srv/www/obs/api/config/database.yml
#change the production section
production:
adapter: mysql
database: api_production
username: obs
password: ************
</code>
And setup the webui to use MySQL...
<code>
vi /srv/www/obs/webui/config/database.yml
#change the production section
production:
adapter: mysql
database: webui_production
username: obs
password: ************
</code>

Populate the database
<code>
cd /srv/www/obs/api/
RAILS_ENV="production" rake db:setup

cd /srv/www/obs/webui/
RAILS_ENV="production" rake db:setup
</code>
If this fails, check /srv/www/obs/api/config/environments/production.rb and /srv/www/obs/webui/config/environments/production.rb for configuration of the SOURCE_HOST and FRONTEND_HOST.

<h3>Setup lighttpd for webui</h3>
Make sure vhosts are enabled by uncommenting the following line:
<code>
# vi /etc/lighttpd/lighttpd.conf
include_shell "cat /etc/lighttpd/vhosts.d/*.conf"
</code>
Setup the regular webui on 80, api on 81, and 82 is the repository.
<code>
vi /etc/lighttpd/vhosts.d/obs.conf
$SERVER["socket"] == ":80" {
rails_app = "webui"
rails_root = "/srv/www/obs/webui"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/webui/log"
include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":81" {
rails_app = "api"
rails_root = "/srv/www/obs/api"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/api/log"

include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":82" {
server.name = "192.168.1.1"
server.document-root = "/srv/obs/repos/"
dir-listing.activate = "enable"
}

</code>
<p>
lighttpd requires some extra modules to be enabled: mod_access, mod_rewrite, mod_magnet, and mod_fastcgi. Do so by editing /etc/lighttpd/modules.conf:
</p>
<code>
# vi /etc/lighttpd/modules.conf
server.modules = (
"mod_access",
# "mod_alias",
# "mod_auth",
# "mod_evasive",
# "mod_redirect",
"mod_rewrite",
# "mod_setenv",
# "mod_usertrack",
)

##
## mod_magnet
##
include "conf.d/magnet.conf"

##
## FastCGI (mod_fastcgi)
##
include "conf.d/fastcgi.conf"
</code>

<p>
You need also to configure /srv/www/obs/webui/config/environments/production.rb to point to correct server names:
</p>
<code>
# vi /srv/www/obs/webui/config/environments/production.rb
FRONTEND_HOST = "192.168.1.1"
FRONTEND_PORT = 81
FRONTEND_PROTOCOL = 'http'
BUGZILLA_HOST = nil
DOWNLOAD_URL = "http://192.168.1.1:82"
ICHAIN_MODE = "off"
BASE_NAMESPACE = nil
</code>

<p>
Do the same for /srv/www/obs/api/config/environments/production.rb. As soon your backend is not on the same machine as the api (frontend), change the following:
</p>
<code>
# vi /srv/www/obs/api/config/environments/production.rb
SOURCE_HOST = "192.168.1.1"
</code>

<p>
Add the server to start by default.
</p>
<code>
chkconfig --add memcached
chkconfig --add lighttpd
chkconfig --add obsapidelayed
chkconfig --add obswebuidelayed
</code>

<p>
ligthttpd user and group need to be the onwer of api and webui dirs (as well as log and tmp):
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>

<h3>BSConfig.pm</h3>
<p>
The file <i>/usr/lib/obs/server/BSConfig.pm</i> is used to configure several settings for the Build Service. One of the major components is setting up the $hostname variable to the correct value. Currently I have this set to the IP address of the server.
</p>

<code>
my $hostname = '192.168.1.1';
</code>

<p>
The list of directories in /srv/obs/repos/ is the repositories, so I changed the $repodownload:
</p>

<code>
our $repodownload = "http://$hostname:82/";
</code>

<h3>Verification</h3>

Start the server.
<code>
# rcmemcached start
# rclighttpd start
# rcobsapidelayed start
# rcobswebuidelayed start
</code>
<p>
At this point you should be able to open a browser and go to your server and login to OBS. Port 80 should be the webui, port 81 should be the api, and port 82 should be the repository directory. The default username/password is Admin/opensuse.
</p>
<h3>Start By Default</h3>

<p>The OBS should start automatically, so they should be added to chkconfig to do so:</p>
<code>
chkconfig --add obsrepserver obssrcserver obsscheduler obsdispatcher obspublisher obswarden obssigner
</code>

<h2>Setting up Cross Compile</h2>
<h3>Configure build types</h3>
<p>
To setup cross compile, add the appropriate machine types to /etc/sysconfig/obs-server. For example, the following will enable ARM builds.
</p>
<code>
# vi /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 armv5el armv7el“
</code>

<h2>Cloning Repositories</h2>

<h3>prj and prjconf</h3>
<p>The project settings and the project config is an important part of the project and should be copied to the local project setup.</p>
<code>
osc -A <remote API URL> meta prj <repository name> > prj.txt
osc -A <remote API URL> meta prjconf <repository name> > prjconf.txt
</code>
<p>
Modify the prj.txt file to name valid users in the userid fields. Once modified, the settings and configuration can be applied to the local project.
</p>
<code>
osc -A <local API URL> meta prj <repository name> -F prj.txt
osc -A <local API URL> meta prjconf <repository name> -F prjconf.txt
</code>

<h3>Mirror</h3>
<p>
obs_mirror_project (/usr/sbin/obs_mirror_project) is used to copy an external OBS project. The script needed to be modified to use build.meego.com as apposed to the hard coded download.opensuse.org site. You need an login to build.meego.com to execute this script.
</p>
<code>
/usr/sbin/obs_mirror_project <repository name> <type> <arch>
</code>

<h3>Rescan Repository</h3>
<p>Once the download of the project is complete, you have to rescan the local repository.</p>
<code>
/usr/lib/obs/server/bs_admin --rescan-repository <repository name> <type> <arch>
</code>

<h2>Troubleshooting</h2>
<p>
Here are common issues that have been seen and how to resolve them.
</p>

<h3>HTTP Error 500</h3>
<p>
Check <b>/srv/www/obs/api/config/environments/production.rb</b>
and <b>/srv/www/obs/webui/config/environments/production.rb</b> for configuration of the
<b>SOURCE_HOST</b> and <b>FRONTEND_HOST</b>.
</p>
<h3>Cannot load person data for Admin in application_helper</h3>
<p>
Make sure you set the permissions on the api and webui directories.
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>
<p>
If this doesn't work then try to recreate the databases:
</p>
<code>
# mysql -u root -p
mysql> drop database api_production;
mysql> drop database webui_production;
</code>
<p>
Rerun the mysql database setup from above and re-run rake.
</p>
----
<h2>External Links</h2>
<p>
<ul>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Installation Maemo OBS Installation]
</li>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Fremantle_Setup Maemo Fremantel Setup]
</li>
</ul>
</p>
----
[[User:Liam | Liam]]

[[User:Dl9pf | Dl9pf]]

[[Category:Build Infrastructure]]

Local Build Without OBS Needed

2011-02-14T08:36:17Z

Z1x2y3121: /* Another language version of this page */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

On Debian, you should install 'qemu-user-static' from Squeeze (Debian 6.0) and later.

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

== Another language version of this page ==

* [[不需要obs的本地build-_简体中文]]

Local Build Without OBS Needed

2011-02-14T08:35:12Z

Z1x2y3121: /* Another language version of this page */

不需要obs的本地创建 - 简体中文

2011-02-14T08:34:45Z

Z1x2y3121: moved 不需要obs的本地创建 - 简体中文 to 不需要obs的本地build- 简体中文

#REDIRECT [[不需要obs的本地build- 简体中文]]

不需要obs的本地build- 简体中文

2011-02-14T08:34:45Z

Z1x2y3121: moved 不需要obs的本地创建 - 简体中文 to 不需要obs的本地build- 简体中文

这页主要是为了那些想尽量不与OBS后台连接的人-比如“尽量原始”

如果你只是想进行一次本地创建，那么你可能会使用“osc build",因为它基本可以为你做任何事。参照[[Build_Infrastructure/Packagers_Developers]]

== 使用build创建你的包 ==

一种更简单的创建包的方法就是使用‘build’，它是OpenSUSE，MeeGo中创建时用到的的基础工具，你可以根据的linux系统从这得到它的二进制包：http://repo.meego.com/MeeGo/tools/repos/，如果你的系统不再那，你可以从这获取它的源码包 http://www.gitorious.org/opensuse/build ，然后手动创建。

安装上它过后（我相信你知道怎么在你的linux系统上安装一个包），你可以通过运行“build --help”查看帮助信息。

你必须以root权限来运行build。如果你的网络需要代理，请设置好代理环境变量，比如：

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

如果你运行的是“sudo build ...” 并且你的网络需要proxy，请确保 sudo 继承了代理环境变量，你可以通过将下面的数据键入/etc/sudoers来实现

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build 会核查rpm包的签名，所以你必须导入你要使用的仓库公钥，比如：

对于 http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

你可以由此获得它的公钥：
http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

这个命令将会创建一个cpio的Meego二进制包。

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

你也可以选择使用spec文件去创建它，就这种情况而言，build将会在当前工作目录中找你的源码tar包和patche文件。

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build将会依据你的repo地址去缓存你的repo，所以对于相同的仓库，请每次使用相同的地址（地址末尾加/和不加/将得到不同的缓存目录），你可以使用多个:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

默认的缓存目录是/var/cache/build.你可以使用--cachedir选项来指定到其他目录。

默认的BUILDROOT目录是/var/tmp/build-root,你可以使用 --root选项指定一个或者更多的目录，一旦build完成了，你可以从BUILDROOT中获得你的二进制包，比如：

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

你的cpio二进制包是 /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm

== 疑难解答（ARM） ==

=== Exec format error ===
碰到这个问题：

在fedora13上使用‘build’去创建 armv7l 的rpm包时
其中可能的原因：可能是'qemu-arm'设置不正确。可以试试运行命令‘file /use/bin/qemu-arm’，如果他的结果显示‘dynamically linked’，那可能问题就在这，它本应该是‘statically linked’。可以使用命令 '
rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' （这个包可能会有更新，所以可以登入这个网址去取它）重新安装这个部分，可能你会因为一些依赖关系遇到些问题，你可以先卸载他们

在ubuntu10.04，你应该现安装‘qemu-arm-static’,使用命令：
apt-get install qemu-arm-static

=== rpm error ===
这个问题出现在ubuntu10.04当使用‘build’ 去创建i686rpm时.

''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
请修改 ‘’‘/usr/lib/build/configs/default.conf’‘’ 在preintall部分添加liblua --[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
这个问题出现在Ubuntu10.04当使用‘build’去创建i586包时
请使用''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
arch必须为'''i686'''

===chroot: cannot run command `rpm'===

当创建armv7lrpm包时，修改/usr/lib/build/build 和/usr/lib/build/configs/meego-1.0.conf ,将文件中的armv7el改成armv7l。可能/usr/lib/build/Build.pm也需要改。

不需要obs的本地build- 简体中文

2011-01-29T08:34:56Z

Z1x2y3121: Created page with "这页主要是为了那些想尽量不与OBS后台连接的人-比如“尽量原始” 如果你只是想进行一次本地创建，那么你可能会使用“osc build",因…"

Local Build Without OBS Needed

2011-01-29T08:14:15Z

Z1x2y3121: /* Another language version of this page */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

== Another language version of this page ==

* [[不需要obs的本地创建 - 简体中文]]

Local Build Without OBS Needed

2011-01-29T08:10:16Z

Z1x2y3121: /* chroot: cannot run command `rpm' */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

== Another language version of this page ==

* [[不通过obs的本地创建 - 简体中文]]

Local Build Without OBS Needed

2011-01-28T07:20:11Z

Z1x2y3121: /* Chinese version */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

[[Local_Build_Without_OBS_Needed/chinese]]

Local Build Without OBS Needed

2011-01-28T07:19:34Z

Z1x2y3121: /* chroot: cannot run command `rpm' */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

====Chinese version ====
[[Local_Build_Without_OBS_Needed/chinese]]

Local Build Without OBS Needed

2011-01-28T07:18:44Z

Z1x2y3121: /* chroot: cannot run command `rpm' */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

Chinese version ：
[[Local_Build_Without_OBS_Needed/chinese]]

Local Build Without OBS Needed

2011-01-28T07:18:03Z

Z1x2y3121: /* chroot: cannot run command `rpm' */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

Chinese version ：
[[chinese]]

Local Build Without OBS Needed

2011-01-28T07:17:01Z

Z1x2y3121: /* chroot: cannot run command `rpm' */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

Chinese version ：
Local_Build_Without_OBS_Needed/chinese

Local Build Without OBS Needed

2011-01-28T07:15:06Z

Z1x2y3121: /* chroot: cannot run command `rpm' */

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

Chinese version ：
http://wiki.meego.com/index.php?title=Local_Build_Without_OBS_Needed/chinese

Local Build Without OBS Needed

2011-01-28T07:13:55Z

Z1x2y3121:

This page is for people who want to avoid any connection with any OBS backend - ie "as raw as possible".

If you simply want to do a local build then you probably want "osc build" which does almost everything for you.
see [[Build_Infrastructure/Packagers_Developers]]

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
This problem on Ubuntu 10.04 when using 'build' to create a i586 package. Please Use ''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
The arch must be '''i686'''.

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

http://wiki.meego.com/index.php?title=Local_Build_Without_OBS_Needed/chinese

Local Build Without OBS Needed/chinese

2011-01-28T07:10:27Z

Z1x2y3121:

这页主要是为了那些想尽量不与OBS后台连接的人-比如“尽量原始”

如果你只是想进行一次本地创建，那么你可能会使用“osc build",因为它基本可以为你做任何事。参照[[Build_Infrastructure/Packagers_Developers]]

== 使用build创建你的包 ==

一种更简单的创建包的方法就是使用‘build’，它是OpenSUSE，MeeGo中创建时用到的的基础工具

你可以根据的linux系统从这得到它的二进制包：http://repo.meego.com/MeeGo/tools/repos/，如果你的系统不再那，你可以从这获取它的源码包 http://www.gitorious.org/opensuse/build ，然后手动创建。

安装上它过后（我相信你知道怎么在你的linux系统上安装一个包），你可以通过运行“build --help”查看帮助信息。

你必须以root权限来运行build。如果你的网络需要代理，请设置好代理环境变量，比如：

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

如果你运行的是“sudo build ...” 并且你的网络需要proxy，请确保 sudo 继承了代理环境变量，你可以通过将下面的数据键入/etc/sudoers来实现

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build 会核查rpm包的签名，所以你必须导入你要使用的仓库公钥，比如：

对于 http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

你可以由此获得它的公钥：
http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

这个命令将会创建一个cpio的Meego二进制包。

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

你也可以选择使用spec文件去创建它，就这种情况而言，build将会在当前工作目录中找你的源码tar包和patche文件。

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build将会依据你的repo地址去缓存你的repo，所以对于相同的仓库，请每次使用相同的地址（地址末尾加/和不加/将得到不同的缓存目录），你可以使用多个:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

默认的缓存目录是/var/cache/build.你可以使用--cachedir选项来指定到其他目录。

默认的BUILDROOT目录是/var/tmp/build-root,你可以使用 --root选项指定一个或者更多的目录，一旦build完成了，你可以从BUILDROOT中获得你的二进制包，比如：

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

你的cpio二进制包是 /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm

== 疑难解答（ARM） ==

=== Exec format error ===
碰到这个问题：

在fedora13上使用‘build’去创建 armv7l 的rpm包时
其中可能的原因：可能是'qemu-arm'设置不正确。可以试试运行命令‘file /use/bin/qemu-arm’，如果他的结果显示‘dynamically linked’，那可能问题就在这，它本应该是‘statically linked’。可以使用命令 '
rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' （这个包可能会有更新，所以可以登入这个网址去取它）重新安装这个部分，可能你会因为一些依赖关系遇到些问题，你可以先卸载他们

在ubuntu10.04，你应该现安装‘qemu-arm-static’,使用命令：
apt-get install qemu-arm-static

=== rpm error ===
这个问题出现在ubuntu10.04当使用‘build’ 去创建i686rpm时.

''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
请修改 ‘’‘/usr/lib/build/configs/default.conf’‘’ 在preintall部分添加liblua --[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
这个问题出现在Ubuntu10.04当使用‘build’去创建i586包时
请使用''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
arch必须为'''i686'''

===chroot: cannot run command `rpm'===

当创建armv7lrpm包时，修改/usr/lib/build/build 和/usr/lib/build/configs/meego-1.0.conf ,将文件中的armv7el改成armv7l。可能/usr/lib/build/Build.pm也需要改。

Local Build Without OBS Needed/chinese

2011-01-28T07:08:16Z

Z1x2y3121: 翻译

这也主要是为了那些想尽量不与OBS后台连接的人-比如“尽量原始”

如果你只是想进行一次本地创建，那么你可能会使用“osc build",因为它基本可以为你做任何事。参照[[Build_Infrastructure/Packagers_Developers]]

== 使用build创建你的包 ==

一种更简单的创建包的方法就是使用‘build’，它是OpenSUSE，MeeGo中创建时用到的的基础工具

你可以根据的linux系统从这得到它的二进制包：http://repo.meego.com/MeeGo/tools/repos/，如果你的系统不再那，你可以从这获取它的源码包 http://www.gitorious.org/opensuse/build ，然后手动创建。

安装上它过后（我相信你知道怎么在你的linux系统上安装一个包），你可以通过运行“build --help”查看帮助信息。

你必须以root权限来运行build。如果你的网络需要代理，请设置好代理环境变量，比如：

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

如果你运行的是“sudo build ...” 并且你的网络需要proxy，请确保 sudo 继承了代理环境变量，你可以通过将下面的数据键入/etc/sudoers来实现

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build 会核查rpm包的签名，所以你必须导入你要使用的仓库公钥，比如：

对于 http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

你可以由此获得它的公钥：
http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

这个命令将会创建一个cpio的Meego二进制包。

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

你也可以选择使用spec文件去创建它，就这种情况而言，build将会在当前工作目录中找你的源码tar包和patche文件。

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build将会依据你的repo地址去缓存你的repo，所以对于相同的仓库，请每次使用相同的地址（地址末尾加/和不加/将得到不同的缓存目录），你可以使用多个:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

默认的缓存目录是/var/cache/build.你可以使用--cachedir选项来指定到其他目录。

默认的BUILDROOT目录是/var/tmp/build-root,你可以使用 --root选项指定一个或者更多的目录，一旦build完成了，你可以从BUILDROOT中获得你的二进制包，比如：

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

你的cpio二进制包是 /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm

== 疑难解答（ARM） ==

=== Exec format error ===
碰到这个问题：

在fedora13上使用‘build’去创建 armv7l 的rpm包时
其中可能的原因：可能是'qemu-arm'设置不正确。可以试试运行命令‘file /use/bin/qemu-arm’，如果他的结果显示‘dynamically linked’，那可能问题就在这，它本应该是‘statically linked’。可以使用命令 '
rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' （这个包可能会有更新，所以可以登入这个网址去取它）重新安装这个部分，可能你会因为一些依赖关系遇到些问题，你可以先卸载他们

在ubuntu10.04，你应该现安装‘qemu-arm-static’,使用命令：
apt-get install qemu-arm-static

=== rpm error ===
这个问题出现在ubuntu10.04当使用‘build’ 去创建i686rpm时.

''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
请修改 ‘’‘/usr/lib/build/configs/default.conf’‘’ 在preintall部分添加liblua --[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

=== Nothing Provides ===
这个问题出现在Ubuntu10.04当使用‘build’去创建i586包时
请使用''build --repository http://repo.meego.com/MeeGo/builds/xxx/core/repos/ia32/packages/ --arch i686 xxxx.src.rpm''
arch必须为'''i686'''

===chroot: cannot run command `rpm'===

当创建armv7lrpm包时，修改/usr/lib/build/build 和/usr/lib/build/configs/meego-1.0.conf ,将文件中的armv7el改成armv7l。可能/usr/lib/build/Build.pm也需要改。

Build Infrastructure/Sysadmin Distro/OBS setup openSUSE114

2011-01-26T01:21:25Z

Z1x2y3121:

Please check http://gitorious.org/opensuse/build-service/blobs/master/dist/README.SETUP
for the latest setup instructions!
<p>
These steps are to setup Open Build Service 1.7.5 on an openSuSE 11.2 installation. Currently this document describes how to setup an evaluation/test setup and is not meant as a production setup.
</p>
<p>
Most users won't need to install their own OBS and can just use an account on a publicly accessible OBS. Once public access is allowed to the global MeeGo OBS, there will be a link to obtain access.
</p>
<p>
There are cases where vendors may rather have full control of their builds and keep source private due to licensing restrictions, etc. These instructions are for these special cases.
</p>
<p>
MeeGo will switch to version 2.1 of the Build Service which is to be released soon. These instructions will be updated for the new version as soon as possible.
</p>

<h2>Add Repositories</h2>

First, we have to add the openSUSE:Tools repository to zypper for qemu-svn and other updated tools.

<code>
cd /etc/zypp/repos.d/;
wget http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
</code>

Accept the trust key.

<h2>Setup the Client</h2>
<h3>Install the Client Packages</h3>

*For obs worker:
<code>
zypper in obs-worker qemu-svn mount-static bash-static
</code>

<h3>Point To The Server</h3>
<p>
Edit the file /etc/sysconfig/obs-worker in order to point to correct repository server. (The example server is 192.168.1.1)
</p>
<code>
# vi /etc/sysconfig/obs-worker
OBS_SRC_SERVER="192.168.1.1:5352"
OBS_REPO_SERVERS="192.168.1.1:5252"
</code>

<h3>Start the Client</h3>
<p>Start the worker service
</p>
<code>
chkconfig --add obsworker
rcobsworker start
</code>

<h2>Setup the server</h2>

<h3>Install the Server packages</h3>

*For server:
<code>
zypper in obs-server obs-signd obs-utils createrepo nfs-client obs-api memcached lighttpd
</code>

<h3>MySQL Setup</h3>
Start daemon by default:
<code>
chkconfig --add mysql
rcmysql start
</code>

Secure the installation
<code>
/usr/bin/mysql_secure_installation
</code>

Create the databases:
<code>
mysql -u root -p
mysql> create database api_production;
mysql> create database webui_production;
</code>

Add the obs user for these databases (substitute the correct password in):

<code>
GRANT all privileges
ON api_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
GRANT all privileges
ON webui_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
FLUSH PRIVILEGES;
</code>

Now, configure OBS to use MySQL, first the API server.

<code>
vi /srv/www/obs/api/config/database.yml
#change the production section
production:
adapter: mysql
database: api_production
username: obs
password: ************
</code>
And setup the webui to use MySQL...
<code>
vi /srv/www/obs/webui/config/database.yml
#change the production section
production:
adapter: mysql
database: webui_production
username: obs
password: ************
</code>

Populate the database
<code>
cd /srv/www/obs/api/
RAILS_ENV="production" rake db:setup

cd /srv/www/obs/webui/
RAILS_ENV="production" rake db:setup
</code>
If this fails, check /srv/www/obs/api/config/environments/production.rb and /srv/www/obs/webui/config/environments/production.rb for configuration of the SOURCE_HOST and FRONTEND_HOST.

<h3>Setup lighttpd for webui</h3>
Make sure vhosts are enabled by uncommenting the following line:
<code>
# vi /etc/lighttpd/lighttpd.conf
include_shell "cat /etc/lighttpd/vhosts.d/*.conf"
</code>
Setup the regular webui on 80, api on 81, and 82 is the repository.
<code>
vi /etc/lighttpd/vhosts.d/obs.conf
$SERVER["socket"] == ":80" {
rails_app = "webui"
rails_root = "/srv/www/obs/webui"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/webui/log"
include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":81" {
rails_app = "api"
rails_root = "/srv/www/obs/api"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/api/log"

include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":82" {
server.name = "192.168.1.1"
server.document-root = "/srv/obs/repos/"
dir-listing.activate = "enable"
}

</code>
<p>
lighttpd requires some extra modules to be enabled: mod_access, mod_rewrite, mod_magnet, and mod_fastcgi. Do so by editing /etc/lighttpd/modules.conf:
</p>
<code>
# vi /etc/lighttpd/modules.conf
server.modules = (
"mod_access",
# "mod_alias",
# "mod_auth",
# "mod_evasive",
# "mod_redirect",
"mod_rewrite",
# "mod_setenv",
# "mod_usertrack",
)

##
## mod_magnet
##
include "conf.d/magnet.conf"

##
## FastCGI (mod_fastcgi)
##
include "conf.d/fastcgi.conf"
</code>

<p>
You need also to configure /srv/www/obs/webui/config/environments/production.rb to point to correct server names:
</p>
<code>
# vi /srv/www/obs/webui/config/environments/production.rb
FRONTEND_HOST = "192.168.1.1"
FRONTEND_PORT = 81
FRONTEND_PROTOCOL = 'http'
BUGZILLA_HOST = nil
DOWNLOAD_URL = "http://192.168.1.1:82"
ICHAIN_MODE = "off"
BASE_NAMESPACE = nil
</code>

<p>
Do the same for /srv/www/obs/api/config/environments/production.rb. As soon your backend is not on the same machine as the api (frontend), change the following:
</p>
<code>
# vi /srv/www/obs/api/config/environments/production.rb
SOURCE_HOST = "192.168.1.1"
</code>

<p>
Add the server to start by default.
</p>
<code>
chkconfig --add memcached
chkconfig --add lighttpd
chkconfig --add obsapidelayed
chkconfig --add obswebuidelayed
</code>

<p>
ligthttpd user and group need to be the onwer of api and webui dirs (as well as log and tmp):
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>

<h3>BSConfig.pm</h3>
<p>
The file <i>/usr/lib/obs/server/BSConfig.pm</i> is used to configure several settings for the Build Service. One of the major components is setting up the $hostname variable to the correct value. Currently I have this set to the IP address of the server.
</p>

<code>
my $hostname = '192.168.1.1';
</code>

<p>
The list of directories in /srv/obs/repos/ is the repositories, so I changed the $repodownload:
</p>

<code>
our $repodownload = "http://$hostname:82/";
</code>

<h3>Verification</h3>
<p>
At this point you should be able to open a browser and go to your server and login to OBS. Port 80 should be the webui, port 81 should be the api, and port 82 should be the repository directory. The default username/password is Admin/opensuse.
</p>
<h3>Start By Default</h3>

<p>The OBS should start automatically, so they should be added to chkconfig to do so:</p>
<code>
chkconfig --add obsrepserver obssrcserver obsscheduler obsdispatcher obspublisher obswarden obssigner
</code>

<h2>Setting up Cross Compile</h2>
<h3>Configure build types</h3>
<p>
To setup cross compile, add the appropriate machine types to /etc/sysconfig/obs-server. For example, the following will enable ARM builds.
</p>
<code>
# vi /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 armv5el armv7el“
</code>

<h2>Cloning Repositories</h2>

<h3>prj and prjconf</h3>
<p>The project settings and the project config is an important part of the project and should be copied to the local project setup.</p>
<code>
osc -A <remote API URL> meta prj <repository name> > prj.txt
osc -A <remote API URL> meta prjconf <repository name> > prjconf.txt
</code>
<p>
Modify the prj.txt file to name valid users in the userid fields. Once modified, the settings and configuration can be applied to the local project.
</p>
<code>
osc -A <local API URL> meta prj <repository name> -F prj.txt
osc -A <local API URL> meta prjconf <repository name> -F prjconf.txt
</code>

<h3>Mirror</h3>
<p>
obs_mirror_project (/usr/sbin/obs_mirror_project) is used to copy an external OBS project. The script needed to be modified to use build.meego.com as apposed to the hard coded download.opensuse.org site. You need an login to build.meego.com to execute this script.
</p>
<code>
/usr/sbin/obs_mirror_project <repository name> <type> <arch>
</code>

<h3>Rescan Repository</h3>
<p>Once the download of the project is complete, you have to rescan the local repository.</p>
<code>
/usr/lib/obs/server/bs_admin --rescan-repository <repository name> <type> <arch>
</code>

<h2>Troubleshooting</h2>
<p>
Here are common issues that have been seen and how to resolve them.
</p>

<h3>HTTP Error 500</h3>
<p>
Check <b>/srv/www/obs/api/config/environments/production.rb</b>
and <b>/srv/www/obs/webui/config/environments/production.rb</b> for configuration of the
<b>SOURCE_HOST</b> and <b>FRONTEND_HOST</b>.
</p>
<h3>Cannot load person data for Admin in application_helper</h3>
<p>
Make sure you set the permissions on the api and webui directories.
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>
<p>
If this doesn't work then try to recreate the databases:
</p>
<code>
# mysql -u root -p
mysql> drop database api_production;
mysql> drop database webui_production;
</code>
<p>
Rerun the mysql database setup from above and re-run rake.
</p>
----
<h2>External Links</h2>
<p>
<ul>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Installation Maemo OBS Installation]
</li>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Fremantle_Setup Maemo Fremantel Setup]
</li>
</ul>
</p>
----
[[User:Liam | Liam]]

[[User:Dl9pf | Dl9pf]]

[[Category:Build Infrastructure]]

Build Infrastructure/Sysadmin Distro/OBS setup openSUSE114

2011-01-18T02:21:27Z

Z1x2y3121:

Please check http://gitorious.org/opensuse/build-service/blobs/master/dist/README.SETUP
for the latest setup instructions!
<p>
These steps are to setup Open Build Service 1.7.5 on an openSuSE 11.2 installation. Currently this document describes how to setup an evaluation/test setup and is not meant as a production setup.
</p>
<p>
Most users won't need to install their own OBS and can just use an account on a publicly accessible OBS. Once public access is allowed to the global MeeGo OBS, there will be a link to obtain access.
</p>
<p>
There are cases where vendors may rather have full control of their builds and keep source private due to licensing restrictions, etc. These instructions are for these special cases.
</p>
<p>
MeeGo will switch to version 2.1 of the Build Service which is to be released soon. These instructions will be updated for the new version as soon as possible.
</p>

<h2>Add Repositories</h2>

First, we have to add the openSUSE:Tools repository to zypper for qemu-svn and other updated tools.

<code>
cd /etc/zypp/repos.d/;
wget http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
</code>

Accept the trust key.

<h2>Setup the Client</h2>
<h3>Install the Client Packages</h3>

*For obs worker:
<code>
zypper in obs-worker qemu-svn mount-static bash-static
</code>

<h3>Point To The Server</h3>
<p>
Edit the file /etc/sysconfig/obs-worker in order to point to correct repository server. (The example server is 192.168.1.1)
</p>
<code>
# vi /etc/sysconfig/obs-worker
OBS_SRC_SERVER="192.168.1.1:5352"
OBS_REPO_SERVERS="192.168.1.1:5252"
</code>

<h3>Start the Client</h3>
<p>Start the worker service
</p>
<code>
chkconfig --add obsworker
rcobsworker start
</code>

<h2>Setup the server</h2>

<h3>Install the Server packages</h3>

*For server:
<code>
zypper in obs-server obs-signd obs-utils createrepo nfs-client obs-api memcached lighttpd
</code>

<h3>MySQL Setup</h3>
Start daemon by default:
<code>
chkconfig --add mysql
rcmysql start
</code>

Secure the installation
<code>
/usr/bin/mysql_secure_installation
</code>

Create the databases:
<code>
mysql -u root -p
mysql> create database api_production;
mysql> create database webui_production;
</code>

Add the obs user for these databases (substitute the correct password in):

<code>
GRANT all privileges
ON api_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
GRANT all privileges
ON webui_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
FLUSH PRIVILEGES;
</code>

Now, configure OBS to use MySQL, first the API server.

<code>
vi /srv/www/obs/api/config/database.yml
#change the production section
production:
adapter: mysql
database: api_production
username: obs
password: ************
</code>
And setup the webui to use MySQL...
<code>
vi /srv/www/obs/webui/config/database.yml
#change the production section
production:
adapter: mysql
database: webui_production
username: obs
password: ************
</code>

Populate the database
<code>
cd /srv/www/obs/api/
RAILS_ENV="production"
rake db:setup

cd /srv/www/obs/webui/
RAILS_ENV="production"
rake db:setup
</code>
If this fails, check /srv/www/obs/api/config/environments/production.rb and /srv/www/obs/webui/config/environments/production.rb for configuration of the SOURCE_HOST and FRONTEND_HOST.

<h3>Setup lighttpd for webui</h3>
Make sure vhosts are enabled by uncommenting the following line:
<code>
# vi /etc/lighttpd/lighttpd.conf
include_shell "cat /etc/lighttpd/vhosts.d/*.conf"
</code>
Setup the regular webui on 80, api on 81, and 82 is the repository.
<code>
vi /etc/lighttpd/vhosts.d/obs.conf
$SERVER["socket"] == ":80" {
rails_app = "webui"
rails_root = "/srv/www/obs/webui"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/webui/log"
include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":81" {
rails_app = "api"
rails_root = "/srv/www/obs/api"
rails_procs = 3
# production/development are typical values here
rails_mode = "production"
log_root = "/srv/www/obs/api/log"

include "vhosts.d/rails.inc"
}
$SERVER["socket"] == ":82" {
server.name = "192.168.1.1"
server.document-root = "/srv/obs/repos/"
dir-listing.activate = "enable"
}

</code>
<p>
lighttpd requires some extra modules to be enabled: mod_access, mod_rewrite, mod_magnet, and mod_fastcgi. Do so by editing /etc/lighttpd/modules.conf:
</p>
<code>
# vi /etc/lighttpd/modules.conf
server.modules = (
"mod_access",
# "mod_alias",
# "mod_auth",
# "mod_evasive",
# "mod_redirect",
"mod_rewrite",
# "mod_setenv",
# "mod_usertrack",
)

##
## mod_magnet
##
include "conf.d/magnet.conf"

##
## FastCGI (mod_fastcgi)
##
include "conf.d/fastcgi.conf"
</code>

<p>
You need also to configure /srv/www/obs/webui/config/environments/production.rb to point to correct server names:
</p>
<code>
# vi /srv/www/obs/webui/config/environments/production.rb
FRONTEND_HOST = "192.168.1.1"
FRONTEND_PORT = 81
FRONTEND_PROTOCOL = 'http'
BUGZILLA_HOST = nil
DOWNLOAD_URL = "http://192.168.1.1:82"
ICHAIN_MODE = "off"
BASE_NAMESPACE = nil
</code>

<p>
Do the same for /srv/www/obs/api/config/environments/production.rb. As soon your backend is not on the same machine as the api (frontend), change the following:
</p>
<code>
# vi /srv/www/obs/api/config/environments/production.rb
SOURCE_HOST = "192.168.1.1"
</code>

<p>
Add the server to start by default.
</p>
<code>
chkconfig --add memcached
chkconfig --add lighttpd
chkconfig --add obsapidelayed
chkconfig --add obswebuidelayed
</code>

<p>
ligthttpd user and group need to be the onwer of api and webui dirs (as well as log and tmp):
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>

<h3>BSConfig.pm</h3>
<p>
The file <i>/usr/lib/obs/server/BSConfig.pm</i> is used to configure several settings for the Build Service. One of the major components is setting up the $hostname variable to the correct value. Currently I have this set to the IP address of the server.
</p>

<code>
my $hostname = '192.168.1.1';
</code>

<p>
The list of directories in /srv/obs/repos/ is the repositories, so I changed the $repodownload:
</p>

<code>
our $repodownload = "http://$hostname:82/";
</code>

<h3>Verification</h3>
<p>
At this point you should be able to open a browser and go to your server and login to OBS. Port 80 should be the webui, port 81 should be the api, and port 82 should be the repository directory. The default username/password is Admin/opensuse.
</p>
<h3>Start By Default</h3>

<p>The OBS should start automatically, so they should be added to chkconfig to do so:</p>
<code>
chkconfig --add obsrepserver obssrcserver obsscheduler obsdispatcher obspublisher obswarden obssigner
</code>

<h2>Setting up Cross Compile</h2>
<h3>Configure build types</h3>
<p>
To setup cross compile, add the appropriate machine types to /etc/sysconfig/obs-server. For example, the following will enable ARM builds.
</p>
<code>
# vi /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 armv5el armv7el“
</code>

<h2>Cloning Repositories</h2>

<h3>prj and prjconf</h3>
<p>The project settings and the project config is an important part of the project and should be copied to the local project setup.</p>
<code>
osc -A <remote API URL> meta prj <repository name> > prj.txt
osc -A <remote API URL> meta prjconf <repository name> > prjconf.txt
</code>
<p>
Modify the prj.txt file to name valid users in the userid fields. Once modified, the settings and configuration can be applied to the local project.
</p>
<code>
osc -A <local API URL> meta prj <repository name> -F prj.txt
osc -A <local API URL> meta prjconf <repository name> -F prjconf.txt
</code>

<h3>Mirror</h3>
<p>
obs_mirror_project (/usr/sbin/obs_mirror_project) is used to copy an external OBS project. The script needed to be modified to use build.meego.com as apposed to the hard coded download.opensuse.org site. You need an login to build.meego.com to execute this script.
</p>
<code>
/usr/sbin/obs_mirror_project <repository name> <type> <arch>
</code>

<h3>Rescan Repository</h3>
<p>Once the download of the project is complete, you have to rescan the local repository.</p>
<code>
/usr/lib/obs/server/bs_admin --rescan-repository <repository name> <type> <arch>
</code>

<h2>Troubleshooting</h2>
<p>
Here are common issues that have been seen and how to resolve them.
</p>

<h3>HTTP Error 500</h3>
<p>
Check <b>/srv/www/obs/api/config/environments/production.rb</b>
and <b>/srv/www/obs/webui/config/environments/production.rb</b> for configuration of the
<b>SOURCE_HOST</b> and <b>FRONTEND_HOST</b>.
</p>
<h3>Cannot load person data for Admin in application_helper</h3>
<p>
Make sure you set the permissions on the api and webui directories.
</p>
<code>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</code>
<p>
If this doesn't work then try to recreate the databases:
</p>
<code>
# mysql -u root -p
mysql> drop database api_production;
mysql> drop database webui_production;
</code>
<p>
Rerun the mysql database setup from above and re-run rake.
</p>
----
<h2>External Links</h2>
<p>
<ul>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Installation Maemo OBS Installation]
</li>
<li>
[http://wiki.maemo.org/OpenSuse_Build_Service/Fremantle_Setup Maemo Fremantel Setup]
</li>
</ul>
</p>
----
[[User:Liam | Liam]]

[[User:Dl9pf | Dl9pf]]

[[Category:Build Infrastructure]]

Local Build Without OBS Needed

2010-12-09T04:59:27Z

Z1x2y3121: /* rpm error */

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem :

on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

on ubuntu10.04,you should install 'qemu-arm-static',use command:apt-get install qemu-arm-static

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

===chroot: cannot run command `rpm'===

when build a armv7l rpm,modify /usr/lib/build/build and /usr/lib/build/configs/meego-1.0.conf ,change armv7el to armv7l in these files,maybe /usr/lib/build/Build.pm also need change.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T10:43:11Z

Z1x2y3121: /* Installing for ubuntu10.04 */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.'build' will create a build system to build rpm

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key ,though it could work normally )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package ,run 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

<pre>
osc -A url
</pre>

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>(maybe select them in the obs web first).I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

==Attention==

====Version====

If you want to build the rpm of version 1.1,you should add 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04, you should install qemu-arm-static,use 'apt-get install qemu-arm-static'.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T10:00:11Z

Z1x2y3121: /* Version */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.'build' will create a build system to build rpm

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package ,run 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

<pre>
osc -A url
</pre>

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>(maybe select them in the obs web first).I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

==Attention==

====Version====

If you want to build the rpm of version 1.1,you should add 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04, you should install qemu-arm-static,use 'apt-get install qemu-arm-static'.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T09:49:15Z

Z1x2y3121: /* second step */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.'build' will create a build system to build rpm

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package ,run 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

<pre>
osc -A url
</pre>

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>(maybe select them in the obs web first).I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

==Attention==

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04, you should install qemu-arm-static,use 'apt-get install qemu-arm-static'.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T09:41:09Z

Z1x2y3121: /* Installing for fedora13 */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.'build' will create a build system to build rpm

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package ,run 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>(maybe select them in the obs web first).I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

==Attention==

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04, you should install qemu-arm-static,use 'apt-get install qemu-arm-static'.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T04:59:03Z

Z1x2y3121: /* Attention */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.'build' will create a build system to build rpm

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>(maybe select them in the obs web first).I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

==Attention==

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04, you should install qemu-arm-static,use 'apt-get install qemu-arm-static'.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T02:26:35Z

Z1x2y3121: /* Building your package using build */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.'build' will create a build system to build rpm

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>(maybe select them in the obs web first).I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

===Attention===

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04, you should install qemu-arm-static,use 'apt-get install qemu-arm-static'.

Local Build Without OBS Needed

2010-12-08T01:15:33Z

Z1x2y3121: /* Exec format error */

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T01:13:27Z

Z1x2y3121: /* Arch */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>(maybe select them in the obs web first).I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

===Attention===

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04, you should install qemu-arm-static,use 'apt-get install qemu-arm-static'.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T01:04:08Z

Z1x2y3121: /* second step */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>(maybe select them in the obs web first).I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

===Attention===

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04,I find 'qemu-arm' in /usr/local/bin,and run 'file /usr/local/bin' ,and it show 'dynamically linked',but it worked normal,and I was puzzled to this.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T01:03:41Z

Z1x2y3121: /* second step */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>(you should select them in the obs web).I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

===Attention===

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04,I find 'qemu-arm' in /usr/local/bin,and run 'file /usr/local/bin' ,and it show 'dynamically linked',but it worked normal,and I was puzzled to this.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-08T00:17:18Z

Z1x2y3121: /* second step */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,maybe any change is ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory include a directory in name of the packagename

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,runing this in this directory you downloaded,and put all files include source code package in this directory.'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>.I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

===Attention===

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04,I find 'qemu-arm' in /usr/local/bin,and run 'file /usr/local/bin' ,and it show 'dynamically linked',but it worked normal,and I was puzzled to this.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-07T10:28:52Z

Z1x2y3121: /* Attention */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

== Osc build using local obs ==

I think it is so much like to build without OBS,so I add it.

=== First step ===

Install 'build' tools like up.

=== second step ===

Sure you have a available local OBS,and use commands:

<pre>
osc -A url meta pkg -e home:yourusername packagename
</pre>

this means create a new package in obs.url is the address of your obs API.(notice the port).
As I seem,we should install 'vi',and remember to type something between <type><>(in fact,may be every change will be ok)

<pre>
osc -A url co home:yourusername/packagename
</pre>

You will find a directory like home:yourusername in your current directory

<pre>
osc -A url build --no-verify MeeGo_1.1.80.6.20101116.1_Core_standard i586
</pre>

Of course,'--no-verify' may be not needed,and 'MeeGo_1.1.80.6.20101116.1_Core_standard' stand the <repository> like using the obs with web ui, and i586 stand <target architecture>.I think It is easy after using the obs with web ui.

Because of 'build' tools,it maybe appear the problem like 'local build without obs'

===Attention===

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04,I find 'qemu-arm' in /usr/local/bin,and run 'file /usr/local/bin' ,and it show 'dynamically linked',but it worked normal,and I was puzzled to this.

Developing in a MeeGo Environment

2010-12-03T06:42:46Z

Z1x2y3121: /* Exec format error */

== Introduction ==

This guide is a way to build packages for the MeeGo 'day one' release, before more proper developer tools are introduced.

== Setting up your development environment ==

To begin developing for the MeeGo 'day one' release, you will need to follow these steps:

* NOTE: These instructions were tested on a Fedora 12 chroot (X86), your experience may vary with other distributions.
* Have access to 'root' on your development machine.
* [http://wiki.meego.com/Image_Creation#Requirements Satisfy the requirements for MIC2 installation]
* [http://wiki.meego.com/Image_Creation#Installation Download MIC2 from the git repository] (development tree)
* [http://wiki.meego.com/Image_Creation#Installation Install MIC2]
* For ARM, Install QEMU: Grab the qemu package for your system. Fedora one is at [http://build.moblin.org/build/devel:tools:building/Fedora_11/i586/qemu/qemu-arm-static-0.12.3-10.1.i386.rpm this url]
* After this, run 'qemu-binfmt-conf.sh' as root. This will enable your system to run ARM binaries and will have to be repeated at system startup.
* If you have Scratchbox and/or Maemo SDK installed, please follow [http://wiki.maemo.org/Mer/Build/Application_Building#Co-existing_with_Scratchbox these instructions to avoid conflicts]
* Download MeeGo development images for [http://repo.meego.com/MeeGo/devel/n900/images/meego-codedrop-ia32-developer-201003311106.img.bz2 MeeGo X86] and [http://repo.meego.com/MeeGo/devel/n900/images/meego-codedrop-arm-developer-201003311152.img.bz2 MeeGo ARM] and bzip2 -d them (they are 3GB loopback images)
* Or you can create your own development images with [[Media:Devel-ia32.ks|this kickstart file for X86]] or [[Media:Devel-arm.ks|this kickstart file for ARM]] and the instructions at [[Image_Creation_For_Beginners]]

== Introducing the tools ==

=== mic-chroot ===

mic-chroot is a tool that allows you to 'chroot' into an existing MeeGo image in order to develop within it, without contaminating your developer machine's environment. Chroot simply means to 'change the root' to a new location (so instead of your root being / on your dev machine, it will be the new root directory within the image).

This restricts access to your real root and your real file system, and instead, uses the image filesystem as its root and filesystem. No contamination, and no effect on your development machine.

With mic-chroot, you will effectively be able to modify and manipulate the image's filesystem as if you were running a shell within an installed image, without having to install the image. When finished, you can also create a new MeeGo image based on your changes.

=== Developer images ===

The developer images contain the exact same packages as is installed when you try to build a package in the MeeGo OBS without any dependencies, along with some helper packages (vim, nano) to make chroot usage easier. The list of these packages can be seen in the kickstart file mentioned above.

This is because, in the end, it will save you time when you want to upload your application into a builder system because it will make sure that you specify your package build dependencies correctly.

You can in the development image chroot run 'yum install <package names>' and that way install your package build dependencies to the chroot to compile your package.

== Building your package: Step by step ==

Prerequisites:

* It is assumed you have already made either a source rpm (.src.rpm) or a package (.spec and attached files) before these steps. For a guide how to create packaging for MeeGo, see [[Packaging]].
* You have already chosen an architecture to build your package towards in these steps. That is the development image <image-name>, either meego-codedrop-ia32*.img (X86) or meego-codedrop-arm*.img (ARM)

=== Step 1: Chrooting into the development image ===

<pre>
sudo mic-chroot <image-name>
</pre>

With this command, you are now transported into the root filesystem of the image. It is possible to exchange files with your normal file system through the /parentroot directory. You can also conduct yum install, yum remove and any other network related operations.

=== Step 2: Setting up the build directories ===

You only need to do this once, but you may want to clean up the directory and remake it once in a while.

<pre>
mkdir -p ~/rpmbuild
cd ~/rpmbuild
mkdir -p SOURCES SPECS BUILD RPMS SRPMS
</pre>

=== Step 3: Staging source package for build ===

You must change directory to the location of your sources.

<pre>
cd /parentroot/path/to/your/sources
</pre>

If you have a source rpm (.src.rpm), you will need to extract it:

<pre>
rpm2cpio <MyPkg>.src.rpm | cpio -idmv --no-absolute-filenames
</pre>

This will result in a .spec file and maybe some attached files (patches, source tarball, etc). The .spec file is in this guide called package.spec.

When you have a .spec file you need to place it in ~/rpmbuild/SPECS and the remaining files in ~/rpmbuild/SOURCES.

=== Step 4: Installing your build dependencies ===

You can see your build dependencies in the package.spec file, which is the lines starting with BuildRequires. Those packages can then be installed using 'yum install':

<pre>
yum install <package names>
</pre>

=== Step 5: Building your package ===

To build your package, you must then run the following command, where package.spec is the name of your spec file:

<pre>
rpmbuild -ba ~/rpmbuild/SPECS/package.spec
</pre>

=== Step 6: Enjoying your built package ===

Provided the build completed without errors, you can now see the resulting rpms in ~/rpmbuild/RPMS/. You can transfer these back to your filesystem through the /parentroot directory and you can then transfer these to your MeeGo device, virtual machine, etc and install them there.

== Including your packages in a MeeGo image ==
Before reading these sections, we suggest to first read [[Image Creation For Beginners]] and [[Image Creation]]

This will give you the basics of what you need to generate a basic MeeGo image.

Specifically, there are important details about how to modify a .ks file here: [[Image_Creation#Modifying_your_.ks]]

KickStart .ks files are the main configuration file that the Image Creator uses to create images, and the brunt of what is talked about in this section has to do with modifying your .ks file.

=== Recreating a standard MeeGo Image ===
To create a standard MeeGo image, please follow the instructions in [[Image Creation For Beginners]].

=== Adding more MeeGo packages to a MeeGo Image ===
Here is a scenario where you want to add additional MeeGo packages to the standard MeeGo image.

First, obtain a standard MeeGo .ks file [http://repo.meego.com/MeeGo/ from here]

Check the [http://repo.meego.com/MeeGo/ MeeGo repos] and make sure that the packages you're looking doesn't already exist in MeeGo

Now within the .ks file, add the MeeGo package names that you want included in this new image. For more on how add packages in a .ks file, please read this important section here: [[Image_Creation#Modifying_your_.ks]]

Run this modified .ks file through the Image Creator MIC.

<pre>
sudo mic-image-creator -c my-new-ks.ks -f livecd
</pre>

For more options and details on image creation and MIC, go here: [[Image_Creation]]

Your new image will now be a standard MeeGo image including the new packages you've added.

Again, this wiki is of great value to you when manipulating and navigating through .ks files: [[Image_Creation#Modifying_your_.ks]]
It is the key to mastering the art of creating custom-made MeeGo images.

=== Adding your own code & and non-MeeGo packages to a MeeGo Image ===

If you have your own packages on your developer machine that you want to test out by creating a new MeeGo image with them.

First obtain a standard MeeGo .ks file. This is possible through the repository.

To add a new repo to your .ks file, go here for easy and detailed steps: [[Image_Creation#Modifying_your_.ks]]

Once you add the new repo(s) that the Image Creator will pull from, you now have to list the packages you want to pull down from these repos. For instructions on adding packages to your .ks file, go here: [[Image_Creation#Modifying_your_.ks]]

If you have local rpms on your local machine that you would like to include, you need to first create a local repo on your machine. Move your rpms into a directory. Then create a local repo with that directory like so:

<pre>
$ mv *.rpms /home/user/my-local-repo

$ createrepo -d /home/user/my-local-repo
</pre>

This turns /home/user/my-local-repo into a local repository that you can point your .ks file to. For steps on how to add a new repo, go here: [[Image_Creation#Modifying_your_.ks]]

And again, make sure you have listed in your .ks all the packages you would like to include in your new MeeGo Image.

Now, simply run this new .ks file through MIC, the Image Creator.

<pre>
sudo mic-image-creator -c my-new-ks.ks -f livecd
</pre>

For more options and details on image creation and MIC, go here: [[Image_Creation]]

Your new image will now be a standard MeeGo image including the new packages and repos you've added.

Again, this wiki is of great value to you when manipulating and navigating through .ks files: [[Image_Creation#Modifying_your_.ks]]
It is the key to mastering the art of creating custom-made MeeGo images.

== Troubleshooting (ARM) ==

=== Error: chroot: cannot run command X: No such file or directory ===

Most likely cause: You have Scratchbox1 installed and you need to follow instructions given in Prerequisites for ARM.

=== Exec format error ===

Most likely cause: You have not run qemu-binfmt-misc.sh as root.

Maybe qemu-arm is not right set,try :
<pre>
rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm
</pre>
(the package maybe changes,so you can go the web address to get it ,then install it )
see here:[[Local_Build_Without_OBS_Needed]]

=== mmap: permission denied ===

Most likely cause: VDSO

Do this as root:

<pre>
echo 0 > /proc/sys/vm/vdso_enabled
echo 4096 > /proc/sys/vm/mmap_min_addr
</pre>

Local Build Without OBS Needed

2010-12-03T06:29:32Z

Z1x2y3121: /* Exec format error */

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' (the package maybe changes,so you can go the web address to get it ,then install it )to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

=== rpm error ===
This problem on ubuntu 10.04 when using 'build' to create a i686 rpm package.
''Error:rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory''
Please modify the '''/usr/lib/build/configs/default.conf''' in preinstall section add liblua.--[[User:Kismeter|Kismeter]] 15:02, 2 December 2010 (UTC)

SDK/Docs/1.1/Getting started with the MeeGo SDK for Linux

2010-12-03T02:33:17Z

Z1x2y3121: /* On Ubuntu */

[[Category:devguide]]
[[Category:meego-1.1]]
[[Category:tutorial]]
[[Category:application-developer]]
[[Category:linux]]
This page describes how to install and configure the MeeGo 1.1 SDK on your Linux development system.

== Prerequisites ==

* '''Hardware:''' Any reasonably modern hardware, such as 32-bit Intel Atom or Intel Core 2 CPU. '''To use QEMU''' to run MeeGo in a virtual machine your system must have support for ''Virtualization Technology'' (VT). See the [[SDK/Docs/1.1/MeeGo_SDK_Graphics_Acceleration|Graphics Acceleration]] page for details.
* '''Software:''' The MeeGo 1.1 SDK has been validated on 32-bit versions of [https://fedoraproject.org/en/index Fedora 12], [[https://fedoraproject.org/en/index Fedora 13], [http://www.ubuntu.com/ Ubuntu 9.10], and [http://www.ubuntu.com/ Ubuntu 10.04 LTS]. For support status and issues using other host OS's see [http://wiki.meego.com/SDK/Docs/1.1/MeeGo_1.1_SDK_Host_OS_Support this page].
* '''Root privileges:''' To install the SDK you will need to have root privileges. Commands that require root privileges are prefaced with "sudo". For convenience, you may wish to setup "sudo" capabilities to easily switch between root and normal user privileges (see [http://www.gratisoft.us/sudo/sudo.man.html sudoers manpage].)
* '''Commands:''' Terminal commands are prefaced with "$". Do not enter $ when entering the commands in your terminal.

== Configuring distributions package manager ==

=== On Ubuntu or Debian ===


<ol>
<li>Add the following line to <code>/etc/apt/sources.list.d/meego-sdk.list</code>.<br>
Replace ${distribution}/${version} with one of the following: "ubuntu/09.10", "ubuntu/10.04", or "debian/5.0".
<pre>deb http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/ / </pre>
</li>
<li>Add the repository public key:
<pre>$ gpg --keyserver pgpkeys.mit.edu --recv 0BC7BEC479FC1F8A
$ gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -</pre>
</li>
<li>Update the packages database:
<pre>$ sudo apt-get update</pre>
</li>
<li>To check that the MeeGo repository has been correctly added, run the following command. The details of the MADDE package should be printed.
<pre>$ apt-cache policy madde</pre>
</li>
</ol>

=== On Fedora ===

<ol>
<li>Go to the yum repository directory:
<pre>$ cd /etc/yum.repos.d/ </pre>
</li>
<li>Add the MeeGo SDK yum repository. <br/>
Replace ${distribution}/${version} with one of the following: "fedora/12" or "fedora/13".
<pre>$ sudo wget http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo</pre>
</li>
<li>Install the signing key:
<pre>$ sudo rpm --import http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/repodata/repomd.xml.key </pre>
</li>
<li>Update the packages database:
<pre>$ sudo yum update</pre>
</li>
</ol>

=== On MeeGo ===
<ul>
<li>To add the MeeGo SDK repository on a system running MeeGo, run the following command. <br>
Replace ${distribution}/${version} with one of the following values: "meego/1.1" or "meego/trunk".
<pre>$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo</pre>
</li>
</ul>
=== On openSUSE ===
<ul>
<li>To add the MeeGo repository, run the following command. <br>
Replace ${distribution}/${version} with one of the following values: "opensuse/11.2" or "opensuse/11.3".
<pre>$ sudo zypper addrepo -f http://repo.meego.com/MeeGo/sdk/host/repos/${distribution}/${version}/meego-sdk.repo</pre>
</li>
</ul>

== Installing the MeeGo SDK ==
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk</pre>
</li>
</ul>

'''For ARM only:'''
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-armv7l</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-armv7l</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-armv7l</pre>
</li>
</ul>

'''For IA32 only:'''http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes
<ul>
<li>Debian / Ubuntu
<pre>$ sudo apt-get install meego-sdk-ia32</pre>
</li>
<li>Fedora
<pre>$ sudo yum install meego-sdk-ia32</pre>
</li>
<li>OpenSUSE / MeeGo
<pre>$ sudo zypper install meego-sdk-ia32</pre>
</li>
</ul>

== Install MeeGo Target ==
A ''Target'' is used to build programs using the MeeGo toolchain and libraries (sysroot). It is downloaded as a large (~250MB) .bz2 file using the commands below. MADDE (MeeGo Application Develop and Debug Environment ([http://wiki.maemo.org/MADDE background])) is a tool that assists in the download and installation of the Target. "mad-admin" is the MADDE command-line tool. You can install multiple Targets and switch easily between them in Qt Creator (described later).

<ol>
<li>Create a MeeGo target using MADDE <br>
Run the command below. Replace <target> with one of
* '''meego-core-armv7l-1.1''': Build applications for ARM handheld devices (such as N900)
* '''meego-handset-ia32-1.1''': Build applications for x86 handheld devices (such as Aava)
* '''meego-netbook-ia32-1.1''': Build applications for x86 netbooks.
Note that the <code>-f</code> flag instructs MADDE to download the Target tarball (bz2) first.
<pre>$ sudo mad-admin create -f <target> </pre>
If you counter problems, check the [http://wiki.meego.com/MeeGo_SDK_Troubleshooting#General_SDK_Errors Troubleshooting page]
</li>
<li>To check that the target has been installed correctly, run the following. <br>
Replace <target> with one of the values described in the previous step
<pre>$ mad -t <target> pscreate -t qt-simple qthello
$ cd qthello
$ mad -t <target> qmake
$ mad -t <target> make
</pre>
</li>
<li>To check that the qt-simple application is created for the correct target, run:
<pre>$ file build/qthello</pre>
</li>
</ol>

== Install MeeGo Runtime ==
A ''Runtime'' is the MeeGo OS image that is run with QEMU when debugging applications on your host system. It is not required if you develop against real hardware running MeeGo. It is downloaded as a large (~650MB) .bz2 file using MADDE. The Runtime is not needed until you have finished configuring Qt Creator. However, as this step may take some time, it is recommended to start it now so that it can proceed in the background while you continue following the steps on this page.

See [http://wiki.meego.com/SDK/Docs/1.1/Configuring_QEMU_runtimes Downloading a Runtime and Using QEMU]

== Configuring Qt Creator to use the MeeGo toolchain(s) ==

Start Qt Creator by selecting '''Applications''' > '''Programming''' > '''Qt Creator'''.

Configure Qt Creator to use the MeeGo toolchain(s):
# Go to '''Tools''' > '''Options''' > '''Qt4''' > '''Qt Versions'''.
# On the right side of the '''Qt Versions''' view, click on the plus sign button to add a new version.
#: A blank, new version appears in the '''Qt Versions''' view.
# On the '''Version Name''' line, specify a name for the new version.
# On the '''qmake location''' line, specify a qmake location for the new version. The toolchain installs by default to <code>usr/lib/madde/linux-i686/targets/<target>/bin/qmake</code>.
# Click '''Rebuild''', '''Apply''' and '''OK'''.

[[File:Qt Creator adding MeeGo toolchains.png|frame|none|Adding the MeeGo toolchain(s) in Qt Creator]]

=== Using the MeeGo SDK Qt version ===

It is also possible to use Qt Creator without a MeeGo toolchain. This option can be useful if you don't need to cross-compile your software: for example, if you are doing QML development with no use of C++.

The steps are the same as above, but the '''qmake location''' is set to the <code>qmake</code> installed with the meego-sdk-qt libraries. The usual location for this on Linux is:

/opt/meego/meego-sdk-qt/bin/qmake

== Developing with the SDK ==

To start developing with the MeeGo SDK, the [[SDK/Docs/1.1/Creating_Hello_World|hello world tutorial]] is a good starting point.

This tutorial covers how to start a project, package it, and deploy it to a device (either a real device, or a QEMU runtime set up through MADDE).

== Removing components ==

=== On Ubuntu ===

To remove installed components, run:
$ sudo apt-get remove --purge meego-sdk-qtcreator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu meego-sdk-qt

To remove dependencies related to installed components, run:
$ sudo apt-get autoremove

To remove MADDE directory (it is not automatically removed when "madde" package is uninstalled):
$ sudo rm -rf /usr/lib/madde

To remove the packages from your local repository (<code>/var/cache/apt/archives/</code>), run:
$ sudo apt-get clean

=== On Fedora ===

To remove installed components, run:
$ sudo yum remove meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

=== On openSUSE ===

To remove installed components, run:
$ sudo zypper remove -u meego-sdk-qt-creator madde qt-tools arm-2009q1 qemu-arm qemu-gl meego-sdk-i586-toolchain meego-qemu

To remove MADDE directory:
$ sudo rm -rf /usr/lib/madde

== Another language version of this page ==

* [[SDK/Docs/1.1/Memulai_dengan_SDK_MeeGo_untuk_Linux|Memulai dengan SDK Meego untuk Linux - Bahasa Indonesia]]

User:Hlzxy/Deatail Local Build Without OBS

2010-12-01T06:47:58Z

Z1x2y3121: /* Arch */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

===Attention===

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf,
'/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04,I find 'qemu-arm' in /usr/local/bin,and run 'file /usr/local/bin' ,and it show 'dynamically linked',but it worked normal,and I was puzzled to this.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-01T06:02:32Z

Z1x2y3121: /* Installing for fedora13 */

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
</pre>

3.install build:

<pre>
yum install build
</pre>

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

===Attention===

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf
, '/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04,I find 'qemu-arm' in /usr/local/bin,and run 'file /usr/local/bin' ,and it show 'dynamically linked',but it worked normal,and I was puzzled to this.

User:Hlzxy/Deatail Local Build Without OBS

2010-12-01T05:50:38Z

Z1x2y3121: Created page with "== Building your package using build == A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions. =…"

== Building your package using build ==

A task of mine is to build rpm packages without OBS,and it cost me a week to do it, and I record the process of it and some questions.

=== Step1: Installing build===

MeeGo use 'build' to work for this,We can get build package from http://repo.meego.com/MeeGo/tools/repos/ according to kind of your host,and another way to get build source package from http://www.gitorious.org/opensuse/build.

==== Installing for ubuntu10.04 ====

1.add the below line to /etc/apt/sources.list

<pre>
deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ /
</pre>

2.'apt-get update'

You should see the following error: W: GPG error: http://repo.meego.com Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0BC7BEC479FC1F8A

To add the repository public key use the following command:

gpg --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg --export --armor 0BC7BEC479FC1F8A | sudo apt-key add -

Now redo 'apt-get update' (I met the problem up,and it seems I failed to add the key .though it could work normally,it maybe is the reason of the questions I want to know at the end of this page )

3.apt-get install build

==== Installing for fedora13 ====

Way 1:

1.run the lines of commands below as root"

<pre>
cat <<REPO > /etc/yum.repos.d/meego-tools.repo
[meego-tools]
name=MeeGo Tools for Fedora
baseurl=http://repo.meego.com/MeeGo/tools/repos/fedora/\$releasever
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-meego
REPO
</pre>

2.add gpg key

<pre>
gpg2 --keyserver subkeys.pgp.net --recv 0BC7BEC479FC1F8A
gpg2 --export --armor 0BC7BEC479FC1F8A > /etc/pki/rpm-gpg/RPM-GPG-KEY-meego
<\pre>

3.install build:

<pre>
yum install build
<\pre>

(It seems I also failed to get the key ,but everything seem to be work well.I am very curious to it )

Way 2:

Load the package build-2010.08.04-1.5.src.rpm from http://repo.meego.com/MeeGo/tools/repos/fedora/13/src/ ,and run comand:

<pre>
rpm -ivh build-2010.08.04-1.5.src.rpm
</pre>

after that you can find them in /root/rpmbuild/ if you run as root.and you can use commands:'rpmbuild -ba <spec file>' to build a rpm,and install it by use 'rpm -ivh <rpm package>'

=== Step2: Building rpm ===

In fact,we build the rpm package with spec file or src.rpm package.

If you already installed 'build' tools,you could find /usr/lib/build/configs/meego-1.0.conf.This file seems like for meego1.0,and in fact when we use it build a rpm of version 1.0 ,it will work directly

Before building ,you should have a spec file or src.rpm package,and also you must run commands below as root because of loading the dependency packages automatic in the process:

<pre>
wget http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/repodata/repomd.xml.key
rpm --import repomd.xml.key
</pre>

(I think the same importing once will be ok,and running the same importing will be failed)

then you can start building:

<pre>
build --repository http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ --arch armv7l cpio-2.11-1.2.src.rpm
</pre>

Complete this ,you will find the rpm package in /var/tmp/build-root/home/abuild/rpmbuild/RPMS/.
because 'build' will create a build system and initialize it every time by default, so you need move the result if you want to keep it.

===Attention===

====Version====

If you want to build the rpm of version 1.1,you should change 'lua' to 'liblua' in Preinstall of meego-1.0.conf. (for me ,it worked on fedora13,and failed on ubuntu10.04,if someone know that,please tell me)

====Arch====

If you want to build a armv7l rpm package,please sure the 'armv7l' or 'armv7el' in meego-1.0.conf
, '/usr/lib/build/build' and '/usr/lib/build/Build.pm'.
If get the error: 'chroot: failed to run command `rpm': exec format error' or 'chroot: failed to run command `rpm': No such file or directory',you should be sure your qemu-arm set right:

On fedora13,you can run 'file /usr/bin/qemu-arm', and if it show 'dynamically linked', you should reset it.you can run 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm',and sure it running well(uninstall all blocking packages),and run command again,and you will see the result of 'statically linked'.

On unbuntu10.04,I find 'qemu-arm' in /usr/local/bin,and run 'file /usr/local/bin' ,and it show 'dynamically linked',but it worked normal,and I was puzzled to this.

Developing in a MeeGo Environment

2010-11-30T11:07:16Z

Z1x2y3121: /* Exec format error */

== Introduction ==

This guide is a way to build packages for the MeeGo 'day one' release, before more proper developer tools are introduced.

== Setting up your development environment ==

To begin developing for the MeeGo 'day one' release, you will need to follow these steps:

* NOTE: These instructions were tested on a Fedora 12 chroot (X86), your experience may vary with other distributions.
* Have access to 'root' on your development machine.
* [http://wiki.meego.com/Image_Creation#Requirements Satisfy the requirements for MIC2 installation]
* [http://wiki.meego.com/Image_Creation#Installation Download MIC2 from the git repository] (development tree)
* [http://wiki.meego.com/Image_Creation#Installation Install MIC2]
* For ARM, Install QEMU: Grab the qemu package for your system. Fedora one is at [http://build.moblin.org/build/devel:tools:building/Fedora_11/i586/qemu/qemu-arm-static-0.12.3-10.1.i386.rpm this url]
* After this, run 'qemu-binfmt-conf.sh' as root. This will enable your system to run ARM binaries and will have to be repeated at system startup.
* If you have Scratchbox and/or Maemo SDK installed, please follow [http://wiki.maemo.org/Mer/Build/Application_Building#Co-existing_with_Scratchbox these instructions to avoid conflicts]
* Download MeeGo development images for [http://repo.meego.com/MeeGo/devel/n900/images/meego-codedrop-ia32-developer-201003311106.img.bz2 MeeGo X86] and [http://repo.meego.com/MeeGo/devel/n900/images/meego-codedrop-arm-developer-201003311152.img.bz2 MeeGo ARM] and bzip2 -d them (they are 3GB loopback images)
* Or you can create your own development images with [[Media:Devel-ia32.ks|this kickstart file for X86]] or [[Media:Devel-arm.ks|this kickstart file for ARM]] and the instructions at [[Image_Creation_For_Beginners]]

== Introducing the tools ==

=== mic-chroot ===

mic-chroot is a tool that allows you to 'chroot' into an existing MeeGo image in order to develop within it, without contaminating your developer machine's environment. Chroot simply means to 'change the root' to a new location (so instead of your root being / on your dev machine, it will be the new root directory within the image).

This restricts access to your real root and your real file system, and instead, uses the image filesystem as its root and filesystem. No contamination, and no effect on your development machine.

With mic-chroot, you will effectively be able to modify and manipulate the image's filesystem as if you were running a shell within an installed image, without having to install the image. When finished, you can also create a new MeeGo image based on your changes.

=== Developer images ===

The developer images contain the exact same packages as is installed when you try to build a package in the MeeGo OBS without any dependencies, along with some helper packages (vim, nano) to make chroot usage easier. The list of these packages can be seen in the kickstart file mentioned above.

This is because, in the end, it will save you time when you want to upload your application into a builder system because it will make sure that you specify your package build dependencies correctly.

You can in the development image chroot run 'yum install <package names>' and that way install your package build dependencies to the chroot to compile your package.

== Building your package: Step by step ==

Prerequisites:

* It is assumed you have already made either a source rpm (.src.rpm) or a package (.spec and attached files) before these steps. For a guide how to create packaging for MeeGo, see [[Packaging]].
* You have already chosen an architecture to build your package towards in these steps. That is the development image <image-name>, either meego-codedrop-ia32*.img (X86) or meego-codedrop-arm*.img (ARM)

=== Step 1: Chrooting into the development image ===

<pre>
sudo mic-chroot <image-name>
</pre>

With this command, you are now transported into the root filesystem of the image. It is possible to exchange files with your normal file system through the /parentroot directory. You can also conduct yum install, yum remove and any other network related operations.

=== Step 2: Setting up the build directories ===

You only need to do this once, but you may want to clean up the directory and remake it once in a while.

<pre>
mkdir -p ~/rpmbuild
cd ~/rpmbuild
mkdir -p SOURCES SPECS BUILD RPMS SRPMS
</pre>

=== Step 3: Staging source package for build ===

You must change directory to the location of your sources.

<pre>
cd /parentroot/path/to/your/sources
</pre>

If you have a source rpm (.src.rpm), you will need to extract it:

<pre>
rpm2cpio <MyPkg>.src.rpm | cpio -idmv --no-absolute-filenames
</pre>

This will result in a .spec file and maybe some attached files (patches, source tarball, etc). The .spec file is in this guide called package.spec.

When you have a .spec file you need to place it in ~/rpmbuild/SPECS and the remaining files in ~/rpmbuild/SOURCES.

=== Step 4: Installing your build dependencies ===

You can see your build dependencies in the package.spec file, which is the lines starting with BuildRequires. Those packages can then be installed using 'yum install':

<pre>
yum install <package names>
</pre>

=== Step 5: Building your package ===

To build your package, you must then run the following command, where package.spec is the name of your spec file:

<pre>
rpmbuild -ba ~/rpmbuild/SPECS/package.spec
</pre>

=== Step 6: Enjoying your built package ===

Provided the build completed without errors, you can now see the resulting rpms in ~/rpmbuild/RPMS/. You can transfer these back to your filesystem through the /parentroot directory and you can then transfer these to your MeeGo device, virtual machine, etc and install them there.

== Including your packages in a MeeGo image ==
Before reading these sections, we suggest to first read [[Image Creation For Beginners]] and [[Image Creation]]

This will give you the basics of what you need to generate a basic MeeGo image.

Specifically, there are important details about how to modify a .ks file here: [[Image_Creation#Modifying_your_.ks]]

KickStart .ks files are the main configuration file that the Image Creator uses to create images, and the brunt of what is talked about in this section has to do with modifying your .ks file.

=== Recreating a standard MeeGo Image ===
To create a standard MeeGo image, please follow the instructions in [[Image Creation For Beginners]].

=== Adding more MeeGo packages to a MeeGo Image ===
Here is a scenario where you want to add additional MeeGo packages to the standard MeeGo image.

First, obtain a standard MeeGo .ks file [http://repo.meego.com/MeeGo/ from here]

Check the [http://repo.meego.com/MeeGo/ MeeGo repos] and make sure that the packages you're looking doesn't already exist in MeeGo

Now within the .ks file, add the MeeGo package names that you want included in this new image. For more on how add packages in a .ks file, please read this important section here: [[Image_Creation#Modifying_your_.ks]]

Run this modified .ks file through the Image Creator MIC.

<pre>
sudo mic-image-creator -c my-new-ks.ks -f livecd
</pre>

For more options and details on image creation and MIC, go here: [[Image_Creation]]

Your new image will now be a standard MeeGo image including the new packages you've added.

Again, this wiki is of great value to you when manipulating and navigating through .ks files: [[Image_Creation#Modifying_your_.ks]]
It is the key to mastering the art of creating custom-made MeeGo images.

=== Adding your own code & and non-MeeGo packages to a MeeGo Image ===

If you have your own packages on your developer machine that you want to test out by creating a new MeeGo image with them.

First obtain a standard MeeGo .ks file. This is possible through the repository.

To add a new repo to your .ks file, go here for easy and detailed steps: [[Image_Creation#Modifying_your_.ks]]

Once you add the new repo(s) that the Image Creator will pull from, you now have to list the packages you want to pull down from these repos. For instructions on adding packages to your .ks file, go here: [[Image_Creation#Modifying_your_.ks]]

If you have local rpms on your local machine that you would like to include, you need to first create a local repo on your machine. Move your rpms into a directory. Then create a local repo with that directory like so:

<pre>
$ mv *.rpms /home/user/my-local-repo

$ createrepo -d /home/user/my-local-repo
</pre>

This turns /home/user/my-local-repo into a local repository that you can point your .ks file to. For steps on how to add a new repo, go here: [[Image_Creation#Modifying_your_.ks]]

And again, make sure you have listed in your .ks all the packages you would like to include in your new MeeGo Image.

Now, simply run this new .ks file through MIC, the Image Creator.

<pre>
sudo mic-image-creator -c my-new-ks.ks -f livecd
</pre>

For more options and details on image creation and MIC, go here: [[Image_Creation]]

Your new image will now be a standard MeeGo image including the new packages and repos you've added.

Again, this wiki is of great value to you when manipulating and navigating through .ks files: [[Image_Creation#Modifying_your_.ks]]
It is the key to mastering the art of creating custom-made MeeGo images.

== Troubleshooting (ARM) ==

=== Error: chroot: cannot run command X: No such file or directory ===

Most likely cause: You have Scratchbox1 installed and you need to follow instructions given in Prerequisites for ARM.

=== Exec format error ===

Most likely cause: You have not run qemu-binfmt-misc.sh as root.

Maybe qemu-arm is not right set,try :
<pre>
rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm
</pre>
see here:[[Local_Build_Without_OBS_Needed]]

=== mmap: permission denied ===

Most likely cause: VDSO

Do this as root:

<pre>
echo 0 > /proc/sys/vm/vdso_enabled
echo 4096 > /proc/sys/vm/mmap_min_addr
</pre>

Developing in a MeeGo Environment

2010-11-29T01:49:17Z

Z1x2y3121:

== Introduction ==

This guide is a way to build packages for the MeeGo 'day one' release, before more proper developer tools are introduced.

== Setting up your development environment ==

To begin developing for the MeeGo 'day one' release, you will need to follow these steps:

* NOTE: These instructions were tested on a Fedora 12 chroot (X86), your experience may vary with other distributions.
* Have access to 'root' on your development machine.
* [http://wiki.meego.com/Image_Creation#Requirements Satisfy the requirements for MIC2 installation]
* [http://wiki.meego.com/Image_Creation#Installation Download MIC2 from the git repository] (development tree)
* [http://wiki.meego.com/Image_Creation#Installation Install MIC2]
* For ARM, Install QEMU: Grab the qemu package for your system. Fedora one is at [http://build.moblin.org/build/devel:tools:building/Fedora_11/i586/qemu/qemu-arm-static-0.12.3-10.1.i386.rpm this url]
* After this, run 'qemu-binfmt-conf.sh' as root. This will enable your system to run ARM binaries and will have to be repeated at system startup.
* If you have Scratchbox and/or Maemo SDK installed, please follow [http://wiki.maemo.org/Mer/Build/Application_Building#Co-existing_with_Scratchbox these instructions to avoid conflicts]
* Download MeeGo development images for [http://repo.meego.com/MeeGo/devel/n900/images/meego-codedrop-ia32-developer-201003311106.img.bz2 MeeGo X86] and [http://repo.meego.com/MeeGo/devel/n900/images/meego-codedrop-arm-developer-201003311152.img.bz2 MeeGo ARM] and bzip2 -d them (they are 3GB loopback images)
* Or you can create your own development images with [[Media:Devel-ia32.ks|this kickstart file for X86]] or [[Media:Devel-arm.ks|this kickstart file for ARM]] and the instructions at [[Image_Creation_For_Beginners]]

== Introducing the tools ==

=== mic-chroot ===

mic-chroot is a tool that allows you to 'chroot' into an existing MeeGo image in order to develop within it, without contaminating your developer machine's environment. Chroot simply means to 'change the root' to a new location (so instead of your root being / on your dev machine, it will be the new root directory within the image).

This restricts access to your real root and your real file system, and instead, uses the image filesystem as its root and filesystem. No contamination, and no effect on your development machine.

With mic-chroot, you will effectively be able to modify and manipulate the image's filesystem as if you were running a shell within an installed image, without having to install the image. When finished, you can also create a new MeeGo image based on your changes.

=== Developer images ===

The developer images contain the exact same packages as is installed when you try to build a package in the MeeGo OBS without any dependencies, along with some helper packages (vim, nano) to make chroot usage easier. The list of these packages can be seen in the kickstart file mentioned above.

This is because, in the end, it will save you time when you want to upload your application into a builder system because it will make sure that you specify your package build dependencies correctly.

You can in the development image chroot run 'yum install <package names>' and that way install your package build dependencies to the chroot to compile your package.

== Building your package: Step by step ==

Prerequisites:

* It is assumed you have already made either a source rpm (.src.rpm) or a package (.spec and attached files) before these steps. For a guide how to create packaging for MeeGo, see [[Packaging]].
* You have already chosen an architecture to build your package towards in these steps. That is the development image <image-name>, either meego-codedrop-ia32*.img (X86) or meego-codedrop-arm*.img (ARM)

=== Step 1: Chrooting into the development image ===

<pre>
sudo mic-chroot <image-name>
</pre>

With this command, you are now transported into the root filesystem of the image. It is possible to exchange files with your normal file system through the /parentroot directory. You can also conduct yum install, yum remove and any other network related operations.

=== Step 2: Setting up the build directories ===

You only need to do this once, but you may want to clean up the directory and remake it once in a while.

<pre>
mkdir -p ~/rpmbuild
cd ~/rpmbuild
mkdir -p SOURCES SPECS BUILD RPMS SRPMS
</pre>

=== Step 3: Staging source package for build ===

You must change directory to the location of your sources.

<pre>
cd /parentroot/path/to/your/sources
</pre>

If you have a source rpm (.src.rpm), you will need to extract it:

<pre>
rpm2cpio <MyPkg>.src.rpm | cpio -idmv --no-absolute-filenames
</pre>

This will result in a .spec file and maybe some attached files (patches, source tarball, etc). The .spec file is in this guide called package.spec.

When you have a .spec file you need to place it in ~/rpmbuild/SPECS and the remaining files in ~/rpmbuild/SOURCES.

=== Step 4: Installing your build dependencies ===

You can see your build dependencies in the package.spec file, which is the lines starting with BuildRequires. Those packages can then be installed using 'yum install':

<pre>
yum install <package names>
</pre>

=== Step 5: Building your package ===

To build your package, you must then run the following command, where package.spec is the name of your spec file:

<pre>
rpmbuild -ba ~/rpmbuild/SPECS/package.spec
</pre>

=== Step 6: Enjoying your built package ===

Provided the build completed without errors, you can now see the resulting rpms in ~/rpmbuild/RPMS/. You can transfer these back to your filesystem through the /parentroot directory and you can then transfer these to your MeeGo device, virtual machine, etc and install them there.

== Including your packages in a MeeGo image ==
Before reading these sections, we suggest to first read [[Image Creation For Beginners]] and [[Image Creation]]

This will give you the basics of what you need to generate a basic MeeGo image.

Specifically, there are important details about how to modify a .ks file here: [[Image_Creation#Modifying_your_.ks]]

KickStart .ks files are the main configuration file that the Image Creator uses to create images, and the brunt of what is talked about in this section has to do with modifying your .ks file.

=== Recreating a standard MeeGo Image ===
To create a standard MeeGo image, please follow the instructions in [[Image Creation For Beginners]].

=== Adding more MeeGo packages to a MeeGo Image ===
Here is a scenario where you want to add additional MeeGo packages to the standard MeeGo image.

First, obtain a standard MeeGo .ks file [http://repo.meego.com/MeeGo/ from here]

Check the [http://repo.meego.com/MeeGo/ MeeGo repos] and make sure that the packages you're looking doesn't already exist in MeeGo

Now within the .ks file, add the MeeGo package names that you want included in this new image. For more on how add packages in a .ks file, please read this important section here: [[Image_Creation#Modifying_your_.ks]]

Run this modified .ks file through the Image Creator MIC.

<pre>
sudo mic-image-creator -c my-new-ks.ks -f livecd
</pre>

For more options and details on image creation and MIC, go here: [[Image_Creation]]

Your new image will now be a standard MeeGo image including the new packages you've added.

Again, this wiki is of great value to you when manipulating and navigating through .ks files: [[Image_Creation#Modifying_your_.ks]]
It is the key to mastering the art of creating custom-made MeeGo images.

=== Adding your own code & and non-MeeGo packages to a MeeGo Image ===

If you have your own packages on your developer machine that you want to test out by creating a new MeeGo image with them.

First obtain a standard MeeGo .ks file. This is possible through the repository.

To add a new repo to your .ks file, go here for easy and detailed steps: [[Image_Creation#Modifying_your_.ks]]

Once you add the new repo(s) that the Image Creator will pull from, you now have to list the packages you want to pull down from these repos. For instructions on adding packages to your .ks file, go here: [[Image_Creation#Modifying_your_.ks]]

If you have local rpms on your local machine that you would like to include, you need to first create a local repo on your machine. Move your rpms into a directory. Then create a local repo with that directory like so:

<pre>
$ mv *.rpms /home/user/my-local-repo

$ createrepo -d /home/user/my-local-repo
</pre>

This turns /home/user/my-local-repo into a local repository that you can point your .ks file to. For steps on how to add a new repo, go here: [[Image_Creation#Modifying_your_.ks]]

And again, make sure you have listed in your .ks all the packages you would like to include in your new MeeGo Image.

Now, simply run this new .ks file through MIC, the Image Creator.

<pre>
sudo mic-image-creator -c my-new-ks.ks -f livecd
</pre>

For more options and details on image creation and MIC, go here: [[Image_Creation]]

Your new image will now be a standard MeeGo image including the new packages and repos you've added.

Again, this wiki is of great value to you when manipulating and navigating through .ks files: [[Image_Creation#Modifying_your_.ks]]
It is the key to mastering the art of creating custom-made MeeGo images.

== Troubleshooting (ARM) ==

=== Error: chroot: cannot run command X: No such file or directory ===

Most likely cause: You have Scratchbox1 installed and you need to follow instructions given in Prerequisites for ARM.

=== Exec format error ===

Most likely cause: You have not run qemu-binfmt-misc.sh as root.

Maybe qemu-arm is not right set,try :
<pre>
rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm
</pre>
=== mmap: permission denied ===

Most likely cause: VDSO

Do this as root:

<pre>
echo 0 > /proc/sys/vm/vdso_enabled
echo 4096 > /proc/sys/vm/mmap_min_addr
</pre>

Local Build Without OBS Needed

2010-11-29T01:39:16Z

Z1x2y3121: /* Exec format error */

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set.
Try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.

Local Build Without OBS Needed

2010-11-29T01:38:44Z

Z1x2y3121: /* Exec format error */

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem on fedora13 when using 'build' to create a armv7l rpm package.
one of reasons: maybe 'qemu-arm' is not right set
try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.
the other commands maybe useful:

Local Build Without OBS Needed

2010-11-29T01:37:34Z

Z1x2y3121:

== Building your package using build ==

A more convenient package build way is to use 'build' which is a project from OpenSUSE, MeeGo build infrastructure used it.

You can get build binary package from http://repo.meego.com/MeeGo/tools/repos/ per your Linux distribution, if your Linux distribution isn't there, you can get build source package from http://www.gitorious.org/opensuse/build to build it yourself manually.

After you install it ( I suppose you know how to install a package on your Linux), you can run “build –help” to get help info.

You must run build as root. If your network needs proxy, please export proxy environment variables, for example:

<pre>
export http_proxy=http://proxy.yourcompany.com:8080/
export no_proxy=localhost,127.0.0.0/8,.yourcompany.com, 172.16.0.0/16
</pre>

If you used to run “sudo build …” and your network needs proxy, please ensure sudo to inherit proxy environment variables, you can do this by adding the below line to /etc/sudoers

<pre>
Defaults env_keep += "http_proxy no_proxy HTTP_PROXY NO_PROXY"
</pre>

build also will check rpm package signature, so you must import public key of repository you're using, for example:

For http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/

You can get its public key for http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key

<pre>
$ wget http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/repodata/repomd.xml.key
$ sudo rpm --import repomd.xml.key
</pre>

This command will build a cpio binary package for MeeGo.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio-2.11-2.6.src.rpm
</pre>

Optionally, you also can use spec file to build it, for this case, build will find your source tar ball and patches under current work dir.

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ --arch i686 cpio.spec
</pre>

build will base your repo URL to cache your repo, so please use the same URL string for the same repo every time (URL with / at the end of it and the same URL without / at the end of it will result in different cache dirs), you can use multiple --repository options to specify multiple repos, for example:

<pre>
build --repository http://repo.meego.com/MeeGo/builds/trunk/preview/core/repos/ia32/packages/ \
--repository http://repo.meego.com/MeeGo/builds/trunk/preview/netbook/repos/ia32/packages/ \
--arch i686 meego-panel-applications-0.2.3-1.10.src.rpm
</pre>

The default cache dir is /var/cache/build, you can use option –cachedir to set to other dir.

The default BUILDROOT dir is /var/tmp/build-root, you can use --root option to specify one more dir, once build is done, you can get your binary package in BUILDROOT, for example:

<pre>
...
Wrote: /home/abuild/rpmbuild/SRPMS/cpio-2.11-2.meego.src.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-2.11-2.meego.i586.rpm
Wrote: /home/abuild/rpmbuild/RPMS/i586/cpio-debuginfo-2.11-2.meego.i586.rpm
...
</pre>

Your cpio binary package is /var/tmp/build-root/home/abuild/rpmbuild/RPMS/i586/2.11-2.meego.i586.rpm
== Troubleshooting (ARM) ==

=== Exec format error ===
Meet this problem on fedora13 when using 'build' to create a armv7l rpm package
one of reasons: maybe 'qemu-arm' is not right set
try command:'file /usr/bin/qemu-arm' ,and if its output show 'dynamically linked',and the problem maye is here,and it should be 'statically linked'.you can use commands 'rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm' to reinstall this part, and maybe you will meet some problem because of its dependencies ,and you can uninstall all of them first.
the other commands maybe useful:

Talk:Local Build Without OBS Needed

2010-11-26T10:48:09Z

Z1x2y3121: Help!

Is anybody met this error:
chroot: failed to run command `rpm': Exec format error

and how I should do to solve it?

Talk:Local Build Without OBS Needed

2010-11-25T08:47:38Z

Z1x2y3121:

if anybody met this error when build package use src.rpm:
rpm: error while loading shared libraries: liblua-5.1.so: cannot open shared object file: No such file or directory

and who know how to solve it

and why I can not use this command : rpm --import remod.xml.key more times ,it always result to "fail"