the buildds should not continue a build when the dist-upgrade fails

Bug #2049020 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
launchpad-buildd
Triaged
High
Unassigned

Bug Description

this is seen in the current perl transition, in several packages like

texinfo builds on armhf, arm64, ppc64el:
  https://launchpad.net/ubuntu/+source/texinfo/7.1-2build1

libmarpa-r2-perl on armhf, arm64, ppc64el:
https://launchpad.net/ubuntu/+source/libmarpa-r2-perl/2.086000~dfsg-8build2

The dist-upgrade at the start fails, leaving the perl packages at version 5.36, however we are aiming the no-change uploads to go with the newly available 5.38 version.

The current work-around is to identify these wrongly built packages, do another no-change upload, and hope that it then succeeds with the dist-upgrade.

So we rely on the upgrade, or else we have to do 600+ sourceful uploads with explicit versioned dependencies on the perl packages, which is not what we want.

So please let a build fail, when the dist-upgrade fails.

Changed in launchpad:
importance: Undecided → High
status: New → Triaged
William Grant (wgrant)
affects: launchpad → launchpad-buildd
Revision history for this message
William Grant (wgrant) wrote :

`apt update` doesn't return non-zero on error unless you set `APT::Update::Error-Mode=any`, apparently. We might want to set that in OverrideSourcesList, where we also set `Acquire::Retries=3`.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.