Unable to build dpkg v3 (quilt) packages

Bug #614768 reported by Severin Heiniger on 2010-08-07
120
This bug affects 22 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Medium
Jelmer Vernooij
bzr-builder
High
Jelmer Vernooij

Bug Description

Now that bug #599102 has been fixed, it's still not possible to successfully run a source build based on a recipe targeting Maverick. dpkg-source fails with the following message:

dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found
dpkg-buildpackage: error: dpkg-source -i -I -b recipe-0.6~bzr1312~1222~201008071601 gave error exit status 255

Example build: https://code.edge.launchpad.net/~lottanzb/+recipe/lottanzb-trunk-ubuntu-9.10-and-newer-daily/+build/705

Don't hesitate to tell me if you need any assistance tracking down this bug.

Related branches

description: updated
James Westby (james-w) wrote :

Actually, not really a dupe of bug 606082, as that one is more general,
the fix for this may be simpler.

As a workaround you could merge a branch to delete debian/source/format, unless
you rely on certain v3 features.

Thanks,

James

summary: - Source build based on recipe targeting Maverick *still* fails
+ Unable to build dpkg v3 (quilt) packages
Changed in bzr-builder:
status: New → Triaged
importance: Undecided → High
Paul Hummer (rockstar) on 2010-08-09
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Medium
tags: added: recipe
James Westby (james-w) wrote :

Note that removing debian/source/format would stop quilt from patching, unless
you explicitly do it in your debian/rules.

Therefore if you actually have patches in your v3 (quilt) package the naïve solution
won't work and you will have to do some more work.

Thanks,

James

Paul Hummer (rockstar) wrote :

I've been thinking about this a lot actually. I think the solution is two-parts:

(1) Remove debian/source/format
(2) Invoke quilt manually to apply the patches.

I think this will actually cover all the bases, but it'd be nice if someone could sanity check that.

Anne van Rossum (annevanrossum) wrote :

This works on my system if I append it to the recipe:

run quilt push -a
run rm debian/source/format

Adding this as a checkbox option on the LP page would be nice. Of course this doesn't mean that you will need to "open up" your system to arbitrary run commands. Only allow yourself to append those two lines to the script when this checkbox option is crossed.

Paul Hummer (rockstar) wrote :

I think Anne is correct, but I think we could be smarter about it in bzr-builder. It could read the format, and if it's a v3 quilt format, then proceed to kill debian/source/format and then invoke quilt directly. James, does this sound reasonable?

On Tue, 24 Aug 2010 02:45:53 -0000, Paul Hummer <email address hidden> wrote:
> I think Anne is correct, but I think we could be smarter about it in
> bzr-builder. It could read the format, and if it's a v3 quilt format,
> then proceed to kill debian/source/format and then invoke quilt
> directly. James, does this sound reasonable?

That will work for most packages. There may be other differences between
the two formats that would cause a failure.

Thanks,

James

Roman Shtylman (shtylman) wrote :

Might be nice to have some sort of quick fix for this for testing on edge when trying to use the build recipes. Even if it isn't the long term solution, it will allow people to build recipes for Maverick and Natty

Jelmer Vernooij (jelmer) wrote :

Paul, I think that'd be a sensible way to handle it for the moment until there is a solution for bug 606082.

Jelmer Vernooij (jelmer) on 2010-12-05
Changed in bzr-builder:
assignee: nobody → Jelmer Vernooij (jelmer)
status: Triaged → In Progress
Jelmer Vernooij (jelmer) wrote :

I've proposed a --force-native option to bzr-builder's "bzr dailydeb" command. If/when that gets merged I'll propose a trivial patch to the buildds.

Jelmer Vernooij (jelmer) on 2010-12-07
Changed in bzr-builder:
status: In Progress → Fix Committed
Paul Hummer (rockstar) wrote :

Jelmer, is the fix for this over to the buildds yet? It's currently blocking a project that I package, and I'd like to get daily (or regular) builds going for them. I'd be happy to test the crap out of this.

Jelmer Vernooij (jelmer) wrote :

Hi Paul,

On Wed, 2011-01-19 at 04:51 +0000, Paul Hummer wrote:
> Jelmer, is the fix for this over to the buildds yet? It's currently
> blocking a project that I package, and I'd like to get daily (or
> regular) builds going for them. I'd be happy to test the crap out of
> this.
No, it has not been deployed yet. I'll talk to Aaron and Lamont tomorrow
about getting it deployed. There is another fix that will help
significantly with some of the memory issues we've been seeing.

Cheers,

Jelmer

Jelmer Vernooij (jelmer) on 2011-01-23
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Jelmer Vernooij (jelmer)
Jelmer Vernooij (jelmer) on 2011-01-28
tags: added: verified
Jelmer Vernooij (jelmer) on 2011-01-29
tags: added: udd
Jelmer Vernooij (jelmer) on 2011-02-03
Changed in launchpad:
status: In Progress → Fix Released
Jelmer Vernooij (jelmer) wrote :

The newer bzr-builder has been deployed on the buildds. Source packages that claim to be 3.0 (quilt) will now automatically be converted to 3.0 (native).

tags: added: qa-ok
Jelmer Vernooij (jelmer) wrote :

Please note that if there are no patches the series file can't exist at the moment, see bug 712822.

Jelmer Vernooij (jelmer) on 2011-02-10
tags: removed: verified
Jelmer Vernooij (jelmer) on 2011-06-14
Changed in bzr-builder:
milestone: none → 0.7
Jelmer Vernooij (jelmer) on 2011-06-14
Changed in bzr-builder:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers