Mer/Build/Common Problems
m (Mer/Documentation/Build/Common Problems moved to Mer/Build/Common Problems: don't need spurious Documentation) |
(removed extra Documentation/ in paths) |
||
| Line 8: | Line 8: | ||
* failed | * 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 | + | 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]] |
* expansion error | * expansion error | ||
| - | The build can not begin, because required packages are either missing or not explicitly defined. [[Mer | + | The build can not begin, because required packages are either missing or not explicitly defined. [[Mer/Build/Common Problems/Expansion Error Diagnosis|Expansion Error Diagnosis]] |
* blocked | * blocked | ||
| Line 36: | Line 36: | ||
* broken | * broken | ||
| - | The sources either contain no build description (eg specfile) or a source link does not work. [[Mer | + | The sources either contain no build description (eg specfile) or a source link does not work. [[Mer/Build/Common Problems/Broken Diagnosis|Broken Diagnosis]] |
* unknown | * unknown | ||
Revision as of 09:43, 4 May 2009
Contents |
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. Failed Diagnosis
- expansion error
The build can not begin, because required packages are either missing or not explicitly defined. 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. 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 . ./.. ./../..