No upgrade testing as standard
Bug #1549380 reported by
Iain Lane
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Auto Package Testing |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
We just got a case where lxd wasn't upgradable in xenial due to a postinst bug. We might have caught this by accident (lxd was on the adt base images by mistake in some cloud regions) - but we didn't, and even if we had it would only have been by chance.
Perhaps it would be possible to test package upgrades routinely. For each upload, install the -release binary packages (all of them). Then enable -proposed and pin the new binary packages high enough so that they become candidates, and try a dist-upgrade. That will catch postinst problems, file conflicts and similar classes of problems.
Revision history for this message
| Balint Reczey (rbalint) wrote | #1 |
| Changed in auto-package-testing: | |
| status: | New → Confirmed |
To post a comment you must log in.
I suggest running piuparts in parallel (or as a prerequisite) to autopkgtests to catch similar issues. Piuparts tests are ran on packages in the Debian infrastructure, but Ubuntu-only packages are not covered and the Ubuntu's delta is not exercised by piuparts either.