On 03-Nov-2019, Paul Gevers wrote: > With a recent upload of python-coverage the autopkgtest of > python-coverage fails in testing when that autopkgtest is run with the > binary packages of python-coverage from unstable. It passes when run > with only packages from testing.
Thank you for investigating this difference between environments. > I copied some of the output at the bottom of this report. I see that the build log does not show any output at all for attempting to build the documentation; for some reason that step is being silently omitted. I will investigate why. > In tabular form: > pass fail > python-coverage from testing 4.5.2+dfsg.1-2 > all others from testing from testing Is there anywhere I can see the output from a successful build of this package release? Or, do you mean that the success is for a *different* (previous?) release of ‘python-coverage’? Also, what does “all others” represent here; what packages? -- \ “I don't accept the currently fashionable assertion that any | `\ view is automatically as worthy of respect as any equal and | _o__) opposite view.” —Douglas Adams | Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
