Source build based on recipe targeting Maverick fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Aaron Bentley |
Bug Description
I'm currently in the process of preparing daily builds for the LottaNZB project based on a recipe. The builds requested using the web interface for Karmic and Lucid succeeded, but the one targeting Maverick did not [1]. The source build process terminated with the following messages:
[...]
dpkg: dependency problems prevent configuration of pbuilder-
pbuilder-
Package debhelper is not installed.
pbuilder-
Package intltool is not installed.
dpkg: error processing pbuilder-
dependency problems - leaving unconfigured
Errors were encountered while processing:
pbuilder-
/usr/lib/
[...]
Except for the last line (aptitude: command not found), the very same messages appear in the log of the successful Lucid source build.
Related branches
- LaMont Jones (community): Approve (packaging)
- Paul Hummer (community): Approve (code)
-
Diff: 85 lines (+22/-7)3 files modifiedlib/canonical/buildd/buildrecipe (+18/-4)
lib/canonical/buildd/test_buildd_recipe (+1/-1)
utilities/soyuz-sampledata-setup.py (+3/-2)
description: | updated |
description: | updated |
tags: | added: recipe |
Changed in launchpad-code: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in launchpad-code: | |
status: | Triaged → Fix Released |
It's great to see this bug being worked upon.
I just wanted to tell you that there's a small mistake in revision 11093 of ~abentley/ launchpad/ force-aptitude. The code name is "Maverick Meerkat" rather than "Maverick Meercat".