Bug#954006: release.debian.org: Please allow postfix to migrate despite autopkgtest failures, they are unrelated
On March 15, 2020 7:05:20 PM UTC, Paul Gevers <elbrus@debian.org> wrote:
>Hi Scott,
>
>On 15-03-2020 18:17, Scott Kitterman wrote:
>> Currently postfix 2.4.10-1 is showing two autopkgtest failures in
>> related packages. Neither of them are postfix related.
>
>Which two, I only see one? Can you please elaborate why you think it is
>not postfix related? I tend to say that resource-agents is flaky on
>arm64 (it's on my potential list for stable on ppc64el as well). That
>warrants a bug report. Has that been filed?
My reading of this one is that it is tied to a postgresql instance failing to start. Clearly nothing to do with postfix.
No idea about bug reports and I'm not convinced I understand the failure well enough to file a useful report.
>fwlogwatch is a clear case, the current version has never passed, so
>once the migration-reference/0 has run, postfix is clear to go on this
>one.
Yes, but since resource-agents is marked as a regression, waiting won't actually solve anything.
>> Postfix's tests and all others passed and the two day wait for
>packages
>> with passing autopkgtests is up, so I would appreciate it if someone
>> would hint it into Testing.
>
>Why the rush and file this bug? Is waiting for the reference run and
>the
>retry really too much (I don't see anything urgent in the changelog)?
Additionally, regarding postfix related regression potential, the change in this upload is a fix for milter processing, which AFAIK isn't relevant for any of the rdepends with autopkgtests. Even without checking the details (which I did anyway), there's an approximately zero chance any test failures are connected to this upload.
Since resource-agents is tagged as a regression, it's my understanding that Postfix won't migrate ever, so why wait?
Although the changes aren't critical, them getting to Testing does affect my work. My intent is to ask SRM to allow 3.4.10 as a buster-pu (as we have been doing for the last two release cycles), but it should be in Testing first. Additionally, the postfix 3.5 release candidates have started and I plan to switch Unstable to 3.5 once this package migrates.
Scott K
Reply to: