mk-sbuild is untruthful
Bug #787051 reported by
Iain Lane
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-dev-tools (Ubuntu) |
Fix Released
|
Low
|
Stefano Rivera |
Bug Description
Binary package hint: ubuntu-dev-tools
mk-sbuild puts a comment in .sbuildrc saying
# Name to use as override in .changes files for the Maintainer: field
# (mandatory, no default!).
but this is not true. You can leave that out (and indeed probably should).
sbuild then passes through Maintainer from the package into the changes file.
Changed in ubuntu-dev-tools (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Rather, it's just outdated. There's some other cruft in there (for instance, the current created sbuild.conf entries will generate deprecation warnings, and they should have been put in conf.d anyway to avoid maintainer script merge issues). I don't know that it's worth fixing it: mk-sbuild should better be folded into sbuild- createchroot.