fails to find orig.tar for package built from daily recipe

[Martin Pool]

When testing a bzr-builder update on launchpad staging, the build failed <https://staging.launchpadlibrarian.net/80692920/buildlog.txt.gz> with

 dpkg-source -i -I -b bzr-2.5.0~beta1+bzr6182
dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found

and this seems to be because there is no upstream tag for that particular revision (which makes sense).

So it seems like either Launchpad should set --allow-fallback-to-native, or perhaps that should be on by default?

[Martin Pool (mbp)]

so the proposed fix is just that lp buildrecipe should pass --allow-fallback-to-native.

it may be that some people would rather it fail but it's not obvious why they would.

[Martin Pool (mbp)]

complication: --allow-fallback-to-native is not supported at all in the bzr-builder currently deployed on lp, so we'd need to do a synchronized update of lp-buildd and bzr-builder.

[Martin Pool (mbp)]

critical through escalation of bug 746822

[Jelmer Vernooij (jelmer)]

marking as high, since this bzr is being deployed separately of bzr-builder for bug 746822.

[Jelmer Vernooij (jelmer)]

The bzr-builder side of this was fixed as part of bug 864339.

[Launchpad QA Bot (lpqabot)]

Fixed in stable r14262 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/14262>.

[Martin Pool (mbp)]

This cannot be qa'd and will need a buildd update.
On Nov 8, 2011 3:00 AM, "Launchpad QA Bot" <email address hidden>
wrote:

> Fixed in stable r14262 <http://bazaar.launchpad.net/~launchpad-
> pqm/launchpad/stable/revision/14262>.
>
> ** Tags added: qa-needstesting
>
> ** Changed in: launchpad
> Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/885497
>
> Title:
> fails to find orig.tar for package built from daily recipe
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/bzr-builder/+bug/885497/+subscriptions
>
>

[Julian Edwards (julian-edwards)]

Actually it can and should be QAed on dogfood or staging's builders. When the upgraded package is rolled by LaMont, we always test it first.

[Martin Pool (mbp)]

On 8 November 2011 23:12, Julian Edwards <email address hidden> wrote:
> Actually it can and should be QAed on dogfood or staging's builders.
> When the upgraded package is rolled by LaMont, we always test it first.

I was talking about lp's deployment-blocking so-called 'qa'. It should be
tested before deployment to production buildds.