sbuild needs to run dpkg-source inside the chroot
Bug #476036 reported by
William Grant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpad-buildd |
Fix Released
|
High
|
Unassigned |
Bug Description
In order to support Debian's new 3.0 source formats, all the buildds need to use >= Karmic's dpkg to extract source packages.
Unfortunately, our sbuild still uses the host's dpkg (Hardy or even Dapper). Rather than being adventurous and attempting to backport dpkg, we should alter sbuild to run dpkg-source inside the chroot.
To do this, we need to have sbuild copy the source files into the chroot, then run dpkg-source over them in the right place. The copying is the non-trivial bit: we can't use the rather convenient 'dcmd' tool to extract a list of required files, as that doesn't exist in Hardy, let alone Dapper. This is the approach used by modern Debian sbuild.
Changed in launchpad-buildd: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in launchpad-buildd: | |
status: | Triaged → In Progress |
To post a comment you must log in.
Note also that Karmic's dpkg-source output has changed slightly, breaking the /^dpkg-source: extracting \S+ in (\S+)/ regexps that sbuild uses. This will become a problem and cause all Karmic/Lucid builds to fail once their dpkg-source is used.
We could either fix the regexps (adding '(?:info: )?' should do it), or give dpkg-source an explicit directory to extract to. I favour the former, as I hope that our fork of sbuild will not survive much longer.