package migration is blocked on failing autopkg tests of packages which are not in the release pocket
Bug #1824049 reported by
Matthias Klose
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| britney |
New
|
Undecided
|
Unassigned | ||
Bug Description
package migration is blocked on failing autopkg tests of packages which are not in the release pocket.
seen at
http://
on 2019-04-10:
rails (2:4.2.10-0ubuntu4 to 2:5.2.2+
Invalidated by dependency
Depends: rails puma (not considered)
puma (- to 3.12.0-2)
58 days old
autopkgtest for puma/3.12.0-2: amd64: Regression ♻ , arm64: Regression ♻ ,
armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ ,
s390x: Regression ♻
rails is ready to migrate, there is no puma package in the release pocket. the failing puma autopkg test in -proposed shouldn't be any concern.
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
To post a comment you must log in.
This is a question of policy, not of implementation.
I think a package which previously existed in the release pocket with passing tests, was removed from the release pocket, and has been reintroduced in the -proposed pocket SHOULD, by default policy, be held to the higher standard and that it should require an override to ignore the regressing autopkgtests.