Packaging build broken: no file to patch
Bug #1052805 reported by
Jeroen T. Vermeulen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Julian Edwards |
Bug Description
Attempts to build the package using “bzr builddep” break.
First there's an error “dh: Unknown sequence get-packaged-
The problem starts at revision 82 of the packaging branch, which introduced tests: http://
Related branches
lp:~julian-edwards/maas/packaging
- Julian Edwards (community): Approve
-
Diff: 27 lines (+2/-3)2 files modifieddebian/changelog (+2/-2)
debian/control (+0/-1)
Changed in maas: | |
assignee: | nobody → Julian Edwards (julian-edwards) |
status: | Triaged → Fix Released |
To post a comment you must log in.
I'm not exactly sure why bzr debuild fails, but I noticed his in http:// bazaar. launchpad. net/~maas- maintainers/ maas/packaging/ revision/ 86 and tried to fix it. Unfortunately, while that was valid and buildable package, it exposed a bug in 'bzr dailydeb' (which is how the dailiy builds run). I reverted my change (and thus knowingly re-broke bzr bd again) at revno 87.
Here is a summary of whats wrong: option= --abort- on-upstream- changes' .
* The tests/ files that were added should not be in the packaging branch.
Its bad packaging to have files outside debian/ in your packaging. And most of the time people enforce that by using 'debuild' with '--source-
* When I removed these files, and instead put them into a patch to be applied, that broke bzr dailydeb because we were creating new files with a patch (which seems like a major bug, but this was verified by jelmer).
I think the right solution is probably to move those tests/ files into debian/tests and then work with them from there.