Editing Mer/Build/Common Problems

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

=Common Problems encountered building for Mer on OBS=

==Diagnosing a problem==
First of all look at the status information

* succeeded
Package has built successfully and can be used to build further packages.

* failed
The package does not build successfully. No packages have been created. Packages that depend on this package will be built using any previously created packages, if they exist. [[Mer/Documentation/Build/Common Problems/Failed Diagnosis|Failed Diagnosis]]

* expansion error
The build can not begin, because required packages are either missing or not explicitly defined.  [[Mer/Documentation/Build/Common Problems/Expansion Error Diagnosis|Expansion Error Diagnosis]]

* blocked
This package waits for other packages to be built. These can be in the same or other projects. Typically you just need to wait.

* scheduled
A package has been marked for building, but the build has not started yet. Again, just wait.

* building
The package is currently being built. Smile and wait.

* dispatching
A package is being copied to a build host. This is an intermediate state before building.

* finished
The package has been built, but has not yet been picked up by the server. This is an intermediate state prior to 'succeeded' or 'failed'.

* disabled
The package has been disabled from building in project or package metadata.

* excluded
The package build has been disabled in package build description (for example in the .spec file) or does not provide a matching build description for the target.

* broken
The sources either contain no build description (eg specfile) or a source link does not work.   [[Mer/Documentation/Build/Common Problems/Broken Diagnosis|Broken Diagnosis]]

* unknown
The scheduler has not yet evaluated this package. Should be a short intermediate state for new packages.

==Non-Problems==
Some things are known issues that (AFAWK) don't affect the build:
* qemu broken pipes

==Specifics==

dh_clean
 dpkg-source -b BUILD
 dpkg-source: warning: source directory 'BUILD' is not <sourcepackage>-<upstreamversion> 'bomberman-1.0 '
 dpkg-source: info: using source format `1.0'
 dpkg-source: info: building bomberman in bomberman_1.0.tar.gz
 dpkg-source: info: building bomberman in bomberman_1.0.dsc
 debian/rules build
 dh_testdir
 # Add here commands to configure the package.
 CFLAGS="-Wall -g -O2" ./configure --prefix=/usr --disable-static
 configure: error: cannot find install-sh or install.sh in . ./.. ./../..

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Ambox (view source) (semi-protected)
Template:Mer (view source) (semi-protected)

Retrieved from "http://wiki.maemo.org/Mer/Build/Common_Problems"

Personal tools

Navigation

Views

Editing Mer/Build/Common Problems

@@ Line 1: / Line 1: @@
-{{Mer}}
 =Common Problems encountered building for Mer on OBS=
@@ Line 10: / Line 8: @@
 * failed
-The package does not build successfully. No packages have been created. Packages that depend on this package will be built using any previously created packages, if they exist. [[Mer/Build/Common Problems/Failed Diagnosis|Failed Diagnosis]]
+The package does not build successfully. No packages have been created. Packages that depend on this package will be built using any previously created packages, if they exist. [[Mer/Documentation/Build/Common Problems/Failed Diagnosis|Failed Diagnosis]]
 * expansion error
-The build can not begin, because required packages are either missing or not explicitly defined.
+The build can not begin, because required packages are either missing or not explicitly defined.  [[Mer/Documentation/Build/Common Problems/Expansion Error Diagnosis|Expansion Error Diagnosis]]
 * blocked
@@ Line 38: / Line 36: @@
 * broken
-The sources either contain no build description (eg specfile) or a source link does not work.
+The sources either contain no build description (eg specfile) or a source link does not work.   [[Mer/Documentation/Build/Common Problems/Broken Diagnosis|Broken Diagnosis]]
 * unknown