Meego Wiki
Views

Build Infrastructure/Packagers Developers

From MeeGo wiki
< Build Infrastructure(Difference between revisions)
Jump to: navigation, search
(How to get started)
(make clear that for bugzilla you need a meego account)
 
(28 intermediate revisions not shown)
Line 1: Line 1:
These pages are in preparation - contributions welcome.
These pages are in preparation - contributions welcome.
 +
 +
Note: See [[OBS|the OBS wiki page]] for explanation of the different OBS services MeeGo offers.
This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com.  
This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com.  
Note: You need an account to access build.meego.com.   
Note: You need an account to access build.meego.com.   
-
If you have no account, you can still learn how the openSUSE Build Service works at the upstream projects own instance [http://build.opensuse.org http://build.opensuse.org] .
+
If you have no account, you can still learn how the OBS works at the upstream project's own instance [http://build.opensuse.org http://build.opensuse.org] .
-
In this track, you'll learn how to use the webinterface, the commandline client and create your first package.
+
In this track, you'll learn how to use the web interface, the commandline client and create your first package.
The packaging guidelines and more advanced topics are also covered.
The packaging guidelines and more advanced topics are also covered.
== How to get started ==
== How to get started ==
-
* You will need a meego.com account
 
-
* You will need to contact lbt on the [irc://irc.freenode.org/meego #meego] channel (irc.freenode.org) so your account can gain access to the obs system
 
-
* go to https://build.pub.meego.com
 
-
== How to use the webinterface ==
+
You need an account on build.meego.com. To request an account:
-
A series of pages will make you familiar with the basic use of the webinterface. Its divided into several subpages:
+
# Go to [http://bugs.meego.com MeeGo bugzilla] (which in turn first requires having a [https://meego.com/user/register MeeGo account]).
 +
# Click New in the upper navigational bar to begin filing a bug.
 +
# On the next page, click MeeGo Community Infrastructure.
 +
# On the following page, click Build Service and file your bug.
 +
 
 +
== How to use the web interface ==
 +
A series of pages will make you familiar with webinterface basics. It's divided into several subpages:
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Part 1 - Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Part 1 - Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Part 2 - Creating a link and adding a repository]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Part 2 - Creating a link and adding a repository]]
-
* Part 3 - Your first own package
+
* [[Developing_in_a_MeeGo_Environment#Building_your_package:_Step_by_step|Part 3 - Your first own package]]
-
* Part 4 - Subprojects and the project monitor page
+
-
* Part 5 - Flags and Attributes
+
== How to use the commandline client ==
== How to use the commandline client ==
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
-
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout of projects, commit]]
+
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout and branch]]
-
* Part 3 - branch, edit, localbuild, commit, submitreq
+
* Part 3 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_3|commit & request]]
-
* part 4 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]
+
* Part 4 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]
== MeeGo Packaging guidelines and Howto ==
== MeeGo Packaging guidelines and Howto ==
* [[Packaging|Packaging]]
* [[Packaging|Packaging]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[Packaging/Guidelines|Packaging Guidelines]]
-
* [[Packaging/Tutorial|Packaging Tutorial]]
+
* [[SDK/Docs/1.0/Packaging/Tutorial|Packaging Tutorial]]
== [[Build_Infrastructure/QA|QA Processes around the OBS]] ==
== [[Build_Infrastructure/QA|QA Processes around the OBS]] ==
-
The initial focus here is on community applications
+
See the [[Quality]] page.
-
* to allow freedom for developers to develop;
+
-
* to provide a build service and SDK
+
-
* to provide excellent quality assured applications for our "app store";
+
-
See the [[Quality]] page too.
+
-
== Multi-Architecture and Multi-Distribution packaging ==
+
-
* architecture macros
+
-
* example multi-arch specfile
+
-
* distribution macros
+
-
* example multi-distribution specfile
+
-
== Tips & Tricks ==
+
== Verifying Your Package Changes Locally and Online ==
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]
== Troubleshooting ==
== Troubleshooting ==
-
* repository stacking
+
* '''I'm getting "error: Package already exists: %package debuginfo"''' &mdash; Disable the debuginfo flag for the repo/arch that gives you this problem. You will probably still get a debuginfo package. This appears to happen when OBS creates debuginfo packages by default, and so this flag causes a sort of doubling-up of the debuginfo package.
-
The repository dependency resolution is confused when you stack same repositories.
+
-
 
+
-
In the following example, Targets:Debian:5.0 repository is used twice:
+
-
Targets:Debian:5.0 <-> devel:tools:sdk:Debian:5.0:backports <-> Targets:Debian:5.0 <-> Debian_5.0
+
-
 
+
-
Make sure to avoid repository stacking and use the appropriate repositories in your project configuration: devel:tools:sdk:Debian:5.0:backports <-> Targets:Debian:5.0 <-> Debian_5.0
+
== IRC / mailinglists / contact ==
== IRC / mailinglists / contact ==
-
If you need help, you can join #meego or #meego-dev on irc.freenode.net . See also [[Meego_irc|this page]] about all MeeGo IRC channels.
+
If you need help, you can join #meego on irc.freenode.net . See also [[Community communication|this page]] about all MeeGo IRC channels.
You can join [http://lists.meego.com/listinfo/meego-dev MeeGo-dev] and [http://lists.meego.com/listinfo/meego-packaging MeeGo-packaging] mailing lists [http://lists.meego.com/mailman/listinfo over here].
You can join [http://lists.meego.com/listinfo/meego-dev MeeGo-dev] and [http://lists.meego.com/listinfo/meego-packaging MeeGo-packaging] mailing lists [http://lists.meego.com/mailman/listinfo over here].
[[Category:Build Infrastructure]]
[[Category:Build Infrastructure]]

Latest revision as of 08:29, 14 September 2011

These pages are in preparation - contributions welcome.

Note: See the OBS wiki page for explanation of the different OBS services MeeGo offers.

This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com. Note: You need an account to access build.meego.com. If you have no account, you can still learn how the OBS works at the upstream project's own instance http://build.opensuse.org .

In this track, you'll learn how to use the web interface, the commandline client and create your first package. The packaging guidelines and more advanced topics are also covered.

Contents

How to get started

You need an account on build.meego.com. To request an account:

  1. Go to MeeGo bugzilla (which in turn first requires having a MeeGo account).
  2. Click New in the upper navigational bar to begin filing a bug.
  3. On the next page, click MeeGo Community Infrastructure.
  4. On the following page, click Build Service and file your bug.

How to use the web interface

A series of pages will make you familiar with webinterface basics. It's divided into several subpages:

How to use the commandline client

MeeGo Packaging guidelines and Howto

QA Processes around the OBS

See the Quality page.

Verifying Your Package Changes Locally and Online

Troubleshooting

  • I'm getting "error: Package already exists: %package debuginfo" — Disable the debuginfo flag for the repo/arch that gives you this problem. You will probably still get a debuginfo package. This appears to happen when OBS creates debuginfo packages by default, and so this flag causes a sort of doubling-up of the debuginfo package.

IRC / mailinglists / contact

If you need help, you can join #meego on irc.freenode.net . See also this page about all MeeGo IRC channels.

You can join MeeGo-dev and MeeGo-packaging mailing lists over here.

Personal tools